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

Ignore some HomeKit devices #15316

Merged
merged 1 commit into from Jul 12, 2018
Merged

Ignore some HomeKit devices #15316

merged 1 commit into from Jul 12, 2018

Conversation

mjg59
Copy link
Contributor

@mjg59 mjg59 commented Jul 6, 2018

There are some devices that speak HomeKit that we shouldn't expose. Some
bridges (such as the Hue) provide reduced functionality over HomeKit and
have a functional native API, so should be ignored. We also shouldn't
offer to configure the built-in Home Assistant HomeKit bridge.

Breaking change: Tradfri will no longer be automatically detected by the HomeKit controller. Use the native integration instead.

Checklist:

  • The code change is tested and works locally.
  • Local tests pass with tox. Your PR cannot be merged unless tests pass

There are some devices that speak HomeKit that we shouldn't expose. Some
bridges (such as the Hue) provide reduced functionality over HomeKit and
have a functional native API, so should be ignored. We also shouldn't
offer to configure the built-in Home Assistant HomeKit bridge.
@ghost ghost assigned mjg59 Jul 6, 2018
@ghost ghost added the in progress label Jul 6, 2018
Copy link
Member

@MartinHjelmare MartinHjelmare 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!

@MartinHjelmare
Copy link
Member

Is this a breaking change?

We should probably document this at least in our docs.

@mjg59
Copy link
Contributor Author

mjg59 commented Jul 6, 2018

It would break anyone who was using a Tradfri via Homekit (Hue doesn't currently work due to a bug in the protocol library). I /doubt/ that anyone's actually doing that, but it seems reasonable to document.

@MartinHjelmare
Copy link
Member

Please highlight the breaking change describing paragraph so we can copy that to the release notes.

@balloob balloob merged commit c587536 into home-assistant:dev Jul 12, 2018
@ghost ghost removed the in progress label Jul 12, 2018
awarecan pushed a commit to awarecan/home-assistant that referenced this pull request Jul 16, 2018
There are some devices that speak HomeKit that we shouldn't expose. Some
bridges (such as the Hue) provide reduced functionality over HomeKit and
have a functional native API, so should be ignored. We also shouldn't
offer to configure the built-in Home Assistant HomeKit bridge.
@balloob balloob mentioned this pull request Jul 20, 2018
michaeldavie pushed a commit to michaeldavie/home-assistant that referenced this pull request Jul 31, 2018
There are some devices that speak HomeKit that we shouldn't expose. Some
bridges (such as the Hue) provide reduced functionality over HomeKit and
have a functional native API, so should be ignored. We also shouldn't
offer to configure the built-in Home Assistant HomeKit bridge.
@andersonshatch
Copy link
Contributor

Wouldn't adding the Hue bridge via HomeKit be more responsive than the current local polling integration?

@home-assistant home-assistant locked as resolved and limited conversation to collaborators Aug 10, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants