#Shelly BLU Gateway setup error

13 messages · Page 1 of 1 (latest)

ivory ledge
#

So, I quite like Home Assistant so far. Many things just work nearly instantly, or at least with far less effort than my attempt at getting an LG TV to work with Google Home. I've been running into an odd issue though: I bought a Shelly BLU TRV + gateway. They pair just fine, and work fine on the app. The Shelly integration in Home Assistant keeps throwing a "Failed setup, will retry: None" error, though. No devices detected. Every few seconds it'll go back to initializing, before showing the same error.

I vaguely remember an error about unsupported firmware, in my notifications? But I clicked ignore on it some days ago while trying other approaches to this issue and can't figure out how to un-ignore an error.

The log doesn't show anything useful. It does normal-looking RPC stuff, grabbing some information from the gateway and even asking about the TRV, before suddenly "RPC device init finished" and "RPC device shutdown", both from aioshelly.rpc_device.device, a millisecond after the last RPC call (GetRemoteConfig)

#

One thing I noticed is that the gateway is running firmware 20241007-074728/1.4.99-blugwg3prod2-g689f175, and insists that it's up to date, while firmware 1.5.0 should be out for this gen.

#

I did manage to update the TRV's firmware without a hitch, though.

#

I've run out of ideas, and I can't find anyone with the same issue on the internet.

#

I am able to access the gateway's web UI at 192.168.11.25 via http, and it looks normal.

#

The gateway offers a websocket debug log, but that also only mentions the RPC calls with nothing that implies an error.

#

Ah, the webui gives me the option of updating to firmware 1.5.1-beta1. Nothing about 1.5.0, though.

#

That's all I can think of. I'll go do something else while I wait for replies.

ivory ledge
#

Shelly BLU Gateway setup error

ivory ledge
#

Still getting the same error, tried various things. I could really use some help.

ivory ledge
#

Okay. In desperation, I updated from firmware 1.49.something to beta 1.50.1 or 1.51 or something... I figured I could just hunt down working firmware if needed.

#

The beta fixed this right away.

#

And I got my TRV to work too.