`numeric_state` trigger with entity as above/below doesn't trigger if only the value of the above/below entity changes

[Cyberbeni]

The problem

I have the following trigger in an automation:

triggers:
  - entity_id:
      - sensor.a
    above: sensor.b
    for:
      hours: 0
      minutes: 0
      seconds: 30
    trigger: numeric_state

If sensor.b changes to fall below sensor.a then the automation won't trigger until sensor.a also changes and stays above sensor.b for 30 seconds.

I would expect sensor.b changing to also trigger the automation.

What version of Home Assistant Core has the issue?

2025.5.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[erkr]

The trigger is defined for sensor a only. You can try to define a second trigger for sensor b above sensor a.

Or create template binary sensor a_is_above_b. And trigger on that one

[mib1185]

Hi @Cyberbeni

We use GitHub for tracking issues with Home Assistant Core itself, not for providing support - so for support requests you should try the Community Forum or join the Discord chat server.
If you still feel it is a bug report, then please provide more details like logs or any other helpful diagnostics data or error details or steps how to reproduce or your configuration.

Thanks! 👍

[Cyberbeni]

@mib1185 this is not a support request. I know there are multiple ways to achieve triggering an automation based on one numeric value being above another one for a certain amount of time. This one is just not working correctly.

The yaml code is for an automation trigger. If you change the sensors to input_numbers then it should be pretty easy to reproduce. Please provide more information about which part of the issue you don't understand, English is not my native language.

[mib1185]

This trigger only fires in case of state changes changes of any of the defined entity_id. It won't fire in case the state of sensor_b is changed, as the trigger doesn't listen for such changes (see also the Numeric state trigger docs: "However, the comparison will only be made when the entity specified in the trigger is updated").

So you need support on how to achieve the automation which fits for your use case

[Cyberbeni]

I was trying to be helpful by reporting a bug. I didn't expect it to be a known issue that just gets shrugged off.

[mib1185]

it's not a known issue - it is by design and documented. If you feel this should be changed, then feel free to place a feature request 😉

[Cyberbeni]

https://www.home-assistant.io/blog/2020/04/14/the-future-of-yaml/

The goal of making it easier is currently the main focus.

Did that change since then?

Sure, I can create a template trigger or create a template sensor and trigger based on that. But the easier thing is to just use the stock numeric_state trigger with the stock "Numeric value of another entity" limit option and have it work the same way instead of being bean boozled by it working differently than how most people would expect it.

[rccoleman]

You're describing a desire for it to work differently than designed, which is a feature request. Please file one if this is important to you.

[tomlut]

This was raised in the beta discussion when the feature was first implemented. It is working as intended. If you want both entities to be monitored for changes then use a template trigger.