jwiseman
(Mr. Wiseman (OH 5.1.4 Stable on Pi5))
360
Chris,
It works . . .
2018-12-31 09:20:36.273 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/ttyACM0'
2018-12-31 09:20:36.550 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Serial port is initialized
2018-12-31 09:20:36.765 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2018-12-31 09:20:36.766 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
I get this during a clean cache/tmp startup (only during the clean startup) but I get these also with other 2.4 bindings running OH 2.3.
file install output
at org.eclipse.osgi.container.Module.start(Module.java:444) [?:?]
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) [?:?]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [9:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [9:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1221) [9:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:515) [9:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [9:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [9:org.apache.felix.fileinstall:3.6.4]
2018-12-31 09:14:10.691 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/volume1/homes/openhab/addons/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [198]
Unresolved requirement: Import-Package: gnu.io
at org.eclipse.osgi.container.Module.start(Module.java:444) [?:?]
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) [?:?]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [9:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [9:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1221) [9:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:515) [9:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [9:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [9:org.apache.felix.fileinstall:3.6.4]
2018-12-31 09:14:10.698 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/volume1/homes/openhab/addons/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [198]
Unresolved requirement: Import-Package: gnu.io
Hereās some readins from some of the zWave devices:
You might want to double check that you donāt have multiple versions installed. Normally these sort of errors mean that the binding wonāt start as it canāt find (in this case) the serial driver. Either that or check a bit earlier in the log as the binding does log the version when it first starts.
jwiseman
(Mr. Wiseman (OH 5.1.4 Stable on Pi5))
362
OH 2.3.0001 which is the version Iām running, does have an issue keeping the serial driver loaded w/o having a binding tied to it installed. Once I remove the original zWave binding through PaperUI, it removes the serial driver also.
Couple ways to get around this in OH 2.3.0001 is load another binding through ADD-ONās file that Iām NOT using but loads the serial driver anyway (Bose Sound Binding) has it built in. Another way is to go into the Karaf console and load it manually every time (that got old).
Iām waiting for the Synology team on OH to release the 2.4 build for my device (not sure when/if that will happen).
Iām a bit green on working with OH in a non-āout of the boxā way, so I apologise in advance for the simple question. I tried to update the binding by dropping the updated jar file into add-ons of my 2.4. stable install, doing a bundle:stop on the previous version and a bundle:start on the new version, as it listed as being installed, however I get the following message:
openhab> bundle
openhab> stop 218
openhab> start 252
Error executing command: Error executing command on bundles:
Error starting bundle 252: Could not resolve module: org.openhab.binding.zwave [252]
Another singleton bundle selected: osgi.identity; type="osgi.bundle"; version:Version="2.4.0"; osgi.identity="org.openhab.binding.zwave"; singleton:="true"
So I then uninstalled the 2.4.0 zwave binding completely via paperUI and tried to start the bundle again and received the following:
openhab> start 252
Error executing command: **Error executing command on bundles:**
**Error starting bundle 252: Could not resolve module: org.openhab.binding.zwave [252]**
**Unresolved requirement: Import-Package: gnu.io**
And after a restart of the OH system, I get the following in the logs:
15:28:53.739 [ERROR] [org.openhab.binding.zwave ] - FrameworkEvent ERROR - org.openhab.binding.zwave
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [252]
Unresolved requirement: Import-Package: gnu.io
at org.eclipse.osgi.container.Module.start(Module.java:444) ~[?:?]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1634) ~[?:?]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1614) ~[?:?]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1585) ~[?:?]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1528) ~[?:?]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) ~[?:?]
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) [?:?]
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) [?:?]
15:28:55.605 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/opt/openHAB2/addons/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [252]
Unresolved requirement: Import-Package: gnu.io
at org.eclipse.osgi.container.Module.start(Module.java:444) ~[?:?]
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) ~[?:?]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [10:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [10:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1221) [10:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:515) [10:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [10:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [10:org.apache.felix.fileinstall:3.6.4]
15:29:05.622 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/opt/openHAB2/addons/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [252]
Unresolved requirement: Import-Package: gnu.io
at org.eclipse.osgi.container.Module.start(Module.java:444) ~[?:?]
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) ~[?:?]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [10:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [10:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1221) [10:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:515) [10:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [10:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [10:org.apache.felix.fileinstall:3.6.4]
Is there some other way I should be updating the zwave jar file? or do i need to move to 2.5 snapshot? Sorry if itās a basic question.
This is updated during the nightly heal. Do your devices show any neighbors in the properties? If so, this is working and itās a problem with the graph itself maybe?
A long time ago (I donāt remember the browser family) I had the picture size set to a very small percentage and could not see the map either. You may want to hit CTRL - 0 to set it to default
i updated to the latest stable build of openhab (version 2.4). With this version all my zwave items working fine, only my vibration sensor ZS5101 making problemsā¦
Battery status and tamper alam are working also, only the why iam using these sensors the shock alarm will not work!
I tested already to exclude and reinclude a device and also to reset one of my devices completly and include it again. The inclusion works without any problems, but the problem with shock alarm will not go awayā¦
With with latest unstable Snapshot (1484) the problem is also there.
I hope someone can help, i dont want to downgrate to 2.3ā¦
Hi,
Issue: zwave devices, such as Fibaro FGD212 Dimmer 2, and ZW096 Smartswtich 6 do not stream data, such as power consumption data either to the logs or for persisting to DB. Nor do manual activation of the device (physical switch) register for on/off events, and therefore habpanel, openab mobile app, etc. do not report the correct state of the device.
On suggestion, I have updated the zwave bundle to version: 2.5.0.201812302011 on OH 2.4.0 Stable, running on a MacMini with OSX (Mojave). Once updated, I left overnight just to ensure healing was complete. I then checked associations and found that none were associated with the controller. I went and set all devicesā group associations to lifeline = controller via habmin. This did not resolve the issue. I then did a restart of the server. This did not resolve the issue.
I then removed one device via paperUI, and recreated it. tested, no change, and then changed the dimmer link to profile type āfollowā, tested, no change.
I cannot get a physical activation of the device to register in OH, nor will the power data, etc. stream updates back to the OH server.
Any suggestions anyone?