Deconz_event stopped triggering simple automations after 0.115.x update

[tosion]

The problem

Deconz_event stopped triggering simple automations after 115 update. I have seen this in two different systems with few different automations. In developer tool event page I can see the event working. Also same devices work in Deconz/Phoscon automations (I moved some of automations to work with Phoscon instead of HA automation)

Environment

arch	x86_64
chassis	embedded
dev	false
docker	true
docker_version	19.03.11
hassio	true
host_os	HassOS 4.13
installation_type	Home Assistant OS
os_name	Linux
os_version	5.4.63
python_version	3.8.5
supervisor	245
timezone	Europe/Helsinki
version	0.115.2
virtualenv	false

• Home Assistant Core release with the issue: 0.115.2
• Last working Home Assistant Core release (if known): 0.114.x
• Operating environment (OS/Container/Supervised/Core): HA NUC image
• Integration causing this issue:
• Link to integration documentation on our website:

Problem-relevant configuration.yaml

- id: mv1_on_off
  alias: mv1_on_off
  trigger:
  - platform: event
    event_type: deconz_event
    event_data:
        id: kytkin4
        value: 1002      
  action:
  - service: switch.toggle
    entity_id: switch.mv1

Traceback/Error logs

Additional information

[probot-home-assistant]

Hey there @Kane610, mind taking a look at this issue as its been labeled with an integration (deconz) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[probot-home-assistant]

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

[Kane610]

If you see the event in hass it's not an issue with the deconz integration

[tubalainen]

Ive got a similar issue - not sure its related to home assistant.

Try restarting both deconz and home assistant several times and see if it "just suddenly works". - This applied only to newly added remotes/switches in my case.

Here is one my automations that "just suddenly started to work" after several restarts of deconz and home assistant.

- id: 'bilfjarr_4002'
  alias: Bilfjärr toggle uppfartsbelysning
  initial_state: 'on'
  trigger:
  - event_data:
      id: remote_bilen
      event: 4002
    platform: event
    event_type: deconz_event
  condition: []
  action:
  - data:
      entity_id: switch.shelly_19_relay
    service: switch.toggle

I just posted an issue here: dresden-elektronik/deconz-rest-plugin#3328

[tosion]

Thanks for your comment!

However I think Kane 610 is pretty much right that my issue in not Deconz-issue as event can be seen in HA event tool. I am basically ok with this issue as I moved my event automations to Phoscon side. Actually I had often planned to do so and this issue was just a trigger for me to do it ;-)

[tubalainen]

Thanks for your comment!

However I think Kane 610 is pretty much right that my issue in not Deconz-issue as event can be seen in HA event tool. I am basically ok with this issue as I moved my event automations to Phoscon side. Actually I had often planned to do so and this issue was just a trigger for me to do it ;-)

Oooh nonono. That would not work for me personally. I am using the zigbee sensors and buttons to trigger other things than internal phoscon devices such as start media streaming, turn on/off non-deconz devices and trigger notifications. I need this to work inside of Home Assistant.

[highground88]

Same issue here I think, multiple different devices, using ZHA.

Until 114.4, I’ve had zha_events firing off actions - eg. Aqara button opening the garage door (via wemo) or turn on a light. Something has broken these Aqara switches and also the mains powered Nue scene switches - the similarity is none of these create entities when added to ZHA/HA, and instead require listening for zha_events.

I can see these events come through, and the unique_id is correct. Everything works fine in 114.3. I am using a HUSBZB-1, tried with original and latest firmware.

Automations work if manually ‘executed’, and this is an example of one that doesnt work:

Trigger type: Event
Event Type: ZHA Event
Event data:
click_type: single
unique_id: ‘00:12:4b:00:1b:a3:bc:ce:1:0x0006’

[highground88]

Same issue here I think, multiple different devices, using ZHA.

Until 114.4, I’ve had zha_events firing off actions - eg. Aqara button opening the garage door (via wemo) or turn on a light. Something has broken these Aqara switches and also the mains powered Nue scene switches - the similarity is none of these create entities when added to ZHA/HA, and instead require listening for zha_events.

I can see these events come through, and the unique_id is correct. Everything works fine in 114.3. I am using a HUSBZB-1, tried with original and latest firmware.

Automations work if manually ‘executed’, and this is an example of one that doesnt work:

Trigger type: Event
Event Type: ZHA Event
Event data:
click_type: single
unique_id: ‘00:12:4b:00:1b:a3:bc:ce:1:0x0006’

I’ve finally found a fix for my issue - not sure if it's the same now?

Where previous to 114.4, this trigger on an automation would work:

Trigger type: Event
Event Type: ZHA Event
Event data:
click_type: single
unique_id: ‘00:12:4a:00:1b:a3:bc:ce:1:0x0006’
From 114.4 the following data works:

Trigger type: Event
Event Type: ZHA Event
Event data:
device_ieee: ‘00:12:4a:00:1b:a3:bc:ce’
endpoint_id: 1
cluster_id: 6
command: 'on'

So it seems that something did change - perhaps to also do with the apparent major breaking change of not being able to use entity_id in templates perhaps, as this is the only change I have been able to find that might correlate? (#39382).