Shelly bluetooth proxy not publishing data from BLU device

Configuration
1

I’m trying to get a BLU H&T connected to my HASS instance via a bluetooth proxy on a Plus 1PM, but it is not being picked up by HASS.

I’ve configured it according to all the various guides on the internet, which all say that it should ‘just work’ - but it isn’t.

I can see in the logs that the 1PM can at least see the BLU H&T (the aioshelly script installed on there is outputting something). I was expecting this to ‘magically’ get forwarded to HASS via the 1PM’s WiFi connection, but that doesn’t seem to be happening (the computer running HASS does not have functioning bluetooth), the Shelly integration isn’t picking up anything, and the ‘add device’ only seems to work for direct WiFi devices - I’m not sure how to manually add a proxied bluetooth device.

I’m now looking at a MQTT forwarding script on the 1PM to forward the H&T data to MQTT, but that seems a bit overkill.

What am I missing here? Am I just not understanding what the bluetooth gateway functionality does?

2

Have you setup the Shelly to act as a BT Proxy in HA?

Settings - Devices & Services - Shelly - Configure button for your device - Anything other than disabled.

I think this defaults to off.

3

Yup, done that. As I said, I followed all the online guides I could find. Tried both active and passive.

4

So, turns out it does Just Work - as long as the battery in it is working. The battery was completely flat!

5

it’s not needed for proxying ble values to mqtt.
This option is needed only with Shelly Cloud

6

I have new batteries, it works in shelly’s app, but nothing is visible in HA, i see the “mini” as is my proxy, but not the HT or the Motion:

How the heck did you do to get it working?