See - this is your first mistake - assuming the devices are identical
The properties for the device you just listed are for a new device - or at least a different device that is NOT in the database. In the information you posted, you shows the manufacturerRef as 1401:2000,1801:1000, but your device properties are 1501:1000.
It needs to be added to the database (I have just done this), the database needs to be exported, and you will then need to use the binding with the updated database that includes this device.
Thanks Chris. This kind of thing happens so rarely with OH that I always forget how to handle it. I see that the database has been updated, thank you. In terms of the export and recompile of the binding, I assume that’s something that I have to wait to happen? I’m not in any rush, just don’t want to be waiting for something to happen when in actual fact the action is with me.
Is my next action to update to a nightly build, perhaps tomorrow?
When the device was unknown, you don’t need to do this as there is nothing to update as it was never discovered in the first place… Just updating the binding should be fine.
Well, there are different parts of discovery… There’s the protocol side, where the binding reads all the bumf out of the device so that it knows what it is, and then there’s the openHAB side, where the binding tries to marry up the device information with the database so that it can create a Thing.
The second part with the database, and creation of the thing/channels etc hasn’t happened when there’s no database entry, so you don’t need to delete the Thing.
Sure - that I understand, but what I don’t know is what triggers a rebuild of the repository? ie will it be built automatically if dependant projects are rebuilt? I don’t know how CI is configured for that project?
The script fails for me unfortunately; I need to run it as the openhab user, and under openhabian, the openhab user (which is the user that runs openhab) doesn’t have the rights for this script - it ends up failing with a 2 minute timeout.
My current version of openhab-addons-2.5.10-SNAPSHOT.kar is dated October 16th, and with that I won’t have the latest database changes you’ve made. I’ve looked at openhab-addons but the ZWave component looks to be separate. With the script failing is there another way to get an updated ZWave file? I’m not sure how often the openhabian snapshot updates - I may just try each day for the next week or so and see if it catches up.
I’ve manually kicked off a build of the OH-distro. I think (but am not 100% sure) that it will also update openhabian (the OH distro build is also 246, so there’s some hope!).
Hopefully that will flow through in the coming hour or two with any luck.
Well, that’s not really the way the CI is configured. CI is configured separately for OH2.5 and OH3, and I have currently triggered the OH2.5 integration build on CI.
The permissions are fine or the script wouldn’t have run. But the script will not work if you are using a kar file. There are more details in your openhab.log.
Hi Scott, thanks for the reply - I avoided expanding so as not to introduce new issues (my passing aquaintance with Linux), but as you’re here I’ll explain.
My install does indeed use a kar file - that’s not something I chose and I suppose it must be the default with openhabian. Running the script leaves nothing in either openhab.log or events.log. Script output below. I reset the openhab password this afternoon so I know that that is correct, but the output reads to me like an authorisation issue:
Script version: 1.2.8
***** SUMMARY *****
Addons path: /usr/share/openhab2/addons
openHAB account: openhab
Requested action: Install or upgrade Z-Wave binding
Current openHAB snapshot version: 2.5.10
Requested Z-Wave version: Development
Is this correct?
Yes, start now
No, take me back to the first menu
Exit
#? 1
Uninstalling any managed binding(s) and installing serial transport…
… if prompted for a password for the Karaf console, the default password is ‘habopen’…
Logging in as openhab
Password:
Password:
No more authentication methods available
… a ‘No matching bundles’ error mesage is normal, if a binding had not been previously installed.
Backing up and uninstalling any unmanaged installs of Z-Wave…
!!! It has taken more than two minutes to uninstall the Z-Wave binding, so exiting !!!
openhab-cli info gives:
Version: 2.5.10-SNAPSHOT (#246)
User: openhab (Active Process 28091)
User Groups: openhab tty dialout sudo audio bluetooth gpio
