I used Z2M version 1.4.xxx without problems. Today I updated to version 2.6.
First the adapter was not detected, but that I solved with the command “adapter: zstack”
Everything works fine again, except 3 Philips Hue Dial switches. In Z2M everything looks fine, but none of the commands send from the switches are working. What could be the problem?
It is also not possible to update the firmware of the switch. Also reconfiguring the switch in Z2M leads to multiple error messages.
Before Z2M version 2.0, it reported a remote-control’s events (like a Philips Hue Tap dial switch) via a sensor entity (like sensor.whatever_click and sensor.whatever_action).
Starting with Z2M version 2.0, a remote-control’s events are reported via an event entity.
This breaking change was reported in the release notes for Z2M version 2.0.
A comprehensive explanation of how to convert your automations and blueprints from using the old sensor entity to the new event entity can be found here:
The alternative is to use MQTT Device Triggers instead of event entities with a State Trigger.
If you currently do not have the time to learn about the event entity (and/or to modify your automations), you can enable Z2M’s legacy_action_sensor option and it will revert to reporting a remote-control’s events via a sensor entity.
Thank you for your reply
For now I would like to go for the easy way and use the action sensor. In the Zigbee2MQTT configuration.yaml the lines are defined:
homeassistant:
enabled: true
legacy_action_snsor: true
In the webUI the legacy_action_sensor option is not activated. When I try to activate I receive a error message like in the screenshot.
If you copied & pasted that directly from your yaml, you have a typo. snsor should be sensor
