core: zwave.network_ready never fires
Home Assistant release with the issue: 0.101.1
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.): Linux
Integration: https://www.home-assistant.io/integrations/zwave/
Description of problem:
So https://www.home-assistant.io/integrations/persistent_notification/ has an example on how to create a persistent notification when Z-Wave is starting up and remove it when it’s ready.
I noticed that zwave.network_ready never fires. I tried it with:
- restarting Home Assistant
- Manually stopping then starting Z-Wave from the frontend.
Also… zwave.network_start only fires when I manually stop/start from the frontend, and not when restarting HA.
I haven’t tried zwave.network_complete.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
- alias: 'Z-Wave network is starting'
trigger:
- platform: event
event_type: zwave.network_start
action:
- service: persistent_notification.create
data:
title: "Z-Wave"
message: "Z-Wave network is starting..."
notification_id: zwave
- alias: 'Z-Wave network is ready'
trigger:
- platform: event
event_type: zwave.network_ready
action:
- service: persistent_notification.dismiss
data:
notification_id: zwave
Traceback (if applicable): Additional information:
2019-11-15 18:06:06 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Z-Wave network is starting
2019-11-15 18:06:06 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Z-Wave network is ready
.
.
.
2019-11-15 18:07:09 INFO (SyncWorker_19) [homeassistant.components.zwave] Stopping Z-Wave network
2019-11-15 18:07:09 INFO (SyncWorker_19) [openzwave] Stop Openzwave network.
2019-11-15 18:07:09 INFO (SyncWorker_19) [openzwave] ZWave configuration written to user directory.
2019-11-15 18:07:18 INFO (SyncWorker_5) [homeassistant.components.zwave] Starting Z-Wave network...
2019-11-15 18:07:18 INFO (SyncWorker_5) [openzwave] Start Openzwave network.
2019-11-15 18:07:18 INFO (MainThread) [homeassistant.components.automation] Executing Z-Wave network is starting
2019-11-15 18:07:18 INFO (MainThread) [homeassistant.helpers.script] Script Z-Wave network is starting: Running script
2019-11-15 18:07:18 INFO (MainThread) [homeassistant.helpers.script] Script Z-Wave network is starting: Executing step call service
2019-11-15 18:07:19 INFO (Dummy-4) [openzwave] Driver ready using library Static Controller version Z-Wave 4.24
2019-11-15 18:07:30 INFO (Dummy-4) [homeassistant.components.zwave] Z-Wave network is complete. All nodes on the network have been queried
2019-11-15 18:07:30 INFO (MainThread) [homeassistant.components.zwave] Z-Wave ready after 12 seconds
2019-11-15 18:07:30 INFO (SyncWorker_16) [homeassistant.components.zwave] Z-Wave polling interval set to 30000 ms
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 16 (3 by maintainers)
Still an issue i 0.107.2
Thats why this Ticket is not closed yet. Documentation says, that
zwave.network_readyis triggered as soon as the net is able to receive commands. I have exactly one dead node, and I can confirm thatzwave.network_complete_some_deadis the only event fired. Imho this is a bug. Home Assistant should fire azwave.network_readyevent always when the network is ready, and either azwave.network_complete_some_deadorzwave.network_completeevent, dependent on the existance of dead Z-Wave Nodes.Ah, i tried this with
0.102.0b1, afaik this happens with some of the USB Sticks, i have azmeeuzb1, but yesterday I read that this also ahppens with theAeotecsticks.