Shelly Blu Gateway not discovering Shelly Blu Motion

Configuration
1

According to Shelly support the Blu Motion should work out-of-the box, however not the case.

The Blu Gateway is discovered by the Shelly Integration, but there seems no way to add the Blu Motion detector.

BTHome says “No devices found on the network” gone through pretty much every setting in the Gateway, Passive or Active scanning, configuration.yaml, HA etc and all software is up-to-date it’s as though bluetooth and/or discovery doesn’t work.

At the moment I’m considering reinstalling HA and starting over, the one bit of history is the HA is running on a pi5 which started life in the developer stages, could there be bluetooth setting outside HA that need attention?

If I take a full backup, install a fresh HA image then restore the backup would this bring in key data e.g devices, database, automations, yaml files and leave the new core intact?

Any advise much appreciated :+1:

2

I have similar problem.
My Shelly devices are discovered by integrated Pi Bluetooth and BTHome integration.
Not by gateway.
But this Shelly devices are far away from Pi, so I lost connection for most of them when in final situ. Gateway seems not used at all.
If I disconnect gateway from power, the only device seen by Pi is still managed.

Seems that there is a overlapping (logic interference?) between integrated Pi Bluetooth and Shelly Blu Gateway.
Or Shelly Blu Gateway is not yet really handled?

Any advice?

3

Simplest resolution is to plug an inexpensive Shelly BLU Gateway into an outlet nearby?

image

Caveat: I have not purchased one of those - however I have NUMEROUS Shelly devices and swear by them…

Here in the US at the Shelly store they are out of stock but Shelly is popular and there are many reseller. These are only about $19

4

Hi!
Yes, is exactly what I did, but seems that the Shelly Blu Gateway is ignored.
I explain better: other Blu devices was registered and discovered very close to the Blu Gateway, but really seems that was discovered by native Bluetooth RPi integration, not by Shelly Blu Gateway.
My tests shows that with Blu devices in the final physical place, Blu Gateway is ignored.
The closest device is seen directly by RPi, the others are not reachable, or best definition, their messages don’t reach RPi, and Blu Gateway seems that is not used at all.

I’m waiting for some M5Stack device to build some BLE proxy… Then I need something very small to power them, hidden inside junction box.

5

I’m experiencing exactly the same issues with getting my native RPi4 Bluetooth to connect to a far-away Switchbot humidity sensor via a Shelly BLU Gateway. Like you I’ve also tried to pair up said sensor via the Gateway, but it keeps wanting to connect to the RPi4 directly.

Will be watching with interest… :blush:

6

I also hope anyone help us to solve this problem (or issue?).

Maybe I should open an issue somewhere?
But I don’t know where.

7

When you set up a BLU device for the first time, you can select which gateays are used and which ones are ignored. I have not seen anywhere to set that setting after the BLU is set up. Possibly factory reset your BLU device/s and tell each of them during their setup to only use that one gateway during the setup process?