Closed scolby33 closed 2 years ago
This is a limitation of HA (you cannot respond to the full payload). You can use https://www.zigbee2mqtt.io/guide/usage/integrations/home_assistant.html#via-mqtt instead
Yes, thank you for pointing out the direct MQTT option.
Is it not possible for Zigbee2MQTT to use separate topics for each groupID/action_group? (I would appreciate if you could differentiate between "not possible due to how Zigbee works" and "not possible because Zigbee2MQTT doesn't have the feature." If it's the latter, would you be open to a pull request? The device triggers are so much more convenient than having to mange MQTT topic names manually 😊)
It is not possible because Home Assistant can only work on string values for the event triggers (and not on objects). So this has to be added to HA not z2m.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
What happened?
The RGB Genie ZB-5001 remote has 5 scene on/off buttons. When it is paired to Zigbee2MQTT and discovered in Home Assistant using device discovery, it is impossible to differentiate between the scene buttons.
The following action topics are used:
The action_on/config message, for example is like:
Unfortunately, this results in the same device trigger for each button.
Zigbee2MQTT can obviously tell the buttons apart, using the
groupID
field, which is translated to theaction_group
payload value. This is the log of me pressing scene 1 on followed by scene 2 on:What did you expect to happen?
zigbee2mqtt/Pretty Name/action_*
topicsHow to reproduce it (minimal and precise)
Zigbee2MQTT version
1.25.2 commit: 3c5854fa
Adapter firmware version
20220219
Adapter
Tube's CC2652P2 USB Coordinator
Debug log
See relevant logs above in the "What happened?" section.