-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Is there anyway to allow access to folders? #2
Comments
already #planned to delete cache and persist folder for that case |
The original plan was to just clear the cache. I will look into listing the accessories. |
Also you should leave the terminal commands in a guide, so we can clear cache |
https://github.com/nfarina/homebridge/wiki/Basic-Troubleshooting#reset-pairingaccessories we will add that as a button in v3.0.0 see here https://github.com/hoobs-org/HOOBS/wiki/1.0-News-from-HOOBS#hoobs-core |
The reset connection button in help will remove persist, accessories and update the username. It does everything from here |
Is there anyway to allow access to folders. Like some apps need us to. Like I need to do this but I can’t “If you remove a camera from HomeKit for some reason (such as live stream troubleshooting), sometimes it will not show up again in the "Add Device" flow in the Home app. If this happens, follow these steps:
Verify that your homebridge server, HomeKit hub, and the device that you are trying to add the camera on are all on the same network without a firewall/router blocking access between them. Stop homebridge Go into your ~/.homebridge/persist directory and finding any AccessoryInfo.${uniqueId}.json files that relate to your camera. You can open them up and they have the device name right at the start of the file. Keep track of the ${uniqueId} values for your cameras. Delete each camera's AccessoryInfo.${uniqueId}.json and associated IdentifierCache.${uniqueId}.json file Remove the cameras from HomeKit via the Home app Start homebridge Re-add the cameras like you did the first time around”
The text was updated successfully, but these errors were encountered: