core: Zwave not starting up
Zwave devices set to unavailable. other not responding
Environment
- Home Assistant release with the issue: 0.107.0
- Last working Home Assistant release (if known): 0.106.x tried going back but no luck
- Operating environment (Hass.io/Docker/Windows/etc.): Unraid docker
- Integration causing this issue: zwave
- Link to integration documentation on our website:
Problem-relevant configuration.yaml
zwave: usb_path: /dev/ttyACM0 network_key: !secret network_key
Traceback/Error logs
2020-03-21 08:41:48 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 14 not ready after 30 seconds, continuing anyway 2020-03-21 08:41:48 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 14 Sensor (node_id: 14) not ready after 30 seconds, continuing anyway 2020-03-21 08:41:49 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 36 not ready after 30 seconds, continuing anyway 2020-03-21 08:41:49 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 36 Sensor (node_id: 36) not ready after 30 seconds, continuing anyway
Additional information
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 4
- Comments: 22 (5 by maintainers)
Having same issue. Logs are essentially identical
Running docker on debian.
Was working fine in 106.x. Tried rolling back to 106.x, was unsuccessful.
@kpine Fair enough. I reverted to 107.5 backup I had. I am not sure what killed the z wave component though. If there is anything you need me to try, I can try to recreate it again. Let me know. Otherwise. I will probably wait till 108 and try to do a full upgrade at that point.
Thanks for your time!