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

Added device whitelist/blacklist #102

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Added device whitelist/blacklist #102

wants to merge 1 commit into from

Conversation

cfurgang
Copy link

@cfurgang cfurgang commented Dec 27, 2016

Issues #85, #71, and #58 all relate to having the ability of specifically including or specifically excluding devices in your nest account from being exposed to HomeKit. This is important, for example, if you have thermostats in multiple locations and you want to control them from two separate homebridge instances (and two different Home instances in HomeKit).

This PR adds the ability to specify specific devices in either a whitelist ("includeDevices") or blacklist ("excludeDevices") config parameter.

@AntonStewart
Copy link

Given that this PR is still open after more than a year, perhaps it would be possible for the OP, cfurgang, to provide the necessary configuration details here. That way, those of us with multiple home instances in HomeKit, can ask Siri to 'turn the heat up' and limit the scope to just the home we're in.
Thanks in advance.

@chrisjshull
Copy link

Great news! I have taken up maintenance of the homebridge-nest plugin in npm. The source code now lives at https://github.com/chrisjshull/homebridge-nest/. To update to the latest version of homebridge-nest, simply run npm update -g homebridge-nest.

I believe this issue has been solved, albeit slightly differently (see the "structureId" config property). You are also welcome to resubmit this PR to that repo. ☺

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.

4 participants