I messed up my zwave controller

Tags: #<Tag:0x00007f43316b52a8>

I’ve about 20 devices in my zwave network, running quite reliable during the last 2 years but had some ghost devices left from the very beginning and so I tried to remove them with all tipps I found on the forum. In the end I used Zensys tool on the Aeotec z-stick Gen5 to delete those ghost nodes. (Remove a Failed Node using Zensys Tool : Aeotec Group).
so far so good, I had a clean and proper working zwave network. recently I upgraded OH from 2.5.9 to 2.5.11 and some zwave items refused to work (Neo Coolcam Window Sensor, Neo Coolcam Dual lightswitch, Spirit z-wave thermostat). I can heal, wakeup or do whatever I want I don’t get them back to business. I can include a device via paper UI, it reports as online but it does not react on any action, nor does it send any status. strangely, when I exclude node59 I get node63 reported as excluded. so it appears that the config of the controller and the OH zwave binding is somehow out-of-sync.

2021-01-02 20:08:06.239 [hingStatusInfoChangedEvent] - 'zwave:device:d7de781e:node62' changed from ONLINE to OFFLINE: Node was excluded from the controller

is there anything I can do to further debug and fix this? thanks for your help!

For the Spirit, there was a database issue in the binding for 2.5.11 that has been fixed in a snapshot version. The entry was missing from the binding.

Use the script to update to a snapshot version of the binding. You can then delete & re-add the Thing to get the changes.
Zigbee and Z-Wave manual install script - Tutorials & Examples - openHAB Community

1 Like

I just ran the script, unfortunately it did not update my zwave binding as expected. I then switched via openhabian to the latest OH snapshot to see if that works.
little confused now as the scripts says I’m on OH 2.5.12. but openhabian and karaf tell me I’m on 2.5.11
at least the zwave binding still keeps on 2.5.11 and some devices are unknown
2021-01-04 19:11:27.020 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 44: Device discovery could not resolve to a thingType! 0148:0003:0001::0.16

2021-01-04 19:11:27.027 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 50: Device discovery could not resolve to a thingType! 0148:0003:0001::0.16

2021-01-04 19:11:27.031 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 52: Device discovery could not resolve to a thingType! Manufacturer data not known.

2021-01-04 19:11:27.034 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 55: Device discovery could not resolve to a thingType! Manufacturer data not known.

… any idea how to proceed?
thanks

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.12
Requested Z-Wave version: openHAB snapshot

Is this correct?
1) Yes, start now                      3) Exit
2) No, take me back to the first menu
#? 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:
... 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 !!!!!

[15:42:47] matthias@openhab25:/usr/share/openhab2/addons$ openhab-cli console

Logging in as openhab
Password:

                          __  _____    ____
  ____  ____  ___  ____  / / / /   |  / __ )
 / __ \/ __ \/ _ \/ __ \/ /_/ / /| | / __  |
/ /_/ / /_/ /  __/ / / / __  / ___ |/ /_/ /
\____/ .___/\___/_/ /_/_/ /_/_/  |_/_____/
    /_/                        2.5.11
                               Release Build

Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown openHAB.

openhab> list -s | grep zwave
305 x Active x  80 x 2.5.11                  x org.openhab.binding.zwave
openhab>

Remove the Z-Wave binding & try again. I think that is the proper path, right @5iver ?

2021-01-04 19:24:02.309 [hingStatusInfoChangedEvent] - 'zwave:serial_zstick:d7de781e' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)

2021-01-04 19:24:02.656 [thome.event.ExtensionEvent] - Extension 'binding-zwave' has been uninstalled.

2021-01-04 19:24:34.438 [thome.event.ExtensionEvent] - Extension 'binding-zwave' has been installed.

2021-01-04 19:25:56.955 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 65: Device discovery could not resolve to a thingType! 0148:0003:0001::0.16

==> /var/log/openhab2/events.log <==

2021-01-04 19:25:56.956 [home.event.InboxAddedEvent] - Discovery Result with UID 'zwave:device:d7de781e:node65' has been added.

==> /var/log/openhab2/openhab.log <==

2021-01-04 19:25:56.956 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:d7de781e:node65' to inbox.

2021-01-04 19:25:56.963 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 67: Device discovery could not resolve to a thingType! Manufacturer data not known.

2021-01-04 19:25:56.970 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 68: Device discovery could not resolve to a thingType! Manufacturer data not known.

2021-01-04 19:25:57.000 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 44: Device discovery could not resolve to a thingType! 0148:0003:0001::0.16

2021-01-04 19:25:57.007 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 50: Device discovery could not resolve to a thingType! 0148:0003:0001::0.16

2021-01-04 19:25:57.011 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 52: Device discovery could not resolve to a thingType! Manufacturer data not known.

2021-01-04 19:25:57.015 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 55: Device discovery could not resolve to a thingType! Manufacturer data not known.

2021-01-04 19:25:57.019 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 59: Device discovery could not resolve to a thingType! Manufacturer data not known.

2021-01-04 19:25:57.022 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 61: Device discovery could not resolve to a thingType! Manufacturer data not known.

still unknown devices after reinstall of zwave binding.
shouldn’t it list 2.5.12 in karaf?

openhab> list -s | grep zwave
309 x Active x 80 x 2.5.11 x org.openhab.binding.zwave

You uninstalled the binding & then tried the update script again? It still looks like 2.5.11.

yes, I always tried to upgrade the binding. now I uninstalled it via PaperUI and installed it via script and voilá, it’s updated!:

openhab> list -s | grep zwave
310 x Active x 80 x 2.5.12.202101030439 x org.openhab.binding.zwave

the spirit thermostat is now a known device. I’ve got a ton of ghost nodes from the tests and a neo coolcam window sensor refuses to work…
I’ll clean up and report back… thanks so far to help on the binding update!

1 Like

The cheap Chinese Neo Coolcam stuff can be problematic. For some devices I found I needed to factory reset them before they would successfully include into the network.

Battery powered device need to be woken up multiple times for the binding to complete discovery after the Thing is added to OH.

right, those battery operated devices can be tricky. not only the cheap chinese ones, I have some Fibaro devices that drop battery status from 100% to 0% in just one day, others reported online with 100% battery but already dead as the battery was gone…

my zwave network is still weired, spirit and coolcam devices are now included and known by their type/model, so thats fine. unfortunately they don’t report any changes and don’t list to commands.
eg. node 69 reports this when manually waked up, but the related items don’t get any updates…

2021-01-05 16:22:24.114 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:d7de781e:node69’ has been updated.

2021-01-05 16:22:26.418 [hingStatusInfoChangedEvent] - ‘zwave:device:d7de781e:node69’ changed from ONLINE to ONLINE: Node initialising: SECURITY_REPORT

2021-01-05 16:22:26.420 [hingStatusInfoChangedEvent] - ‘zwave:device:d7de781e:node69’ changed from ONLINE: Node initialising: SECURITY_REPORT to ONLINE: Node initialising: MANUFACTURER

2021-01-05 16:22:26.676 [hingStatusInfoChangedEvent] - ‘zwave:device:d7de781e:node69’ changed from ONLINE: Node initialising: MANUFACTURER to ONLINE: Node initialising: APP_VERSION

2021-01-05 16:22:32.008 [hingStatusInfoChangedEvent] - ‘zwave:device:d7de781e:node69’ changed from ONLINE: Node initialising: APP_VERSION to ONLINE: Node initialising: DISCOVERY_COMPLETE

2021-01-05 16:22:32.010 [hingStatusInfoChangedEvent] - ‘zwave:device:d7de781e:node69’ changed from ONLINE: Node initialising: DISCOVERY_COMPLETE to ONLINE: Node initialising: VERSION

2021-01-05 16:24:34.578 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:d7de781e:node69’ has been updated.

2021-01-05 16:24:34.626 [hingStatusInfoChangedEvent] - ‘zwave:device:d7de781e:node69’ changed from ONLINE: Node initialising: VERSION to OFFLINE (BRIDGE_OFFLINE): Controller is offline

2021-01-05 16:24:34.627 [hingStatusInfoChangedEvent] - ‘zwave:device:d7de781e:node69’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE

Habmin shows a little more status information:

I would simply factory reset all devices including the zwave stick, but some of my devices are mounted behind wall-switches which will be a fight to get to the HW reset button…

there was a zwave logging tool some time ago, but that link doesn’t exist anymore. is there a tool to further debug my problem?

did you try to activate DEBUG log to see which updates are being sent on which channels?
Here’s how to do so: https://www.cd-jackson.com/index.php/openhab/5-zwave-debugging-openhab 1
Also the Log Viewer at https://www.cd-jackson.com/index.php/openhab/zwave-log-viewer 2 is very helpful for understanding the log messages.

HABmin shows the devices have not responded to the binding with their information to complete discovery.

The log viewer is here.