Shelly Binding

thx :wink:

Today Iā€™ve restarted openHAB and I am having trouble with the shelly binding.
Iā€™ve configured all my shelly25 like this:

Thing   shelly:shelly25-roller:SHELLY_ID   "Shelly25" @ "Room"     [deviceIp="X.X.X.X"]

However the majority of the shelly25 donā€™t seem to initialize properly (but some from the file work). In the GUI I donā€™t see any channels related to the shutter.

grafik

All devices are mains powered, reachable and use Firmware >= 1.11.
I would have expected that this is not an issue since all devices can directly be queried and they also show ā€œONLINEā€ as a status.
How can I trigger an initialization so my shutters will work again?
Is there any way I can configure the thing in a way that it will always contain the shutter channel?

at the moment it is advisable to physically switch off the server for a moment. That resolved a couple of problems which you cannot solve by restarting OH or the server - especially when you are on 3.4.0 or 3.4.1

What do you mean by that?

Still on 3.3


I think this might be an initialization issue and a bug.
Can I do anything to help - e.g. provide more information?
About 80% of my Shelly device do not work right now.
Iā€™ve configured CoIoT to use unicast

Is there any way to add a configuration to the *.things which will hint at the correct channel configuration? The device is working - itā€™s just the channels on the thing which are missing.

some weeks ago i had the same issue at my two shellys: after a reboot the thing was online but no channels where connected.

for me the problem solved from alone just by doing several restarts (reboot) rpi with openhabian, nothing else. some days later they suddenly worked again and since then i hab no more problems.

Itā€™s possible to fix the issue by manually removing the *.things file which defines the shellys and then adding it again.
However itā€™s super annoying and imho a critical bug which should be fixed.

1 Like

Hello!

Iā€™ve been using Shelly binding since the beginning. I have Shelly Duo RGBW Bulb, and it was working without any problems. Yesterday, Iā€™ve updated OpenHAB to the latest version (3.4.1, release branch), and my bulb stop functioning properly.

I donā€™t remember if Iā€™ve initially added it manually, or it was discovered automatically, but the thing type was shelly:shellybulb. I have a switch in OH UI that was able to switch modes between color and white. The switch stopped working, so I tried to delete thing and automatically rediscover it, and it finds it, but shows different thing type (shelly:shellycolorbulb). It wouldnā€™t be a problem, if I had a way to switch modes (color/white), but this type of thing doesnā€™t have Mode channel. I tried to revert back to shelly:shellybulb by adding thing manually, but mode switching still doesnā€™t work.

Any help would be appreciated.

Best regards,
Davor

as written a couple of times above in this thread, switch off your server, i.e. stop oh and shutdown the server. That helped with various problems with 3.4 and 3.4.1

Hello!

Iā€™ve tried disconnecting OH server from power supply, and then connecting it again after a minute or so, but it hasnā€™t solved this problem. Thing type shelly:shellybulb Mode channel still doesnā€™t work (doesnā€™t change from Color to White and vice verse), and thing type shelly:shellycolorbulb still doesnā€™t have Mode channel. Is there another type Iā€™m not aware of, that I should be using for Shelly Duo RGBW Bulb?

Best regards,
Davor

Edit: I forgot to mention that bulb has latest firmware, and I can change from Color to White and vice verse via Shelly interface.

I also have shelly bulb, working perfectly. However, I am on 3.4 M6 and FW 1.11.
And I will definitely stay a while at this levelā€¦
Did you test the latest dev binding from marcus? see link aboveā€¦

Hello!

Iā€™ve tried manually adding org.openhab.binding.shelly-3.4.2-SNAPSHOT.jar (before adding it, Iā€™ve removed Shelly binding via PaperUI), and then shutting down and powering up OH server. In OH console I can see that binding is installed, but not active. In the logs, I get following error:

2023-01-30 17:02:19.132 [WARN ] [org.apache.felix.fileinstall        ] - Error while starting bundle: file:/usr/share/openhab/addons/org.openhab.binding.shelly-3.4.2-SNAPSHOT.jar

org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.shelly [302]

  Unresolved requirement: Import-Package: org.eclipse.californium.core; version="[2.7.0,3.0.0)"

	at org.eclipse.osgi.container.Module.start(Module.java:463) ~[org.eclipse.osgi-3.17.200.jar:?]

	at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:445) ~[org.eclipse.osgi-3.17.200.jar:?]

	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [bundleFile:3.7.4]

	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [bundleFile:3.7.4]

	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1221) [bundleFile:3.7.4]

	at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:515) [bundleFile:3.7.4]

	at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [bundleFile:3.7.4]

	at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [bundleFile:3.7.4]

Thank you in advance.

Best regards,
Davor

Hello!

I forgot to ask, what kind of Shelly Bulb you have? And what thing type is it? Do you have Mode channel to switch between Color and White, or you do it some other way?

Best regards,
Davor

you also need to install californium. On marcus website you find the modules. Shelly binding normally installs this as dependency but here you have to do it manually.

Sorry, I use shelly bulb duo, not bulbā€¦

And today my Shelly Manager stopped working again.
So it would be very interesting to know why.
Maybe one reason is I deleted cache and made a restart of openhab yesterday.

Hello!

Iā€™ve managed to manually install 3.4.0-SNAPSHOT, but I had the same problems as I had with binding installed via PaperUI. On Marcusā€™ github I found 3.1.0-SNAPSHOT of the binding and after installing it, it started working again as it was before OpenHAB update. One other thing Iā€™ve noticed is warning in openhab.log that constantly shows up (with 3.4, as well as with 3.1):

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

It shows 4 warnings every half a minute or so.

Hopefully, someone will find out whatā€™s going on with official (PaperUI) binding, so I can go back to that version again.

Thank you for your help.

Best regards,
Davor

Hello everybody,

shelly has published an new device: Shelly Plus Plug S

It is the successor of the Plug S switch with new functions (messuring and rgb-LED-ring)
I think, there are new channels, which are not supported by the actual binding.

However, as far as I know, the Shelly binding determines the available channels dynamically. Does that mean that such a new device is then automatically recognized or does the binding for the new device have to be extended?

I find the device itself interesting because the colored signaling can also be used for status displays (alarm system or ā€œwindows/doors openā€) and the plug is considerably cheaper than the one from Fibaro, for example.

Thanks, Ralph

Hello,

Since a long time, I have problems with my Shelly Buttons, but now the problem gets massive and renders them all nearly unusable. Hope that someone here can help me:

With Openhab 3.0 everything was fine and the buttons worked great. After installing OH 3.1, the problem started: After a restart of OH, button presses werenā€™t recognized - to be precise, the first two werenā€™t recognized and the third and all following ones worked normal.
Since some time (guessing OH 3.4, maybe earlier), after a restart of OH, all buttons wonā€™t work for a long time, no matter how often I press them etcā€¦ As an example: I tested around yesterday evening, and this morning most of the buttons need to be pressed three times until recognized by OH.

What I found out is, that the buttons seem to normally send their network packages: I sniffed with Wireshark on the machine that runs OH and found that for all button presses I could reliably receive CoAp network packages. I also saw that after a OH restart, the first button press (sometimes?) caused OH to call the /settings endpoint of the Shelly. But after that, any further button press didnā€™t result in any OH reaction. It takes a long time and/or lots of button presses to make OH react to button eventsā€¦

I also tested if I mis-configured something in OH and started a clean installation of OH on my machine. I added just the button thing manually with its IP using UI but no button presses got recognized and the thing stayed in status UNKNOWN.
I repeated the steps on a second PC with the same result.

This is the output from my clean installation:

21:49:32.447 [INFO ] [re.automation.internal.RuleEngineImpl] - Rule engine started.
21:49:58.982 [DEBUG] [.shelly.internal.ShellyHandlerFactory] - Shelly Button 1: Create new thing of type shelly:shellybutton1 using ShellyRelayHandler
21:49:59.025 [DEBUG] [.shelly.internal.ShellyHandlerFactory] - Thing handler for uid shelly:shellybutton1:3a7eb8ed7f added, total things = 1
21:49:59.040 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'shelly:shellybutton1:3a7eb8ed7f' changed from UNINITIALIZED to INITIALIZING
21:50:01.046 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Thing name derived from UID shelly:shellybutton1:3a7eb8ed7f
21:50:01.048 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Using userId admin from bindingConfig
21:50:01.049 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Device config: IP address=192.168.101.194, HTTP user/password=admin/***, update interval=900
21:50:01.051 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Configured Events: Button: false, Switch (on/off): true, Push: true, Roller: true, Sensor: false, CoIoT: true, Enable AutoCoIoT: true
21:50:01.053 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Start initializing for thing Shelly Button 1, type shellybutton1, IP address 192.168.101.194, Gen2: false, CoIoT: true
21:50:01.054 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'shelly:shellybutton1:3a7eb8ed7f' changed from INITIALIZING to UNKNOWN (CONFIGURATION_PENDING): Initializing or device in sleep mode.
--Button pressed--
21:50:16.070 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Unable to initialize: API Timeout for GET http://192.168.101.194/shelly, retrying later
21:50:16.074 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Update status job started, interval=300*3=900sec.
--Button pressed 2x--
--Shelly Button connnected to USB--
--Setting status interval query time to 60s in UI--
21:52:16.874 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Stopping Thing
21:52:16.875 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Shutting down
21:52:16.877 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Shelly statusJob stopped
21:52:16.881 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Thing config updated, re-initialize
21:52:18.882 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Thing name derived from UID shelly:shellybutton1:3a7eb8ed7f
21:52:18.884 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Using userId admin from bindingConfig
21:52:18.886 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Device config: IP address=192.168.101.194, HTTP user/password=admin/***, update interval=60
21:52:18.889 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Configured Events: Button: false, Switch (on/off): true, Push: true, Roller: true, Sensor: false, CoIoT: true, Enable AutoCoIoT: true
21:52:18.891 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Start initializing for thing Shelly Button 1, type shellybutton1, IP address 192.168.101.194, Gen2: false, CoIoT: true
21:52:18.896 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f: Starting CoAP Listener
21:52:18.898 [DEBUG] [helly.internal.api1.Shelly1CoapServer] - Initializing CoIoT listener (local IP=10.244.235.192:5683)
21:52:26.053 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f: Using CoAP device description from successful HTTP /cit/d
21:52:26.054 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f: CoIoT Device Description for shellybutton1-3a7eb8ed7f: {"blk":[{"I":1,"D":"sensor_0"},{"I":2,"D":"device"}],"sen":[{"I":9103,"T":"EVC","D":"cfgChanged","R":"U16","L":2},{"I":2102,"T":"EV","D":"inputEvent","R":["S/L/SS/SSS",""],"L":1},{"I":2103,"T":"EVC","D":"inputEventCnt","R":"U16","L":1},{"I":3115,"T":"S","D":"sensorError","R":"0/1","L":1},{"I":3112,"T":"S","D":"charger","R":["0/1","-1"],"L":2},{"I":3111,"T":"B","D":"battery","R":["0/100","-1"],"L":2},{"I":9102,"T":"EV","D":"wakeupEvent","R":["battery/button/periodic/poweron/sensor/ext_power","unknown"],"L":2}]}
21:52:26.056 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f:    id=1: sensor_0
21:52:26.057 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f:    id=2: device
21:52:26.060 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f: Adding 7 sensor definitions
21:52:26.061 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f:    id 9103: cfgChanged, Type=EVC, Range=U16, Links=2
21:52:26.062 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f:    id 2102: inputEvent, Type=EV, Range=S/L/SS/SSS;, Links=1
21:52:26.062 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f:    id 2103: inputEventCnt, Type=EVC, Range=U16, Links=1
21:52:26.063 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f:    id 3115: sensorError, Type=S, Range=0/1, Links=1
21:52:26.064 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f:    id 3112: charger, Type=S, Range=0/1;-1, Links=2
21:52:26.065 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f:    id 3111: battery, Type=B, Range=0/100;-1, Links=2
21:52:26.066 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f:    id 9102: wakeupEvent, Type=EV, Range=battery/button/periodic/poweron/sensor/ext_power;unknown, Links=2
21:52:26.194 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Auto-CoIoT is enabled, disabling action urls
21:52:26.195 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Starting CoIoT (autoCoIoT=true/true)
21:52:26.196 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f: Stopping CoAP Listener
21:52:26.197 [DEBUG] [helly.internal.api1.Shelly1CoapServer] - CoAP Listener stopped
21:52:26.198 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f: Starting CoAP Listener
21:52:26.199 [DEBUG] [helly.internal.api1.Shelly1CoapServer] - Initializing CoIoT listener (local IP=10.244.235.192:5683)
21:52:26.225 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f: Using CoAP device description from successful HTTP /cit/d
21:52:26.226 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f: CoIoT Device Description for shellybutton1-3a7eb8ed7f: {"blk":[{"I":1,"D":"sensor_0"},{"I":2,"D":"device"}],"sen":[{"I":9103,"T":"EVC","D":"cfgChanged","R":"U16","L":2},{"I":2102,"T":"EV","D":"inputEvent","R":["S/L/SS/SSS",""],"L":1},{"I":2103,"T":"EVC","D":"inputEventCnt","R":"U16","L":1},{"I":3115,"T":"S","D":"sensorError","R":"0/1","L":1},{"I":3112,"T":"S","D":"charger","R":["0/1","-1"],"L":2},{"I":3111,"T":"B","D":"battery","R":["0/100","-1"],"L":2},{"I":9102,"T":"EV","D":"wakeupEvent","R":["battery/button/periodic/poweron/sensor/ext_power","unknown"],"L":2}]}
21:52:26.228 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f:    id=1: sensor_0
21:52:26.230 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f:    id=2: device
21:52:26.231 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f: Adding 7 sensor definitions
21:52:26.232 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f:    id 9103: cfgChanged, Type=EVC, Range=U16, Links=2
21:52:26.234 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f:    id 2102: inputEvent, Type=EV, Range=S/L/SS/SSS;, Links=1
21:52:26.235 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f:    id 2103: inputEventCnt, Type=EVC, Range=U16, Links=1
21:52:26.236 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f:    id 3115: sensorError, Type=S, Range=0/1, Links=1
21:52:26.236 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f:    id 3112: charger, Type=S, Range=0/1;-1, Links=2
21:52:26.237 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f:    id 3111: battery, Type=B, Range=0/100;-1, Links=2
21:52:26.237 [DEBUG] [elly.internal.api1.Shelly1CoapHandler] - shellybutton1-3a7eb8ed7f:    id 9102: wakeupEvent, Type=EV, Range=battery/button/periodic/poweron/sensor/ext_power;unknown, Links=2
21:52:26.238 [DEBUG] [g.shelly.internal.api1.Shelly1HttpApi] - shellybutton1-3a7eb8ed7f: Set Sensor Reporting URL
21:52:26.241 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Updating channel definitions, 4 channels
21:52:26.242 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Adding channel device#deviceName
21:52:26.243 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Adding channel device#updateAvailable
21:52:26.245 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Adding channel device#heartBeat
21:52:26.246 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Adding channel device#statusLed
21:52:26.251 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Channel definitions updated
21:52:26.257 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Initializing device shellybutton1-3c6105f44d2d, type SHBTN-2, Hardware: Rev: prod-2020-10, batch 1; Firmware: v1.12.1-ga9117d3 / 20221027-094830
21:52:26.258 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Shelly settings info for shellybutton1-3c6105f44d2d: {"device":{"type":"SHBTN-2","mac":"3C6105F44D2D","hostname":"shellybutton1-3C6105F44D2D","sleep_mode":true},"wifi_ap":{"enabled":false,"ssid":"shellybutton1-3C6105F44D2D","key":""},"wifi_sta":{"enabled":true,"ssid":"Link","ipv4_method":"static","ip":"192.168.101.194","gw":"192.168.101.22","mask":"255.255.255.0","dns":"192.168.101.22"},"wifi_sta1":{"enabled":false,"ssid":null,"ipv4_method":"dhcp","ip":null,"gw":null,"mask":null,"dns":null},"mqtt": {"enable":false,"server":"192.168.33.3:1883","user":"","id":"shellybutton1-3C6105F44D2D","reconnect_timeout_max":60.000000,"reconnect_timeout_min":2.000000,"clean_session":true,"keep_alive":60,"max_qos":0,"retain":false,"update_period":30},"coiot": {"enabled":true,"update_period":15,"peer":""},"sntp":{"server":"time.google.com","enabled":false},"login":{"enabled":false,"unprotected":false,"username":"admin"},"pin_code":"","name":"multimedia-button.wohnzimmer.i","fw":"20221027-094830/v1.12.1-ga9117d3","discoverable":true,"build_info":{"build_id":"20221027-094830/v1.12.1-ga9117d3","build_timestamp":"2022-10-27T09:48:30Z","build_version":"1.0"},"cloud":{"enabled":false,"connected":false},"timezone":null,"lat":500.000000,"lng":500.000000,"tzautodetect":true,"tz_utc_offset":0,"tz_dst":false,"tz_dst_auto":true,"time":"","unixtime":0,"led_status_disable":false,"debug_enable":false,"allow_cross_origin":false,"actions":{"active":false,"names":["shortpush_url","longpush_url","double_shortpush_url","triple_shortpush_url"]},"hwinfo":{"hw_revision":"prod-2020-10","batch_id":1},"sleep_mode":{"period":12,"unit":"h"},"led_status_disable":false,"longpush_duration_ms":{"max":800},"multipush_time_between_pushes_ms":{"max":500},"remain_awake":0,"inputs":[{"name":null}]}
21:52:26.259 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Device hasRelays:false (numRelays=0),isRoller:false (numRoller=0),isDimmer:false,numMeter=0,isEMeter:false), ext. Switch Add-On: n/a,isSensor:true,isDS:false,hasBattery:true (low battery threshold=20%),isSense:false,isMotion:false,isLight:false,isBulb:false,isDuo:false,isRGBW2:false,inColor:false,alwaysOn:false, updatePeriod:43260sec
21:52:26.260 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Thing successfully initialized.
21:52:26.268 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Update status job started, interval=20*3=60sec.
21:52:26.270 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'shelly:shellybutton1:3a7eb8ed7f' changed from UNKNOWN (CONFIGURATION_PENDING): Initializing or device in sleep mode. to ONLINE
21:52:28.359 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Updating channel definitions, 4 channels
21:52:28.362 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Adding channel status#input
21:52:28.364 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Adding channel status#button
21:52:28.366 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Adding channel status#lastEvent
21:52:28.368 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Adding channel status#eventCount
21:52:28.377 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Channel definitions updated
21:52:28.409 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Updating channel definitions, 6 channels
21:52:28.410 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Adding channel device#charger
21:52:28.412 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Adding channel battery#batteryLevel
21:52:28.414 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Adding channel battery#lowBattery
21:52:28.415 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Adding channel sensors#lastError
21:52:28.416 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Adding channel device#wakeupReason
21:52:28.417 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Adding channel status#lastUpdate
21:52:28.422 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Channel definitions updated
21:52:28.424 [DEBUG] [ly.internal.handler.ShellyBaseHandler] - shellybutton1-3a7eb8ed7f: Event filtered: EXT_POWER

I donā€™t know if it was coincidence, but I saw the following message in the log on my production machine after the first button press that was recognized by OH:

coap Exchange[L2241] with manual token overrides existing Exchange[L2111] with open request: KeyToken

I am running OH inside a Docker container with --net host with openhab/openhab:latest, currently v3.4.1 . All Shelly Buttons run latest firmware v1.12.1-ga9117d3 and have a static IP configured. All devices are in same subnet. The problem is present for buttons that I own for about 2 years and for buttons that I recently bought and integrated into OH.

I would be thankful for any hint what I could do to track this down.

Thanks, Andreas

Edit: Note that the problem is limited to Shelly Buttons; other battery-powered Shelly devices like e.g. DW2 work as expected.

Hey Andreas,
I might be in the same boat as you, but havent had time for extensive testing.
I have a shelly1 connected to my doorbell so that the shelly sends the Button press and oh knows the doorbell rang. Since a few weeks this doesnt work any longer.
Since i also moved to a docker setup with own dedicated IP, im not sure if it was an Update or the move to Docker.
I set the Shelly to unicast by IP and Port. The only thing i noticed when entering the docker Container, that i was not able to list the listening Port where OH is set to receive the COAPs.
ā€œNetstat -tulpn pipe grep Portā€ should have found a Java process and Listening Port on the interface IP at least, i guess.

But yeah, i havent had time to troubleshoot in more detail.
Best

@davorf Usually you could ignore this message or turn on DEBUG log and provide an extract to locate the state. Make sure to use the matching version. If you are on 3.4.2 use the version coming with the Dist.

@RalphSester As mentioned Iā€™ll look into that shortly. I already have a Plus Plug S and a Smoke available.

@atetzner @waitz_sebastian I think you are right. The binding shouldnā€™t call /shelly and /settings for battery powered devices once they were initially added. The device could already returned to sleep mode and is no longer accessible.

Did I forgot to respond to an open issue?

1 Like