[SOLVED] Z-Wave supported devices missing

[kdsnet3410 (Kevin S)]

I am running openhabian with the latest testing/milestone build. Over the past few weeks I have setup setup and configured about 40 z-wave devices in my openhab setup. Today I was cleaning up some entries in Paper UI and started to get a 500 server error when going into the properties for some devices. After doing some investigation, it appears that the z-wave binding is not showing many of my devices as supported devices. They are in the z-wave database because I was able to do the initial setup and I contributed to having the devices added to the database.

Screenshot above shows only one RF96xx devices supported. There should be at least 4 different device models supported in RF96xx series.

I uninstalled the binding, cleared the cache, and reinstalled the binding. I also tried stable openhab builds. Everything was almost working the way I wanted to it and now a seemingly random number of devices are missing from the z-wave database. HABmin has the items with the missing device database entry grayed out. I would really hate to have to start over.

[5iver (Scott Rushworth)]

[zwave] openHAB 2.5.0 Build #1723 exception during startup

Before I open an issue I wanted to see if there are others seeing this error and gather more information others may have. I’m running OH in a Docker container and just upgraded this morning. When OH comes up I see the following exception in the logs: 2019-10-14 07:58:16.519 [ERROR] [ig.xml.osgi.XmlDocumentBundleTracker] - Could not send adding finished event for the module 'org.openhab.binding.zwave'! java.lang.IllegalArgumentException: UID must have at least 2 segments. at org.eclipse…

[Bruce_Osborne]

@kdsnet3410

the latest testing/milestone build.

You are running 2.5M3 then? I have been running that for a while and just set up a test zwave network with no issues.

Some people are having issues with the lates unstable snapshot builds but the testing Milestones have been working solidly.

[AndyMB (Andy)]

Hi,

@kdsnet3410 you are not alone

While trying to sort out a defective z-wave motion sensor I took the opportunity to upgrade to the latest snapshot (1724 ?). I also had a number of things marked for deletion (as shown in Kevin’s habmin screenshot).

I deleted these and then re-scanned the network using paper UI. All items were discovered but could not be found within the z-wave device database. Turned on debug logging. Deleted items were all previously working / matched in the device database.

Yesterday I upgraded to 2.5.0~S1725-1 (Build #1725) to see if this made any difference. Today additional items (but not all) were shown in Habmin with the “delete” option. These were deleted and the network was re-scanned. Results below:

2019-10-16 13:30:34.486 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 34: Device discovery completed
2019-10-16 13:30:34.505 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 34: Device discovery could not resolve to a thingType! 010F:0800:1001::2.6
2019-10-16 13:30:34.524 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery completed
2019-10-16 13:30:34.542 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! 0148:0001:0001::0.4
2019-10-16 13:30:34.560 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery completed
2019-10-16 13:30:34.576 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! 0148:0001:0001::0.4
2019-10-16 13:30:34.647 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery completed
2019-10-16 13:30:34.661 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery could not resolve to a thingType! 0148:0001:0001::0.4
2019-10-16 13:30:34.678 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery completed
2019-10-16 13:30:34.686 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery resolved to thingType zwave:horstmann_ssr302_00_000
2019-10-16 13:30:34.706 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery completed
2019-10-16 13:30:34.714 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery could not resolve to a thingType! 010F:0200:100A::2.1
2019-10-16 13:30:34.727 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery completed
2019-10-16 13:30:34.738 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery could not resolve to a thingType! 0002:0005:0003::2.51
2019-10-16 13:30:34.787 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 12: Device discovery completed
2019-10-16 13:30:34.796 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 12: Device discovery could not resolve to a thingType! 0148:0001:0001::0.4
2019-10-16 13:30:34.807 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 13: Device discovery completed
2019-10-16 13:30:34.815 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 13: Device discovery could not resolve to a thingType! 0118:0101:0103::1.4
2019-10-16 13:30:34.826 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Device discovery completed
2019-10-16 13:30:34.835 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Device discovery could not resolve to a thingType! 010F:0800:1001::2.6
2019-10-16 13:30:34.847 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 15: Device discovery completed
2019-10-16 13:30:34.855 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 15: Device discovery could not resolve to a thingType! 010F:0800:1001::2.6
2019-10-16 13:30:34.895 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 17: Device discovery completed
2019-10-16 13:30:34.903 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 17: Device discovery could not resolve to a thingType! 010F:0100:100A::2.2
2019-10-16 13:30:34.915 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 18: Device discovery completed
2019-10-16 13:30:34.919 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 18: Device discovery resolved to thingType zwave:aeon_dsb05_00_000
2019-10-16 13:30:34.929 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 19: Device discovery completed
2019-10-16 13:30:34.936 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 19: Device discovery could not resolve to a thingType! 010F:0200:100A::2.1
2019-10-16 13:30:34.947 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 23: Device discovery completed
2019-10-16 13:30:34.963 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 23: Device discovery could not resolve to a thingType! 0002:0005:0003::2.51
2019-10-16 13:30:34.975 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 24: Device discovery completed
2019-10-16 13:30:34.983 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 24: Device discovery could not resolve to a thingType! 013C:0002:000E::1.16
2019-10-16 13:30:35.026 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 25: Device discovery completed
2019-10-16 13:30:35.036 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 25: Device discovery could not resolve to a thingType! 0118:0101:0103::1.4
2019-10-16 13:30:35.049 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Device discovery completed
2019-10-16 13:30:35.062 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Device discovery could not resolve to a thingType! 0118:0202:0611::1.12
2019-10-16 13:30:35.075 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 27: Device discovery completed
2019-10-16 13:30:35.080 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 27: Device discovery resolved to thingType zwave:aeon_zw100_01_010
2019-10-16 13:30:35.094 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 28: Device discovery completed
2019-10-16 13:30:35.104 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 28: Device discovery could not resolve to a thingType! 010F:0800:1001::2.7
2019-10-16 13:30:35.143 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 29: Device discovery completed
2019-10-16 13:30:35.151 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 29: Device discovery could not resolve to a thingType! Manufacturer data not known.
2019-10-16 13:30:35.160 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:2f436676:node29' to inbox.

I have manually checked a couple of items with the database:

In Paper UI:
Z-Wave Node 007 (010F:0200:100A:2.1)
Unknown Device

In XML:
  <nodeId>7</nodeId>
  <version>4</version>
  <manufacturer>0x10f</manufacturer>
  <deviceId>0x100a</deviceId>
  <deviceType>0x200</deviceType>
  <listening>true</listening>
  <frequentlyListening>false</frequentlyListening>
  <routing>true</routing>
  <security>false</security>
  <beaming>true</beaming>
  <maxBaudRate>40000</maxBaudRate>
  <sleepDelay>1000</sleepDelay>
...
  <protocolVersion>3.42</protocolVersion>
  <applicationVersion>2.1</applicationVersion>

looks like it should have matched to the database entry:
FGS221 Double Relay Switch 2x1.5kW

and

In Paper UI:
Z-Wave Node 013 (0118:0101:0103:1.4)
Unknown Device

In XML:
  <nodeId>13</nodeId>
  <version>4</version>
  <manufacturer>0x118</manufacturer>
  <deviceId>0x103</deviceId>
  <deviceType>0x101</deviceType>
  <listening>true</listening>
  <frequentlyListening>false</frequentlyListening>
  <routing>true</routing>
  <security>false</security>
  <beaming>true</beaming>
  <maxBaudRate>40000</maxBaudRate>
  <sleepDelay>1000</sleepDelay>
...
  <protocolVersion>3.40</protocolVersion>
  <applicationVersion>1.4</applicationVersion>

looks like it should have matched to the database entry:
TZ68 Wall Plug

Comparing these with one of the few devices that is still matching in the database:

  <nodeId>27</nodeId>
  <version>4</version>
  <manufacturer>0x86</manufacturer>
  <deviceId>0x64</deviceId>
  <deviceType>0x2</deviceType>
  <listening>true</listening>
  <frequentlyListening>false</frequentlyListening>
  <routing>true</routing>
  <security>false</security>
  <beaming>true</beaming>
  <maxBaudRate>40000</maxBaudRate>
  <sleepDelay>1000</sleepDelay>
...
  <protocolVersion>4.54</protocolVersion>
  <applicationVersion>1.13</applicationVersion>

Correctly resolved to:
ZW100 Multisensor 6

So as best I can tell at this point, it looks like a “matching” issue introduced sometime in the last few snapshots. I’ve not been able to establish a pattern to differenctiate between the devices that are matched and those that are not.

As best I can guess I was probably a week or so behind with snapshot updates, prior to this problem. If I can find a way to work out what build numbers I moved from/to etc. I’ll post an update.

Any pointers on further diagnosis/resolution steps gratefully received.

Hardware is raspberry Pi running latest openHABian build (all upgrades / snapshots done via openhabian-config utility).

Thanks for any help, Andy

[Bruce_Osborne]

OK, you are running the latest unstable / snapshot build then.

[AndyMB (Andy)]

Fix in latest snapshot, worked for me.

github.com/openhab/org.openhab.binding.zwave

[kdsnet3410 (Kevin S)]

@Bruce_Osborne

You are running 2.5M3 then

Yes.

@AndyMB

Fix in latest snapshot, worked for me.

I uninstalled ZWave Binding from Paper UI

Downloaded the latest Zwave Binding from:
https://ci.openhab.org/job/openHAB2-Bundles/lastSuccessfulBuild/artifact/bindings/org.openhab.binding.zwave/target/

Added the Zigbee binding for the org.eclipse.smarthome.io.transport.serial dependency

Copied the zwave jar to the addons folder.

And now everything seems to be working now.

Thanks!

[5iver (Scott Rushworth)]

In the future, it may be easier to just do…

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

If you already have zwave installed through Paper UI, no other steps should be needed. Using this method, Karaf will resolve the dependencies for you, which is not just the serial transport feature, but xstream too.

[jwiseman (Mr. Wiseman (OH 4.2 Snapshot on Pi4))]

@kdsnet3410

Added the Zigbee binding for the org.eclipse.smarthome.io.transport.serial dependency

This reference above fixed my zWave issue when starting OH 2.4 up. I would have to, via Karaf console, stop/start the zWave binding for it to actually start the binding correctly. I try to run the latest zWave binding via manual drop in very few months.

Best, Jay

[kdsnet3410 (Kevin S)]

Thanks. I didnt know that would work when running running the Milestones. I though it you could only use that when running the latest snapshot.

[5iver (Scott Rushworth)]

You’re welcome! This method will work to update any addon, if you know the URL, on any release… even stable.