When distance increases, Shelly BLU H&T updates get propagated to the Cloud but not to MQTT

VPN/Proxy erkannt

Es scheint, dass Sie einen VPN- oder Proxy-Dienst verwenden. Bitte beachten Sie, dass die Nutzung eines solchen Dienstes die Funktionalität dieser Webseite einschränken kann.

    • Autor

    I have a strange problem, have not been able to see anyone reporting anything similar.

    On my home LAN I have a dozen different devices, both sensors and relays. Among them four BLU HT with firmware version 1.0.22 (the latest). I also have a Shelly Pro EM 50 firmware version 1.6.2 (also the latest) connected via WiFi which I use to measure power consumption of the house. The PRO EM also has Bluetooth enabled, and so it serves also as a Bluetooth gateway, and all four BTs view it as their gateway. All four HT regularly transmit their measurements: this is testified by the fact that the changes are visible on my phone's App. The Pro EM has also MQTT enabled, and the measurements from the HTs (as well as the power consumption from the PRO EM) are transmitted to a remote Linux MQTT server that records the data into a database for historical reasons. So far so good, everything works as expected. Just to clarify, no script is involved, this is pure "PRO EM as Gateway" functionality.

    But if I move one of the HT to a different room, the Cloud is still continuously updated (the values change on the App, the activity register shows the timestamps of the updates, etc) BUT the MQTT messages with the values from that particular HT immediately stop. If I move the HT back into the room where the PRO EM is, the MQTT messages from that HT start again. I have tried with all the HTs, and they behave all in the same way. Does not seem to be an issue with one particular device.

    I would expect that the PRO EM and the HT communicate via BLE and thus the signal is either powerful enough to establish the communication or not enough for the two to communicate. Therefore at all times the Cloud and MQTT for that HT should either both work or both not work. What am I missing? Any test I can do to better understand? How can I keep MQTT working, since the PRO EM seems to be receiving the BLE signal? Any hint is appreciated! Thanks!

    Einmal editiert, zuletzt von stefmorp (5. Juni 2025 um 23:37)

    You don't have a Shelly Wifi-based device other than the Shelly Pro EM 50, right? (which could inadvertently also work as a BLU gateway)?

    Überwiegend PRO 3EM im Einsatz zur Haus und PV Überwachung

    • Autor

    Hi TVB,

    thanks for your prompt response. Yes I have other shellies, about a dozen. One of them is a Shelly Plus 2PM which I use to manage my courtains, and has a BLU gateway enabled. It is very far from both the PRO EM and the BLU HT, so that when I turn off the PRO EM, the BLU HT tries to connect to the 2PM but does not reach it, and shows "offline" on the APP. Needless to say, also MQTT messages stop. However, if I put the BLU HT in the same room as the 2PM, it goes online and starts sending MQTT messages too. I have no other BLE devices. Hope this helps better understand the configuration...