Inconsistency in automation after upgrade to 2023.8.2

Configuration
1

Hello all

Like many of you i’m sure are having issues with automations following the upgrade to 2023.8.2

In my case following the upgrade to 2023.8.2 i have an inconsistent behaviour in automations.

but communications between device (this i will open a different thread) for example in my light control automation (the one mentioned above) at dusk when the first instance of the detection of the condition (lux less than 3) the shelly light will take up to 4 second to light up. after that the light turns on immediately)

The automation is very simple
trigger
aeotec multisensor starts to detect motion
condition
aeotec multisensor luminosity is less than 3

Action
if time is between 08:30 and 23:59:59
turn on shelly light at 60 if at 60%
wait 30 seconds
turn off shelly light

else if time is between 0:0:01 and 08:29:59
turn on shelly light at 30%
wait 30 seconds
turn off shelly light

when for the first time of the day,aAs dusk will settle, this light sensor fall below 3 the motion sensor detect motion the light take 4 seconds to turn on.

The light and the sensor are in the same network.

all subsequent occurrences work perfectly

Since i have 2 automations with this functionality i see both automations behavin the same way.

Since these automations have been working correctly for the past 4 years I smell the footprint of the upgrade to 2023…8.2, Being the cause of this.

Thank you for looking at this

2

Post your automation please. As well as the trace where it messes up.

3

Hello @petro

Thank you for your prompt response

Here is a copy of the automation as it shows in the trace menu of the automation
I have copied and pasted the code here and as i see it it reflect the format as is shown in the automation

I know that many time i post such content and i get feed back that it is not conforming to the format

would you be so king and explain to me How i can apy and past the code to this site

id: ‘1691861129725’
alias: Entrance Hall Light
description: Automate light based on motion and lux
trigger:

  • type: motion
    platform: device
    device_id: 9f73be16806c11a362a968f214d7cd6d
    entity_id: f615f6c0f405553ee45f8d7efa225841
    domain: binary_sensor
    condition:
  • type: is_illuminance
    condition: device
    device_id: 9f73be16806c11a362a968f214d7cd6d
    entity_id: f10d835cf0214dd69accb1e6dd8b094a
    domain: sensor
    below: 3
    action:
  • if:
    • condition: time
      before: ‘23:59:59’
      weekday:
      • mon
      • tue
      • wed
      • fri
      • sat
      • sun
        after: ‘08:30:00’
        then:
    • type: turn_on
      device_id: 1101cf6550bf765c490afd9a658cf3ba
      entity_id: 0b00012b0910558802470181993d4904
      domain: light
      brightness_pct: 60
    • delay:
      hours: 0
      minutes: 0
      seconds: 30
      milliseconds: 0
    • type: turn_off
      device_id: 1101cf6550bf765c490afd9a658cf3ba
      entity_id: 0b00012b0910558802470181993d4904
      domain: light
      else:
    • if:
      • condition: time
        after: ‘00:00:01’
        before: ‘08:29:59’
        weekday:
        • mon
        • tue
        • wed
        • thu
        • fri
        • sat
        • sun
          then:
      • type: turn_on
        device_id: 1101cf6550bf765c490afd9a658cf3ba
        entity_id: 0b00012b0910558802470181993d4904
        domain: light
        brightness_pct: 30
      • delay:
        hours: 0
        minutes: 0
        seconds: 30
        milliseconds: 0
      • type: turn_off
        device_id: 1101cf6550bf765c490afd9a658cf3ba
        entity_id: 0b00012b0910558802470181993d4904
        domain: light
        mode: single

i do not see anything unusual

If I may is there a way to avoid the devices and entities to have an alfa numerical id in the automations and substitute it with a friendly name. This is by no means a first , second third or n priority

Thank you

4

Please format your posted config correctly for the forum, like this: https://community.home-assistant.io/t/how-to-help-us-help-you-or-how-to-ask-a-good-question/114371#oneone-format-it-properly-16

1 Like
5

It should look something like this - use the preformatted text button (</> in the toolbar):

trigger:
  - platform: state
    entity_id:
      - binary_sensor.yard_motion_sensor_motion
    to: "on"
  - platform: numeric_state
    entity_id: sensor.yard_motion_sensor_light_level
    below: 3

Could I ask why you are using the device platform? It’s longer, harder to read and just storing up trouble for later. :grinning_face_with_smiling_eyes:

6

Not just later. There are at least a couple of open issues with device automations at the moment. They do not affect entity_id driven automations.

Don’t use device automations. They are awful. What happens if I have to replace a device - #2 by tom_l

1 Like