Please reply on this thread with any bug reports concerning Lion for both Indigo 4.x and Indigo 5. There are a few known issues already:

• Dragging a variable in the var window causes a crash
• Duplicating a Trigger that's a device state change causes a crash
• Selecting a control page object that represents a device causes a crash

If you don't see your issue above or on any of the replies, please include a detailed description of the problem including steps needed to reproduce the problem.

NOTE: Indigo versions prior to Indigo 4 will not be updated to work on Lion. Check out our official position on Lion support.

On Lion server (maybe Lion general), it seems like there is a problem with launchd and trying to start the process more than once. Problem is solved by telling the server to shut down, then start a new server.


7/5/11 9:25:56.843 AM IndigoServer: fatal error -- server already running
7/5/11 9:25:56.843 AM IndigoServer: Quiting Indigo Server - unloading launchd plist
7/5/11 9:25:56.846 AM IndigoServer: Quiting Indigo Server - complete
7/5/11 9:25:56.848 AM com.apple.launchd.peruser.501: (com.perceptiveautomation.IndigoServer2[470]) Exited with code: 1
7/5/11 9:25:56.848 AM com.apple.launchd.peruser.501: (com.perceptiveautomation.IndigoServer2) Throttling respawn: Will start in 10 seconds
7/5/11 9:26:06.912 AM IndigoServer: fatal error -- server already running
7/5/11 9:26:06.914 AM IndigoServer: Quiting Indigo Server - unloading launchd plist
7/5/11 9:26:06.917 AM IndigoServer: Quiting Indigo Server - complete
7/5/11 9:26:06.920 AM com.apple.launchd.peruser.501: (com.perceptiveautomation.IndigoServer2[482]) Exited with code: 1
7/5/11 9:26:06.921 AM com.apple.launchd.peruser.501: (com.perceptiveautomation.IndigoServer2) Throttling respawn: Will start in 10 seconds
7/5/11 9:26:16.970 AM IndigoServer: fatal error -- server already running
7/5/11 9:26:16.970 AM IndigoServer: Quiting Indigo Server - unloading launchd plist
7/5/11 9:26:16.973 AM IndigoServer: Quiting Indigo Server - complete
7/5/11 9:26:16.975 AM com.apple.launchd.peruser.501: (com.perceptiveautomation.IndigoServer2[491]) Exited with code: 1
7/5/11 9:26:16.975 AM com.apple.launchd.peruser.501: (com.perceptiveautomation.IndigoServer2) Throttling respawn: Will start in 10 seconds

That happens periodically on OS upgrades - I suspect that somehow the launchd doc gets it's permissions munged. But, stopping/starting the server fixes it because the launchd doc gets recreated.

Just an FYI, so far my MacMini has the latest Apple Remote Desktop required for Lion (running Lion on a different machine) and no problems with Indigo. Upgraded my iPad 2 to ios5 and I am constantly asked to log in to Indigo (user ID and password). Not a big deal since when I log on everything works on the Indigo for the iPad.

Yes, it appears that the iOS betas have a problem with storing username/passwords (that's built-in to iOS). As we get closer to iOS 5 release we'll look into it to see if we now have to do something special to have it stored, but I'm pretty sure it's an iOS bug that should be fixed before release.

lharris9 wrote:Just an FYI, so far my MacMini has the latest Apple Remote Desktop required for Lion (running Lion on a different machine) and no problems with Indigo. Upgraded my iPad 2 to ios5 and I am constantly asked to log in to Indigo (user ID and password). Not a big deal since when I log on everything works on the Indigo for the iPad.

What version of ARD are you using?

I have not found a version of ARD that works when run on Lion yet... (3.4 is the latest I have seen, and it will not run on Lion... Although I have not yet tested the Gold Master....)

- Benjamin

Apple has posted ARD 3.5 (lion support) in the developer downloads section

on the launchd problem, this problem persists every reboot. stopping+starting the server only solves the issue for the current session. Could this be related to lion's new resume feature?

It might very well be related - we haven't looked too closely at how that auto launch thing plays with launchd documents. Does it only do it if you quit the Indigo Client app before restarting (thus avoiding the auto start feature)? I'm just guessing, but if the client is running when you restart, the autolaunch thing will start the client, probably before the server gets launched by launchd - the client then starts it's own server and then launchd fails because the server is already running.

If that's the problem, it's unclear how we'll handle it. I wonder if there's some way to not have the client auto launched...

By quitting indigo before rebooting seems to squash the problem... Im guessing this is definitely the client starting the server if it isn't started. I would possibly have the client check for the existence of the launchd config, if it DOES exist, don't start the server.

Yeah, we'll definitely have to think about this one.

Create a new Schedule
Fill in Time, Name, etc.
Select Action Type - Control Thermostat

Now if I click OK without selecting one of my thermostats, everything is fine.

Once I select a thermostat, Indigo Crashs hard when I click OK.

Indigo will also crash every time if I attempt to open the Schedule once a thermostat is selected.

Does it both on the local machine and when I try with the client.

Lion 11A511

I'll try to reproduce it, but it's likely the same issue as the last two bullets on the OP. Manipulating devices in various places in the UI caused a problem because of an underlying problem with the device objects.

Thanks for the report!

Sorry to add to list, but I am unable to add sprinkler schedule times, nor to modify an action group involving my sprinklers.

Yep, probably the same device object bug. Manipulating any device object, either directly or in actions and triggers will most likely end up in a crash. We hope to have a Lion-tested version out later next week.