BTHome: Shelly BLU Door/Window not updating

I replaced the Shelly Door/Window 2 (Wifi) with the BLU Door/Window (Bluetooth only) for my garage doors. I integrated them in Home Assistant via BTHome.

It does not update in Home Assistant! In Shelly App it shows it status correctly tho.

Is there anything I can do? Are there some settings (in Shelly or BTHome/Home Assistant)?
I remember that for the previous Door/Window 2 CoIoT must have been enabled and for Gen. 2 devices outbound websocket. Any similar tricks for the BLU Door/Window?

Somehow I have no luck with my garage doors Shelly sensors. None of them work accurately.

Thanks for any hints!

3 Likes

I had the same problem. You need to be sure that each BLE Observer (Gateway) is set to “Passive”. Then HA will recognize the state changes from the D/W BLU. However, while it recognizes the transitions of state, when the D/W BLU is idle it’s HA state is “unavailable”. I haven’t figured out this one yet. I put a query on Shelly’s facebook page and an admin deleted it without explaination!

1 Like

Hi,
I habe also a bug with the shelly blu d/w. Is this the same?

I have just noticed that it makes and difference how long the door is open. In our house the door is the front door, so if soneone opens the doors, go through it and close it. Home Assistant detect this as open.

When I open the door for letting fresh air in, and close it after a while, the door status in HA is right.

After I noticed that, I investigated that i litle bit further. When I close the door after HA has notified it is open, everything is okay.

It seems to me that the Shelly Blu is awaking when I open the door, and needs some time to send a “The door is open” bluetooth package. When I close the door fast, the “The door is closed” Data-Package is send before the open package.

Can someone give me a hint where to fill an issue, so that this bug can be fixed?

1 Like

​Hi all,
​
​I also experience the same issues with my Shelly BLU D/W sensors (2 sensors at home) as well as my Shelly BLU motion sensors (I have 6 at home). All of them show issues with “motion reset” or “door closed” every now and then. It could be fine for a few days and suddenly, the reset is not recognized by home assistant, although they are always perfectly fine in the shelly cloud app.
​
​Any solution yet?
​
​PS: I am now trying to use active scanning instead of passive to see if it makes a difference.
​
​Many thanks in advance!

Hello,

I had the same problem, with Home Assistant Container and I think I solved it by configuring the bluetooth properly on the host.

In my case I was missing to activate the bluetooth daemon on the host (ubuntu):

sudo systemctl daemon-reload
sudo systemctl unmask bluetooth.service
sudo systemctl restart bluetooth

You can check the status later:

sudo systemctl status bluetooth

Check also that in the HomeAssistant container you have access to the d-bus (/run/dbus:/run/dbus:ro).

After restarting, it updates the status of the Shelly Blu Door correctly.

Regards,

Hello,

Forget the previous message, after a while it stopped working again :frowning:

I kept trying with:

bluetoothctl power off
systemctl stop bluetooth

And it started working again, but I don’t know for how long…

I’m having a similar issue and can’t figure out what the problem is. I have 6 Shelly Blu D/W sensors, 5 of which work flawlessly. One of them is properly updating its status in the shelly app, but not in HA.
I can sometimes get it to sync to HA again when I disable the device, then enable it again and then open and close the window, effectively changing the status. It then works for a couple of hours and then stops working again. I don’t think that the one D/W sensor that I’m having issues with is connected to a different bluetooth gateway than at least 1 other one that works perfectly.

Put me down as a “me too”
I’ve done pretty much all of the steps above and have tried both the internal Bluetooth radio on my HA box as well as an external USB one and it makes no difference. Also some folks have said that updating the firmware of the sensor solves the issue, but mine is up to date as of 02/20 and it made no difference. People that maintain BTHome are blaming Shelly, and Shelly says “it works in our own app(which it does), so it must be your third party integration”
Sigh

Hi all,
I am joining the complaint about the Shelly Door/Window BLU failing to report the correct state to HA so many times (i.e. remaining “OPEN” while it is actually & on Shelly Control App is CLOSED).

Note: I think Shelly DW BLU has some FW update issues. on the Shelly BLU Debug app it says “The FW you’re trying to install is the same as the FW on the device” While the Shelly Control App when checking for update show there is an update but can’t install it (breaks in the middle of the process).

Hmm put me also to the “me too” group…
But I could update my Shelly BLU Firme to a new Version: 20240227-093929/v1.0.13@8042064c (readable in Shelly Debug BLE)
And with some hope I tried it again… and I think it’s a lot better now - but …still the same issue: In Shelly Smart Control App it works perfect within seconds in HA sometimes there is no update.
I tried it with and without encryption and with beacon mode on and off.
But nothing made me really happy - Any ideas?

good night!
Tobi

1 Like

Just here to report that mine is having the same issues.

It does not report Closed when the door is opened and closed quickly. It stays in the Open state.

This isn’t true 100% of the time but often enough to be very annoying.

This is such a terrible experience now :frowning:
Otherwise very happy with Shelly.

Same story here.

I bought two to test them and they did great. They are broadcasting to a Shelly switch and showing accurately in HA.

I then ordered 6 more and none of those six are working. I have no idea what is going on. They show in HA, I can configure them and sometimes they change status, once a day or so. They do work perfectly in the Shelly app, so something must be laying with the BLE gateway.

Two of the new ones are with the original gateway I tested the first ones with and they don’t even show up in HA.

Open for any ideas.

Same story.

But the worst case is, I deleted the BTHome Integration in order to try to implement Shelly BluDW with an updated firmware etc, but now if i try to install BTHome Integration I always get an Notification: No device is detected.

The Shelly app works flowlessly and shows the Status Chaning via Seconds.
WTF.

Any Ideas to get the sensor back in to the HA even without the updates of the status?

Thx

1 Like

When you delete entity or device, it lands in a registry as deleted and won’t be available for re-adding until you delete that record.

In my case (HA OS) they’d have to be deleted from /root/config/.storage/core.device_registry and /root/config/.storage/core.entity_registry. Look for deleted_devices and deleted_entities keys respectively. Pay attention to preserving correct JSON formatting (e.g. there’s no comma after last element in an array).

After that restart Home Assistant and you’ll be able to re-add them. (You may need to manually pick integration from “Add integration” view).

Finally, this message is a “me too” - I also have problem with Shelly BLU DW sensor, despite having two Shelly Plus 2PM with BT gateways enabled nearby.

Just for the records: Same problem here.
3 sensors working correctly, 2 don’t.
If I move the not working to a room with working sensors, they begin to work.
Problem with bluetooth range? Shelly App has no problems. And:
Put a gateway to the room where the sensors didn’t work, nothing changes, still no display of correct state.

This is not the same!

You Need to activate the BT in Homeassistant not in the Shelly App

Thats just what I did!

What I wanted to say is that the Shelly-App displays every open/close instantly and reliably.
HA doesn’t.

After some testing this is even more funny.
If (in HA) i look at the sensor’s log, most of the time I can see the window open/close. But in the Dashboard there is no change of state visible.

Strange, my status changes immediately

Same problem here…it’s making me crazy…