I can not get a Shelly PlusH&T sending status updates to openhab running in a container on a Raspi. I assume the outbound Websocket from the device does not get through to openhab in docker. Is there any specific docker configuration required to accept an incoming websocket communication?
thanks for your support
I’m having (I think) a similar issue. My Shelly PlusHT connects when it’s in setup mode and the web ui is reachable, but does not seem to update…or at least updates a couple times a day at most…when left on its own. I’m wondering if I need to change the websocket url from what the binding input:
ws://192.168.254.103:8080/shelly/wsevent with “Default TLS”
For what it’s worth, my OH install is running on host, and internal port 80 traffic is being redirected to OH.
Having the same issue as the original post on openHAB 4.2.3.
OH is running in a docker container on a synology.
I do not get updates from the Shelly H&T Gen3 to openHAB once it leaves setup mode.
After setting up the HTG3 as a new thing and after linking a channel to an item the “outbound websocket” entry on the Shelly is set to ws://172.17.0.2:8080/shelly/wsevent. I dont see how this can work since the synology is running on 192.168.10.103 and redirects 7100 to 8080 in the container.
I have tried to modify the outbound websocket entry in the shelly to `ws://192.168.10.103:7100/shelly/wsevent but that did not help. Sometimes it is overwritten, but even if it stays, there are no events reaching the openHAB instance.
I have some “old” CoIoT based Shelly Floods and they work fine after manually setting the address.
Searching around I only found this 2 year old post, so it feels like I am missing something obvious.
Thanks for any hints
It works if you run the docker container in host network mode, which is the recommended approach.