Shelly Binding

STSC · January 4, 2023, 7:09am

I’m getting this error since upgrading to OH3.4:
Handler ShellyRelayHandler tried updating the thing status although the handler was already disposed.

Does setting the log level to ERROR solve the issue or does readding all Shelly devices help?

Baschtlwaschtl · January 4, 2023, 2:25pm

Thx, good idea.
I did the upgrade with build in binding.

Baschtlwaschtl · January 4, 2023, 2:29pm

I had this too. After rebooting the openhab machine no errors in the log…

Larsen · January 4, 2023, 2:31pm

The error log doesn’t solve the problem, it only shows more detailled information.
In my case after deinstalling the binding, cleaning cache and reinstalling those messages disappered. Maybe I re-created the things too.

STSC · January 4, 2023, 2:49pm

Removing seems not to work. Now my Shelly device says “REMOVING”, but nothing happens and it is still there.

STSC · January 4, 2023, 2:56pm

It seems that I can only remove an online Shelly device. If it is offline I need to do a force remove.

markus7017 · January 7, 2023, 7:03pm

No, REMOVING indicates that the biding serving the thing is not active. Just click Remove again and the thing gets hard deleted.

Larsen · January 7, 2023, 11:11pm

One info regarding the ShellyRelayHandler-problem. You have to completely reboot the server. Just restarting openhab is not enough.

markus7017 · January 9, 2023, 4:46am

I updated the DEV build to include support Shelly Plus Wall Dimmer US. Pro 3EM gets discovered too, but is WIP.

org.openhab.binding.shelly-3.4.2-SNAPSHOT.jar
org.openhab.binding.shelly-4.0.0-SNAPSHOT.jar

Matthias_Kaufmann · January 9, 2023, 9:34am

Thanks for the 3.4.2 release. Is there anything fixed within that release regarding correct roller shutter position control with Shelly 2.5?

Update: I tried to install it but in the console I get an error:

294 │ Installed │  80 │ 3.4.2.202301090432     │ openHAB Add-ons :: Bundles :: Shelly Binding Gen1+2
openhab> bundle:restart 294
Error executing command: Error restarting bundles:
        Unable to start bundle 294: Could not resolve module: org.openhab.binding.shelly [294]
  Unresolved requirement: Import-Package: org.eclipse.californium.core; version="[2.7.0,3.0.0)"

Thanks!

markus7017 · January 9, 2023, 12:48pm

Check the notes, you need to

uninstall the version coming with the official dist (from the UI)
run “feature:install openhab-transport-coap” on the OH console
copy the jar into the addons folder

markus7017 · January 9, 2023, 12:52pm

Are always the same TRVs affected? or randomly?

Turn on the DEBUG log:

open OH console
“log:set DEBUG org.openhab.binding.shelly”

extract the proper sequence. This shows communication on the thing level. If you want to see complete API interaction you could also use TRACE.

markus7017 · January 9, 2023, 12:56pm

Check the device UI to verify that the Outbound Web Socket is enabled and the URL points to you OH system. This should be done automatically when initializing the device by the binding. Turn on DEBUG log (see above) and check if the event is posted to the log when you wakeup the Plus HT.

Do you have a “raw” installation or are you running OH in a Docker container? The will be an inbound http/ws request to the port you are running OH (usually 8080).

goligo · January 9, 2023, 1:07pm

Thanks for your reply, I have upgraded to OpenHAB 3.4.0 in the meantime, which did cause some other issues due to changes in the TRV handling, but I haven’t experienced any failed updates since.

To answer your question: It was randomly, between 2 and 5 out of the 17 TRVs didn’t change their profile, when changing the group state.

Garbisa · January 9, 2023, 4:39pm

Hi Markus
The ourbound web socket is configured correct:

Garbisa · January 9, 2023, 4:42pm

…
ws://10.0.yy.xx:8083/shelly/wsevent
I also changed to “TLS no validation” for testing.

The debug log shows no message when I wakeup the device. But I found at least one message:
"discovery.ShellyDiscoveryParticipant] - ServiceInfo [ServiceInfoImpl@1556540618 name: ‘ShellyPlusHT-C049EF8AF6CC._http._tcp.local.’ address: ‘(null):80’ status: ‘DNS: Master01-xxxx.local. [Master01.xxxxx.local/10.0.yy.xx] state: probing 1 task: null’, has NO data, empty]

Garbisa · January 9, 2023, 4:49pm

After some minutes I had some more message:
shellyplusht-c049ef8af6cc: Status update triggered thing initialization
shellyplusht-c049ef8af6cc: Start initializing for thing ShellyTE01, type shellyplusht, IP address 10.0.xx.yyy, Gen2: true, CoIoT: false
shellyplusht-c049ef8af6cc: Ignore API Timeout, retry later

markus7017 · January 9, 2023, 7:13pm

hmm, maybe the binding tries to do an API call to get some device config, which will fail, because already went back to sleep mode. Please provide a TRACE log of this situation

Garbisa · January 10, 2023, 7:54am

Here the trace: (repeated every 15Min)

2023-01-10 08:27:41.684 [DEBUG] [y.internal.handler.ShellyBaseHandler] - shellyplusht-c049ef8af6cc: Status update triggered thing initialization
2023-01-10 08:27:41.684 [DEBUG] [y.internal.handler.ShellyBaseHandler] - shellyplusht-c049ef8af6cc: Start initializing for thing ShellyTE01, type shellyplusht, IP address 10.0.xx.yyy, Gen2: true, CoIoT: false
2023-01-10 08:27:41.684 [TRACE] [shelly.internal.api.ShellyHttpClient] - shellyplusht-c049ef8af6cc: HTTP GET for http://10.0.xx.yyy/shelly

scheuerer · January 10, 2023, 8:58am

I have updated yesterday from 3.4.0. to 3.4.1.
Where I can see the changelog from the Shelly addon?
I have had to recreate my TRV, otherwise it was not more display some values.
What else I need to look on it?

BR
Jochen