Z-wave js ui crashes when saving settings

HAOS Supervised on Raspberry Pi 3. Brand new install. First installed Z2M and everything works fine.

I now want to add back my z-wave devices using my old network keys. I enter the serial port, the 4 keys, and generate random keys for long range (I did not have any long range keys from before).

I click save. The wheel keeps spinning then Home Assistant reboots/restarts after a few minutes.

1 Like

Hi @kaws I’m having the same issue, In my case it works if I do a fresh install of the haos. But as I do a restart of the host it breakes. When I detach the zwave stick ( aeotec Zstick Gen 5+ ) HAOS keeps running well.
At this point if I disable the Zwave jS UI ( I have tryied with Zwave js as well ) and the re-insert the zstick the system keeps working.
At the moment I start the component ( or when I save the configuration if it is not already set ) the system keeps restarting. The errors seems to be related to the storage, I’ll post here asap.
Did you found a solution?
Thanks

Hello,
It sounds like you’re encountering an issue with adding your Z-Wave devices after a fresh install of HAOS on your Raspberry Pi 3. Here are a few steps to troubleshoot: NCEdCloud Org

  1. Check Logs: Review the Home Assistant logs for any error messages that might give clues about what’s causing the issue.
  2. Verify Network Keys: Ensure that the network keys you entered are correct and match the keys used in your previous setup.
  3. Update Z-Wave JS: Make sure you have the latest version of Z-Wave JS installed, as updates often include bug fixes.
  4. Restart Services: Try restarting the Z-Wave JS service manually from the Home Assistant interface.
  5. Check USB Path: Verify that the USB path to your Z-Wave stick is correct in your configuration.

If the issue persists, consider reaching out to the Home Assistant community or support for further assistance.

Best regards,
Jennifer Block

Not sure which version you are running or if you’ve seen this.

I downgraded 1-2 versions and everything works fine.

I have not upgraded or looked to see if this has been resolved.