Trying to troubleshoot a number of things with Z-Wave since moving to a standalone Z-Wave JS server instance on a Windows 2022 server with the Hyper-V role, but anyway. Right now it was functioning and did a heal of the entire network. Everything returned back green except for a device still spinning that is battery based and one that is wired. The wired one failed though shows online. Error was:
assigning return route failed: The source and destination node must not be identical
Any idea?
I’d rejoin that one device with the busted route (that’s what that message says) then try to heal the battery device after.
Don’t forget you’ll have to wake the battery device to successfully heal it.
Thanks Nathan. So I don’t do anything beyond what I should have done, are we saying to go to Failed Nodes and Remove it? Then Include the device again?
Yes. Remove that one node. Then factory reset /exclude that one node and try to rejoin it… For some reason it thinks it should route through itself. Rather than fight, take it out and rejoin. After you fixed that one node, heal the battery one and see if it fixed both issues.
Thanks. When I go to Failed Noted for in this case Node 2 and click Remove I get:
Error while calling api removeFailedNode: The node removal process could not be started because the node responded to a ping. (ZW0360)
Then exclude it first.
Crap. This is a FGFS101 and have to turn the top to open it to exclude/include. It’s double sided taped to the wall and can’t get the top to turn open while on the wall. Think it’s because it’s modified to run on wall power and probably on pretty tight. Ugh…
I feel ya, I have to rejoin one of my aeotec sensor 6… Because it joined S0.
It’s mounted on a recessed mount in the ceiling… And the button is inside the housing… Bleh.
Ok that worked kind of. Had to use an exacto knife to get some sealant off the cover as I sealed the wires I mounted inside and then out since in a water area. Oddly I excluded the device then included it and all showed good. Did a heal for good measure and turned to failed. Did it again and worked. So not sure what that was about.
Side comment, wonder if this could be an issue as I can’t manually do this. Below is what my prior flood sensor had in it before exclude/include:
So the group points to itself. So it’s NodeID_2 pointing to NodeID_2. I know when i try and recreate that I can’t. Not an option to select that Node.
Yeah that’s not a valid association
Getting that one fixed may not fix your others but now it should not be hurting anything.
