Shelly Binding

Baschtlwaschtl · September 22, 2020, 5:15pm

I just proved it again
Immediately after initializing, it works for a short time.
After that, the error occurs again

markus7017 · September 22, 2020, 7:51pm

Deinstall Tradi & Shelly binding, restart OH, install Shelly binding 2.5.9 in PaperUI

Baschtlwaschtl · September 22, 2020, 7:53pm

Will my tradfri configuration be retained or deleted?

markus7017 · September 22, 2020, 8:30pm

if will be restored when you reinstall the binding and re-discover the things

peter_demus · September 22, 2020, 8:44pm

Hello Markus,

using SHELLY EM3 for photovoltage measurements

using OH 2.5.7 and shelly binding 2.5.9 snapshot 2020-09-06

i’m missing the overall total energy [kwH] - i’ve got overall accumulated returned energy …

2020-09-13 19:05:01.605 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: CoIoT Message from /192.168.42.115:5683 (MID=12946): {“G”:[[0,9103,8],[0,1101,0],[0,4105,0.00],[0,4106,168.9],[0,4107,0.0],[0,4108,231.47],[0,4109,0.31],[0,4110,-0.00],[0,4205,-2.45],[0,4206,169.2],[0,4207,5.8],[0,4208,232.11],[0,4209,0.32],[0,4210,-0.03],[0,4305,0.00],[0,4306,170.5],[0,4307,1.6],[0,4308,231.26],[0,4309,0.32],[0,4310,-0.01],[0,6102,0]]}
2020-09-13 19:05:01.606 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: CoIoT Sensor data {“G”:[[0,9103,8],[0,1101,0],[0,4105,0.00],[0,4106,168.9],[0,4107,0.0],[0,4108,231.47],[0,4109,0.31],[0,4110,-0.00],[0,4205,-2.45],[0,4206,169.2],[0,4207,5.8],[0,4208,232.11],[0,4209,0.32],[0,4210,-0.03],[0,4305,0.00],[0,4306,170.5],[0,4307,1.6],[0,4308,231.26],[0,4309,0.32],[0,4310,-0.01],[0,6102,0]]} (serial=24320)
2020-09-13 19:05:01.607 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: 21 CoAP sensor updates received
2020-09-13 19:05:01.608 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[0]: id=9103, Value=8.0 (cfgChanged, Type=EVC, Range=U16, Link=5: device)
2020-09-13 19:05:01.608 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[1]: id=1101, Value=0.0 (output, Type=S, Range=0/1, Link=1: relay_0)
2020-09-13 19:05:01.609 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[2]: id=4105, Value=0.0 (power, Type=P, Range=0/31800;-1, Link=2: emeter_0)
2020-09-13 19:05:01.609 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[3]: id=4106, Value=168.9 (energy, Type=E, Range=U32;-1, Link=2: emeter_0)
2020-09-13 19:05:01.610 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[4]: id=4107, Value=0.0 (energyReturned, Type=E, Range=U32;-1, Link=2: emeter_0)
2020-09-13 19:05:01.611 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[5]: id=4108, Value=231.47 (voltage, Type=V, Range=0/265;-1, Link=2: emeter_0)
2020-09-13 19:05:01.612 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[6]: id=4109, Value=0.31 (current, Type=I, Range=0/120;-1, Link=2: emeter_0)
2020-09-13 19:05:01.613 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[7]: id=4110, Value=-0.0 (powerFactor, Type=S, Range=0/1;-1, Link=2: emeter_0)
2020-09-13 19:05:01.614 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[8]: id=4205, Value=-2.45 (power, Type=P, Range=0/31800;-1, Link=3: emeter_1)
2020-09-13 19:05:01.614 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[9]: id=4206, Value=169.2 (energy, Type=E, Range=U32;-1, Link=3: emeter_1)
2020-09-13 19:05:01.615 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[10]: id=4207, Value=5.8 (energyReturned, Type=E, Range=U32;-1, Link=3: emeter_1)
2020-09-13 19:05:01.616 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[11]: id=4208, Value=232.11 (voltage, Type=V, Range=0/265;-1, Link=3: emeter_1)
2020-09-13 19:05:01.617 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[12]: id=4209, Value=0.32 (current, Type=I, Range=0/120;-1, Link=3: emeter_1)
2020-09-13 19:05:01.617 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[13]: id=4210, Value=-0.03 (powerFactor, Type=S, Range=0/1;-1, Link=3: emeter_1)
2020-09-13 19:05:01.618 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[14]: id=4305, Value=0.0 (power, Type=P, Range=0/31800;-1, Link=4: emeter_2)
2020-09-13 19:05:01.618 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[15]: id=4306, Value=170.5 (energy, Type=E, Range=U32;-1, Link=4: emeter_2)
2020-09-13 19:05:01.619 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[16]: id=4307, Value=1.6 (energyReturned, Type=E, Range=U32;-1, Link=4: emeter_2)
2020-09-13 19:05:01.620 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[17]: id=4308, Value=231.26 (voltage, Type=V, Range=0/265;-1, Link=4: emeter_2)
2020-09-13 19:05:01.621 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[18]: id=4309, Value=0.32 (current, Type=I, Range=0/120;-1, Link=4: emeter_2)
2020-09-13 19:05:01.621 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[19]: id=4310, Value=-0.01 (powerFactor, Type=S, Range=0/1;-1, Link=4: emeter_2)
2020-09-13 19:05:01.622 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyem3-68c63afaec2e: Sensor value[20]: id=6102, Value=0.0 (overpower, Type=A, Range=0/1;-1, Link=1: relay_0)
2020-09-13 19:05:01.809 [TRACE] [y.internal.handler.ShellyBaseHandler] - shellyem3-68c63afaec2e: Updating status
2020-09-13 19:05:01.810 [TRACE] [ng.shelly.internal.api.ShellyHttpApi] - shellyem3-68c63afaec2e: HTTP GET for http://192.168.42.115/status

i’m using following items

Number PVsma_accumulated_Power
“SMA PV SHELLY Leistung [%.1f W]”

(gPVsma_Power)
{ channel=“shelly:shellyem3:68c63afaec2e:device#accumulatedWatts” }

Number PVsma_accumulated_TotalKWH
“SMA PV SHELLY total energie [%.3f kWh]”

(gPVsma_Total)
{ channel=“shelly:shellyem3:68c63afaec2e:device#accumulatedTotal” }

Number PVsma_accumulated_ReturnKWH
“SMA PV SHELLY retuned energie [%.3f kWh]”

(gPVsma_Total)
{ channel=“shelly:shellyem3:68c63afaec2e:device#accumulatedReturned” }

device#accumulatedReturned and device#accumulatedWatts are plausibel
device#accumulatedTotal is missing

Is this missing in shelly coap message or just forgotten in shelly binding ?

Could
meter1#totalKWH
meter2#totalKWH
meter3#totalKWH
simply added becaused it’s already Wirkleistung?

best regards,
Peter

Baschtlwaschtl · September 23, 2020, 5:31am

That makes me mad.
After uninstall tradfri and Shelly snapshot and installing Shelly from paperUI I saw error from Shelly 2.5.6
So I deinstalled Shelly again, searched my Filesystem, found found a tmp folder with adons 2.5.6 and 2.5.8
I delete the 2.5.6 add-ons.
Now the 2.5.8 addon is installed and I got this:

2020-09-23 07:21:04.537 [ERROR] [org.openhab.binding.shelly          ] - bundle org.openhab.binding.shelly:2.5.8 (245)[org.openhab.binding.shelly.internal.api.ShellyEventServlet(229)] :  Error during instantiation of the implementation object
java.lang.IllegalArgumentException: argument type mismatch
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0_265]
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) ~[?:1.8.0_265]
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0_265]
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:1.8.0_265]
	at org.apache.felix.scr.impl.inject.ComponentConstructor.newInstance(ComponentConstructor.java:309) ~[bundleFile:?]
	at org.apache.felix.scr.impl.manager.SingleComponentManager.createImplementationObject(SingleComponentManager.java:277) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.SingleComponentManager.createComponent(SingleComponentManager.java:114) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:982) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.SingleComponentManager.getServiceInternal(SingleComponentManager.java:955) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:900) [bundleFile:?]
	at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse$1.run(ServiceFactoryUse.java:212) [org.eclipse.osgi-3.12.100.jar:?]
	at java.security.AccessController.doPrivileged(Native Method) [?:1.8.0_265]
	at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.factoryGetService(ServiceFactoryUse.java:210) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.getService(ServiceFactoryUse.java:111) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.serviceregistry.ServiceConsumer$2.getService(ServiceConsumer.java:45) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:508) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.getService(ServiceRegistry.java:461) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.framework.BundleContextImpl.getService(BundleContextImpl.java:624) [org.eclipse.osgi-3.12.100.jar:?]
	at org.ops4j.pax.web.extender.whiteboard.internal.tracker.AbstractTracker.addingService(AbstractTracker.java:173) [bundleFile:?]
	at org.ops4j.pax.web.extender.whiteboard.internal.tracker.AbstractTracker.addingService(AbstractTracker.java:46) [bundleFile:?]
	at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941) [osgi.core-6.0.0.jar:?]
	at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870) [osgi.core-6.0.0.jar:?]
	at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256) [osgi.core-6.0.0.jar:?]
	at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229) [osgi.core-6.0.0.jar:?]
	at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:901) [osgi.core-6.0.0.jar:?]
	at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:109) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:920) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:862) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:801) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:127) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:225) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:469) [org.eclipse.osgi-3.12.100.jar:?]
	at org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:906) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:892) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.RegistrationManager.changeRegistration(RegistrationManager.java:128) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.AbstractComponentManager.registerService(AbstractComponentManager.java:959) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:732) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.AbstractComponentManager.enableInternal(AbstractComponentManager.java:666) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.AbstractComponentManager.enable(AbstractComponentManager.java:432) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.ConfigurableComponentHolder.enableComponents(ConfigurableComponentHolder.java:665) [bundleFile:?]
	at org.apache.felix.scr.impl.BundleComponentActivator.initialEnable(BundleComponentActivator.java:338) [bundleFile:?]
	at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:382) [bundleFile:?]
	at org.apache.felix.scr.impl.Activator.access$200(Activator.java:49) [bundleFile:?]
	at org.apache.felix.scr.impl.Activator$ScrExtension.start(Activator.java:264) [bundleFile:?]
	at org.apache.felix.scr.impl.AbstractExtender.createExtension(AbstractExtender.java:196) [bundleFile:?]
	at org.apache.felix.scr.impl.AbstractExtender.modifiedBundle(AbstractExtender.java:169) [bundleFile:?]
	at org.apache.felix.scr.impl.AbstractExtender.modifiedBundle(AbstractExtender.java:49) [bundleFile:?]
	at org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:482) [osgi.core-6.0.0.jar:?]
	at org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:415) [osgi.core-6.0.0.jar:?]
	at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:232) [osgi.core-6.0.0.jar:?]
	at org.osgi.util.tracker.BundleTracker$Tracked.bundleChanged(BundleTracker.java:444) [osgi.core-6.0.0.jar:?]
	at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:908) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:213) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:120) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:112) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:168) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.container.Module.publishEvent(Module.java:476) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.container.Module.start(Module.java:467) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1634) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1614) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1585) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1528) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) [org.eclipse.osgi-3.12.100.jar:?]

And this:


2020-09-23 07:21:07.424 [ERROR] [.eclipse.californium.core.CoapClient] - could not set and start client endpoint
java.net.SocketException: Invalid argument
	at java.net.PlainDatagramSocketImpl.join(Native Method) ~[?:1.8.0_265]
	at java.net.AbstractPlainDatagramSocketImpl.join(AbstractPlainDatagramSocketImpl.java:178) ~[?:1.8.0_265]
	at java.net.MulticastSocket.joinGroup(MulticastSocket.java:323) ~[?:1.8.0_265]
	at org.eclipse.californium.elements.UdpMulticastConnector.start(UdpMulticastConnector.java:89) ~[?:?]
	at org.eclipse.californium.core.network.CoapEndpoint.start(CoapEndpoint.java:506) ~[?:?]
	at org.eclipse.californium.core.CoapClient.setEndpoint(CoapClient.java:356) ~[?:?]
	at org.openhab.binding.shelly.internal.coap.ShellyCoapHandler.start(ShellyCoapHandler.java:118) ~[?:?]
	at org.openhab.binding.shelly.internal.handler.ShellyBaseHandler.initializeThing(ShellyBaseHandler.java:276) ~[?:?]
	at org.openhab.binding.shelly.internal.handler.ShellyBaseHandler.lambda$0(ShellyBaseHandler.java:158) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_265]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_265]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_265]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_265]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_265]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_265]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_265]

I think I start from scratch

I was so keen on openhab. But that’s really annoying.

markus7017 · September 23, 2020, 6:22am

why are you using 2.5.8?
you need 2.5.9 to use firmware 1.8.x

a) from the Addons 2.5.9 release or
b) the DEV build + Californium libs

—

Latest DEV build - README - Installation - Firmware Index - Firmware Archive - API Doc

Baschtlwaschtl · September 23, 2020, 7:00am

I didn’t get the update to 2.5.9
I’m on freenas.
I deinstalled Shelly, stopped openhab, copied the snapshot and the californium.
now after restart openhab.

2020-09-23 08:54:56.918 [ERROR] [org.jupnp.transport.Router          ] - Unable to initialize network router: org.jupnp.transport.spi.InitializationException: Could not initialize MulticastReceiverImpl: java.net.SocketException: Invalid argument
2020-09-23 08:54:56.919 [ERROR] [org.jupnp.transport.Router          ] - Cause: org.jupnp.transport.spi.InitializationException: Could not initialize MulticastReceiverImpl: java.net.SocketException: Invalid argument
2020-09-23 08:54:57.302 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
2020-09-23 08:54:57.324 [INFO ] [ebuilder.internal.HomeBuilderServlet] - Started Home Builder at /homebuilder
2020-09-23 08:54:57.389 [INFO ] [openhab.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
2020-09-23 08:55:02.381 [WARN ] [org.apache.felix.fileinstall        ] - Error while starting bundle: file:/usr/local/libexec/openhab2/addons/org.openhab.binding.shelly-2.5.9-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.shelly [203]
  Unresolved requirement: Import-Package: org.eclipse.californium.core.coap; version="[2.0.0,3.0.0)"
    -> Export-Package: org.eclipse.californium.core.coap; bundle-symbolic-name="org.eclipse.californium.core"; bundle-version="2.0.0"; version="2.0.0"; uses:="org.eclipse.californium.core,org.eclipse.californium.core.network,org.eclipse.californium.core.network.stack,org.eclipse.californium.core.server.resources,org.eclipse.californium.elements,org.eclipse.californium.elements.util,org.slf4j"
       org.eclipse.californium.core [241]
         Unresolved requirement: Import-Package: org.eclipse.californium.elements; version="[2.0.0,3.0.0)"
  Unresolved requirement: Import-Package: org.eclipse.californium.core; version="[2.0.0,3.0.0)"
    -> Export-Package: org.eclipse.californium.core; bundle-symbolic-name="org.eclipse.californium.core"; bundle-version="2.0.0"; version="2.0.0"; uses:="org.eclipse.californium.core.coap,org.eclipse.californium.core.network,org.eclipse.californium.core.network.config,org.eclipse.californium.core.observe,org.eclipse.californium.core.server,org.eclipse.californium.core.server.resources,org.eclipse.californium.elements,org.eclipse.californium.elements.exception,org.slf4j"

	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.startAllBundles(DirectoryWatcher.java:1221) [bundleFile:3.6.4]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:515) [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]
2020-09-23 08:55:02.388 [WARN ] [org.apache.felix.fileinstall        ] - Error while starting bundle: file:/usr/local/libexec/openhab2/addons/californium-core-2.0.0.jar
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.californium.core [241]
  Unresolved requirement: Import-Package: org.eclipse.californium.elements; version="[2.0.0,3.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.startAllBundles(DirectoryWatcher.java:1221) [bundleFile:3.6.4]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:515) [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]

I will wait for the update…

Nightman · September 23, 2020, 7:10am

Hi Markus, I have updated openhab from .8 to .9 as well as the shelly binding. I see the same issue as @Baschtlwaschtl with my PlugS. I have de-installed the shelly binding and the re-installed it. A short timeframe after re-adding the shelly binding, the CoIoT communication works and after that it does not work any more and device updates are coming only every 60 seconds. Even log with trace show only 9 and then 5 coap messages and then nothing more (only the ‘normal’ http get / response messages).

I want to help, but have currently only a very limited time to do diagnostics. So please let me know how I could help (e.g. what logs you need and what exactly should be done during that logging).

Edit 28.09.2020 07:43
It turn out that my network configuration makes this kind of problems. I am running the Shelly plugs in another subnet than the openHAB. Something must have changed on my router to no more forwarding these udp broadcasts. I checked by bringing one Shelly PlugS into my home network where openHAB resides and everything worked as designed. Sorry for not checking this first. My fault.

Thank you @markus7017 for all the great work you are doing for us all.

krikk · September 23, 2020, 7:59am

there is no accumulatedTotal it is called accumulatedWTotal"

my shelly 3EM config:

Number emonAccumulatedWatts "Kumulierter Verbrauch [%.0f]" (gEnergyCounter)  {channel="shelly:shellydevice:xxxxxxxxx:device#accumulatedWatts"}
Number emonAccumulatedWTotal "Kumulierter Gesamtverbrauch [%.0f]" (gPersist1min)  {channel="shelly:shellydevice:xxxxxxxxx:device#accumulatedWTotal"}
// Number emonAccumulatedReturned "Kumulierter Rückstrom [%.0f]" (gPersist1min)  {channel="shelly:shellydevice:xxxxxxxxx:device#accumulatedReturned"}

peter_demus · September 23, 2020, 9:57am

Thanks a lot, now it’s working using accumulatedWTotal

was able to look up the “W” in
https://github.com/markus7017/openhab-addons/blob/shelly_snapshot/bundles/org.openhab.binding.shelly/src/main/java/org/openhab/binding/shelly/internal/ShellyBindingConstants.java

@markus7017 : Was the W inserted by intention ?

according to Shelly - Bindings | openHAB

accumulatedTotal Number yes Accumulated total power in kw/h of the device (including all meters)

it’s typo in code (not in docu), isn’t it?

my proposal:

a)
add following to channel selection:
accumulated_totalKWH
accumulated_returnedKWH
accumulated_currentWatts
to have consistent naming compared to meter1 e.g. and no API break if someone is using “accumulatedWTotal” with typo

b)
change “kw/h” to “kWh” in documentation

thanks for having the “accumulated” values for 3EM

Best regards ,
Peter

markus7017 · September 23, 2020, 9:31pm

did you followed the „How to install“? there are 2 files for Californium, otherwise try cleaning the cache, your installation is not valid

Baschtlwaschtl · September 24, 2020, 2:26pm

I got update to 2.5.9
I stopped openhab service. Deleted cache and tmp and addons.
I did the update, Restarted the service and installed the 2.5.9 binding from paperUI.
I now have the same errors as before.

2020-09-24 15:49:54.956 [INFO ] [openhab.ui.paper.internal.PaperUIApp] - Stopped Paper UI
2020-09-24 15:49:54.971 [INFO ] [ebuilder.internal.HomeBuilderServlet] - Stopped Home Builder
2020-09-24 15:49:54.978 [INFO ] [panel.internal.HABPanelDashboardTile] - Stopped HABPanel
2020-09-24 15:49:54.994 [INFO ] [basic.internal.servlet.WebAppServlet] - Stopped Basic UI
2020-09-24 15:49:55.090 [INFO ] [.dashboard.internal.DashboardService] - Stopped Dashboard
2020-09-24 16:00:58.754 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'fritz.sitemap'
2020-09-24 16:00:58.775 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'dummy.sitemap'
2020-09-24 16:00:58.809 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'Fritz.items'
2020-09-24 16:00:58.820 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'dummy.items'
2020-09-24 16:00:59.409 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Time zone set to 'Europe/Berlin'.
2020-09-24 16:00:59.410 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Location set to 'bla87,bla057397'.
2020-09-24 16:00:59.412 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Locale set to 'de_DE'.
2020-09-24 16:00:59.412 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Measurement system set to 'SIUnits'.
2020-09-24 16:01:00.421 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'lauflicht.rules'
2020-09-24 16:01:00.516 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'trep.rules'
2020-09-24 16:01:00.833 [INFO ] [thome.core.items.ManagedItemProvider] - Finished loading the items which could not have been created before.
2020-09-24 16:01:01.055 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at http://192.168.0.10:8080
2020-09-24 16:01:01.056 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at https://192.168.0.10:8443
2020-09-24 16:01:01.235 [INFO ] [thome.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2020-09-24 16:02:06.370 [ERROR] [org.jupnp.transport.Router          ] - Unable to initialize network router: org.jupnp.transport.spi.InitializationException: Could not initialize MulticastReceiverImpl: java.net.SocketException: Invalid argument
2020-09-24 16:02:06.371 [ERROR] [org.jupnp.transport.Router          ] - Cause: org.jupnp.transport.spi.InitializationException: Could not initialize MulticastReceiverImpl: java.net.SocketException: Invalid argument
2020-09-24 16:02:06.529 [INFO ] [openhab.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
2020-09-24 16:02:06.636 [INFO ] [ebuilder.internal.HomeBuilderServlet] - Started Home Builder at /homebuilder
2020-09-24 16:02:06.748 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
2020-09-24 16:02:06.885 [WARN ] [iscovery.TradfriDiscoveryParticipant] - Discovered Tradfri gateway doesn't have an IP address: [ServiceInfoImpl@1322164893 name: 'gw-d44da437515d._coap._udp.local.' address: '(null):0' status: 'DNS: JmDNS-/2003:d8:1710:1200:f4aa:14ff:fec7:f244 [/2003:d8:1710:1200:f4aa:14ff:fec7:f244] state: probing 1 task: null', has NO data
	gw-d44da437515d._coap._udp.local.: ]
2020-09-24 16:02:40.317 [ERROR] [.eclipse.californium.core.CoapClient] - could not set and start client endpoint
java.net.SocketException: Invalid argument
	at java.net.PlainDatagramSocketImpl.join(Native Method) ~[?:1.8.0_265]
	at java.net.AbstractPlainDatagramSocketImpl.join(AbstractPlainDatagramSocketImpl.java:178) ~[?:1.8.0_265]
	at java.net.MulticastSocket.joinGroup(MulticastSocket.java:323) ~[?:1.8.0_265]
	at org.eclipse.californium.elements.UdpMulticastConnector.start(UdpMulticastConnector.java:89) ~[?:?]
	at org.eclipse.californium.core.network.CoapEndpoint.start(CoapEndpoint.java:506) ~[?:?]
	at org.eclipse.californium.core.CoapClient.setEndpoint(CoapClient.java:356) ~[?:?]
	at org.openhab.binding.shelly.internal.coap.ShellyCoapHandler.start(ShellyCoapHandler.java:118) ~[?:?]
	at org.openhab.binding.shelly.internal.handler.ShellyBaseHandler.initializeThing(ShellyBaseHandler.java:276) ~[?:?]
	at org.openhab.binding.shelly.internal.handler.ShellyBaseHandler.lambda$0(ShellyBaseHandler.java:158) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_265]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_265]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_265]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_265]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_265]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_265]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_265]

tradfri runs fine.
What is this error with the multicastReceiver?

Maybe I should try the raspberry version…

Oliver2 · September 26, 2020, 12:52pm

I was constantly reading in the past this thread as I planned to update my Shellys’ firmware to v1.8 once the new shelly binding is available via a regular openHAB update.

Now I already updated openHAB and everything works fine so far (with v1.6 Firmware).

I am going to update my Shellys to v1.8 now but what exactly do I need to do then?
Is uninstalling and re-installing of the binding mandatory?
Could somebody please advice a little bit in detail?
Many thanks in advance!

Regards
Oliver

Oliver2 · September 26, 2020, 2:18pm

ok - stupid me.
Binding documentation has been updated acordingly:

Once you have updated the device you should delete and re-discover the openHAB Thing. This makes sure that the Thing is correctly initialized and all supported channels are created. openHAB will kill the item linkage. At a minimum you should restart the binding on the openHAB console if you don’t want to re-discover the things.

Baschtlwaschtl · September 27, 2020, 4:53am

Now I finally got it to run.
It’s probably because of the multicast. This does not work in freenas jail
I installed Debian in a VM. Openhab and the shelly-binding run smoothly on this.

Thx

markus7017 · September 27, 2020, 8:21am

sounds good, maybe your freenas environment didn‘t passed multicast ip or the firewall rules blocks this. I‘m not sure, but assume that Tradfi doesn’t use multicast

markus7017 · September 28, 2020, 6:36am

CoIoT/CoAp is based on Multicast IP, this needs to be supported by the router between subnets, otherwise communication is not possible. I can‘t explain why some messages work and then it stops. The discovery is send directly to the device IP, but all status messages are broadcasted by Multicast IP (224.x.x.x)

Izharm · September 28, 2020, 10:59am

Hi,
Just upgraded to 1.8/2.5.9, all is working.
I do get quite a lot of status updates, some every few seconds. It seems the binding is no longer polling at ‘update interval’ for status, but gets unsolicited updates from the devices. Is this the case? if so is there a way to limit the devices report interval ?

Izhar

markus7017 · September 28, 2020, 2:38pm

We are using CoIoT to get near realtime events/updates. You could disable CoIoT for this thing and get updates every 60sec

I could check, as I remember you could set the update interval with an URL call (increasing from 15sec to xx sec).

There is nothing changed with 2.5.9, is the same logic as in 2.5.8