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

ESPHome component to use zeroconf discovery #24043

Merged
merged 2 commits into from May 23, 2019

Conversation

Kane610
Copy link
Member

@Kane610 Kane610 commented May 22, 2019

Description:

Related issue (if applicable): fixes home-assistant/architecture#198 (comment)
home-assistant/home-assistant.io#9506

Checklist:

  • The code change is tested and works locally.
  • Local tests pass with tox. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
  • Untested files have been added to .coveragerc.

If the code does not interact with devices:

  • Tests have been added to verify that the new code works.

@Kane610 Kane610 requested a review from OttoWinter as a code owner May 22, 2019 18:43
@ghost
Copy link

ghost commented May 22, 2019

Hey there @OttoWinter, mind taking a look at this pull request as its been labeled with a integration (esphome) you are listed as a codeowner for? Thanks!

This is a automatic comment generated by codeowners-mention to help ensure issues and pull requests are seen by the right people.

@pvizeli pvizeli merged commit 085303c into home-assistant:dev May 23, 2019
@Kane610 Kane610 deleted the zeroconf-discovery-esphome branch May 23, 2019 18:17
@OttoWinter
Copy link
Member

Should this be tagged as a breaking change?

ESPHome was only configurable through a config flow ever - discovery was only used to initiate the config flow. So no user could have relied on this.

@Kane610
Copy link
Member Author

Kane610 commented May 30, 2019

The breaking change flag was added initially when I removed references to ESPHome in the discovery component, but that has been reverted. So no breaking change exist anymore

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Manifest.json: support zeroconf discovery
4 participants