Domoticz

Hello,

In the times of OZW 1.4, to remove nodes that were obviously failed (no more communication possible to trigger device exclusion, for instance because of HW failure or some device bug) but not market as "dead" by controller, I was doing this:

-Stop domoticz/zwave.
-Edit zwcfgXXX.xml, find node and remove it's whole COMMAND_CLASS_WAKE_UP section.
-Restart domoticz.

Then, at the end of modules interview (a few mn), failed nodes were marked "dead" by controller and could be remove using z-wave control panel:

- "Remove failed node" controller operation.

Problem: No more "dead" flag at domoticz restart after config edit+all node query ending, so removing such failed nodes does not work anymore.

If someone have a working solution for this: Have a Fibaro KeyFob that did not worked after Domoticz 2021.1 upgrade (from old stable v4.10717), showing zeroed IDs & not solved by wake-up etc... even exclusion was not possible: Had to factory reset it & worked after re-inclusion.

But no exclusion possible & not marked "dead", even after trying here-upper tip that used to work = help needed!

Thanks.

With zwavejs2mqtt, it's a breeze to remove dead nodes. It's available in a docker.

Sent from my SM-G980F using Tapatalk

heggink wrote: ↑Sunday 16 May 2021 8:41 With zwavejs2mqtt, it's a breeze to remove dead nodes. It's available in a docker.

Thanks for the info, but meantime I used zensys tool... Had to use a windows PC for this (still had an old double boot on one), a pain as I'm Linux only since years, but looks this worked.

Funny: Nop operation also looks to succeed (like checking if nod dead from OZW/Domoticz) from zensys tool but at least manage to remove a failed node anyway. So I think OZW just do not send the command if not marked dead. Otherwise it should work in the same way IMO. This makes this recovering this issue complex even if this should also be a breeze from OZW.

Procedure I used here, may help others:
https://help.aeotec.com/support/solutio ... ensys-tool