feat: Add command_move and command_stop to Philips/Signify Hue Wall Switch Module (929003017102/RDM001) #7489
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It has been discovered earlier that the Philips Hue Wall Switch Module has a neat feature where it can also directly control the brightness of a bound group through the
LevelCtrl
cluster. If the Wall Switch is bound to a group, it sends its commands to the group instead of the coordinator. These Zigbee messages are translated and published through MQTT, but I noticed that some messages I can see in the logs, but are not published:commandMove
,commandMoveWithOnOff
,commandStop
,commandStopWithOnOff
This PR aims to fix this, and these messages are now published to MQTT.
FYI the Zigbee commands will map to the following actions in Home Assistant:
commandMove
→brightness_move_down
commandMoveWithOnOff
→brightness_move_up
commandStop
→brightness_stop
commandStopWithOnOff
→brightness_stop