Sensor states "home" and "not_home" are not clearly separated

I run into an issue by using the auto-entities card.

When you have the states for devices_trackers like “home” and “not_home”, it is bad in this way that the wildcard of “home” will match “home” and “not_home”. In german it is “abwesend” und “zu hause”, but the states remain english.
There is definitely the potential for confusion in the selection, which then may lead to incorrect classifications.

While you can hardcode “home” vs. “not_home” as state as it is, it not a clear/n solution.

A better solution will be to find two different words that are not contained in each other as they are not used in a boolean way.

It is not a bug, but a thing to harden the architecture.

Just exclude "*not_*".

No thank you.
That is a massive breaking change that will destroy thousands of automations and templates.
This is a very bad idea.

1 Like