Wrong entity state in automation

I have this sensor from ElkM1 that has the states Normal and Violated when checked via the entities menu. When trying to use this in an automation (trigger / state) I only see status unavailable and unknown.

Why this discrepancy?

See here:

Developer Tools / States will show you the actual states of the entity. The front end might map these — for example, a binary sensor’s state is always 'on' or 'off' (or unavailable / unknown), but if you declare it as device_class: door, the front end will show it as “open” or “closed”.

For automation state triggers, you must use the real underlying state.

1 Like