You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Last working Home Assistant release (if known):
Unknow
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io - Hass.io supervisor - 130
System Resin OS 2.3.0+rev1
Component/platform:
Zwave
Homekit
Description of problem:
Changed hass.io HomeBridge plugging for native homeKit intergration. When i use the auto_start false, I want enable homeKit on zwave network ready or complate. With the config below, i want to see the persistent note, but they don't appear. As you can see in the logs, the network is ready after x seconds, al nodes al ready.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
The death node is a battery powered motion sensor, when I walk past it, it will immediately triggers and got ready inside home assistant, and the lights turn on.
Home Assistant release with the issue:
0.78.0
Last working Home Assistant release (if known):
Unknow
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io - Hass.io supervisor - 130
System Resin OS 2.3.0+rev1
Component/platform:
Description of problem:
Changed hass.io HomeBridge plugging for native homeKit intergration. When i use the auto_start false, I want enable homeKit on zwave network ready or complate. With the config below, i want to see the persistent note, but they don't appear. As you can see in the logs, the network is ready after x seconds, al nodes al ready.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Additional information:
When i call homekit.start from the services view inside home assistant, the following rules are appended to the config.
The text was updated successfully, but these errors were encountered: