When it gets into the state where the NOAA script isn't updating variables, open AppleScript Editor and try the following:

Code: Select all

tell application "IndigoServer"
   set value of variable "Weather_Wind_MPH" to "0"
end tell

Did it change the value correctly? If so, uncomment the following log line and restart the NOAA script:

Code: Select all

      with timeout of webQueryTimeout seconds
         -- my LogNOAA("Weather NOAA Script Started", "", 0)


(uncomment the my LogNOAA line). Is it showing up in the log every "variableRefreshRate" seconds? The default is every 30 minutes...

I restarted the server.

I ran the NOAA sync script start up trigger.

I ran the TED start up trigger.

I ran the applescript specified in the Applescript editor. The applescript editor "hung" with the stop icon active.

Indigo continued to run fine.

Eventually the Applescript editor gave me the message: "IndigoServer got an error: AppleEvent timed out."

Do you have any trigger actions that are getting executed when one of the TED variables is getting updated? Seems like either the TED script (unlikely) or something that's getting triggered because of the TED script is causing the server to get out of whack. I'd disable all triggers based on those variable values changing and see if that stops the hang.

Another couple of thoughts:

1) How often is the TED script polling and updating the variables in Indigo?
2) Have you been running them both together for some time or have you added one of them recently?

I don't understand the TED script well, but I think it's constantly pulling data from Serial Bridge.

I've had them running together for some time but up until recently I had my own weather station running and haven't been paying attention to the NOAA output.

gregjsmith wrote:I found the issue. I am also running a start up action for TED per this script: viewtopic.php?p=20257#p20257

What do you mean by "running a start up action" exactly?

When the NOAA script stops updating because you start the TED script, what happens if you then quit Serial Bridge? Does the NOAA script (or Jay's suggestion of trying to change a variable from the Script Editor) then work?

By "start up action" I mean that I ensure that the NOAA sync script start up action trigger executtes. The TED script also starts by a start up action but I have that one disabled.

If I quit serial bridge, something happens with the indigo server that cause the client to become "unresponsive" I can force quit the client then reconnect to the server and see that the NOAA script is running again.

By the way, I reported an issue with the TED script a while ago. It seems to mess with the powerlinc if the scripts runs at start up, if I start it 30 seconds after the indigo server starts I don't have this problem. See: viewtopic.php?p=28243#p28243

Hopefully this isn't too confusing.

How frequently is your weather script updating?

It's set to the default of 30 minutes, but I have tried it at other intervals with no change in behavior.

I'm thinking that maybe there's an issue between SB and Indigo sending apple events at such a rapid pace. Try modifying the SB script to delay (there's a delay line at the top that's commented out) like maybe 15 seconds and see if that clears it up.

I've set the delay to as long as 30 seconds on the TED script but the NOAA script does not process. Another thing I noted was that the words "executing applescript" are always present when the TED script is running. I don't see that when it is not running.

That indicates that an embedded AppleScript is running and hung up. Are you sure you don't have any embedded scripts that are triggered when one of the TED variables is updated? Whatever the trigger is, it's an embedded script that's getting hung up.

Fixed! The TED script was embedded in the trigger. I saved it as a script file and attached it to the trigger. I no longer get the script executing message and the NOAA script is running.

Which TED script -- the one that communicates with Serial Bridge? If not, what is the script doing?

Embedding scripts that talk to other applications is generally a bad idea unless you're really careful to put in timeouts since AppleScripts have to run on the main thread. It can result in exactly what you saw - hangups.