-
Notifications
You must be signed in to change notification settings - Fork 27
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
Delete old bulb #72
Comments
@straubus Delete the plugin and config.json, then delete the persist and accessories directories inside the homebridge folder, and restart homebridge to clear all previous devices. |
Little overkill with the deletion? Maybe a little more delicate deletion process would be possible? |
Hello, this is something related to homebridge itself. As far as I know the easiest way is to use something like homebridge-config-ui-x which will offer an option to It can also be done manually directly on the filesystem but will take some care. The files that you should look into are: |
Allow setting `"blacklist": true` in `config.json` to not expose a discovered device to HomeKit (see #86). This can also be used to make homebridge forget a device that you have removed without having to manually edit `cachedAccessories` (see #72). Example Usage: ``` { "bridge": { "name": "Raspberry Pi" }, "accessories": [{}], "platforms": [ { "platform": "yeelight", "name": "Yeelight", "defaultValue": { "aed78s": { "blacklist": true } } } ] } ```
As of 2.4.0 you can remove a light by blacklisting it in
|
Hi, One of my bulbs broke, so I disconnected it from power and deleted from yeelight account. Now I am trying to also delete it from Homekit, but homebridge still finds that old device, even when I uninstall Your plugin. How to clear the catche from old/broken devices?
The text was updated successfully, but these errors were encountered: