Shelly Binding

violine · February 19, 2020, 5:39pm

Hello, here is the information you want.
Thanks for your great commitment!
settings.json (1.7 KB) status.json (891 Bytes)

Nuno_Conceicao · February 20, 2020, 12:33am

Hi Markus
I also recently got my Shelly 3em.
I’m available for testing the binding though, if possible on OH 2.4

Cheers

Nuno

markus7017 · February 20, 2020, 6:46am

ok, let‘s see what I could prepare by mid next week
thx

markus7017 · February 22, 2020, 9:47am

fyi: the lastest 2.5.5 distro also contains my PR 6764 even this was not mentioned the the release notes

Chris_si · February 22, 2020, 12:51pm

Unfortunately the ‘next few days’ were a bit longer than anticipated, sry for that.

Today I tried the latest build (from about six days ago) I could find in your repository in combination with my RGBW2s. I tried controlling them with both coap enabled and coap disabled. In both cases I get the same timeout messages as before.

Also there are no button and relay events and action urls enabled since the RGBW2 is not supporting those as far as I know.

Mario_Aerni · February 22, 2020, 2:14pm

Hi,
I think he means - as he saids - the Thing config.
There you have an attribute, called eventsCoIoT. You have to set it to eventsCoIoT=true

E.g.

Thing shelly:shellyrgbw2:12345                     	"Shelly RGBW 12345" 	[deviceIp="192.168.2.xxx", userId="xxx", password="xxx", eventsButton=false, eventsSwitch=false, eventsCoIoT=true]

CoIoT is always enabled in the shelly. You don’t have to enable or disable it in the WebApp, but you can enable or disable it in your Openhab Thing-Config.

In the WebApp of your RGBW2 you just have to clear the Action URLs.
Hope that helps a bit.

Cheers
Mario

Chris_si · February 22, 2020, 6:20pm

The Shelly RGBW2s don’t have action URLs implemented in the current firmware (v1.5.7).
With ‘coap enabled/disabled’ I meant setting ‘eventsCoIoT=true/false’ in the things config file.

markus7017 · February 26, 2020, 6:41am

fyi:

I added support for the ext temp sensors of Shelly 1/1PM (for now the additional channels are static and become N/A when the temp sensors are not installed. I’ll change this to dynamic creation of channels. thanks @hmerk for testing
Next will be Shelly Duo, testing with @igi
Basic info for EM3 is above, testing with @RolfV, @violine
@jcosta46 I just received an EM for testing and will look into the totalEnergy problem
@javaboon Did you tried the build with the build I provided?

markus7017 · February 26, 2020, 11:04pm

@RolfV, @violine first build for EM3 is ready to test
https://github.com/markus7017/myfiles/blob/master/shelly/org.openhab.binding.shelly-2.5.2-SNAPSHOT.jar?raw=true

violine · February 27, 2020, 12:57am

Hi Markus,
great! Thank you!
I updated the binding. It works!
In the appendix I have given the physical names and their units as examples for 1 phase.
Maybe you want to change that?

Look at the status output and the output in the PaperUI. Not all values are output.

markus7017 · February 28, 2020, 7:51am

@violine ok, will have a look to that

general: please don’t use the version in the repo for know, I inform here when problem is fixed

markus7017 · February 29, 2020, 11:39am

fyi: problem is fixed, dev build ok

external temp sensors for 1/1PM are now supported

does someone has a Shelly Door Window and could help with testing?

marian.tudor · February 29, 2020, 5:41pm

Hello Markus,
I’m counting the same problem described by @dilisi. Shortly I got the “UNINITIALIZED” status for Shely HT sensors after system (RPI) reboot and the OH will not receive sensor’s updates . You can find details in my last post on the community:
Unknown status for Shelly H&T Sensor after reboot.
I found until now that if I’ll restart the OH2 service after a system reboot, the define ShellyThings will change the state in “ONLINE”. But If I will again restart the OH2 service the state will again become “UNKNOWN” and I received the following error:

2020-02-29 20:34:42.145 [hingStatusInfoChangedEvent] - ‘shelly:shellyht:f2b672’ changed from INITIALIZING to UNKNOWN

2020-02-29 20:34:42.156 [hingStatusInfoChangedEvent] - ‘shelly:shellyht:f2b670’ changed from INITIALIZING to UNKNOWN

==> /var/log/openhab2/openhab.log <==

2020-02-29 20:34:47.322 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:

java.lang.NullPointerException: null

at org.openhab.binding.shelly.internal.handler.ShellyBaseHandler.authorizationFailed(ShellyBaseHandler.java:616) ~[?:?]

at org.openhab.binding.shelly.internal.handler.ShellyBaseHandler.lambda$0(ShellyBaseHandler.java:134) ~[?:?]

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_222]

at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_222]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) ~[?:1.8.0_222]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) ~[?:1.8.0_222]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_222]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_222]

at java.lang.Thread.run(Thread.java:748) [?:1.8.0_222]

Please let me know if I should use your developed builds (The official 2.5 SNAPSHOT build or your private 2.5 DEV build ) considering that I’m using now openHAB 2.5.1-2 (Release Build). Please let me know how to proceed next…

Thank you in advance!

markus7017 · February 29, 2020, 7:00pm

yes, please the the dev build
is the device password protected?

marian.tudor · February 29, 2020, 7:07pm

Thank you for your prompt respond.
the device is with password protected. The password and user ID that I configure in the sensor WEB API (Internet & Security - > RESTRICT LOGIN ) I’m using inside of Shelly Binding Configuration and also for ShellyThings.

markus7017 · February 29, 2020, 11:00pm

please provide a TRACE Log with the latest DEV build

violine · February 29, 2020, 11:04pm

Hi Markus,
Do you mean the problem with the 3EM?

markus7017 · March 1, 2020, 7:46am

Nope, for the HT issue above

but I already integrated the missing channels for EM3, will upload a new version later

markus7017 · March 1, 2020, 7:52am

In general:

If the device is in sleep mode there is no way to make it up (AFAIK, also no Wake-on-LAN)
the thing will state in state UNKNOWN until the device wakes up and can be initialized - that’s normal
even the device is in sleep mode and OH is restarted: that changes nothing to the device status, so it still remembers the IP address of the listener
a new event if triggered when the device wakes-up and send to the listener (http callback and/or CoIoT packet)
this is received by the binding and triggers an auto-initialization, you should see that in the log
once initialized the thing goes ONLINE

If that does not work for you or @dilisi I need a TRACE log showing initialization, restart and next device wakeup/event

dilisi · March 1, 2020, 8:22am

My described problem has already been fixed (Shelly Binding). I also have no problem with the openHAB 2.5.1-2 (Release Build).