Homekit precence sensor spam toggle

HI!

Yesterday this started.

11:36
HomeKit send command turn_on for “name” is Home
11:36
“name” is Home turned off
11:36
HomeKit send command turn_off for “name” is Home
11:33
“name” is Home turned on
11:33
HomeKit send command turn_on for “name” is Home
11:33
“name” is Home turned off
11:33
“name” send command turn_off for “name” is Home
11:30
“name” is Home turned on
11:30
“name” is Home turned off

This is spamming my log with both our phones, i use this as precence sensors and the automations are going haywire!

I hear you. I have similar issues and I can’t track down how to get around them.
Regarding your issue: if you use phones for presence detection, rely on the gps signal in the first place using zones plus wifi connection as additional source and/ or local bluetooth availability.
My hint to get this spot on: dump your phone wifi, gps, bluetooth plus a possibly available fitness wearable such as a wrist watch, armband or whatever you are carrying on you into a bayesian presence sensor to let probability statistics decide when you are actually home!
prioritize the sensors according to their probability of accuracy with values between 0.9 and 0.1 to give the algorithm an idea which device sensor delivers the best matching information in a reliable and consistant way.
iPhone wifi is really sketchy and apple watch wifi as well as bluetooth just the same due to energy saving measures. That’s why you keep getting the on- and off behaviour.
Once you have the bayesian presence sensor up and running, add it to a person in the config backend as the only reliable location sensor. Works like a charm and brings some reliable steadyness into the guestimation work :slight_smile:

Now to my issue:
The Homekit integration is a PAIN! Tell you why: It’s hard to configure, if something breaks you have to re-configure stuff in the home app again. No good. But that’s all doable.
The real pain comes from HomeKit itself: The damn HomePods start sending out shut_down commands sometimes. Especially if the update: they just send out a kill command that switches ALL devices in HA off!! WTF?!
The commands look like this:

HomeKit send command turn_off to Set state to False for Livingroom

So if I’m in the middle of a video call with my clients, suddenly my screen turns off because I have it hooked to a switched plug. What a pain!
Other cases: I watch TV through AppleTV and a projector and at 22:00 my door lock automatically goes to “night mode”, communicating this to HomeKit instantly, resulting in a collective shut-down of all appliances! Ridiculous!
As soon as I switch off this night-mode feature, everything works as expected.
Even worse: sometimes HomeKit devices - especially HomePods start doing something in the background, resulting in my device switches go sideways - out of nowhere. I actually need the HomeKit integration but decided to refactor my setup without HomeKit in HA. It’s a nightmare!
If anyone can help me out with this issue, I’d be seriously grateful.
I tried debugging it, monitoring the network traffic coming from the HomePods in such situations but can’t read the commands its sending. All encrypted. :- :rage:

Yup! Came across this post after trying to find out why my logs are telling me HomeKit sent the “turn_off” command to a bunch of my input booleans. Random.