mirror of
https://github.com/mtan93/homebridge.git
synced 2026-03-08 05:31:55 +00:00
New "Common Issues" section
This commit is contained in:
12
README.md
12
README.md
@@ -117,7 +117,17 @@ There isn't currently an example for how to publish a Platform (which allows the
|
||||
|
||||
See more examples on how to create Platform classes in the [Legacy Plugins](https://github.com/nfarina/homebridge-legacy-plugins/tree/master/platforms) repository.
|
||||
|
||||
# Why?
|
||||
# Common Issues
|
||||
|
||||
### My iOS App Can't Find Homebridge
|
||||
|
||||
Two reasons why Homebridge may not be discoverable:
|
||||
|
||||
1. Homebridge server thinks it's been paired with, but iOS thinks otherwise. Fix: deleted `persist/` directory which is next to your `config.json`.
|
||||
|
||||
2. iOS device has gotten your Homebridge `username` (looks like a MAC address) "stuck" somehow, where it's in the database but inactive. Fix: change your `username` in the "bridge" section of `config.json` to be some new value.
|
||||
|
||||
# Why Homebridge?
|
||||
|
||||
Technically, the device manufacturers should be the ones implementing the HomeKit API. And I'm sure they will - eventually. When they do, this project will be obsolete, and I hope that happens soon. In the meantime, Homebridge is a fun way to get a taste of the future, for those who just can't bear to wait until "real" HomeKit devices are on the market.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user