From dbfe4d34d7b71ce3ed5d6a1daa87a7105d914052 Mon Sep 17 00:00:00 2001 From: Robbert Gurdeep Singh Date: Thu, 3 Oct 2024 23:58:07 +0200 Subject: [PATCH] ikea_e2001_e2002: handle "unknown" state Since the update to HA2024.10, the state of my zigbee2mqqt linked Stybar becomes "unknown" instead of "None" UI of stybar before the update: - changed to None 00:24:55 - 23 hours ago - changed to arrow_right_click 00:24:55 - 23 hours ago - changed to None 00:24:55 - 23 hours ago now the same event looks like: - became unknown 23:52:22 - 3 minutes ago - changed to arrow_right_click 23:52:22 - 3 minutes ago - became unknown 23:52:21 - 3 minutes ago --- blueprints/controllers/ikea_e2001_e2002/ikea_e2001_e2002.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blueprints/controllers/ikea_e2001_e2002/ikea_e2001_e2002.yaml b/blueprints/controllers/ikea_e2001_e2002/ikea_e2001_e2002.yaml index 9f6533575..d10654f6a 100644 --- a/blueprints/controllers/ikea_e2001_e2002/ikea_e2001_e2002.yaml +++ b/blueprints/controllers/ikea_e2001_e2002/ikea_e2001_e2002.yaml @@ -382,7 +382,7 @@ condition: {{ trigger.event.data.command }}{{"_" if trigger.event.data.args|length > 0}}{{ trigger.event.data.args|join("_") }} {%- endif -%} {%- endset -%} - {{ trigger_action not in ["","None"] }} + {{ trigger_action not in ["","None","unknown"] }} # only for zigbee2mqtt, check if the event is relative to a real state change, and not only some minor changes in the sensor attributes # this is required since multiple state_changed events are fired for a single button press, with the result of the automation being triggered multiple times - '{{ integration_id != "zigbee2mqtt" or trigger.event.data.new_state.state != trigger.event.data.old_state.state }}'