FGWPB-121 Not in Database - but it is

Tags: #<Tag:0x00007f432ff86320>

Thanks Bruce also - I apprecaite the reply, despite the ninja from Chris.

Yes, I’ll probably do this later today, so tomorrow should be fine (or later tonight if you’re in the US :wink: ).

UK; perfect, thank you.

Then you need to install the snapshot version of the binding using the script.

Zigbee and Z-Wave manual install script - Tutorials & Examples - openHAB Community

You then need to delete the unknown Thing from OH ( do NOT exclude) and rediscover . add to get the new binding settings.

1 Like

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.

I thought it was discovered & the binding wrote out the NIF information. You know better than I though.

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.


Hi Chris, I’ve used opanhabian to update to the latest nightly - it says version 2.5.10~S246-1. However, the devices are still unrecognised:

2020-10-18 14:48:47.186 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 24: Device discovery completed
2020-10-18 14:48:47.189 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 24: Device discovery could not resolve to a thingType! 010F:1501:1000::4.2
2020-10-18 14:48:47.192 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 25: Device discovery completed
2020-10-18 14:48:47.195 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 25: Device discovery could not resolve to a thingType! 010F:1501:1000::4.2

Is there a jar file I need to add manually?

Possibly - I’m not sure when (or if) the build of openhabian is triggered. I recompiled the binding last night.

You can install the latest snapshot using the following script -:

It just uses the apt repositories for OH. The image is just basically the OS and other supporting files.

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?

1 Like

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.

Much apprecaited Chris - I have my fingers crossed.

1 Like

That would be an openhab2-snapshot. (openhab-snapshot is OH3)

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?

  1. Yes, start now
  2. No, take me back to the first menu
  3. 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
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

Directories: Folder Name | Path | User:Group
----------- | ---- | ----------
OPENHAB_HOME | /usr/share/openhab2 | openhab:openhab
OPENHAB_RUNTIME | /usr/share/openhab2/runtime | openhab:openhab
OPENHAB_USERDATA | /var/lib/openhab2 | openhab:openhab
OPENHAB_CONF | /etc/openhab2 | openhab:openhab
OPENHAB_LOGDIR | /var/log/openhab2 | openhab:openhab
OPENHAB_BACKUPS | /var/lib/openhab2/backups | openhab:openhab


There are several warnings in the docs and in the script itself… you should not use the development version of the binding unless specifically told to do so. Sorry for the confusion! I should really remove that option all together. You are looking for the snapshot version.

1 Like

Unpacking openhab2 (2.5.10~S248-1) over (2.5.10~S246-1)

The repository updated at some point over the past 12 hours and the new plugs are now recognised.

Thank you everyone for the assistance in getting this sorted.

1 Like