I’ve been using Home Assistant for over 5 years and I don’t recall the State Trigger ever working that way. It has worked the way it’s described in the documentation:
If you use one of the additional options (to, from, etc) then it will only listen for changes to the entity’s state property (and ignore changes to the entity’s attributes).
Example
This listens for any changes to the sensor’s state value and ignores changes to the entity’s attributes.
trigger:
- platform: state
entity_id: sensor.foo
to:
This is not possible using the visual editor and your first explanation didn’t actually explain the behaviour of a null to value.
This totally feels like a workaround - state change of entity is now recursive to the attributes, but you can suppress that by supplying a to value, supplying null for to will function as wildcard but still disables attribute checks
It stated: " This listens for any changes to the sensor’s state value and ignores changes to the entity’s attributes." The example contains the to option with no value, just like the one in the documentation.
You’re free to call it what you want but that’s how the State Trigger works. It never worked the way you explained in your first sentence:
Previously you could select a state trigger and if you didn’t select an attribute it would only trigger if the value of the entity changed.