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

Add Elgato Key Light integration #29592

Merged
merged 5 commits into from Dec 8, 2019
Merged

Add Elgato Key Light integration #29592

merged 5 commits into from Dec 8, 2019

Conversation

frenck
Copy link
Member

@frenck frenck commented Dec 7, 2019

Description:

Adds support for Elgato Key Lights to Home Assistant

https://www.elgato.com/en/gaming/key-light

2019-12-07 17 00 51

Related issue (if applicable): n/a

Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#11391

Example entry for configuration.yaml (if applicable): n/a

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.

Copy link
Member

@Kane610 Kane610 left a comment

Choose a reason for hiding this comment

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

Looks good to me!

# Cleanup
del hass.data[DOMAIN][entry.entry_id]
if not hass.data[DOMAIN]:
del hass.data[DOMAIN]
Copy link
Member

Choose a reason for hiding this comment

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

Don't clean this up, because it is not set by the config entry.

By deleting this, if we are to reload a single config entry, we would crash on line 36, because hass.data[DOMAIN] is no longer a dictionary.

Copy link
Member Author

@frenck frenck Dec 7, 2019

Choose a reason for hiding this comment

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

Addressed in 33023fe.

I moved it out of the setup, allowing both cleaning things up and prevent the described issue from occurring.

Is that an acceptable solution?

Copy link
Member

@balloob balloob left a comment

Choose a reason for hiding this comment

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

ok to merge when final comment addressed.

Dev automation moved this from Needs review to Reviewer approved Dec 7, 2019
@balloob balloob merged commit cc9589c into dev Dec 8, 2019
Dev automation moved this from Reviewer approved to Done Dec 8, 2019
@delete-merged-branch delete-merged-branch bot deleted the frenck-2019-0288 branch December 8, 2019 08:26
@lock lock bot locked and limited conversation to collaborators Dec 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Dev
  
Done
Development

Successfully merging this pull request may close these issues.

None yet

4 participants