-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
Z-Wave nodes not working anymore #38110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This comment has been minimized.
This comment has been minimized.
zwave documentation |
Hey there @home-assistant/z-wave, mind taking a look at this issue as its been labeled with an integration ( |
I am finding on restart of 0.113.1 the zwave network is not starting and I have to manually go into the integration to start it. |
@jurgenweber Same for me. Annoying. Any workaround ? |
yeah, my issue was nothing to do with zwave... HASS was not starting up, it was being blocked by a bad integration or something I am unsure. In the end I feel the issue was related to #38134 (I was switching the logging on and off with the problems, I found that when on debug it wold work and when not it would not.. but then magically it worked.. I dunno) but, my testing was inconclusive. |
Works again in 0.113.1 |
@jurgenweber I'm hitting that as well w/ 0.113.1 (#38274), I'm going to try putting core to debug logging. |
Uh oh!
There was an error while loading. Please reload this page.
The problem
Open Z-Wave is not working anymore, .xml configuration of existing nodes are corrupted (reproducable) on startup.
Environment
Docker on Synology
Problem-relevant
configuration.yaml
Traceback/Error logs
N/A
Additional information
The text was updated successfully, but these errors were encountered: