Geedsen
October 23, 2023, 8:16pm
1
I just updated HA to the latest version (Core and other things, everything that could be updated).
2023-10-23 21:32:40.918 WARNING (MainThread) [homeassistant.config_entries] Config entry ‘Z-Wave JS’ for zwave_js integration not ready yet: None; Retrying in background
Geedsen
October 23, 2023, 8:54pm
2
I did now find that this issue was mentioned two weeks ago already here Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value · Issue #101532 · home-assistant/core · GitHub
I had similar issues last week after a z-wave update. In my case, I had two devices that appeared ‘dead’. This caused the entire system to be sluggish. I excluded those device and then re-included and that cleared everything up.
Geedsen
October 23, 2023, 9:19pm
4
Just went back to version 2023.9.2 . Same problem
freshcoast
October 23, 2023, 11:07pm
5
You probably need to disable soft-reset in the add-on configuration.
opened 09:39AM - 29 Sep 23 UTC
Restarting (aka. soft-resetting) a Z-Wave controller is automatically done at st… artup of Z-Wave JS to start from a clean state where the controller isn't doing anything weird. This is also necessary in certain situations, e.g. to apply configuration changes, or to work around firmware bugs.
Simply put, for **700 and 800 series** controllers, restarting is **required** from time to time.
For **500 series** and older, it is strongly **recommended**. Unfortunately, 500 series controllers may reconnect to USB when restarted, which can cause issues in certain setups. This is especially true in VMs, where the USB passthrough stops working unless the VM is configured correctly.
Until the update to v12, Z-Wave JS would detect these situations where the controller stayed unavailable after restarting and would disable soft-reset going forward. However this feature caused false negatives that could be nearly impossible to recover from, aside from manually editing a file that can be hard to get to. As a result, it was removed and the burden is now on the user to ensure their environment is set up correctly.
#### There are a few known solutions to this:
1. Prefer `/dev/serial/by-id/...` paths over `/dev/tty...` in case the path changes after reconnecting
1. When using the Aeotec Gen5 or Gen5+, [updating the firmware to 1.2](https://aeotec.freshdesk.com/support/solutions/articles/6000252294-z-stick-gen5-v1-02-firmware-update) can help, plus you get SmartStart support for free. **Warning:** A failed update can brick the controller, proceed at your own risk or look at other options first.
1. If you're using ESXi, [updating to 7.0u1](https://community.home-assistant.io/t/vmware-esxi-7-0-usb-compatibility/185939) can help.
1. For some other VMs, [this document](https://github.com/AlCalzone/ioBroker.zwave2/blob/master/docs/en/vm-usb.md) contains instructions for properly setting up USB passthrough.
1. [Expose the serial port via TCP](https://zwave-js.github.io/node-zwave-js/#/usage/tcp-connection), either from the host or a different device.
1. As a last measure, [soft-reset can be disabled](https://zwave-js.github.io/zwave-js-ui/#/usage/setup?id=z-wave) in the Z-Wave JS UI settings. The stick may need to be re-plugged, or the VM may need a restart before it starts working again. It is preferable to try the other solutions first, since being able to restart the stick has the aforementioned upsides.
Solution: disable Soft-Reset and reboot the System
EDIT: Failed again after about 1 hour.
I have 13 devices. I don’t want to reconfigure all of them again.