FAKRO covers go into DEAD state
vyagi opened this issue · 1 comments
Problem/Motivation
I have 4 FAKRO window covers (ARZ solar). I bought them in May and I have been using then since then every day. However, despite working fine for 4-5 months, now they go dead very often - almost each of them becomes dead at least once a day. I tried to ping them with HomeAssistant automation every 5 minutes but it didn't help. Apart from the covers I have bought a z-wave controlled socket which acts (or should) act as an extender and I also bought an actual stand-alone zwave extender. The problem is that when I go to the network graph, all the devices are connected directly to the controller which is in my garage. The covers have extender and the socket very close so it would be better if they use them as repeaters. This does not look to be the case when I go to the Network graph in ZwaveJS UI. What is interesting I am able to click a device in the network graph and click Priority route-> SET. Then I can choose a socket or extender (or both) and click SET. This can help in waking up the cover but it does not get updated in the Node properties. SOMETIMES it gets updated in the map but only for short time (like a day or two).
Expected behavior
I assume that I can expect the Primary Route -> SET to get effect in the node properties. I also assume that I should expect the devices to use the repeaters.
Actual behavior
It does not work like this. Setting Primary Route does not get reflected in the node properties. The device do not seem to use the extenders available in the network
Steps to reproduce
(How can someone else make/see it happen)
Proposed changes
It would be nice if it worked as (I think) it should. Nevertheless, if it works like it should (and I am simply mistaken how it should work), it would be nice to have a programmatic way to bring the node from the dead. As i mentioned it is done by going to the node in the graph, clicking it and set the primary route - then node becomes alive again. If this was programatically available for example through Node-red automation, it would be a workaround enough.
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!