-
-
Notifications
You must be signed in to change notification settings - Fork 431
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
Fix wrong event subscription in CommunicationManager
#3529
Conversation
#3141 introduced an ItemStateUpdatedEvent and updated CommunicationManager to require this for sending state updates. However, it was forgotten to update the subscribed event types. Signed-off-by: Florian Hotze <[email protected]>
Signed-off-by: Florian Hotze <[email protected]>
LGTM, why is this a draft? |
I wanted to test this on my production, but I am finished now 👍 This fixes openhab/openhab-addons#14753 according to my tests, which is logical: state updates are now again relayed to the thing and therefore send to the KNX bus. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks.
The CI / Build action seems unstable, it already failed two times because of the |
CI will be more stable after #3518 is merged. |
CI finally succeeded 🥳 |
* Fix wrong event subscription in CommunicationManager Signed-off-by: Florian Hotze <[email protected]> GitOrigin-RevId: 633002c
#3141 introduced an
ItemStateUpdatedEvent
and updatedCommunicationManager
to only receive updates on this event.However, it was forgotten to update the subscribed event types, so no updated were received at all.
The
CommuncationManagerOSGiTest
was not able to detect this regression, because in the test the event isreceived
via a method call, but not an event subscription/the event bus.This also renames the method for creating a
GroupStateUpdatedEvent
for more clarity.