Automation issue when trigeered by Deconz event

[Xavier80]

The problem

Since migration to version 2024.2 (Same behavior on 2024.3, Deconz devices (mainly switches) are unreliable. The first point is that, once migrated, none of the automations are triggered by a switch even if i can see events (Ikea switch through deconz). However, by activating and desactivating the automations, deconz events can now trigger an automation. However, state of device remain unstable. Automations are not triggered as they should and even after removing all automations link to a device, the state of all power switches change ! State changes but physically they are not triggered. This is a really strange behavior. Switching back to version 2024.1.6 solve the issue.

What version of Home Assistant Core has the issue?

2024.2

What was the last working version of Home Assistant Core?

2024.1.6

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Automation / Deconz

Link to integration documentation on our website

https://www.home-assistant.io/docs/automation/

Diagnostics information

Enregistreur: homeassistant.components.automation.bouton_bas_ac_4_allumer_lumiere_max_luminosite_chambre_invites Source: components/automation/init.py:756 intégration: Automatisation (documentation, problèmes) S'est produit pour la première fois: 20:47:12 (1 occurrences) Dernier enregistrement: 20:47:12

Got error 'No deconz_event tied to device "TRÅDFRI remote control - Ch. inv" found' when setting up triggers for Bouton bas AC_4 - Allumer lumière max luminosité chambre invites

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (automation) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `automation` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign automation` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

automation documentation automation source _{^{(message by IssueLinks)}}

[thijsputman]

Seeing the same issue in 2024.3.

For me, the No deconz_event tied to device...-errors have occurred occasionally on Home Assistant (re)start for a very long time already – I'm guessing due to some unfortunate race-condition/timing issue between starting the deCONZ integration and initialising the automations?

It used be solved (I'm coming from 2023.12, so at least up to there) by calling automation.reload after starting Home Assistant to reload all automations. At that point, all automations relying on deCONZ device_id-triggers started working again.

Since upgrading tot 2024.3, the error occurs at (almost) every start of Home Assistant, I'm guessing related to Home Assistant booting faster in 2024.3?

The solution to call automation.reload doesn't restore functionality to the automations any more. The only solution – as mentioned by @Xavier80 – is to disable/enable each individual automation in question...

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.