DrLove wrote:Hi!
Just started to use this brilliant plugin! Love it so far.
Instead of using a delayed start w/ OSx like in the instructions, is it not better to have Indigo start the server/plugin w/ a trigger at startup? Is that possible? I guess you cant have 2 instances of the HomeKit server so if I only restart Indigo server (not OSx) it wont start another instance of HomeKit?!?
I have like 250 ID's so I have to use "include" and right now I make allot of changes to the Include list, is there a way to reload the HomeKit settings, from terminal or even better from Indigo? The 60 sec delay is kind of annoying
Best regards, L
Yes, you can't have two instances running, as they will both try to claim the same port. So if you were to do this, you would need to have a script that kills the previous instance before starting a new one. It should be doable with a little bit of scripting, if someone adventurous wants to give it a try.
The simplest answer to your question about making a lot of changes is to unload the launchctl item (
launchctl unload -w ~/Library/LaunchAgents/com.webdeck.homebridge.plist), and instead run
homebridge directly from Terminal. Then you can press Control-C to stop it and restart it again on the Terminal as many times as you want until you're happy with the configuration, and then you can stop it one last time and then go back and load the launchctl item (
launchctl load -w ~/Library/LaunchAgents/com.webdeck.homebridge.plist) to have it autostart again (with the 60 second delay.)