I’m trying to get openhab 2.4 running on Ubuntu 18.04 (x86) with the latest snapshot zwave driver. After installing openhab, I use the script by @5iver to manually install the serial driver as well as the latest zwave snapshot. I rebooted, then added the zwave serial controller thing. I have a HUSB…

For the 2.5 binding, you’ll need to use to the Karaf console to install the serial transport. [image] [SOLVED] Link to Zwave binding SNAPSHOT 2.5 Bindings OK, it is resolved. I found in another thread that sometimes you also need to " feature:install openhab-t…

The serial transport is already installed using the manual installer script. Verified by looking in karaf.

Sorry, I honestly don’t know what I was thinking when I posted that. You’re actually having the same issue I was working on earlier today, and I don’t know why that wasn’t obvious. It’s dinnertime, so I’ll claim hunger. :wink: Anyway, the issue is the 2.5 binding. I downloaded it a little over a we…

Ok, thanks for the clarification. Unfortunately, I need some stuff that is not in the 2.4 release device database. Any pointers to where the discussion was happening about the 2.5 issue?

thanks @rpwong for the hint!!! I do indeed have the same issue. It worked fine yesterday, only immediately after the installation of the 201904202118 snapshot of 2.5.0. However, later last night it started showing the controller as offline. Since I also updated the VM host, I falsely attributed the …

The new binding uses the ESH internal serial provider rather than using the serial driver directly. Probably something isn’t installed, so it can’t find the provider that it’s looking for. Unfortunately I’m not sure what’s not installed as my understanding is that installing the serial transport sho…

[image] chris: Unfortunately I’m not sure what’s not installed I don’t know how to identify the internal serial provider, but what I did notice after a clean 2.5 snapshot #1572 installation: as soon as the zwave binding is installed I see two serial drivers installed: 247 │ Active │ 80 │ 3…

[image] sihui: this should not matter anymore, I guess. It does matter. The ESH serial provider is simply acting as a proxy - if you use a normal serial port, then it proxies for nrjavaserial. The proxy bundle is in org.eclipse.smarthome.io.transport.serial.

[image] chris: It does matter. :sunglasses: So the 3.15.0.OH2 is the proxy and the 3.14.0 is the actual serial driver???

No SerialPort Provider error with Ubuntu 18.04 and Zwave 2.5.x snapshot

Add-ons Bindings

rpwong (Russ) April 22, 2019, 1:31am 6

Here are the two I saw when I searched for “zwave 2.5”. Sounds like some people are having success with different builds, but I didn’t look into that since the 2.4 covers me. Good luck!