Will triggers with not_to be triggered when attribute changes?

Configuration
1

Hi all:

I read from HA document below:
If at least one of from , to , not_from , or not_to are given, the trigger fires on any matching state change, but not if only an attribute changed.

So I configured the below trigger with not_to, my idea is to ensure invalid values are not passed to my automation:

     not_to:
        - unknown
        - unavailable
        - none

I’m aware that not_to is not supported by UI editor, however I’m surprised to see in the description that my trigger will fire both for state and attribute changes, which is conflicting with what’s written in the document.

So is the document or UI editor correct?

2

Afaik the UI editor is incorrect. Because it does not register the not_to it falsely assumes there is no test for the state.

2 Likes