Does this version of the binding work with an Openhab 2.2 snapshot? In my case I see the 2.1.0 version of the binding installed in the Karaf console but my Z-Wave controller is not showing up. Any ideas?
What does this actually mean? You add the controller, but the port doesn’t open? Or something else?
No, I see the correct binding with the bundle:list command but in the PaperUI or Habmin none of my Z-Wave devices is listed. Maybe the particular Openhab snapshot is faulty? I am now restoring my backed-up image and try again.
Ok, I have installed the newest version of this Z-Wave binding. Accidentally I had both binding versions installed for a time but this was resolved by uninstalling the old binding and restarting the new one. Now, however, the Z-wave binding shows up as “resolved” using the bundle:list command. I can then bundle:restart it but after a reboot it is again not active.
Any ideas on how to resolve this?
The issue is probably that you haven’t resolved the serial dependancy. Use the following command to do this -:
Is the serial the ID I get from bundle:list?
No, the name of the feature is “openhab-transport-serial”. So “serial” is the actual word “serial”
Exactly - just type in the line I said above - no magic
Hmm, that did not work. No error message after I entered the command. Bust after a reboot the binding is still shown as “resolved”.
What do you get if you run “feature:list|grep openhab-transport-serial”?
I get the following:
openhab-transport-serial | 2.2.0.SNAPSHOT | x | Started | distro-2.2.0-SNAPSHOT | Serial Transport
Looks quite correct to me. I guess this is the point where @chris has to jump in again
Btw, have you looked in the logs?
What happens if you start the binding (with the start command)?
The binding starts and is shown as “Active”.
Are you running any other bindings that use a serial port? I had the Zwave binding issue related to the binding for my security system and had to change the start priority so that the security system binding started last.
Then it’s ok - right? I think you probably just didn’t start the binding after removing the old one…
I think you’re missing the problem. Apparently the binding doesn’t start by itself after a reboot although a manual start of it works.
@sloth0815: I’d suggest you dig through whatever gets in the log after a start of openHAB and see if you find any errors there.
Was it ever started though? I don’t see anything that said the binding ever started. If not, then I don’t think it will start when the system starts due to the fact that both bindings were running at the same time.
Having started the binding now, does it restart if OH is restarted?
No, unfortunately it does not start after a reboot.
Ok, sorry, but I’ve no idea why this is then. It’s likely to be an issue with your system rather than the binding…