Okay slightly less dramatic, but no less frustrating.

Beta 4 wouldn't launch the server on login as it claimed. It *would* start after the client was launched, and then everything was fine.

Saw Beta 5 posted today, and note that it is now the public version, so I figured it must have fixed that startup thing and loaded it.

Beta 5 will not connect to the PowerLinc V2 USB. Beta 4 was connected just one restart earlier, so I doubt it's the PowerLinc. At work now, so can't quote the errors exactly.

Tried to reload Beta 4. Can't do it.

Tried to reload Beta 3. Can't do it.

Customize in both cases won't let me select the client or the server. Can only select the scripts. This is after trashing both client and server from Beta 5.

Haven't tried to run 1.8 again, as I'm afraid so much has changed I might mess something up.

How can I get so I can reload Beta 3 or 4?

Byron

Hi Byron,

bcmayes wrote:Saw Beta 5 posted today, and note that it is now the public version, so I figured it must have fixed that startup thing and loaded it.

Nope, no such fixes in beta 5. No one had posted about any problems with beta 4, so I released beta 5. If you have a problem with a beta, then please speak up.

Did you remove the login item from you System Preference? Indigo (b4) should have removed that for you, but if it didn't then you need to do it manually.

I think the problem with beta 5 not connecting with the PowerLinc is because beta 4, or a zombie process of beta 4, is still hanging around. Reboot your computer and try again. What does:

   ps -axwww | grep "Indigo"

show when run from the terminal?

What version of OS X are you running?

I'm not sure why the installer won't let you select the client or server options. Are you targeting a volume that is a boot drive? Have you tried rebooting and running the installer again?

Regards,
Matt

support wrote:I'm not sure why the installer won't let you select the client or server options. Are you targeting a volume that is a boot drive?

Okay, I know the answer to this one now. This is because you are trying to run the older version of the installer. The installer won't let you "upgrade" from the newer version to the older version. To re-enable those options, delete the Indigo 2 client file, and the Indigo 2 support folder (containing the server app and your database/registration file -- make copies of those). Next, delete the installer receipt files:

  /Library/Receipts/IndigoClient.pkg
  /Library/Receipts/IndigoServer.pkg

Now you can run the installer.

All that said, I'd really like to figure out why beta 5 is not starting up and running on your machine (instead of having you revert to beta 3). It is working on my test machines and has worked for some other folks, so it should be possible to get it up and working on your system. We just need to troubleshoot it some more. If you can provide details about the exact steps and settings you are using, as well as the failures that would be great. Some questions:

1) What version of OS X are you running?
2) Are you running the client/server/installer all under the same admin user account?
3) Do you have the "Start and connect to Indigo Server..." checkbox turned on (Start Local Server dialog)?
4) Do you have the "Auto start Indigo Server on user login..." checkbox turned on?
5) Presuming those are both on and Indigo Server is not starting, then run the following from the Terminal and post the response back to the forum. Actually, run the following regardless of your settings on #3 and #4:
  ps -axwww | grep "Indigo"
  ls -al ~/Library/LaunchAgents/
  launchctl list
6) What does the Indigo Event Log look like? Is it even trying to start the server? Are there any errors in the system console.log file related to Indigo?
7) Do you have any custom AppleScript running on Server Launch or periodically via a Time/Date Action? Do you have any custom attachment scripts? If so, what are they doing?

Let me know how it goes. Unfortunately, I'm not going to have access to the forum for a couple of days (starting in a few hours). If you need to revert back to beta 3, then follow the instructions above to reset the installer. You can download beta 3 here.

Lastly, has anyone else had problems getting beta 4 or 5 to launch, or to connect to their PowerLinc? Is it launching on login correctly? Note just the server silently launches on login -- not the GUI client.

Regards,
Matt

support wrote:Hi Byron,

bcmayes wrote:Saw Beta 5 posted today, and note that it is now the public version, so I figured it must have fixed that startup thing and loaded it.

Nope, no such fixes in beta 5. No one had posted about any problems with beta 4, so I released beta 5. If you have a problem with a beta, then please speak up.

Yeah, I know. Didn't notice until this AM before I left for work (spent all last night getting my DynDNS working) which was the first time I tried to access the server from the web via DNS instead of pointing to it locally. Saw the new number and just assumed. We all know what happens when you assume!

Oh, and never load a new version of software -- beta, distribution, or otherwise -- on your home computer as you're getting ready to leave for work. As if I didn't know that already.

I will follow the instructions when I get home. Beta 4 did remove the login item in the System Preferences, so that did work as it should.

bcmayes wrote:I will follow the instructions when I get home. Beta 4 did remove the login item in the System Preferences, so that did work as it should.

Great -- thanks in advance for the additional info. I'll be back on the forum Sunday evening most likely. Hopefully you can get beta 5 up and running somehow in the mean time. Otherwise, I guess it is back to beta 3.

So beta 4/5 does run on your system (even though it doesn't auto launch on login), but you can no longer connect to the PowerLinc? I cannot think of anything that changed in b4/5 that would effect PowerLinc communication, but you never know. Try switching ports, unplugging the PowerLinc V2 from the outlet and computer for a few seconds, etc.

Matt

I just installed beta 5 (never installed beta4).

It seems to work, but the log says:
-----------------
Sep 29, 2006 11:25:38 AM
Starting Indigo Server version 2.0.0 beta 5
Loading attachments
"AccuWeather.scpt" script loaded
"device target attachment.scpt" script loaded
"group target attachment.scpt" script loaded
"iSEEu.scpt" script loaded
"iTunes attachment.scpt" script loaded
"scenes attachment.scpt" script loaded
"SpyCamera.scpt" script loaded
"time stamp attachment.scpt" script loaded

Sep 29, 2006 11:25:46 AM
Error script error: Expected end of line, etc. but found identifier.
Connected to SmartHome PowerLinc USB E
PowerLinc address 07.8B.BB, firmware version 2.12
Client connected
------------

Is the error from the time stamp script, or one of mine?

EDIT: Ok, stupid question. I'll just run them one by one to find out.

Let me know if it turns out to be one of the Indigo default attachment scripts. It would be nice if Indigo told you what script fails, but it doesn't...

Matt

support wrote:So beta 4/5 does run on your system (even though it doesn't auto launch on login), but you can no longer connect to the PowerLinc? I cannot think of anything that changed in b4/5 that would effect PowerLinc communication, but you never know. Try switching ports, unplugging the PowerLinc V2 from the outlet and computer for a few seconds, etc.

Matt

Okay, looks like I had a strange confluence of events. Without going into too much detail, the PowerLinc, the Indigo reload, and my dynamic DNS all wigged out at the same time I loaded beta 5. This meant that not five minutes after everything was working, everything stopped working and the only obvious change was beta 5 (which it turns out wasn't the problem). All is well...almost.

The server still does not start on startup. I'm sure of that because 1) I can't get to it via the web, 2) the Widget doesn't load the devices, and 3) a trigger that is supposed to run at server startup doesn't run until I start the client.

Once I start the client, the web server works fine, the Widget sees all, and as mentioned before, the "at Indigo Server Startup" trigger actually triggers. Your questions:

1) What version of OS X are you running? 10.4.7

2) Are you running the client/server/installer all under the same admin user account? Yes. There is only one account on this machine.

3) Do you have the "Start and connect to Indigo Server..." checkbox turned on (Start Local Server dialog)?
zyes

4) Do you have the "Auto start Indigo Server on user login..." checkbox turned on?
yes

5) Presuming those are both on and Indigo Server is not starting, then run the following from the Terminal and post the response back to the forum. Actually, run the following regardless of your settings on #3 and #4:

Code: Select all

[Mini:~] bcmayes% ps -axwww | grep "Indigo"
  444  ??  S      0:02.24 /System/Library/CoreServices/Dock.app/Contents/Resources/DashboardClient.app/Contents/MacOS/DashboardClient /Users/bcmayes/Library/Widgets/Indigo.wdgt/ 129 41a59c7db9b69b39 f
  450  ??  S      0:24.79 /Applications/Indigo 2.app/Contents/MacOS/Indigo 2 -psn_0_6946817
  454  ??  Ss     0:06.65 /Library/Application Support/Perceptive Automation/Indigo 2/IndigoServer.app/Contents/MacOS/IndigoServer
  455  ??  S      0:03.37 python /Library/Application Support/Perceptive Automation/Indigo 2/IndigoWebServer/IndigoWebServer.py -i 1176 -w 6484 -cfn
[Mini:~] bcmayes% ls -al ~/Library/LaunchAgents/
total 8
drwxrwxr-x    3 bcmayes  staff   102 Sep 30 01:59 .
drwx------   56 bcmayes  staff  1904 Sep 29 23:31 ..
-rw-rw-r--    1 bcmayes  staff   551 Sep 30 01:59 com.perceptiveautomation.IndigoServer2.plist
[Mini:~] bcmayes% launchctl list
com.perceptiveautomation.IndigoServer2

6) What does the Indigo Event Log look like? Is it even trying to start the server? Are there any errors in the system console.log file related to Indigo?

Event log doesn't indicate server startup until the time I actually launch the client.

7) Do you have any custom AppleScript running on Server Launch or periodically via a Time/Date Action? Do you have any custom attachment scripts? If so, what are they doing?

I'm running the embedded script posted in another topic that queries all devices for status. I've removed the "delay" verb from the script, however I've instructed the trigger to delay by .25 minutes.

I'm up and running otherwise, but for now, I have to remember to start the Indigo client or I come home to a dark house.

Byron

Sorry to be cutting in again on this topic, but I thought I'd include my trouble here because it has to do with starting the server after installing beta 5.

I still get an error the first time it loads my scripts, but I don't get an error when I click "reload scripts". I doesn't really matter to me, but I'm mentioning it because it may mean something to Matt.

I included one "off" command at the end just to put a timetsamp in after the reload.

Log follows:

Sep 30, 2006 10:58:20 PM
Starting Indigo Server version 2.0.0 beta 5
Loading attachments
"AccuWeather.scpt" script loaded
"device target attachment.scpt" script loaded
"group target attachment.scpt" script loaded
"iSEEu.scpt" script loaded
"iTunes attachment.scpt" script loaded
"scenes attachment.scpt" script loaded
"SpyCamera.scpt" script loaded
"time stamp attachment.scpt" script loaded
Error script error: Expected end of line, etc. but found identifier.
Client connected
Client connected
Client connected

Sep 30, 2006 10:58:23 PM
Connected to SmartHome PowerLinc USB E
PowerLinc address 07.8B.BB, firmware version 2.12

Sep 30, 2006 10:58:26 PM
PowerLinc Read links database
PowerLinc INSTEON plc link to controller 00.02.98, flags 03, group 01, data 00 00 FF
PowerLinc INSTEON plc link to controller 00.5B.B0, flags 03, group 01, data 00 00 FF
PowerLinc INSTEON plc link to controller 01.1C.B6, flags 03, group 01, data 00 00 FF
PowerLinc INSTEON plc link to controller 03.26.96, flags 03, group 01, data 00 00 FF
PowerLinc INSTEON plc link to controller 03.38.34, flags 03, group 01, data 00 00 FF
PowerLinc INSTEON plc link to controller 03.80.51, flags 03, group 01, data 00 00 FF
PowerLinc INSTEON plc link to controller 05.9F.90, flags 03, group 01, data 00 00 FF
PowerLinc INSTEON plc link to controller 05.9F.DF, flags 03, group 01, data 00 00 FF
PowerLinc INSTEON plc link to controller 06.1F.C2, flags 03, group 01, data 00 00 FF
PowerLinc INSTEON plc link to controller 07.8D.A3, flags 03, group 01, data 00 00 FF
PowerLinc INSTEON plc link to controller 07.A0.5B, flags 03, group 01, data 00 00 FF

Sep 30, 2006 10:58:37 PM
Loading attachments
"AccuWeather.scpt" script loaded
"device target attachment.scpt" script loaded
"group target attachment.scpt" script loaded
"iSEEu.scpt" script loaded
"iTunes attachment.scpt" script loaded
"scenes attachment.scpt" script loaded
"SpyCamera.scpt" script loaded
"time stamp attachment.scpt" script loaded

Sep 30, 2006 10:59:02 PM
Sent X10 "LR Table Lamp" off

czvi wrote:   Error    script error: Expected end of line, etc. but found identifier.

Because it doesn't occur on reloading the attachments, I don't believe that error message is related to your attachment scripts. I think the problem is in one of your embedded AppleScripts inside of one of your Trigger Actions, Time/Date Actions, or Action Groups.

Regards,
Matt

Hi Byron,

Thanks for the details -- I'm glad it looks like beta 5 is working for you now. I'm still puzzled by the fact that the IndigoServer isn't auto-launching on login though.

If you choose the Indigo 2->Stop Server menu item, then that not only stops the server but it also prevents it from auto-launching the next time the machine is booted. But choosing the Start Local Server option or quitting and running the client will re-install the auto-launch on login item. Did you by chance choose the Stop Server item before you did a shutdown/reboot?

If not, then we need to dig a bit deeper. The answers to my questions and Terminal output you gave aren't showing anything obviously wrong. Try these steps:

  1. Launch the client.

  2. Choose Start Local Server... and make sure the appropriate checkboxes are enabled. Press the Start Server or Change Settings button.

  3. Quit the client.

  4. Do these terminal commands:

Code: Select all

ps -axwww | grep "Indigo"

launchctl list

less ~/Library/LaunchAgents/com.perceptiveautomation.IndigoServer2.plist | grep "Disabled"


  5. Restart the machine.

  6. Do the terminal commands from #4 again.

  7. Open the Console application (in Applications/Utilities) and view the console log with the filter (search) words "indigo" and then with "launchd" and "launchctl". Any hits?

  8. Launch the client.

  9. Do the terminal commands from #4 again.

Thanks for helping to track this one down...

Regards,
Matt

Disregard all of the above -- I believe I have found the problem and will have it fixed for beta 7.

Matt

support wrote:Disregard all of the above -- I believe I have found the problem and will have it fixed for beta 7.

Matt

Matt,

A weekend of testing reveals that all is now well in this regard, as well as the AppleScript error and the "unhandled" thingy.

Thanks! I'll be ponying up once my charge card rolls over into a new cycle.

Byron

Hi Byron,

Thanks for the update. And I'm glad everything seems to be working better now...

Regards,
Matt