Sorry to add another “me too” to this thread, but I discovered this topic whilst trying to search for a solution. My problem sounds a lot like other folks on here.
I have 4 of these Shelly BLU Door/Window sensors and 90% of the time they seem to work OK. However every now and then (roughly one in 10, or maybe slightly more) events are missed and it’s always a transition from door open->closed (never the other way).
What is REALLY weird is that HA will see a door open event when the door physically opens - all good. However the door then closes and HA sees nothing! Then about 15, sometimes 20 or even 30 minutes later, a door-closed event triggers in HA!? Quite often, it will also log another door opened event at the same time, but this door opened event will have a timestamp of when the door was originally opened!?
I know categorically this is not a sensor issue for two reasons:
- I have downloaded the Shelly BLE debug app to my mobile and I can see the raw Bluetooth packets on door open/closed being transmitted by the sensor. I can see the door close packet on my phone, but HA registers nothing (intermittently).
- The Shelly App always reflects the correct status, which supports the above theory the sensor is doing its job.
Finally, I’m confident this isn’t a radio problem in terms of the events getting to a HA BLE proxy/gateway for two reasons - one, because of the time delay issue above (i.e. the events eventually do turn up, just very late and when they do, there is no way the actual radio event would have happened at that time!) and also, because I even went to the lengths of setting up an ESPHome bluetooth proxy using an ESP32 module (in addition to the 10 or so Shelly proxies I have dotted around the house). Even with this ESP32 BLE proxy sitting just 2-3 meters away from the sensors, this issue still occurs.
What is bizarre is this time-delay phenomenon, where about 15-30 minutes late, the door-closed status finally registers in HA. I mean the sensors only transmit on an actual door/open or close (they are not in beacon mode). So it almost seems like the events are getting back-logged in HA somewhere? I’m pretty convinced this is some sort of BLE event logic processing issue inside HA itself.
Here’s a demonstration in my HA logs that literally just happened, that shows exactly what I’m referring to. Just to be clear, the door physically opened at 08:04:22, and was closed almost immediately afterwards at 08:04:26 (i.e. the door was only open for about 4 seconds). 26 minutes after the door was closed, HA finally registered the door closed event at 08:30:36 and at the same time it registered a SECOND door open event at 08:04:22. So this data is getting backlogged somewhere in HA.
The shelly app log (right hand side of screenshot) shows the door open/closed event at the correct times, when it actually physically happened - again supporting the fact this isn’t a sensor problem, nor a BLE radio issue.
I’d be grateful for any Ideas, even in terms of how I could troubleshoot this problem further? I’m not sure if there is a way to trace these BLE events through the HA logic to see why they are getting held up by 15-30 minutes at times? And why is it always the door-closed rather than door-open that causes the trouble! All very weird!!
But it’s highly selective, it’s only one single sensor for me, all of my sensors are on 1.0.23 and I’m using a bunch of 1PM Minis (not controlling any power, just acting as BLE receivers). 19 devices and all report properly, except one. I did notice one difference - it shows up in HA as a Shelly Blu sensor, wheras the others are “Unknown.” I didn’t add it specially or different than the others, but perhaps this is a clue?