Numeric_state trigger in automation. False executions

[knst]

will not work - numeric_state fires on first change of sensor value after restart if it is in range. It may happen much later than 10s after start.

[Mutt (Muttley)]

No, The bit being on, as a condition, in its firing, stops it !

[knst]

1. sensor value is 0, automation trigger has below:30
2. HA is rebooted
3. Bit is set on start
4. 10s passes since HA started
5. Bit is changed to off
6. in an hour sensor reports value 1
7. At this point, bit is off and it is first time sensor reports value since HA start thus automation fires

[Mariusthvdb (Marius)]

@knst

Actually I solved it with template sensor

still this would be a more elegant way to do it:

Numeric_state trigger in automation. False executions

you should leave this out, no need for that, the numeric_state uses the entity_id, which you have declared already you should use the template if you need an attributes: https://www.home-assistant.io/docs/automation/trigger/#numeric-state-trigger but since your using state here, thats not needed as to the trigger itself: you might want to experiment creating an extra binary_sensor, with value ‘on’ if the state is below 30 for 5 minutes. binary_sensor: - platform: template sensors: …

in the automation, you can leave out 'from: ‘off’ ', since it is a binary, and that only has 2 states. Using the delay_on in the binary_sensor definition, you can leave out the timing issue from the trigger…

making it even nicer, you can write your condition as:

condition: template
value_template: >
  {{is_state('binary_sensor.occupied','on')}}

Like this you can check the templates in the templates editor.

[Guyohm]

Thanks @pnbruckner for explaining how numeric_state trigger works.
I think I have found why I get false triggers randomly. For my part, the problem seems there after I reload the automations.

Since reloading the automations reset them, I guess it makes it loose it’s last state and then on the next state change, the trigger happens. Same as when rebooting I guess.

It would be nice if there was a way restore automatically the last known value taken from the recorder data on restart and on automations reload.

[sygys]

You could always make an automation that sends you a message when it gets the unavailable state. I found it quite helpful to put telegram send message actions to my automations to see what home assistant is doing during the day. This helps debugging automation allot more easy. Mostly i add these actions to new automation for some time and when everything keeps running like it should I remove it. This way you get instant messages in telegram everytime an automation triggers and it’s easier to find a problem