mark battery device as dead for removing

michapr commented 8 years ago

If you will have dead battery devices (maybe while testing with different controllers without excluding it before - or if defective device,..) you can not remove the node immediately.

Would be nice to have an option "mark device as dead" so that node could be removed from network immediately. Controllers support it. In this time it take a long time until such a dead device will be removed.

Maybe issue is duplicated, but didn't found it. I think I'm not the first one who is missing this ;) If duplicated, then sorry,....

nechry commented 8 years ago

Yes +1 for this feature if is possible.

My current workaround is stop network edit node remove wakeup CC xml element and restart network then the controller think the device is dead.

michapr commented 6 years ago

Can this be implemented? As sample in Z-Way I can mark a device as broken - and then remoce it from controller. Just now I have in result of testing (and defective devices) a lot of invalid nodes in my list. Would be really nice if it can be marked and removed.

Thanks!

joydashy commented 6 years ago

Would be a very handy feature, having a lot of trouble getting rid of ghost devices the controller still considers to be alive, but they are not!

daringer commented 5 years ago

bump, I am the https://github.com/daringer/zwave-core developer, the current goal is to have a modern ozwcp replacement and an easy standalone z-wave configuration frontend. I am also struggling with the removal of dead battery nodes and would highly appreciate any workaround or hack you guys made to remove a node which cannot answer anymore.

@nechry, could you maybe be a little more precise what you do within the xml file?

@michapr, any more info about the Z-Way solution, what's their zwave backend? openzwave? any hint where to look to get details of the process they apply?

(FYI, for me I have several nodes which have somehow lost the association with the zwave controller, thus are unreachable and currently not removable)

EDIT:

@nechry, do I correctly understand that you are suggesting to remove the <CommandClass id="132">....<../> xml-sub-tree within the to-be-deleted node. Means CacheLoad query stage would not "know" anymore that this is a wake-up device? Sounds like a plan, will try it.
Another possibility I came up with: There is an "AssumeAwake" option to be provided for network/zwave-controller startup. It's rarely documented somewhere and haven't seen any tool providing this option, but at least this would be "less hacky"

In general, is it really true that there is simply no proper solution from zwave-protocol side?

Even openzwave.com openly suggests to hard-reset the controller, which is absolutely not an option, i.e., re-adding all nodes.

In proprietary zwave stations this issue seems simply hidden from the user as I've also observed skipped node-ids within those systems once deletion for such nodes is issued from user-side.

Fishwaldo commented 5 years ago

Have you tried the Manager::HasNodeFailed Call? This should get the Controller to check the node.

http://www.openzwave.com/dev/classOpenZWave_1_1Manager.html#a8000a9c5faf089be93daa63e92573fd5

michapr commented 5 years ago

@daringer : Z-Way is an own certified software solution - I have taken this sample (some years ago :) ) only as reference. Today many commercial solutions (as sample Zipato, ...) can remove any device from controller, even battery nodes. Would be really good if this will be possible in OZW, even while testing devices it happen, that device must be deleted.

nechry commented 5 years ago

@daringer sorry for late answer. Yes this is exactly I perform to mark a Battery operated device as dead. To do this You must stop the network, remove the ....<../> xml-sub-tree within the to-be-deleted node and restart the network. You can found my helper : https://github.com/jeedom/plugin-openzwave/blob/beta/resources/openzwaved/ozwave/node_utils.py#L178

@Fishwaldo unfortunately the Manager::HasNodeFailed call will never mark a device if they can Sleep. With this hack I remove the capability in the cache.

@Fishwaldo If we implement this hack in openzwave, the best would be not to have to restart the network and force the taking into account of the suppression of the CC Wakeup.

daringer commented 5 years ago

@nechry, in fact this is the only solution, which worked for me so far to remove a dead battery device. Out of curiosity: is this intended behavior from the zwave - specification point of view?

anyways, thanks a lot works for me :wave:

nechry commented 5 years ago

@daringer No, it's more of an interpretation in the library. So this hacking does a simple works-around.

OpenZWave / open-zwave

mark battery device as dead for removing #808