The suggested “Start Homekit after zwave” automation isn’t working for me. It seems like the zwave.network_ready isn’t being recognized.
I can see in the logbook that zwave changed to ready, and in my logs [homeassistant.components.zwave] Z-Wave ready after 2 seconds, but I don’t get the HomeKit persistent notification. (I am stopping hass, removing the .homekit.state file, and restarting.)
If I manually fire zwave.network_ready, I immediately get the push notification and the HomeKit persistent notification, so I think the automation is set up correctly.
It seems to be an issue with the zwave.network_ready event trigger. I personally don’t have any issues with it. As an alternative the following might work:
Still have not figured this out. I’m aware I could work around by using a delay, but it would be nice to find out why my zwave.network_ready event doesn’t seem to be triggering.
I’m using the husbzb1, which seems to be working fine, and only have 1 light in the network, which gets detected properly and also works fine.
I’ve tried removing all zwave related config files and starting from scratch, with no difference.
Anybody with a husbzb-1 have this issue with 0.66.0?
I have the same problem with a regular Aeotec z-wave stick. I just created a script to manually start it when home assistant is done booting. Would be nice to know why the event doesn’t trigger though.
@jwelter I see you have a notify_engine script. Can you share that? Looks handy to pass in a msg and a target person to abstract the sending of notifications from each of your automations.