-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Fix duplicate device trigger error in HA 2024.2 #2829
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix duplicate device trigger error in HA 2024.2 #2829
Conversation
…icate trigger. In HA2024.2, device triggers are now identified as `f"{device_id}_{trigger_type}_{trigger_subtype}"`, so each trigger must have a unique type/subtype combination per device.
Can some regular HA users check this? Do we need to change other keys? @kcpants @unverbraucht @deviantintegral |
My doorbell uses the secret knock field, so it's not affected by this: rtl_433/examples/rtl_433_mqtt_hass.py Lines 767 to 794 in 1e7e56e
But from a static read, this change should be OK. Am I reading it right that this broke in HA without a deprecation period? Or did we miss a notice from before? |
I haven't seen any depreciation notices and it seems it was just a side effect of this bigger change home-assistant/core#108309 |
Hello, what is the status to fix this error or how can it be fixed manually? I am constantly getting errors like this `Config for device trigger Thermopro-TX2-9-3-74 Thermopro-TX2-9-3-74-BTN conflicts with existing device trigger, cannot set up trigger, got: {'automation_type': 'trigger', 'type': 'button_short_release', 'subtype': 'button_1', 'topic': 'rtl_433/9b13b3f4-rtl433/devices/Thermopro-TX2/9/3/74/button', 'device': {'identifiers': ['Thermopro-TX2-9-3-74'], 'name': 'Thermopro-TX2-9-3-74', 'model': 'Thermopro-TX2', 'manufacturer': 'rtl_433', 'connections': []}, 'encoding': 'utf-8', 'qos': 0, 'payload': None, 'value_template': None} Config for device trigger Thermopro-TX2-9-1-129 Thermopro-TX2-9-1-129-BTN conflicts with existing device trigger, cannot set up trigger, got: {'automation_type': 'trigger', 'type': 'button_short_release', 'subtype': 'button_1', 'topic': 'rtl_433/9b13b3f4-rtl433/devices/Thermopro-TX2/9/1/129/button', 'device': {'identifiers': ['Thermopro-TX2-9-1-129'], 'name': 'Thermopro-TX2-9-1-129', 'model': 'Thermopro-TX2', 'manufacturer': 'rtl_433', 'connections': []}, 'encoding': 'utf-8', 'qos': 0, 'payload': None, 'value_template': None} Config for device trigger Thermopro-TX2C-1-8 Thermopro-TX2C-1-8-BTN conflicts with existing device trigger, cannot set up trigger, got: {'automation_type': 'trigger', 'type': 'button_short_release', 'subtype': 'button_1', 'topic': 'rtl_433/9b13b3f4-rtl433/devices/Thermopro-TX2C/1/8/button', 'device': {'identifiers': ['Thermopro-TX2C-1-8'], 'name': 'Thermopro-TX2C-1-8', 'model': 'Thermopro-TX2C', 'manufacturer': 'rtl_433', 'connections': []}, 'encoding': 'utf-8', 'qos': 0, 'payload': None, 'value_template': None}` |
The change slipped through. Thanks for the reminder. |
Sorry for clarifying question - to fix this, one needs to update HA to the newer version, RTL433 or both? |
You just need the new |
Change the subtype of the BTN device trigger to avoid creating a duplicate trigger.
In HA 2024.2, device triggers are now identified as
f"{device_id}_{trigger_type}_{trigger_subtype}"
, so each trigger must have a unique type/subtype combination per device.home-assistant/core#110072 (comment)