Shelly in different VLan - outgoing websocket configuration does not help to get updates

[Terra]

Hi there,

I am in the process of moving all my shelly devices in a different Vlan.
As I am still experimenting I have allowed all traffic between the Vlan where the OpenHab server is located and the IoT VLan where the shelly’s should be in the end.

The status now is, that I can control the shelly’s with OpenHab but OpenHab does not get status infos back from the shelly’s.
e.g. When I press the physical switch OpenHab does not get the info that the light is on.

I read that I should configure the outgoing websockets url in the shelly’s, but this seems do not do the trick.
Am I missing anything?

I have configured the following URL in outgoing websocket:
ws://192.168.0.15:8080/shelly/wsevent
With the “Default TLS” option.

When enabling debugging I see that updates seem to hit openhab, but they get discarded?

22:09:59.599	DEBUG	
org.openhab.binding.shelly.internal.api2.Shelly2ApiRpc
shellyplus2pm-3ce90e2eab84 - 192.168.0.140: NotifyStatus update received: {"src":"shellyplus2pm-3ce90e2eab84","dst":"ws","method":"NotifyStatus","params":{"ts":1.7893302E9,"switch:0":{"aenergy":{"total":997.916,"by_minute":[263.582,263.738,264.032],"minute_ts":1789330200}}}}

22:09:59.599	DEBUG	
org.openhab.binding.shelly.internal.api2.Shelly2ApiRpc
shellyplus2pm-3ce90e2eab84 - 192.168.0.140: Thing is shutting down, ignore WebSocket message

thanks

[justaoldman (Justan Oldman)]

How are you managing intravlan routing? is your OpenHAB on your default untagged VLAN and is the shelly is on a tagged VLAN yet both on same subnet? What ever way you have it configured you must provide both VLan’s a route to communicate with each other.

[Spaceman_Spiff (Sebastian)]

@Terra

I read that I should configure the outgoing websockets url in the shelly’s, but this seems do not do the trick.
Am I missing anything?

Where have you read that? The last time I checked outgoing websockets were not supported.
But this was a long time ago so it would be great if that has changed!

[Terra]

@Spaceman_Spiff

Where have you read that? The last time I checked outgoing websockets were not supported.
But this was a long time ago so it would be great if that has changed!

From what I understood the Shelly Binding uses websockets for all Shelly’s Gen2+. It is mentioned in the documentation that it is required at least for battery powered devices to get status updates. But maybe this then is really only for battery powered devices?!

Regarding where I got that, I found some pointers here:

Generation 2: WebSockets - Shelly - Bindings

Shelly Plus devices, websocket and Openhab Docker

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

[shelly] Plus 2PM Gen3 has occasional websocket error

[Terra]

@justaoldman

How are you managing intravlan routing? is your OpenHAB on your default untagged VLAN and is the shelly is on a tagged VLAN yet both on same subnet? What ever way you have it configured you must provide both VLan’s a route to communicate with each other.

As mentioned right now I have no blocks between the VLans. This is realized In the UniFi controller where I have both VLans in the Firewall Zone “Internal”. At a later stage, when I have solved the issues, I want to separate this properly.

However, I assume broadcast/multicast is still blocked between the Subnets/Vlans and that is why I do not get status updates.

[Terra]

Well, for some reason it works now!

I have deleted the thing and readded it manually in OpenHab. Now I get proper status updates

It definitely only works with outbound websockets enabled and configured. If I disable it in the Shelly I do not get any status updates. I am testing right now with a “Shelly Plus 2PM”

Here is my config in the Shelly; 192.168.0.15 is my OpenHab server.

[polychronov (Konstantin Polychronov)]

I use COIOT configuration of the shellys and seems to work for me. Same setup - my OH is in a separate VLAN than the IoT devices. No problem for me, just make sure you allow the connections on the forward chain of the router.

[Terra]

Are you using Gen2/3/4 devices? From what I understood there is no CoIoT after Gen1?

I also cannot find a CoIoT setting in my Gen4 PM2

[v61 (Valter Lindström)]

CoIoT is only in gen1.

I am using mqtt for gen2- when state updates are important.

I have separate vlan’s and also a couple of shellies in the summer house that I access via vpn.

[v61 (Valter Lindström)]

Just did some quick tests and ws works fine. Also via vpn.

[Terra]

So just to summarize how this worked for me:

Shelly (Gen 1)

Open Shelly config page in browser
→ Internet & Security → Advanced - Developer Settings

Enable CoIoT: Yes
CoIoT Peer: :5683

Shelly (Gen2,Gen3,Gen4,…)

Open Shelly config page in browser
→ Settings → Connectivity settings → Outbound websocket

Enable: Yes
Connection Type: Default TLS
Server: ws://:8080/shelly/wsevent

I did not change anything in the OpenHab Shelly Binding Config, “Auto CoIoT” is still on in my case.

I have 18 Shellies and for 1-2 Shellies I still did not get any state updates, I had to remove the thing and add it manually again and then it worked.