Is the Z-Wave config "sticky" / cached on the USB device?

Configuration Z-Wave
1

I use a GoControl HUSBZB-1 hub, plugged into a RaspberryPi which is running hassio / HassOS 3.13.

Due to a power outage my Linear GD00Z-4 garage door opener went off-mesh, and several hours of fiddling haven’t got it back. I expect my next step is to delete the ZW integration altogether and then re-add my collection of ZW devices. Grrrr!!

There are dozens of threads on this forum, going back several years, re: ZW configuration. Sounds like some are out of date and shouldn’t be followed, but it’s not clear which to follow if I want optimum behavior.

Is it advised to simply follow the latest directions at https://www.home-assistant.io/docs/z-wave/installation, especially if I have secure devices like a garage door opener and door locks? For example, should I assume that my configurations.xml file includes the following, at minimum?:

zwave:
  usb_path: /dev/ttyACM0
  config_path: /config/z-wave/open-zwave/config
  network_key: (an appropriate 16-byte value)

Note: as of today I have a few auto-generated zwcfg_####.xml files in the root of my /config directory. If I follow latest guidance will I still see these XML files placed in /config by the system?

2

(Note: Changed title from “Is the Z-Wave documentation accurate and up-to-date?”)

I decided to blow up my Z-Wave integration and re-adopt the devices I want to carry forward. But it’s not as simple as it sounds!

No matter my efforts to erase the former Z-Wave setup (devices, entities, etc.), when I re-add the ZW integration my former devices are re-enumerated and brought back into the config, including the zombie devices I want to leave behind.

My current theory is that the latest config gets cached on the USB device (Nortek HUSBZB-1 Z-Wave + Zigbee), and I would take out the USB stick except I don’t want to mess with my Zigbee setup.

While under other scenarios I might appreciate HA’s resiliency, in this case it’s annoying. How do I achieve a clean start?

p.s. the “Remove Failed Node” spoofing trick only seems to work on valid nodes, not on bona fide failed nodes. Those appear to enjoy an eternal life in zombie mode, as evidenced by this on the OZW log:
WARNING: Received reply to FUNC_ID_ZW_REMOVE_FAILED_NODE_ID - Node not found

3

I can speak for the Aeotec hub that you have to use their service tool to delete a ghost/failed device. I don’t know if GoControl has a similar tool.

4

Correct the zwave association are stored on the stick they all do that.

Techncially you’d factory reset the stick, but I am pretty sure that’d fubar your zigbee network as well.

5

Thanks for the replies. I ended up shutting down HA, removing the stick, inserting into my Windows 10 box, and firing up the Z-Wave PC software (version 5.39, non-standard driver install process needed).

I clicked on [ Controller View --> Reset Controller ] to reset the stick, then put the stick back into my RPi running Hassio. The Zigbee config wasn’t affected by this, and I got the desired result: all of the nodes have been removed from my HA Z-wave setup.

Warning: clicking on [ Controller View --> Reset Controller ] in the PC software doesn’t come with any explanation / warning / “are you sure” kind of message, so use with caution.

1 Like