Moved HA and lost Zwave mostly

[urbanscribe (alex)]

Moved from PI to OS X instance, all hell broke loose
(can confirm that running HA on OS X is obviously way faster and effective for response time for automation etc)

Question: how do i get 1) full Zwave network running again, 2) my proper node metadata identified.

Followed instructions and moved Aeotec Stick to new system
Copied final zwcfg_XXX.xml + files to Mac
Started new HA

Redid this 3 times using thread validated multiple but similar instructions, same results

Normal

1. Zwave restarts just fine

Symptoms after transition

1. Zwave network under config shows undefined nodes (and all but two states are unavailable)
   with Node :undefined undefined for all real nodes (which is existed before)
   

   

2. Nonetheless, 2 nodes show up under their friendly name and report new values (temp in this case)
   Even for those nodes which seem to be reporting the Zwave still shows Node: unavailable unavailable
   here is one:
   

3. No OZW_Log.txt log being written. Had to add logger logging to see any Zwave activity (example below)
   i can copy the old one (from Pi) or delete it completely and no activity ever.

4. Leaving the Network to heal fix itself for 1 day does nothing,. No node identified.

5. If i take the Stick back to the old Pi and fire it up i get the full list back to normal
   

   

Nonetheless here is some of the log dump which seems to be showing SOME success in network activity
Please note Node 8 and 12 are repeater and not the sensors reporting temp above, they still show as undefined undefined

2020-01-27 10:07:04.881 Info, Node008, Sending (Command) message (Callback ID=0x00, Expected Reply=0x80) - Get Routing Info (Node=8): 0x01, 0x07, 0x00, 0x80, 0x08, 0x00, 0x00, 0x03, 0x73
2020-01-27 10:07:04.887 Detail, Node008,   Received: 0x01, 0x20, 0x01, 0x80, 0x61, 0x08, 0xea, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xdd
2020-01-27 10:07:04.887 Detail, 
2020-01-27 10:07:04.887 Info, Node008, Received reply to FUNC_ID_ZW_GET_ROUTING_INFO
2020-01-27 10:07:04.887 Info, Node008,     Neighbors of this node are:
2020-01-27 10:07:04.887 Info, Node008,     Node 1
2020-01-27 10:07:04.887 Info, Node008,     Node 6
2020-01-27 10:07:04.887 Info, Node008,     Node 7
2020-01-27 10:07:04.887 Info, Node008,     Node 12
2020-01-27 10:07:04.887 Info, Node008,     Node 18
2020-01-27 10:07:04.887 Info, Node008,     Node 20
2020-01-27 10:07:04.887 Info, Node008,     Node 22
2020-01-27 10:07:04.887 Info, Node008,     Node 23
2020-01-27 10:07:04.887 Info, Node008,     Node 24
2020-01-27 10:07:04.887 Detail, Node008,   Expected reply was received
2020-01-27 10:07:04.887 Detail, Node008,   Message transaction complete
2020-01-27 10:07:04.887 Detail, 
2020-01-27 10:07:04.887 Detail, Node008, Removing current message
2020-01-27 10:07:04.887 Detail, Node012, Query Stage Complete (Associations)
2020-01-27 10:07:04.887 Detail, Node012, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Neighbors live=1
2020-01-27 10:07:04.887 Detail, Node012, QueryStage_Neighbors
2020-01-27 10:07:04.887 Detail, Requesting routing info (neighbor list) for Node 12
2020-01-27 10:07:04.887 Detail, Node012, Queuing (Command) Get Routing Info (Node=12): 0x01, 0x07, 0x00, 0x80, 0x0c, 0x00, 0x00, 0x03, 0x77
2020-01-27 10:07:04.887 Detail, Node012, Queuing (Query) Query Stage Complete (Neighbors)
2020-01-27 10:07:04.887 Detail, 
2020-01-27 10:07:04.887 Info, Node012, Sending (Command) message (Callback ID=0x00, Expected Reply=0x80) - Get Routing Info (Node=12): 0x01, 0x07, 0x00, 0x80, 0x0c, 0x00, 0x00, 0x03, 0x77
2020-01-27 10:07:04.893 Detail, Node012,   Received: 0x01, 0x20, 0x01, 0x80, 0xe0, 0x00, 0x22, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x9c
2020-01-27 10:07:04.893 Detail, 
2020-01-27 10:07:04.893 Info, Node012, Received reply to FUNC_ID_ZW_GET_ROUTING_INFO
2020-01-27 10:07:04.893 Info, Node012,     Neighbors of this node are:
2020-01-27 10:07:04.893 Info, Node012,     Node 6
2020-01-27 10:07:04.893 Info, Node012,     Node 7
2020-01-27 10:07:04.893 Info, Node012,     Node 8
2020-01-27 10:07:04.893 Info, Node012,     Node 18
2020-01-27 10:07:04.893 Info, Node012,     Node 22
2020-01-27 10:07:04.893 Detail,   Expected reply was received
2020-01-27 10:07:04.893 Detail,   Message transaction complete

notes on Q

• some have mentioned data stored in .storage which needs to move also
• would like to get the OZW_Log.txt logger to work instead of spamming the main log
• copying the zwcfg_XXX.xml seem to have NO impact
• what about the pyozw.sqlite file, i’ve copied it also in some testing with no impact
• i’m ignoring (and not copying in my main research thread) zwscene.xml which seems mostly empty
• USB path for OS X is verified and works, some nodes reporting and properly identified and changed in config files
• I did check permissions on OZW_Log.txt and set chmod 777 OZW_Log.txt

kinda ran out of Community threads to try out and ideas

[flamingm0e]

@urbanscribe

some have mentioned data stored in .storage which needs to move also

Have you tried this?

Your entities that come from the Integrations page in your frontend get added in here.

[urbanscribe (alex)]

thanks flaming, yes i did copy everything. then had to clean up user ID etc, that did not change outcome for this Zwave issue.

[dap35]

Where any of the nodes added in secure mode? If so, you would also need the network key from your previous setup.

[walt]

Not sure why, but I had to use the “cu” /dev device under Mac OS X with the HUSBZB-1 which should have the same chip as your Aeotec.

zwave:
  usb_path: /dev/cu.GoControl_zwave

[urbanscribe (alex)]

thanks for asking. None were secure. no network key in the original working setup

[urbanscribe (alex)]

agreed mine also

  usb_path: /dev/cu.usbmodem641

[FredTheFrog (Keith)]

Could this be the modemmanager package interfering?

[Atle_Ravndal]

I experienced the same problem after upgrading from hassio 0.104.2 to 0.104.3. I’ve checked the .storage/core.* files and zwcfg_##.xml and does not find any changes after the upgrade. After several restarts of hassio, some of the zwave devices has appeared but the rest is still marked as “Node: undefined undefined”.

[mitchese (Sean)]

I have the same issue without changing of hardware. My system is hassio on a rpi3. I switched from an SD card to a USB stick for booting, and in doing so I installed a fresh copy of hassio on the USB drive and did a snapshot restoration.

After restoration, I have two or three z-wave devices which are reporting values in the frontend, but all of my nodes in the zwave management are dining area (Node:undefined undefined)

Looking at the ozw log, the nodes appear to be there as I can see power consumption and sensor values for the nodes.

[mitchese (Sean)]

I’ve done a bunch of refreshing and clicking around trying to diagnose the issue, and suddenly most things are restored - at least all of my nodes are currently in a CacheLoad and it seems to be iterating through everything and re-building the network.

I did not restore any additional files under .storage. I don’t know exactly what I did to restore it, but I suspect it is something along the lines of doing a “Refresh Node” of the zwave stick itself, then stopping and starting the zwave network.

The battery devices (which are sleeping) are still in the broken “undefined undefined” state. I am trying a zwave.refresh_node manual call with my node_id, and I will report back if this works

[urbanscribe (alex)]

not that it will help much, i had to migrated to a hass.io/VirtualBox install on an old mac mini and after getting the USB passthrough to work i was able to restore the working config from the aeotec z stick.

it’s important to note that moving the stick from pi to the vnv (non virtual box) instance broke the z wave indetification (as reported above) but that putting the stick back on the Pi with HA 104.3 did work with all nodes reporting and identified. could never get it to work on OSX/HAvnv but all worked eventually in OSX/VirtualBox/Hassio

[joselito1 (jose litomans)]

I have disabled modemmanager long time ago, but got node:undefined undefined

few weeks ago: https://imgur.com/a/lmkjivr

[stephenmarcantonio]

This happened to me, and it looks like something caused my zwcfg_*.xml file to be corrupted with a lot of important values replaced with zeros and defaults.

For example, these lines in the working file…

	<Node id="8" name="" location="" basic="4" generic="33" specific="1" roletype="5" devicetype="3079" nodetype="0" type="Routing Multilevel Sensor" listening="true" frequentListening="false" beaming="true" routing="true" max_baud_rate="40000" version="4" secured="true" query_stage="Complete">
		<Manufacturer id="86" name="AEON Labs">
			<Product type="2" id="64" name="ZW100 MultiSensor 6" />

…became these lines in the broken file…

	<Node id="8" name="" location="" basic="4" generic="33" specific="1" type="Routing Multilevel Sensor" listening="true" frequentListening="false" beaming="true" routing="true" max_baud_rate="40000" version="4" query_stage="CacheLoad">
		<Manufacturer id="0" name="">
			<Product type="0" id="0" name="" />

I got it working by stopping the homeassistant container, restoring an old version of the file and starting the container again. Unfortunately I don’t know what caused the problem.

[krissen (Kristian Niemi)]

There’s a github issue that seems related.