Z-Wave JS ZMNHJD going dead

[Toukite]

Describe the issue you are experiencing

Hello,

I am using multiple Qubino ZMNHJD devices to manage my heating system. One of them is regularily set as 'dead' in Home Assistant Z-Wave JS (at least once a day).

I am not sure about how to identify the root cause for this, all other devices are working well (including ones that are furthest from the Z-Stick Aeotec controller than the failing device)

As soon as I go to Configuration > Integrations > Z-Wave JS, click on 'Devices', select my failing device and click on the 'RE-INTERVIEW DEVICE' button, issue is resolved (until the next failure).

Unfortunately, this action is manual. I tried using the service zwave_js.ping, but this is not working. I have an automation that sends me a notification as soon as a Z-Wave device is going dead. But I would very much like to have also the possibility to automatically re-interview the device when this happens (since this is fixing the issue) using a service and not a GUI button.

So this is a two-in-one ticket: first, to investigate the bug causing this device to go dead ; and second, to ask for a zwave_js.reinterview service as a possible workaround.

Thanks & Regards

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

Z-Wave JS

What is the version of the add-on?

0.1.49

Steps to reproduce the issue

N/A

Anything in the Supervisor logs that might be useful for us?

No response

Anything in the add-on logs that might be useful for us?

No response

Additional information

No response

[probot-home-assistant[bot]]

zwave_js documentation zwave_js source _{^{(message by IssueLinks)}}

[probot-home-assistant[bot]]

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

[MartinHjelmare]

Please create a dump of your Z-Wave network and upload the dump as a text file here.

The dump tool is available in the configuration panel of the Z-Wave JS integration, reached from the integrations page in the Home Assistant GUI.

The network dump will help us troubleshoot your device.

Thanks!

[Toukite]

Hello,

Please find the network dump below: zwave_js_dump.txt

However, I had the warning " Some of your devices didn't respond and are assumed dead. These will not be fully exported. " Indeed, I was mistaken, today's manual re-interview did not succeed after this morning's failure (on the previous days, it did).

I also managed to get the following logs as I am able to connect as root on HassOS: zwave_js_logs.txt The relevant device is 'Node 013'

Regards

[xtego]

I am having a similar issue with my zwave-js network. Randomly I lose control over devices as they are presumed dead. There doesn't seem to be any rhyme or reason as to which devices go inactive. It seems to happen more frequently with inovelli devices, but not exclusively. The devices can be brought back online by reinterviewing them, but this becomes very annoying having to do this multiple times a week. This never happened prior to upgrading to zwave-js.

I have more details on the issue over on the inovelli forum: https://community.inovelli.com/t/issues-with-inovelli-switches-and-bulbs-with-home-assistant-zwave-js/9668

[mikesumbler]

Hi Ditto. Dump attached - Node 5 is the issue. The device is an older z wave device (Horstman Thermostat Switch / Secure 322) which perhaps has some issue with its protocol zwave_js_dump.txt ?

[MartinHjelmare]

If devices go dead it's most likely a connection problem to the device. Connection problems to devices are rarely the fault of the driver or integration but due to faulty device or that messages are having trouble reaching the device. This can be due to Z-Wave network issues.

[mikesumbler]

Could well be - just been watching the debugger and got this showing up as the device went unavailable:

2021-12-08 14:17:53.973 WARN GATEWAY: Unable to discover climate device, there is no valid setpoint valueId

[mikesumbler]

Removed a clothes airer and ironing board (both metal) from near the switch and seems to now be behaving - apparently signal issue. Will monitor. Thanks Mike

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.