node-zwave-js: Cannot heal nodes on 700 series controller with firmware 7.11 and 7.16.2

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?

NO, my problem is NOT within Home Assistant or the ZWave JS integration

Is your problem within ZWaveJS2MQTT?

NO, my problem is NOT within ZWaveJS2MQTT

Checklist

Describe the bug

What causes the bug? It appears to be something in the combo Debian 11/Home Assistant Supervised.

What do you observe? Heal does not work anymore, for any node.

What did you expect to happen? Heal works.

Steps to reproduce the behavior:

  1. Install Home Assistant Supervised on Debian 11 following this guide: https://community.home-assistant.io/t/installing-home-assistant-supervised-on-a-raspberry-pi-with-debian-11/247116
  2. Install the Z-Wave JS to MQTT addon
  3. Go to the Z-Wave JS Ingress
  4. Try to heal any node

Previously I was using zwavejs2mqtt compiled from sources on my Raspberry Pi 2 with Raspberry Pi OS and my Aeotec Z-Pi 7. Now I moved to Debian 11 with Home Assistant Supervised and the Z-Wave JS to MQTT addon. Everything works (I can even re-interview nodes) but somehow it fails to heal them.

Device information

No response

How are you using node-zwave-js?

  • zwavejs2mqtt Docker image (latest)
  • zwavejs2mqtt Docker image (dev)
  • zwavejs2mqtt Docker manually built (please specify branches)
  • ioBroker.zwave2 adapter (please specify version)
  • HomeAssistant zwave_js integration (please specify version)
  • pkg
  • node-red-contrib-zwave-js (please specify version, double click node to find out)
  • Manually built from GitHub (please specify branch)
  • Other (please describe)

Which branches or versions?

version: node-zwave-js branch: 8.4.1 zwavejs2mqtt branch: 5.7.3

Did you change anything?

no

If yes, what did you change?

No response

Did this work before?

Yes (please describe)

If yes, where did it work?

Installing zwavejs2mqtt from source on Raspberry Pi OS.

Attach Driver Logfile

zwavejs_heal.log

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 94 (65 by maintainers)

Most upvoted comments

Interestingly, when I did it I’d actually forgotten to shutdown zjs2mqtt. I aborted at the boot loader so I don’t know if the update would have worked with it running but it should have at that point. Maybe we’re initializing the Z-Pi and that’s required? What do we do to open the port?

+2
blhoward2 on Oct 10, 2021 
2021-10-07T17:23:06.100Z CNTRLR   received version info:
                                    controller type: Bridge Controller
                                    library version: Z-Wave 7.11

As @AlCalzone mentioned, update the Stick to 7.15 (assuming I have found the correct line)

+2
marcus-j-davies on Oct 7, 2021

I sent this issue to them and explained about Simplicity Studio not working.

+1
blhoward2 on Oct 7, 2021

It can be easily updated? We have instructions to do it in Linux. Hang on.

+1
blhoward2 on Oct 7, 2021

Start from here. https://github.com/zwave-js/node-zwave-js/discussions/3319#discussioncomment-1309268

Short Version. Download Simplicity Studio, This will contain Gen 7 Firmware files, which you can use with Simplicity Studio, to update your Gen 7 Stick.

Previous versions of the Gen 7 FW has known issues with Healing. Disclaimer: I dont have a Gen 7

+1
marcus-j-davies on Oct 7, 2021
Read more comments on GitHub
← node-zwave-js: [bug] tcp://ip:port connection ETIMEDOUT error doesn't match `ZWaveErrorCodes.Driver_Failed`
node-zwave-js: ConfigurationCCBulkGet causes error when reading non-existant parameter →