mtan93/homebridge
1
0
Fork 0
mirror of https://github.com/mtan93/homebridge.git synced 2026-04-19 06:13:10 +01:00
Code Issues Packages Projects Releases Wiki Activity

Add README example for plugin development

Browse Source
This commit is contained in:
Nick Farina
2016-03-07 11:49:13 -08:00
parent 842ec105be
commit 9b42fafdaf
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@@ -111,6 +111,16 @@ And you can find an example plugin that publishes an individual accessory at [he
See more examples on how to create Platform classes in the [Legacy Plugins](https://github.com/nfarina/homebridge-legacy-plugins/tree/master/platforms) repository. See more examples on how to create Platform classes in the [Legacy Plugins](https://github.com/nfarina/homebridge-legacy-plugins/tree/master/platforms) repository.
# Plugin Development
When writing your plugin, you'll want Homebridge to load it from your development directory instead of publishing it to `npm` each time. You can tell Homebridge to look for your plugin at a specific location using the command-line parameter `-P`. For example, if you are in the Homebridge directory (as checked out from Github), you might type:
```sh
DEBUG=* ./bin/homebridge -D -P ../my-great-plugin/
```
This will start up Homebridge and load your in-development plugin from a nearby directory.
# Common Issues # Common Issues
### My iOS App Can't Find Homebridge ### My iOS App Can't Find Homebridge