-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[insteon] Fix x10 device message handling #18031
Conversation
This pull request has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/insteon-x10-setup-broke-after-update-to-4-3-1/161382/2 |
Signed-off-by: Jeremy Setton <jeremy.setton@gmail.com>
95c2a73
to
09c234a
Compare
These fixes have been fully tested on the legacy and new implementation as per the community thread linked above. |
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.
Thanks for the fix!
Signed-off-by: Jeremy Setton <jeremy.setton@gmail.com>
Signed-off-by: Jeremy Setton <jeremy.setton@gmail.com>
Signed-off-by: Jeremy Setton <jeremy.setton@gmail.com> Signed-off-by: Christian Koch <78686276+chilobo@users.noreply.github.com>
This change fixes the message handling for x10 device.
This includes 3 bug fixes:
X10Address
house code is incorrect when instantiated with a message address byte. This is affecting the legacy implementation as well preventing incoming X10 messages from being processed by the binding.X10Address
failed to instantiate with a string based X10 address including a unit code with more than 1 digit (e.g.L.15
). This is affecting the legacy implementation which rely on a string based address being parsed, opposed to the new one that has the house and unit configuration already separated.This change should be back ported as the X10 integration is currently broken.