webdeck wrote:First, stop your custom homebridge. Then install HBB, make sure it isn't running, and then disable the HBB plugin. Then you should be able to run these commands to copy over your custom config and run the embedded homebridge manually:
- Code: Select all
cd "/Library/Application Support/Perceptive Automation/Indigo 7/Plugins (Disabled)/EPS Homebridge.indigoPlugin/Contents/Server Plugin/bin/hb/homebridge"
./createdir test
cp -rp ~/.homebridge/* test
./load test
You can see the homebridge log file in test/homebridge.log
To stop the server, run
- Code: Select all
./unload test
Excellent, thanks for that. This would be instructions for someone who used a manually installed HB at some point, correct? Terry, can you try this?
I'm also assuming that anyone who has HBB running can just shut down the plugin, then go to that directory and do a:
- Code: Select all
cd "/Library/Application Support/Perceptive Automation/Indigo 7/Plugins (Disabled)/EPS Homebridge.indigoPlugin/Contents/Server Plugin/bin/hb/homebridge"
./load 123456789
where 123456789 is the ID of the homebridge device in Indigo (I seem to have one in there that matches)? @cuhouse can you give that a try? Make sure to leave the HBB plugin disabled.
Anyone else who's experienced the problem can follow these directions above - if you at any point have run HB from a manual install then try the first set of instructions. To reiterate, the goal here is to run the precompiled homebridge that's distributed with the HBB plugin without the plugin running/managing it. If it runs without issue, then it's likely that there's something about the plugin that's triggering the problem. If it continues to fail, then it's likely that the precompiled HB is the issue.
Thanks everyone for helping to get to the bottom of this. Debugging these sorts of issues can be a major time suck given all the permutations so having you guys involved closely should make the diagnostic time much shorter than if just one person were trying to figure it out.