I updated the DEV build and keep the warning, but removed disabling CoIoT by default. Maybe there are good reasons for a setup like that (like your’s). You need to update to the latest DEV build.
I installed 2.5.13, but I get the same issue: the updateInterval doesn’t do anything
I even reinstalled openhab completely, so the thing is completely new.
I will test the 3.0 version in my test 3.x setup later today.
I have several docker container running on my synology and I found the warnings from the browsers annoying, when going to the pages with http.
Also I found the different ports from the different services annoying.
So I decided to start a container with traefik reverse proxy, so I could reach all services with https (traefik manages the certificates) and on the same port.
The only thing is, that this construct only works with dns-names and not with ip-adresses, when connecting over traefik.
I updated the DEV build and keep the warning, but removed disabling CoIoT by default. Maybe there are good reasons for a setup like that (like your’s). You need to update to the latest DEV build.
Thanks a lot.
I will give it a try at the weekend.
In openHAB 3, it’s working fine!.. very strange, because I didn’t changed anything on my 2.5 setup.
I also tried the DEV version first (I want to connect my UNI), but I get an error when putting the .jar file (I first stoped OH, added californium-core-2.0.0 & element-connector-2.0.0 and started OH again without errors):
2021-04-13 17:53:30.296 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/openhab/addons/org.openhab.binding.shelly-3.1.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.shelly [291]
Unresolved requirement: Import-Package: org.osgi.framework; version=“[1.9.0,2.0.0)”
at org.eclipse.osgi.container.Module.start(Module.java:444) ~[org.eclipse.osgi-3.12.100.jar:?]
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) ~[org.eclipse.osgi-3.12.100.jar:?]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:520) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [bundleFile:3.6.4]
My OH3 setup is running on Docker, my 2.5 setup on a Pi.
They are working on updating the core components of the framework, in fact Karaf with OSGi. That means even I didn’t changed my code the build environment puts in dependencies on newer component versions than 3.0/3.1M1…3 have. Let me try to work around. Switching back to an older build environment should fix that issue, but I need to think of a proper way to keep backward compatibility. Having 3 versions (2.5.x, 3.0 and 3.1 latest) is no option.
Well, 3.0 build hopefully will not be needed anymore, after OH 3.1 stable release. Till then, temporary building of shelly binding in 3.0.x environment should be solution?
Damn should have come here first. Have the same error as well, after updating a friend’s installation to test issues with another binding. I suspected cache problems and cleaned out all bindings and cache, then added them again. Didn’t help. But if it’s a general 3.1m3 problem, I’ll just wait. Or is there an older version I could fall back to?
2021-04-15 22:12:14.593 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/usr/share/openhab/addons/org.openhab.binding.shelly-3.1.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.shelly [208]
Unresolved requirement: Import-Package: org.osgi.framework; version="[1.9.0,2.0.0)"
at org.eclipse.osgi.container.Module.start(Module.java:444) ~[org.eclipse.osgi-3.12.100.jar:?]
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) ~[org.eclipse.osgi-3.12.100.jar:?]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:520) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [bundleFile:3.6.4]
2021-04-15 23:49:49.207 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/usr/share/openhab/addons/org.openhab.binding.shelly-3.1.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.shelly [208]
Unresolved requirement: Import-Package: org.osgi.framework; version="[1.9.0,2.0.0)"
at org.eclipse.osgi.container.Module.start(Module.java:444) ~[org.eclipse.osgi-3.12.100.jar:?]
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) ~[org.eclipse.osgi-3.12.100.jar:?]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:520) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [bundleFile:3.6.4]
Yes, as Daniel said, still indeed the same error with 3.1.0.202104061052 build of binding.
Just let me add that my version of OH is a stable release build 3.0.1. May be upgrade to 3.1.0.M3 is needed?
Anyone know why the RGBW2 (COLOR MODE) channel description is gone from the official Shelly Binding page on OH website now? I see White mode, but no color mode any longer…
Which is correct as per the “V2” binding page, but nothing happens with that channel. When i send an ON or OFF command, i see in the log:
2021-04-17 21:15:03.752 [ome.event.ItemCommandEvent] - Item 'play_strip_sw' received command ON
2021-04-17 21:15:03.760 [nt.ItemStatePredictedEvent] - play_strip_sw predicted to become NULL
I’m using DEV build 2.5.13 . Any suggests on what i’m doing wrong here
Cheers!
Please try the latest DEV build. It should create a channel control#power. Maybe you need to delete and re-discover the thing. Please try first within PaperUI before defining in the .things file.
You should see a message “Switch light xx” (ON/OFF) in the log if you enable DEBUG, You’ll also find the link to the matching README below.
Was having some problems with the motion sensor not responding again, but after a factory reset it seems to work again for now. Since the internal webserver wasn’t reachable either, this has to be something else.
Good morning together,
I tried figuring out my issue by cross reading this thread, but didn’t find a solution yet.
Any quick approach for my issue would be highly appreciated.
Here is my setup:
Raspberry with Openhab 3.
Shelly Binding 3.0.1, yesterday switched to latest DEV 3.1.
Different Shelly’s in use, one of them in detached mode.
Shellys with each newest firmware.
Issue:
I’m using the input#relay or last event channels to control some lights. That was working for me over the last months with small delays (<2sec.).
Since 2 days, the delay until Openhab receives input relay status increased to roughly 10-20 seconds.
No changes to the setup were made.
I yesterday tried to install the DEV built and I factory reset yes the Shelly 1. I ensured coloT with mcast being activated.
Autodiscovery doesn’t work, shellys are recognized by manual adding over IP.
The delay remains after installing new binding and factory reset.
Any idea what to try next?
Might there be some data to delete on the raspberry (cache files,…) from the binding?
Controlling the shellys over Openhab works flawlessly and with no delay.
Highly appreciate your answers,
Best wishes, Christian