Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SMHE-1871 Onbekende meter events die niet gemapped kunnen worden onde… #1179

Conversation

natasja-n
Copy link
Contributor

@natasja-n natasja-n commented Feb 26, 2024

Log UNKNOWN_EVENT_HEADEND in case of an unknown event.

https://jenkins.fdp.osgp.cloud/view/SMHE-cucumber/job/gxf-smhe-cucumber-build/199/

@@ -42,4 +44,23 @@ public void theBundleResponseShouldContainAFindEventsResponse(final int nrOfEven
final FindEventsResponse findEventsResponse = (FindEventsResponse) response;
assertThat(findEventsResponse.getEvents()).hasSize(nrOfEvents);
}

@And(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@and is aangepast naar @then

@@ -51,7 +51,8 @@ public enum EventType {
NTP_SYNC_SUCCESS(43),
AUTHENTICATION_FAIL(44),
LIGHT_SENSOR_REPORTS_DARK(45),
LIGHT_SENSOR_REPORTS_LIGHT(46);
LIGHT_SENSOR_REPORTS_LIGHT(46),
UNKNOWN_EVENT_HEADEND(47);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

HEADEND reference in core?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

klopt, dit is de naam zoals gegeven in de story. Het lijkt me het beste als hij overal hetzelfde heet.

@@ -576,7 +574,8 @@ enum EventTypeDtoLookup {
KEY_SENT_TO_MBUS_DEVICE_ON_CHANNEL_4(
EventTypeDto.KEY_SENT_TO_MBUS_DEVICE_ON_CHANNEL_4, 0x83A0, null),
KEY_ACKNOWLEDGED_BY_MBUS_DEVICE_ON_CHANNEL_4(
EventTypeDto.KEY_ACKNOWLEDGED_BY_MBUS_DEVICE_ON_CHANNEL_4, 0x83A1, null);
EventTypeDto.KEY_ACKNOWLEDGED_BY_MBUS_DEVICE_ON_CHANNEL_4, 0x83A1, null),
UNKNOWN_EVENT_HEADEND(EventTypeDto.UNKNOWN_EVENT_HEADEND, 0x84A1, null);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where does this int code come from 0x84A1?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deze had ik als nog niet bestaande code toegevoegd. Ik heb er nu 999 van gemaakt, zodat duidelijk is dat hij buiten de bestaande ranges valt.

@@ -303,7 +303,8 @@ public enum EventType {
MBUS_STATUS_BIT_30_MANUFACTURER_SPECIFIC_CHANNEL_4(0x839E),
MBUS_STATUS_BIT_31_MANUFACTURER_SPECIFIC_CHANNEL_4(0x839F),
KEY_SENT_TO_MBUS_DEVICE_ON_CHANNEL_4(0x83A0),
KEY_ACKNOWLEDGED_BY_MBUS_DEVICE_ON_CHANNEL_4(0x83A1);
KEY_ACKNOWLEDGED_BY_MBUS_DEVICE_ON_CHANNEL_4(0x83A1),
UNKNOWN_EVENT_HEADEND(47);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

HEADEND reference in core?
EventCode 47 also is used for CONFIGURATION_CHANGE?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deze is ook aangepast naar 999 zoals in de opmerking hierboven.

…r verzamel event

use 999 from unknown event, use then in BundledFindEventsSteps

Signed-off-by: Natasja <[email protected]>
Copy link

sonarqubecloud bot commented Mar 4, 2024

@natasja-n natasja-n merged commit 7e720ab into development Mar 4, 2024
6 checks passed
@jasperkamerling jasperkamerling deleted the feature/SMHE-1871_Onbekende_meter_events_onder_verzamel_event branch June 12, 2024 12:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants