I imported the blueprint, activated "Home Assistant legacy entity attributes” in zigbee2mqtt, and it works great - almost. Hold is not working.
When pressing and holding brightness up, I get two traces:
First trace:
Directly after this (same timestamp), the second trace. Can’t upload a screenshot, because this is my first post.
But in the trace no condition is met, so the outermost right path is taken.
When releasing brightness up, I get two more traces with no condition met (outermost right path).
Any hint?
Edit:
zigbee2mqtt uses these two topics
A) The “new way” how mqtt messages should be sent to HA
topic: zigbee2mqtt/TRADFRI remote control 1
payload: {“action”:“brightness_up_hold”,“battery”:74,“linkquality”:21,“update”:{“state”:“idle”},“update_available”:null}
B) Home Assistant legacy entity attributes
topic: zigbee2mqtt/TRADFRI remote control 1/action
payload: up_hold
When holding and releasing brightness up, the following is sent out via mqtt:
- Press and hold brightness up
A) {“action”:“brightness_up_hold”,“battery”:74,“linkquality”:21,“update”:{“state”:“idle”},“update_available”:null}
B) up_hold
A) {“action”:"",“battery”:74,“linkquality”:21,“update”:{“state”:“idle”},“update_available”:null}
So the action is cleared immediately for topic A (the new way how mqtt messages should be send).
Only for Topic B the payload stays correctly at “up_hold”
- Relase brightness_up
A) {“action”:“brightness_up_release”,“battery”:74,“linkquality”:21,“update”:{“state”:“idle”},“update_available”:null}
B) up_release
A) {“action”:"",“battery”:74,“linkquality”:21,“update”:{“state”:“idle”},“update_available”:null}
So this blueprints obviously reacts to messages of kind A), where the action is immediatly cleared out.
Shouldn’t it use triggers of kind B)?
And if I have a look at the state, then this is confirmed:
So I thought this blueprint is using the “legacy entity attributes”, but it is not, right?
Because of the same reason, if e.g. for “Left button - short press” you define several actions, only the first action is executed.