Skip to content

Start HomeKit on network_ready or network_complete #5501

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

Merged
merged 1 commit into from
Jun 7, 2018

Conversation

n8henrie
Copy link
Contributor

@n8henrie n8henrie commented Jun 6, 2018

Description: Some setups will emit zwave.network_complete instead of zwave.network_ready -- the example displayed in the docs should work for either.

See: home-assistant/core#14270

Pull request in home-assistant (if applicable): home-assistant/home-assistant#

Checklist:

  • Branch: Fixes, changes and adjustments should be created against current. New documentation for platforms/components and features should go to next.
  • The documentation follow the standards.

Some setups will emit `zwave.network_complete` instead of `zwave.network_ready` -- the example displayed in the docs should work for either.

See: home-assistant/core#14270
Copy link
Contributor

@turbokongen turbokongen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank You 👍

@turbokongen turbokongen merged commit 774a166 into home-assistant:current Jun 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants