Create special device (shelly-protected) when device is password protected
CoIoT/COAP support added (experimental, needs to be activated in thing config)
channel name meter.totalWatts changed to meter.totalKWH (returns kw/h, not Watts)
Roller: re-added OnOffType (so you could send OPEN or ON / CLOSE or OFF / STOP)
RGBW2: adjust numMeter (doesn’t report this as part of the device property) -> work around for meter.Watts missing
Sense: read IR code list for Sense from device rather than hard coded list
fixed update scheduling on exceptions (e.g. HT not reachable)
Activation of Channel Cache is delayed for 60s to make sure that Persinstence restore is already done
logging revised (include device name on most logs), more details about the bundle on startup
I’m going to close this release shortly. Let me know if you are aware of issues or have a small feature request.
This will be 2.4.2. After that I start re-factoring and get ready for PR submission. OH 2.5 will be release in December, I try to make it into this release.
Unfortunately I had an issue trying to install the most recent shelly binding causing in an error of my existing config. All Z-wave devices got UNINITIALIZED after adding the shelly…jar manual installation procedure.
The Z-Wave binding is also a manually installed binding: org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar
It took a while to get it back repaired with the following through Karaf:
feature:install openhab-transport-serial
After reboot, the Z-Wave Binding worked again as expected!
Hope this helps for troubleshooting. I will use the shelly’s 2.5 with MQTT until the binding is ready.
I‘m pretty sure that this was a side effect from another action,. I also run zwave and Shelly in parallel. Shelly doesn‘t deal with serial connections nor install/uninstalls any features or other modules/files. Maybe a cache problem?
I was emptying the cache and temp folders before and I also have stopped the openhab2 instance… Maybe some other hints how to try again adding the binding?
sounds good, please provide the log so I could check what sensors 118 and 128 are or go to the thing ptoperties and copy the coapDeviceDescriptiom here
delete the Shelly things
stop OH
delete old version from addons folder
clean cache
copy snapshot build to addons folder
start OH and wait until everything is initialized
run thing discovery from Inbox
Ps always the same flood of update events (might disapears in final revision)
thx for your great work again
I tried another run with the way you have proposed…
Again all Z-Wave things moved to uninitialised and I have fixed it with:
feature:install openhab-transport-serial
OH has discovered the Shelly 2.5 in Rollershutter mode but it is still not initialised:
Shellyswitch25-xxxxx - OFFLINE-COMMUNICATION_ERROR
and more detailed:
Status: OFFLINE - COMMUNICATION_ERROR Shelly API call failed on url=http://192.168.0.91/settings, response=ERROR: java.util.concurrent.TimeoutException: Total timeout 2500 ms elapsed - class java.io.IOException
Also the logs are flooded with the following every three seconds:
I have no vlue what causes that problem. I‘m still on 2.4 and run Shelly and zwave in parallel without any issues
really the complete sequence? yes, I still need to change the level for sone messages, but you should see the initialization sequence only once per thing, othetwisr something is wrong in your setup