-
Notifications
You must be signed in to change notification settings - Fork 518
IKEA STYRBAR and Minor changes #4627
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
Conversation
Add IKEA-specific scene commands as sent by the TRADFRI remote control on the left and right buttons.
See #4572.
SYRBAR bindings.
Fix double button events, see #4572.
Ah damn I pressed "Ready for review" thinking I was starting review but now PR status changed. |
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.
Looks fine so far
Expose TRADFRI wireless dimmer as two buttons: Turn Right and Turn Left, cf. SYMFONISK. See Wiki, https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/IKEA-controllers#ictc-g-1. New map is for `mode` 1, old map for mode 4 will remain in effect, until you patch the database to mode 1.
- Disable check on "too fast event" - it causes weird effects for IKEA and Hue switches. - Allow ModeScenes for TRADFRI wireless dimmer.
I think this is good to go for now. Still sanity-checking the older IKEA controllers (see also new [Wiki](https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/IKEA-controllers page). @manup, @SwoopX please note that I commented out the check for "too fast event": it's perfectly legal for IKEA and Hue devices to send more events within 0.5s. The check causes mismatches in x000/x001/x003 sequences. I think we need to whitelist the devices for which this check is needed, if at all. The double events for IKEA are all due to the device sending the command twice, once by groupcast and once by unicast; as a remedy, I simply ignore the unicast. |
This was introduced in v2.5.33 in 2018 0f89afe due problems with Busch Jaeger switches 0ed3d17 So it might be that these are the only ones (or perhaps it isn't needed at all anymore). |
If it's no longer needed, let's please remove it. If still needed, can we whitelist Busch Jaeger on manufacturer code or manufacturer name, or do we need each model identifier? Alternatively, I could blacklist manufacturer codes for Philips and IKEA. Not sure if there's other devices that have come to rely on this check. |
That's a good question I can't test the BJ switch currently. Would like to remove this code as well, but I guess the safest bet is to disable it for IKEA and Philips since these are the ones we can be certain? |
Disable check for "too fast event" for Hue and IKEA devices, but enable it for others.
Done. |
For IKEA the issue was already addressed in dresden-elektronik#4627
Access to deCONZ::Node wasn't checked for nullptr and could crash when a button was pressed for a sensor which doesn't have the node set. - SEGV since v2.11.0 PR: dresden-elektronik#4627 - Related issue: dresden-elektronik#4766
de_web_plugin.cpp
;button_map.json
;checkSensorButtonEvent()
to ignore additional commands on holding left or right button (see issue);button_map.json
;checkSensorButtonEvent()
;general.xml
the IKEA-specific scene commands as sent by the TRADFRI remote control on the left and right buttons, so they can be sent from the GUI. Still cannot get them to work, though...mode
1, see Wiki.