Problem with Shelly new ht plus sensor

Configuration
144

Yes I noticed the same! That is the reason I landed on this page. I took this moment to update the firmware on the shelly h&t and after that I deleted the device from HA and then re-added the device.

Everything works as before again. Hope this helps

145

Fix will be available in HA 2024.1.1.

4 Likes
146

FWIW, my device didn’t show up in HA until I moved it to the same subnet as HA. I was using a separate IoT network and couldn’t figure out how to make the port adjustments needed when the device is on a different subnet…

147

Thank you so much. I don’t know why the Shelly integration page (Shelly - Home Assistant) doesn’t mention this. I spent hours trying to get this working and that’s all it was!

148

You need to open the firewall in your home LAN to allow the port 8123 traffic to pass from the IOT LAN into your HOME LAN, similar to a port forward, but this is in the firewall settings.

149

Add it then please :pleading_face:

150

I created Update shelly.markdown for wss protocol by steini86 · Pull Request #30720 · home-assistant/home-assistant.io · GitHub. Was my first PR, so please don’t hesitate to correct me :grinning:

151

It’s already accepted, great going.

152

whats the correct one? /shelly not /Shelly right? i changed the url but it keeps changing back to /Shelly
finally managed to do it, you have to the ip and not the name in the url.

153

with Shelly or shelly? To me it accepted shelly, it found it alone in discovery in home assistant, but keeps in wait with this message


Please wait, starting configuration wizard for the integration

Also I do not understand this


In case your installation is set up to use SSL encryption (HTTP**S** with certificate), an additional `s` needs to be added to the WebSocket protocol,

I mean Sheely are installed locally no? SO I do not understand why shoulf be ssl

Now I received this


Do you want to set up the Shelly H&T Gen3 at 192.168.1.27?

Battery-powered devices that are password protected must be woken up before continuing with setting up.
Battery-powered devices that are not password protected will be added when the device wakes up, you can now manually wake the device up using a button on it or wait for the next data update from the device.

Invalid flow specified

“Invalid flow specified” error

155

Any updates on this?

I am able to connect a Shellt H&T Plus to my wifi network.
I am able to add it to my HomeAssistant server on the same network.

Yet I don’t have “a device” or “entities”.
It is empty.

Am I missing something for this integration?
Would the Shellt H&T “push” its data to the HomeAssistant server?

156

You need to configure the websocket outbound correctly.

157

I had the same problem adding these and won’t attempt to explain the why of it but what worked for me was to set up the websocket like:
ws://192.168.1.120:8123/api/shelly/ws
TLS No validation

I have another Home Assistant at our cabin and this worked:
wss://192.168.1.121:8123/api/shelly/ws

Both instances are set up the same so I’m not sure why one would take the wss and the other would not. I gave up on trying to figure out the ‘why’ since it worked.
Hope this helps. Now to figure out why the Flood sensors are flaky.

158

This worked great! Thanks