Shelly Binding

Tallman · February 13, 2023, 6:58pm

It seems that the names in the thing file cannot contain spaces. Should that be so ?

Oliver2 · February 13, 2023, 7:01pm

in MainUI spaces for thing names are allowed. Not sure for file based configuration

Tallman · February 14, 2023, 5:35pm

So the name displayed in the Shelly Manager is not the Shelly label but its network address and when I display the menu, the name is empty. But it shows up in the GUI.

Oliver2 · February 14, 2023, 5:48pm

The shelly name comes from the device itself (settings → device name). Not sure what effect it has but try to set your devices to discoverable: yes

Tallman · February 14, 2023, 6:42pm

I had never given my Shellys a name in the device. Now I’ve done it and the Shelly manager is working again. Interesting that it worked without it until now.
Thank you

Oliver2 · February 14, 2023, 6:47pm

Quite useful: if you add new devices the binding uses the device name for the thing’s name.
Especially if you are using the dev binding from time to time you need to delete and re-add all things. By setting the device name in the device this task is done within a couple of seconds

hmerk · February 14, 2023, 6:48pm

This is not the reason. I have three shelly-plug-s which don’t even have the option to set a device name, but showing up with their network name in shelly manager. Might be that setting the device name just triggered a network announcement on the shelly devices which was then cought by the binding and shelly manager, finally resulting in showing up.

Oliver2 · February 14, 2023, 6:53pm

Not related to the problem in any way but Plug S do have the option to set a device name (unless you have a very old FW)

hmerk · February 14, 2023, 7:01pm

I know, I have a newer one with actual fw and three old ones which are stuck on old fw….

z4nD4R · February 15, 2023, 5:14pm

Hello Everyone,

I’d like to ask you about pointing me to right direction. I’ve bought recently Shelly Duo RGBW2 bulb. I’ve added that bulb using shelly binding and Shelly Bulb (SHBLB-1) type of the thing. I’m able to power it, but I can not control the color. Even I set the mode for color nothing happened (I can just see the brightness is changing). Even I change the mode directly in web interface of the Bulb itself, I can not than control the color of the bulb.

Also the setting the temperature of the bulb doesn’t works, but maybe it is coupled with some general issue. Any advice is welcome.

Thx
Y

sengscfr · February 18, 2023, 8:21am

Shelly Plus Smoke is out and it can be ordered now. Is it supported by the Shelly Binding?

Oliver2 · February 18, 2023, 5:40pm

Hi Markus, here you go. this is a debug log between two of such messages:

2023-02-18 18:31:56.669 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler ShellyLightHandler tried updating the thing status although the handler was already disposed.
2023-02-18 18:31:56.671 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellyrgbw2-49d23a: 22 CoAP sensor updates received
2023-02-18 18:31:56.671 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellyrgbw2-49d23a: CoIoT Sensor data {"G":[[0,9103,1],[0,1101,1],[0,5101,42],[0,1201,1],[0,5201,28],[0,1301,0],[0,5301,1],[0,1401,0],[0,5401,1],[0,4101,9.87],[0,4103,653],[0,4201,6.58],[0,4203,435],[0,4301,0.00],[0,4303,0],[0,4401,0.00],[0,4403,0],[0,6102,0],[0,2101,0],[0,2102,""],[0,2103,0],[0,9101,"white"]]} (serial=59137)
2023-02-18 18:31:56.675 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellyrgbw2-49d23a: 22 CoAP sensor updates received
2023-02-18 18:31:56.688 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellyrgbw2-49d23a: 2 channels updated from CoIoT status, serial=59137
2023-02-18 18:31:57.239 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellyrgbw2-a638e4: CoIoT Message from /192.168.178.79:5683 (MID=29522): {"G":[[0,9103,1],[0,1101,0],[0,5101,16],[0,1201,0],[0,5201,54],[0,1301,0],[0,5301,0],[0,1401,0],[0,5401,0],[0,4101,0.00],[0,4103,0],[0,4201,0.00],[0,4203,0],[0,4301,0.00],[0,4303,0],[0,4401,0.00],[0,4403,0],[0,6102,0],[0,2101,0],[0,2102,""],[0,2103,0],[0,9101,"white"]]}
2023-02-18 18:31:57.241 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellyrgbw2-a638e4: Serial 512 was already processed, ignore update
2023-02-18 18:31:59.943 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellydimmer-d484e5: CoIoT Message from /192.168.178.24:5683 (MID=3412): {"G":[[0,9103,1],[0,1101,0],[0,5101,70],[0,2101,0],[0,2102,""],[0,2103,0],[0,2201,0],[0,2202,""],[0,2203,0],[0,4101,0.00],[0,4103,0],[0,6102,0],[0,6109,0.00],[0,6104,0],[0,3104,50.48],[0,3105,122.87],[0,6101,0],[0,9101,"white"]]}
2023-02-18 18:31:59.945 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellydimmer-d484e5: Serial 512 was already processed, ignore update
2023-02-18 18:32:00.016 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shelly1-e098069657aa: CoIoT Message from /192.168.178.22:5683 (MID=21187): {"G":[[0,9103,1],[0,1101,0],[0,2101,0],[0,2102,""],[0,2103,0]]}
2023-02-18 18:32:00.018 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shelly1-e098069657aa: Serial 512 was already processed, ignore update
2023-02-18 18:32:00.295 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellydimmer-d0e053: CoIoT Message from /192.168.178.34:5683 (MID=57259): {"G":[[0,9103,0],[0,1101,1],[0,5101,40],[0,2101,0],[0,2102,""],[0,2103,0],[0,2201,0],[0,2202,""],[0,2203,0],[0,4101,23.02],[0,4103,1067],[0,6102,0],[0,6109,0.00],[0,6104,0],[0,3104,31.75],[0,3105,89.15],[0,6101,0],[0,9101,"white"]]}
2023-02-18 18:32:00.297 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellydimmer-d0e053: CoIoT Sensor data {"G":[[0,9103,0],[0,1101,1],[0,5101,40],[0,2101,0],[0,2102,""],[0,2103,0],[0,2201,0],[0,2202,""],[0,2203,0],[0,4101,23.02],[0,4103,1067],[0,6102,0],[0,6109,0.00],[0,6104,0],[0,3104,31.75],[0,3105,89.15],[0,6101,0],[0,9101,"white"]]} (serial=1280)
2023-02-18 18:32:00.299 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellydimmer-d0e053: 18 CoAP sensor updates received
2023-02-18 18:32:00.307 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellydimmer-d0e053: 3 channels updated from CoIoT status, serial=1280
2023-02-18 18:32:00.573 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellyix3-68c63afa94dd: CoIoT Message from /192.168.178.72:5683 (MID=32143): {"G":[[0,9103,0],[0,2101,1],[0,2102,""],[0,2103,3],[0,2201,0],[0,2202,""],[0,2203,0],[0,2301,0],[0,2302,""],[0,2303,0]]}
2023-02-18 18:32:00.575 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellyix3-68c63afa94dd: Serial 1536 was already processed, ignore update
2023-02-18 18:32:02.435 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shelly1-e09806961050: CoIoT Message from /192.168.178.67:5683 (MID=7870): {"G":[[0,9103,1],[0,1101,0],[0,2101,1],[0,2102,""],[0,2103,0]]}
2023-02-18 18:32:02.437 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shelly1-e09806961050: Serial 2048 was already processed, ignore update
2023-02-18 18:32:04.925 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellyswitch25-e098068cecb0: CoIoT Message from /192.168.178.35:5683 (MID=12658): {"G":[[0,9103,1],[0,1102,"stop"],[0,1103,60],[0,2101,0],[0,2102,""],[0,2103,0],[0,2201,0],[0,2202,""],[0,2203,0],[0,4102,0.00],[0,4104,140],[0,6103,"normal"],[0,3104,49.86],[0,6101,0],[0,9101,"roller"],[0,4108,232.77]]}
2023-02-18 18:32:04.927 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellyswitch25-e098068cecb0: CoIoT Sensor data {"G":[[0,9103,1],[0,1102,"stop"],[0,1103,60],[0,2101,0],[0,2102,""],[0,2103,0],[0,2201,0],[0,2202,""],[0,2203,0],[0,4102,0.00],[0,4104,140],[0,6103,"normal"],[0,3104,49.86],[0,6101,0],[0,9101,"roller"],[0,4108,232.77]]} (serial=4864)
2023-02-18 18:32:04.929 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellyswitch25-e098068cecb0: 16 CoAP sensor updates received
2023-02-18 18:32:04.931 [DEBUG] [y.internal.api1.Shelly1CoIoTVersion2] - shellyswitch25-e098068cecb0: CoAP update roller position: control=40, position=60
2023-02-18 18:32:06.045 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellyplug-s-9d8de0: CoIoT Message from /192.168.178.75:5683 (MID=45519): {"G":[[0,9103,0],[0,1101,1],[0,4101,5.11],[0,4103,467],[0,6102,0],[0,6109,0.00],[0,3104,30.20],[0,3105,86.37],[0,6101,0]]}
2023-02-18 18:32:06.047 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellyplug-s-9d8de0: CoIoT Sensor data {"G":[[0,9103,0],[0,1101,1],[0,4101,5.11],[0,4103,467],[0,6102,0],[0,6109,0.00],[0,3104,30.20],[0,3105,86.37],[0,6101,0]]} (serial=1792)
2023-02-18 18:32:06.049 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellyplug-s-9d8de0: 9 CoAP sensor updates received
2023-02-18 18:32:06.054 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellyplug-s-9d8de0: 2 channels updated from CoIoT status, serial=1792
2023-02-18 18:32:06.883 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shelly1-84cca8a81036: CoIoT Message from /192.168.178.78:5683 (MID=33731): {"G":[[0,9103,1],[0,1101,0],[0,2101,0],[0,2102,""],[0,2103,0]]}
2023-02-18 18:32:06.885 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shelly1-84cca8a81036: Serial 512 was already processed, ignore update
2023-02-18 18:32:07.369 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellyswitch25-e098068d4ef7: CoIoT Message from /192.168.178.36:5683 (MID=46775): {"G":[[0,9103,1],[0,1102,"stop"],[0,1103,100],[0,2101,0],[0,2102,""],[0,2103,0],[0,2201,0],[0,2202,""],[0,2203,0],[0,4102,0.00],[0,4104,0],[0,6103,"normal"],[0,3104,52.38],[0,6101,0],[0,9101,"roller"],[0,4108,232.16]]}
2023-02-18 18:32:07.371 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellyswitch25-e098068d4ef7: CoIoT Sensor data {"G":[[0,9103,1],[0,1102,"stop"],[0,1103,100],[0,2101,0],[0,2102,""],[0,2103,0],[0,2201,0],[0,2202,""],[0,2203,0],[0,4102,0.00],[0,4104,0],[0,6103,"normal"],[0,3104,52.38],[0,6101,0],[0,9101,"roller"],[0,4108,232.16]]} (serial=3072)
2023-02-18 18:32:07.374 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellyswitch25-e098068d4ef7: 16 CoAP sensor updates received
2023-02-18 18:32:07.376 [DEBUG] [y.internal.api1.Shelly1CoIoTVersion2] - shellyswitch25-e098068d4ef7: CoAP update roller position: control=0, position=100
2023-02-18 18:32:07.382 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellybulbduo-d0dba6: CoIoT Message from /192.168.178.76:5683 (MID=60554): {"G":[[0,9103,1],[0,1101,0],[0,5101,70],[0,5103,3688],[0,5104,26],[0,4101,0.00],[0,4103,0]]}
2023-02-18 18:32:07.384 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellybulbduo-d0dba6: Serial 512 was already processed, ignore update
2023-02-18 18:32:07.668 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellyrgbw2-49d23a: CoIoT Message from /192.168.178.73:5683 (MID=19037): {"G":[[0,9103,1],[0,1101,1],[0,5101,42],[0,1201,1],[0,5201,28],[0,1301,0],[0,5301,1],[0,1401,0],[0,5401,1],[0,4101,13.60],[0,4103,663],[0,4201,9.07],[0,4203,442],[0,4301,0.00],[0,4303,0],[0,4401,0.00],[0,4403,0],[0,6102,0],[0,2101,0],[0,2102,""],[0,2103,0],[0,9101,"white"]]}
2023-02-18 18:32:07.668 [DEBUG] [lly.internal.api1.Shelly1CoapHandler] - shellyrgbw2-49d23a: CoIoT Message from /192.168.178.73:5683 (MID=19037): {"G":[[0,9103,1],[0,1101,1],[0,5101,42],[0,1201,1],[0,5201,28],[0,1301,0],[0,5301,1],[0,1401,0],[0,5401,1],[0,4101,13.60],[0,4103,663],[0,4201,9.07],[0,4203,442],[0,4301,0.00],[0,4303,0],[0,4401,0.00],[0,4403,0],[0,6102,0],[0,2101,0],[0,2102,""],[0,2103,0],[0,9101,"white"]]}
2023-02-18 18:32:07.670 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler ShellyLightHandler tried updating the thing status although the handler was already disposed.

I am on 3.4.2 and replaced old dev binding with dist binding.
Unfortunately this is flooding my log (~each 5 seconds one message)

Oliver2 · February 18, 2023, 6:13pm

No, it is not yet supported.
@markus7017 : I got a new smoke detector today. Is there anything I can do to help?

To all users of new Shelly Plus Smoke:
Before you go mad (so did I - nearly…)

1. to start pairing mode: 5x short button press (wake up device and activate WIFI Access Point)
2. to wake up device: 3x short button press (as opposed to the manual which says 3 seconds)

Some more information:

The device closes an active connection without any notification even though you are currently accessing the internal web server.
Make sure to cover the speaker with your thumb when pressing the button

Oliver2 · February 18, 2023, 6:33pm

After some more investigation I found out how to resolve the following warning message:

Handler ShellyLightHandler tried updating the thing status although the handler was already disposed.

Most probably at least one of your devices still has the setting:

CoIoT peer: mcast

If you change this to (OH IP address):5683 the warning goes away
@davorf

davorf · February 20, 2023, 5:26pm

Hello!

Thank you for this information. Warning message stopped showing in log after I’ve changed this setting.

Best regards,
Davor

scheuerer · February 21, 2023, 1:25pm

Hello,

I have one of over 40 Shelly’s which makes problems only in the log file. The shelly1 works in pricipal normal,
but he spam’s the logfile all the time with this information. He is not NOT switching on/off like the logfile shows me:

2023-02-21 14:22:07.216 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Aussenlichter_Betrieb’ changed from OFF to ON

2023-02-21 14:22:08.172 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Aussenlichter_Betrieb’ changed from ON to OFF

2023-02-21 14:22:22.121 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Aussenlichter_Betrieb’ changed from OFF to ON

2023-02-21 14:22:23.219 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Aussenlichter_Betrieb’ changed from ON to OFF

2023-02-21 14:22:37.140 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Aussenlichter_Betrieb’ changed from OFF to ON

2023-02-21 14:22:38.270 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Aussenlichter_Betrieb’ changed from ON to OFF

2023-02-21 14:22:52.140 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Aussenlichter_Betrieb’ changed from OFF to ON

2023-02-21 14:22:53.363 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Aussenlichter_Betrieb’ changed from ON to OFF

2023-02-21 14:23:07.150 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Aussenlichter_Betrieb’ changed from OFF to ON

2023-02-21 14:23:08.405 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Aussenlichter_Betrieb’ changed from ON to OFF

2023-02-21 14:23:22.146 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Aussenlichter_Betrieb’ changed from OFF to ON

2023-02-21 14:23:23.446 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Aussenlichter_Betrieb’ changed from ON to OFF

2023-02-21 14:23:37.146 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Aussenlichter_Betrieb’ changed from OFF to ON

2023-02-21 14:23:38.496 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Aussenlichter_Betrieb’ changed from ON to OFF

2023-02-21 14:23:52.149 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Aussenlichter_Betrieb’ changed from OFF to ON

2023-02-21 14:23:53.587 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Aussenlichter_Betrieb’ changed from ON to OFF

2023-02-21 14:24:07.143 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Aussenlichter_Betrieb’ changed from OFF to ON

2023-02-21 14:24:08.632 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Aussenlichter_Betrieb’ changed from ON to OFF

2023-02-21 14:24:22.147 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Aussenlichter_Betrieb’ changed from OFF to ON

2023-02-21 14:24:23.684 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Aussenlichter_Betrieb’ changed from ON to OFF


This happens on my Testsystem PI under 3.4.2-1 and also on my Productionsystem with 3.4.1-1
(booth systems are in the same network and are a 1:1 copy) the IP-Adress is differnet, and the Rules are off on the teststem.

Any idea why this happens?

markus7017 · February 21, 2023, 4:47pm

I habe the smoke and plus plug s on the table, hit this problem and was annoyed , moved to the plusplugs and ran into
problems with the dev environment, annoying too and that was it for the weekend

I need to find some more time

markus7017 · February 21, 2023, 4:48pm

did you checked events.log?

did you tried to delete and re-discover the thing (OH preserves the item linkage).

Are there other Shelly 1s showing the same symptom?

markus7017 · February 21, 2023, 4:50pm

That‘s strange. The setting changes from multicast (the binding receives traffic from all Shellys) to peer mode (traffic only from selected devices). How many Shellys do you have on the network?

scheuerer · February 21, 2023, 6:16pm

OK, here some answers:

I have already had deleted the shelly1 and have added him by scanning.–> Same effect
Today, once more, → Same effect
230V Power off and on also was done…
The shelly has the latest firmware 20221027-091427/v1.12.1-ga9117d3
I have nearly 40 shellys in the same network.
Several shelly1 with the same 1:1 settings, (sure different IP Adresses)