Automations do not execute

Configuration Zigbee
1

Hi HA Gurus,

Very much new to HA as only been using it for a few months, so please accept my apologies in advance for saying something silly and big thanks in advance for your assistance.

I have come across very odd situation, it looks like my new automations stopped executing even though they are being triggered, however my old automations still work perfectly fine. This seem to has happened after operating system update to 10.0. Also as a trial purpose I’ve mended my old automation by adding new actions and now automation stops at that new action and does not get executed, please see example below:
Running HA on generic x86 machine
Home Assistant 2023.4.5
Supervisor 2023.04.0
Operating System 10.0
Frontend 20230411.1 - latest

image
image1032×675 92.6 KB

Also in the logs start seeing odd errors, any ideas what this could be?:
Logger: zigpy.zcl
Source: runner.py:179
First occurred: 09:46:14 (9 occurrences)
Last logged: 09:56:18

[0x5841:1:0xef00] Unknown cluster command 6 b’\x00\x00n\x02\x00\x04\x00\x00\x00d’
[0x5841:1:0xef00] Unknown cluster command 6 b’\x00\x00k\x02\x00\x04\x00\x00\x00\xd7’
[0x5841:1:0xef00] Unknown cluster command 6 b’\x00\x00l\x02\x00\x04\x00\x00\x004’
[0x5841:1:0xef00] Unknown cluster command 6 b’\x00\x00k\x02\x00\x04\x00\x00\x00\xd8’
[0x5841:1:0xef00] Unknown cluster command 6 b’\x00\x00l\x02\x00\x04\x00\x00\x003’

Below is the whole automation as an example:

alias: Camera Position Based on Doors and Garden Motion
description: ""
trigger:
  - platform: state
    entity_id:
      - binary_sensor.kitchen_door_new_sensor_state_any
    id: Kitchen Door Open
    from: "off"
    to: "on"
  - platform: state
    entity_id:
      - binary_sensor.main_door_new_sensor_state_any
    id: Main Door Open
    from: "off"
    to: "on"
  - platform: state
    entity_id:
      - binary_sensor.garden_shed_motion
    id: Garden Motion
    from: "off"
    to: "on"
condition: []
action:
  - choose:
      - conditions:
          - condition: trigger
            id: Kitchen Door Open
        sequence:
          - service: foscam.ptz_preset
            data:
              entity_id: camera.foscam_front_door
              preset_name: Kitchen_Door
          - condition: state
            entity_id: switch.tz3000_pmz6mjyu_ts011f_switch_2
            state: "on"
      - conditions:
          - condition: trigger
            id: Main Door Open
        sequence:
          - service: foscam.ptz_preset
            data:
              preset_name: Main_Door
            target:
              entity_id: camera.foscam_front_door
      - conditions:
          - condition: trigger
            id: Garden Motion
        sequence:
          - service: foscam.ptz_preset
            data:
              preset_name: Kitchen_Door
            target:
              entity_id: camera.foscam_front_door
mode: single

type or paste code here
2

Hi – I’m not quite sure I follow. It looks like the service fiscal.ptz_preset is being called from the trace above. (you can click on the “timeline” to see if that is the case more readily.) It might help if you could explain what the “condition:state” for the tz3000 is supposed to do. That condition will just block later services, but there are no later services on that sequence branch.

Perhaps you could add a -service: home assistant.turn_on targeting the tz3000 instead of the “condition:state” to see if it turns on the light?

3

Hi David,

It should just switch the lights on or off.

However the Call service definitely works, just tried it and all ok, simple automation below:
But when I tried to add additional state condition for second switch it says it was aborted on timeline, or I’m using condition:state for the wrong purpose?
I’m sure that I have automations that work perfectly fine with condition state, for example when I open kitchen doors at night outdoor lights switches “on”, so why would it not work in this case?

Below is just call service for the light to switch on

alias: New Automation
description: ""
trigger:
  - platform: state
    entity_id:
      - binary_sensor.multisensor_iaszone
    from: "off"
    to: "on"
condition: []
action:
  - service: homeassistant.turn_on
    data: {}
    target:
      entity_id: switch.tz3000_pmz6mjyu_ts011f_switch_2
mode: single

below example with additional light switch were it does abort automation:

alias: New Automation
description: ""
trigger:
  - platform: state
    entity_id:
      - binary_sensor.multisensor_iaszone
    from: "off"
    to: "on"
condition: []
action:
  - service: homeassistant.turn_on
    data: {}
    target:
      entity_id: switch.tz3000_pmz6mjyu_ts011f_switch_2
  - condition: state
    entity_id: switch.tz3000_pmz6mjyu_ts011f_switch
    state: "on"
mode: single

image
image1726×639 112 KB