Everytime after a nas reboot the z-wave bining lost the z-wave usb stick configurartion and all node previously discovered are off-line.
As soon as I update the serial port of z-wave binding the new nodes are re-discovered as new node, so I need to configure any node, channel and parameter from the beginning.
Welcome to the forum! Is the port changing? If so, look into using a udev rules. If not, look into /userdata/jsondb/org.eclipse.smarthome.core.thing.Thing.json (the uderdata directory location will depend on the type of installation used). Does the file exist after a restart and are your Things still in there?
That’s odd. Test something… in the Karaf console, run list -s | grep zwave. Maybe you have multiple zwave bindings installed and OH is getting confused after the restart. Since you manually installed the binding, you should not see it as being installed in Paper UI.
Hi
it looks like if I’ve two:
openhab> list -s | grep zwave
212 x Active x 80 x 2.5.0.201904160017 x org.openhab.binding.zwave
221 x Installed x 80 x 2.4.0 x org.openhab.binding.zwave
OK! So, uninstall the one you see in Paper UI, or run bundle:uninstall 221 in the console. You will then see errors in the log due to the serial transport missing. You will need to run feature:install openhab-transport-serial to install it, if you don’t have any other binding installed that has that dependency.
Hi I run the unistall command
and now the output of list - s | grep wave is
openhab> list -s | grep wave
212 x Active x 80 x 2.5.0.201904160017 x org.openhab.binding.zwave
But I don’t understand if I’ve to run also “feature:install openhab-transport-serial”, because I’ve installed other binding like network binding and samsung binding.
If they use serial, then you should be OK. Another trick is to just install the serial binding, which has this dependency too. If you manually install the serial transport, you need to instal it again after upgrading OH. If you check your openhab.log and see errors about gnu.io missing, you need to install it.
Try a restart of your nas and see if zwave comes up.
feature:install openhab-transport-serial
org.apache.karaf.features.internal.util.MultiException: Error restarting bundles:
Could not resolve module: org.openhab.binding.zwave [225]
Another singleton bundle selected: osgi.identity; type=“osgi.bundle”; version:Version=“2.5.0.201904160017”; osgi.identity=“org.openhab.binding.zwave”; singleton:=“true”
at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:1005)
at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1025)
at org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:964)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Suppressed: org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [225]
Another singleton bundle selected: osgi.identity; type="osgi.bundle"; version:Version="2.5.0.201904160017"; osgi.identity="org.openhab.binding.zwave"; singleton:="true"
at org.eclipse.osgi.container.Module.start(Module.java:444)
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383)
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:402)
at org.apache.karaf.features.internal.service.BundleInstallSupportImpl.startBundle(BundleInstallSupportImpl.java:161)
at org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1116)
at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:997)
... 6 more
Error executing command: Error restarting bundles:
Could not resolve module: org.openhab.binding.zwave [225]
Another singleton bundle selected: osgi.identity; type=“osgi.bundle”; version:Version=“2.5.0.201904160017”; osgi.identity=“org.openhab.binding.zwave”; singleton:=“true”
Check the list of bundles again… the other one is back. Did you manually configure the binding line in addons.cfg? If so, make sure zwave is not in there.
openhab> list -s | grep zwave
212 x Active x 80 x 2.5.0.201904160017 x org.openhab.binding.zwave
225 x Installed x 80 x 2.4.0 x org.openhab.binding.zwave
Strange. Try uninstalling the binding in Paper UI then. Removing it through the console should do the same thing though. Or do you maybe have another zwave jar in addons?