I was hoping someone might be able to help, this problem only started with one of the latest upgrades of HA.
I’m currently on: core-2021.12.3
What I have is a simple Arduino button in my bedroom, which turns of everything when I lie down, by sending an MQTT publish to a certain topic.
Every morning I get up, I have to then enable the hue motion sensor manually via the Hue app.
I had this button for about 1 year already, never was a problem, but all of a sudden, it disables the hue sensor (not the entity).
Anyone an idea why or what I could improve?
The reason btw, why I use entity_id all, because groups are tedious to maintain
well, I figured as much, but how can I prevent it or make the script better?
Or is this maybe a bug that was introduced, given it never did this before?
It’s not a bug, as part of the updated hue integration you now have additional switches exposed to home assistant from hue for enabling or disabling the hue motion sensors.
So simply your call to turn off all switches is correctly turning off all switches as you asked, it just so happens to now include the hue motion sensor switches.
Maybe time to update the way you turn things off as this is a classic example of why simply turning everything off is not the best option as every time something is updated and new switches are exposed consideration needs to be given.
@rossk Thanks for the answer, I guess it’s rather unfortunate (in my situation) that this is now become a switch too.
What would be a good practice to turn off everything I want? Is it only groups which I manually have to maintain or can you think of another way?
Thanks
Thanks @arganto, I’ve just disabled it for testing and the motion sensor still works after I turn off all. What is this switch for? I thought Hue motion sensor is only a binary_sensor. What could a switch do for someone? Thanks