New feature
- Zigbee2MQTT blueprints no longer depend on the
/action topic (#77, thanks @FredrikM97): Zigbee2MQTT only republishes a button press to zigbee2mqtt/<device>/action when its Home Assistant integration is enabled (and advanced.output is json). Switches using one of the 79 zigbee2mqtt/+/action blueprints now also listen on the device's state topic zigbee2mqtt/<device> and use the action key of its JSON payload. When Zigbee2MQTT publishes both, the duplicate is dropped; retained state messages are ignored so a restart never replays the last press. Identifiers stay zigbee2mqtt/<device>/action, auto discovery works either way. See the README troubleshooting section for details.
Included since v5.2.2
Dialog fixes when adding a switch (#76), see v5.2.2.