Indigo Domotics

The 6.0.4 Installer states:

Indigo 6 Home Automation Server

version 6.0.5

?? November 2013

I also had an odd, transient, problem with Indigo 6.0.3 and OS 10.9. AppleScripts run outside of Indigo. At a tell application "IndigoServer" block, I received an error that the application was not available? I needed to upgrade to 6.0.4 anyway, and after the upgrade (or probably just the restart) the problem cleared ?? Not really an issue, but maybe this will correlate with other reports.

Thanks for a great product and great support.

Whoops. My bad. Fixed now -- thanks for catching it.

berkinet wrote:

I also had an odd, transient, problem with Indigo 6.0.3 and OS 10.9. AppleScripts run outside of Indigo. At a tell application "IndigoServer" block, I received an error that the application was not available? I needed to upgrade to 6.0.4 anyway, and after the upgrade (or probably just the restart) the problem cleared ?? Not really an issue, but maybe this will correlate with other reports.

Unfortunately, this doesn't really surprise me for a couple of reasons. First, after doing a switch to the first GM build on my development Mac and using it for a few hours, I felt the need to revert back. Too many unexplained issues - Mail was seriously flaking out, spinning beach balls all over the place, etc. - just a general feel of instability. I'll be waiting for a couple of dot releases before trying to move my dev environment forward. My suspicion is that this release was a bit rushed out in order to get the new Mac Pro and updated MacBooks out. Of course, your mileage may vary - my Mac Pro is pretty old (~4 years) so there may be some quirks with this hardware. Newer Macs where most likely more thoroughly tested.

Second, Apple is really sending mixed signals about AppleScript - on the one hand they added some nice features. On the other hand, they basically pulled the AS support in the new iWork apps. The security stuff in the Mountain Lion release that broke some interprocess scripting (not to mention cross machine scripting) was the first sign of trouble (don't know if they've changed that behavior for the better).

(Indigo 6.0.4, OS-10.9

I have encountered the problem again and this time restarting the Indigo Server did not clear the problem. Also, Indigo is not logging any errors. Shouldn't it at least log that the script failed (non 0 return code)?

To try and track down the problem I ran the following AppleScript:

Code: Select all

tell application "System Events"
   repeat with p in every process
      log name of p as string
   end repeat
end tell

tell application "IndigoServer"
   log "GOT HERE"
end tell
end

Nothing is logged by Indigo. And, here is the script's Events & Replies

Code: Select all

tell application "System Events"
   count every process
      --> 46
   get name of item 1 of every process
      --> "loginwindow"
   (*loginwindow*)
   ... ...
   get name of item 41 of every process
      --> "IndigoServer"
   (*IndigoServer*)
        ... ...
end tell
tell application "IndigoServer"
   log "GOT HERE"
   log "GOT HERE"
   log "GOT HERE"
   log "GOT HERE"
   log "GOT HERE"
   log "GOT HERE"
   log "GOT HERE"
Result:
error "IndigoServer got an error: Application isn’t running." number -600

Next step, restart the Mac.

EDIT A restart did NOT clear the problem.
Calling the test script from the shell with osascript produces the same error and a return code of 1
Also note, nothing showing up in the system log either.
And, Googling the error message finds one similar report, but no responses.

How about 'tell app' blocks to other apps (do they work)?

If restarting IndigoServer didn't fix it then it sounds to me like the OS made be in a bad state. Does rebooting get it working again?

Haven't tried app blocks with other programs yet. That will have to wait till tonight when I get back to the house. Rebooting did not clear the problem. Looks like its time to convert my last couple of AppleScripts to Python.

The problem seems to be isolated to IndigoServer. But, since I have found at least one similar report, it strongly suggests a system problem.

One other small bit of information... No surprise, when run as an embedded script, the script works as expected.

matt (support) wrote:

How about 'tell app' blocks to other apps (do they work)?

Yes, well the few I tried: Terminal, Safari and Indigo 6, all of those respond in some manner.

So, if you quit the server and client, then go to the server app in the Finder:

/Library/Application Support/Perceptive Automation/Indigo 6/IndigoServer.app

and double-click it there (which will launch it) then try a script from the script editor does it work? The last time we saw a problem similar to this (Mountain Lion) it had to do with (what we consider a bug) how the server process was started. I'm just wondering if launching it from the Finder (rather than having the client launch it) makes any difference.

jay (support) wrote:

...go to the server app in the Finder:

/Library/Application Support/Perceptive Automation/Indigo 6/IndigoServer.app

and double-click it there (which will launch it) then try a script from the script editor does it work?

That works! And, of course, not starting it through the client now also works. So, it seems starting the server from the finder resets something... and that something will no doubt break again. At least I know how to "reset" now

Sigh. Apple's going a bit overboard on the app security front I think.

Anyway, we'll add a todo to try to dig through the Mavericks docs to see if we can find something that might explain this (not a lot of confidence that we'll find something though).

I had this problem recently after upgrading to version 7. Deleting version 6 from /Library/Application Support and re-installing 7 fixed it.