Since I just managed to get Indigo running as a daemon, I thought I'd post my experiences as an update to this thread.
I'm using an early 2008 iMac (2.8 GHz Core 2 Duo, 4 GB) running 10.10.5 "Yosemite" and Indigo 6.1.11.
Things went for me mostly as documented in this thread, with the following caveats...
1. There have indeed been further changes to the plist format, with additional tags having been deprecated. Here's the launchd plist that eventually worked for me. Note that I've also included StandardOutPath and StandardErrorPath tags to redirect output to files under /tmp; this was helpful for debugging.
- Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>UserName</key>
<string>indigo</string>
<key>GroupName</key>
<string>indigo</string>
<key>Label</key>
<string>com.perceptiveautomation.IndigoServer2</string>
<key>KeepAlive</key>
<true/>
<key>Program</key>
<string>/Library/Application Support/Perceptive Automation/Indigo 6/IndigoServer.app/Contents/MacOS/IndigoServer</string>
<key>StandardErrorPath</key>
<string>/tmp/indigo.err</string>
<key>StandardOutPath</key>
<string>/tmp/indigo.out</string>
</dict>
</plist>
2. I didn't get any errors in the console about not being able to communicate with the window server. However, I did get errors about the application not being able to initialize. To resolve this, I eventually had to log in as the 'indigo' account. In my case, I allowed the account to have a home directory, so I was able to log in with no difficulty. Once in as the indigo user, I was able to call launchd to start the program as a daemon, and its worked ever since.
3. In another thread (
viewtopic.php?f=131&t=18085), I posted about how speech doesn't work when the Mac's login screen is displayed. In that thread, I was specifically talking about logging in as a user, launching Indigo, leaving it running, and then switching to the login screen. Speech appears to work perfectly when Indigo runs as a daemon, whether anyone is logged in or not.
4. Plugins indeed are disabled. The only place where that's bugged me is that the "match brightness" action isn't available, so I'll have to figure out some way to work around that for the responders in my Insteon three-way switches.
Matt, Jay, I know you guys are busy with v7 and other features, but please add my vote for better support of running Indigo as a daemon.
--Jeff