Shelly Binding Thing websocket error

[xvs03 (Mario M.)]

Hello, I wanted to connect a Shelly plus 1 PM with openHAB. It has an add-on with three DS18B20 temperature sensors.
The Shelly was found via Thing Scan. It found 3 channels for external temperature.

If I now want to link the temperature items, it is like a random generator which sensor I get. Sometimes sensor (100) sometimes sensor (101). But I never get the sensor that matches the item.

The Thing goes to “error communication” “websocket error” in the meantime and has to be switched on and off again.

The following messages are displayed in the Shelly diagnosis, which I have not yet been able to explain.

Shelly Firmware 1.2.0
OpenHAB 4.4.1 with Shelly Binding 4.4.1

helly_notification:116 ch type=WS_in info=192.168.178.22:56568 has no DST
18:30:00
shelly_notification:116 ch type=WS_in info=192.168.178.22:43900 has no DST
18:30:00
shelly_notification:163 Status change of temperature:101: {"id":101,"tC":17.44,"tF":63.39}
18:30:15
shelly_notification:116 ch type=WS_in info=192.168.178.22:56568 has no DST
18:30:15
shelly_notification:116 ch type=WS_in info=192.168.178.22:43900 has no DST

.22 is the OpenHAB Server

I will probably switch to MQTT until the problem is solved.

[Oliver2 (Oliver)]

Please close this thread and post your problem in this thread:

Shelly Binding

Hi, I started to develop a binding for Shelly products. I have a Shelly1 and a Shelly2. These will be implemented and tested for the time being, the rest of the product family I will implement as well as possible, but can not test. Is there any interest in having the binding published in due course? I’m only doing it because I wanted to work on programming bindings and I’m not really a fan of MQTT You can just contact me and let me know if someone is interested or not.

This is where the developer helps users.

[xvs03 (Mario M.)]

Ok I have changed the topic on your recommendation. Thanks for the hint