Skip to content
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

Zwave doesn't fire network_complete or network_ready #16750

Closed
janvanhelvoort opened this issue Sep 20, 2018 · 1 comment · Fixed by #16894
Closed

Zwave doesn't fire network_complete or network_ready #16750

janvanhelvoort opened this issue Sep 20, 2018 · 1 comment · Fixed by #16894

Comments

@janvanhelvoort
Copy link
Contributor

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:

  • 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):

# Enables z-wave
zwave:
  usb_path: !secret zwave_usb_path
  network_key: "!secret zwave_key"

# Enables Apple HomeKit
homekit:
  auto_start: false
  filter:
    include_domains:
      - light
      - switch

# Temp - logger
logger:
  default: warning
  logs:
    homeassistant.components.zwave: info
    homeassistant.components.homekit: debug
    pyhap: debug

automation:
  - alias: 'Zwave ready or complete'
    trigger:
      - platform: event
        event_type: zwave.network_ready
      - platform: event
        event_type: zwave.network_complete
    action:
      - service: persistent_notification.create
        data:
          message: "zwave ready or something"

Additional information:

2018-09-20 17:27:07 DEBUG (MainThread) [homeassistant.components.homekit] Begin setup HomeKit
2018-09-20 17:27:08 INFO (MainThread) [homeassistant.components.zwave] Z-Wave network autoheal is enabled
2018-09-20 17:27:10 DEBUG (SyncWorker_1) [pyhap.characteristic] set_value: Name to Home Assistant Bridge
2018-09-20 17:27:10 DEBUG (SyncWorker_1) [pyhap.characteristic] set_value: SerialNumber to default
2018-09-20 17:27:10 DEBUG (SyncWorker_1) [pyhap.characteristic] set_value: FirmwareRevision to 0.78.0
2018-09-20 17:27:10 DEBUG (SyncWorker_1) [pyhap.characteristic] set_value: Manufacturer to Home Assistant
2018-09-20 17:27:10 DEBUG (SyncWorker_1) [pyhap.characteristic] set_value: Model to Bridge
2018-09-20 17:27:10 DEBUG (SyncWorker_1) [pyhap.characteristic] set_value: SerialNumber to homekit.bridge
2018-09-20 17:27:11 INFO (SyncWorker_9) [homeassistant.components.zwave] Starting Z-Wave network...
2018-09-20 17:27:15 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-09-20 17:28:44 INFO (MainThread) [homeassistant.components.zwave] Z-Wave ready after 92 seconds
2018-09-20 17:28:44 INFO (SyncWorker_7) [homeassistant.components.zwave] Z-Wave polling interval set to 60000 ms

When i call homekit.start from the services view inside home assistant, the following rules are appended to the config.

2018-09-20 17:32:53 DEBUG (SyncWorker_5) [pyhap.characteristic] set_value: Name to Keuken
2018-09-20 17:32:53 DEBUG (SyncWorker_5) [pyhap.characteristic] set_value: SerialNumber to default
2018-09-20 17:32:53 DEBUG (SyncWorker_5) [pyhap.characteristic] set_value: FirmwareRevision to 0.78.0
2018-09-20 17:32:53 DEBUG (SyncWorker_5) [pyhap.characteristic] set_value: Manufacturer to Home Assistant
2018-09-20 17:32:53 DEBUG (SyncWorker_5) [pyhap.characteristic] set_value: Model to Light
2018-09-20 17:32:53 DEBUG (SyncWorker_5) [pyhap.characteristic] set_value: SerialNumber to light.keuken
2018-09-20 17:32:53 DEBUG (SyncWorker_5) [pyhap.characteristic] set_value: ColorTemperature to 153
2018-09-20 17:32:53 DEBUG (SyncWorker_5) [pyhap.characteristic] set_value: Saturation to 75
... More nodes...
2018-09-20 17:32:53 INFO (SyncWorker_5) [pyhap.accessory_driver] Loading Accessory state from `/config/.homekit.state`
2018-09-20 17:32:53 INFO (SyncWorker_5) [homeassistant.components.homekit.util] Pincode: ***-**-***
2018-09-20 17:32:53 DEBUG (SyncWorker_5) [homeassistant.components.homekit] Driver start
2018-09-20 17:32:53 INFO (SyncWorker_12) [pyhap.accessory_driver] Starting the event loop
2018-09-20 17:32:53 INFO (SyncWorker_0) [pyhap.accessory_driver] Starting accessory Home Assistant Bridge on address 192.168.179.20, port 51827.
2018-09-20 17:32:54 DEBUG (SyncWorker_0) [pyhap.accessory_driver] AccessoryDriver started successfully
@janvanhelvoort
Copy link
Contributor Author

in the logs of OZW_Log.txt: around the time of where zwave logs it is ready, are this rules:

2018-09-20 17:28:44.228 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=0
2018-09-20 17:28:44.228 Warning, CheckCompletedNodeQueries all=1, deadFound=1 sleepingOnly=1
2018-09-20 17:28:44.228 Info,          Node query processing complete except for dead nodes.
2018-09-20 17:28:44.229 Detail, Node031, Notification: NodeQueriesComplete
2018-09-20 17:28:44.237 Detail, contrlr, Notification: AllNodesQueriedSomeDead

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.

@ghost ghost added the in progress label Sep 26, 2018
@ghost ghost removed the in progress label Sep 28, 2018
@home-assistant home-assistant locked and limited conversation to collaborators Feb 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant