Light does not switch on

[tough pulsar]

It worked for days but suddenly the light control no longer works and I don't understand why. The motion detector detects movement but the lamp doesn't switch on. Lamp works. Can you help me?

description: ""
triggers:
  - entity_id:
      - binary_sensor.bewegungsmelder_eingang_eg_occupancy
    from: "off"
    to: "on"
    trigger: state
conditions:
  - condition: or
    conditions:
      - type: is_illuminance
        condition: device
        device_id: a5ef976635d588d412257389a9538859
        entity_id: 1eea69ddeb1a15882922e603aeebaca1
        domain: sensor
        below: 1
      - condition: or
        conditions:
          - condition: sun
            before: sunrise
            after: sunset
actions:
  - action: light.turn_on
    metadata: {}
    data:
      brightness_pct: 100
      kelvin: 2000
    enabled: true
    target:
      device_id: ae70bfd1a0fef4a177b7c4fef002d8f9
  - wait_for_trigger:
      - entity_id:
          - binary_sensor.bewegungsmelder_eingang_eg_occupancy
        from: "on"
        to: "off"
        for:
          hours: 0
          minutes: 0
          seconds: 0
        trigger: state
  - action: light.turn_off
    metadata: {}
    data: {}
    target:
      device_id: ae70bfd1a0fef4a177b7c4fef002d8f9
mode: single

[verbal flame]

can you pull up your automation trace from a time it didn't work?

[gusty umbra]

Your triggers are all weird, like they were written by chatGPT or something.
NM, just the way my screen formatted it.

If this gets into any state other than on or off it won't work,
binary_sensor.bewegungsmelder_eingang_eg_occupancy
If it becomes unavailable or unknown, for instance.

I might just look for the 'to' part of those triggers and lose the 'from' part.

[tough pulsar]

Don't quite understand you now? It worked before without any problems

Apparently the last HA update caused errors that I don't understand. The next light control has failed or it only comes on for a second

[gusty umbra]

We have not discussed your actual error yet, we need to see the info Hilburn asked for. My comment was a suggested improvement and likely not the problem.

[tiny gyro]

Have you checked that all entities involved have the same name they are expected to have?

[tough pulsar]

yes

With the light control, the lamp only goes on for one second and then switches off again immediately

The other one is suddenly white again

Earlier the SMLIGHT LSZB-06 also simply switched off for no apparent reason and I had to restart it.

[verbal flame]

The actions listed are literally:
0. Turn Light On

1. Wait
2. Turn Light Off

[gusty umbra]

Well if the service or code that is populating this binary_sensor.bewegungsmelder_eingang_eg_occupancy is turning it on and right back off, that is what the physical actions look like. Tell us more about that switch.

[tough pulsar]

It is responsible for setting the lux value for the entire light control.

Can you please tell me why the light is half a second on flash? I have already deleted this automation and rewritten it. The same thing happens again.

The strange thing is also. After a short while, the light switches on by itself and stays on

[verbal flame]

show the same history for that occupancy sensor

[tough pulsar]

However, the sensor is not the one that controls the lamp.

[verbal flame]

OK yeah, so your sensor is turning off, so your automation is turning the light off

Look into using the hold on value for the occupancy sensor

Should cut down on the sensor jittering

[tough pulsar]

Do you mean this one?

[verbal flame]

No

[tough pulsar]

Shouldn't everyone else also have this error?
As I said, this is only the sensor that controls the automation for the other automations for when the light should switch on. it does not control the movement.

[verbal flame]

No

[tough pulsar]

I'm sorry, I have to use a translator and then it's difficult for me to understand you properly

[verbal flame]

The way you have written your automation is:

Trigger: occupancy on
If: light is low or at night
Then:

1. Turn light on
2. Wait for occupancy sensor to turn off
3. Turn light off

[tough pulsar]

Right, the light should only come on under a certain lux value

[verbal flame]

Yup. So from the history of that occupancy sensor you sent, it looks like it only turns on for a very short time, and then turns off again

Which would explain the behaviour you described, where the light turns on them immediately off

It's effectively speedrunning the actions 1, 2, 3

[tough pulsar]

I would like to give you some more information. I deactivated the condition earlier and the error was still the same

[verbal flame]

This isn't about the condition. It's the wait in action 2

If you remove the wait and turn light off actions, does it still flicker?

[tough pulsar]

this therefore

moment I test

now the light doesn't come on at all

[verbal flame]

The bottom one as well

Licht Ausschalten

[tough pulsar]

the whole control system no longer works

[verbal flame]

Does it turn on and then not turn off?

[tough pulsar]

It's not about him at all

[verbal flame]

I don't understand.
You turned off the bit of the automation that switches the light off, and now it's not turning the light on any more?

[tough pulsar]

no i have deactivated the wait

as a result, the entire automation no longer works, or in other words, the light does not go on

[verbal flame]

Deactivate the wait and the turn off

Without just the wait, the automation is still running, it's just turning the light off immediately which makes it seem like it's not running at all

[tough pulsar]

Like this?

[verbal flame]

That turns the light on with no flickering, right?

[tough pulsar]

it doesn't even go on