Nope, it does not work even adding all ports to Extra_java_opts. I have been using symlinks for quite some time now, and have never been able to get it to work,
I have not tried with newer builds, as the google cloud seems to be broken.
Best and easist way to get the serial driver installed, is to install zigbee binding from PaperUI, even though you´re not using it… @5iver script might also be an option, but I have never gotten that to work regarding the serial driver.
2 Likes
Thanks for this, @Kim_Andersen
@5iver: feature:install org.openhab.transport.serial doesn’t work, because “Error executing command: No matching features for org.openhab.transport.serial/0”
feature:install openhab.transport.serial works, but it’s volatile. Deleting the cache and tmp folders and the org.eclipse.smarthome.io.transport.serial disappears again, disabling the z-wave binding and taking the entire z-wave network with it.
2019-06-20 12:17:35.149 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/usr/share/openhab2/addons/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [192]
Unresolved requirement: Import-Package: org.eclipse.smarthome.io.transport.serial
Kim’s method (installing the Zigbee binding because it includes openhab.transport.serial as a dependency I guess?) works so far, but I have not yet tried to delete /tmp and /cache again.
Oops… sorry…
Yes, that will happen, since dependencies are not resolved for manually installed bindings. The easiest workaround is to install a binding that has the same dependency, such as the Serial binding. Zigbee works too, unless you end up using it and also install it manually.
1 Like
Makes sense now. Thank you!
Is there a way to declare dependencies manually, the way you can declare bindings manually in addons.cfg?
Unfortunately, no. You could use a kar file (instead of a jar), which include the dependencies, but it looks like they are no longer being built. Something else you can do, which I haven’t tried since I don’t use a repository installation, is to change the repo to the snapshots and use the console to update the binding…
bundle:update org.openhab.binding.zwave
Yet another option is to use the console to pull the binding from the repo…
bundle:update org.openhab.binding.zwave https://openhab.jfrog.io/openhab/online-repo-snapshot/2.5/org/openhab/binding/org.openhab.binding.zwave/2.5.0-SNAPSHOT/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar
When the binding is installed through Karaf, the dependencies will be resolved. However, I’ve only played with this once and don’t know how well this will survive cache clearing. I’ve been meaning to play with this to use in my install script, rather than copying jars to the addons directory.
Edit: I just tried this and that link pulled down an older version of the zwave binding. This one got the latest…
bundle:update org.openhab.binding.zwave 'https://ci.openhab.org/job/openHAB2-Bundles/lastSuccessfulBuild/org.openhab.addons.bundles$org.openhab.binding.zwave/artifact/org.openhab.addons.bundles/org.openhab.binding.zwave/2.5.0-SNAPSHOT/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar'
Edit: It is best not to use the CI server for this… use Bintray…
bundle:update https://openhab.jfrog.io/openhab/online-repo-snapshot/2.5/org/openhab/addons/bundles/org.openhab.binding.zwave/2.5.0-SNAPSHOT/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar
1 Like
Is there any specific reason why org.openhab.transport.serial isn´t installed as default. Even though a user may not be using it?
There seem to be alot of struggle around this, and I my opinion it could have been easily solved just by having the org.openhab.transport.serial installed as default from start.
1 Like
I believe it was needed after 2.4 was released.
That command gives me this error:
Error executing command: Server returned HTTP response code: 403 for URL: https://ci.openhab.org/job/openHAB2-Bundles/lastSuccessfulBuild/org.openhab.addons.bundles$org.openhab.binding.zwave/artifact/org.openhab.addons.bundles/org.openhab.binding.zwave/2.5.0-SNAPSHOT/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar
EDIT: I think this command works. The file date looks correct.
bundle:update org.openhab.binding.zwave 'https://openhab.jfrog.io/openhab/online-repo-snapshot/2.5/org/openhab/addons/bundles/org.openhab.binding.zwave/2.5.0-SNAPSHOT/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar'
Don’t use the CI server… it is not meant for downloads and is not always available, That is what Bintray is for. Use this (I’ll correct the old post)…
bundle:update https://openhab.jfrog.io/openhab/online-repo-snapshot/2.5/org/openhab/addons/bundles/org.openhab.binding.zwave/2.5.0-SNAPSHOT/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar
1 Like
My the way, the command I ran did not seem to find the xstream dependency from 2.4. I doubt using the bintray link would make any difference.
Sorry, I did not realize I was chaining off an old post. O was looking for the one you posted earlier today.
Interesting. I’ll need to try again on 2.4. When I tested it, I did not run into this, but I also did not have a controller in the system. I am surprised that xstream would not have been resolved, but maybe it’s an ESH reintegration thing.
Looks like if 2.4, upgrade to 2.5 or use a manual install. If 2.5, then use bundle:update/install.
I am getting ready to retry now. I have 2.4 installed with the 2.4 zwave binding & a controller.
I will then try the console upgrade again.
EDIT: Nope
Error executing command: Bundle https://openhab.jfrog.io/openhab/online-repo-snapshot/2.5/org/openhab/addons/bundles/org.openhab.binding.zwave/2.5.0-SNAPSHOT/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar does not match any bundle
openhab>
I think you meant
bundle:update org.openhab.binding.zwave 'https://openhab.jfrog.io/openhab/online-repo-snapshot/2.5/org/openhab/addons/bundles/org.openhab.binding.zwave/2.5.0-SNAPSHOT/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar'
EDIT2: Cannot resolve dependency
207 │ Installed │ 80 │ 2.5.0.201911150347 │ openHAB Add-ons :: Bundles :: ZWave Binding
openhab> bundle:start 207
Error executing command: Error executing command on bundles:
Error starting bundle 207: Could not resolve module: org.openhab.binding.zwave [207]
Unresolved requirement: Import-Package: com.thoughtworks.xstream; version="[1.4.0,2.0.0)"
Yes - we don’t install something that the user doesn’t need - it takes memory which may be essential on small systems so the system should only install bundles that it needs. Otherwise you extend your statement to just installing everything even if the user doesn’t require it!
2 Likes