Event Action Delayed but should be immediate

[manxam]

Hey! I'm wondering if someone can help shed some light on something for me.

I have a Sonos ZP90 connected to an amplifier and am using the Sonos Real Time Script to update the "Transport State" (play/stop/pause) in HSPRO to power up/down and adjust inputs on my amplifier as required.

I have an event that is triggered when the Sonos Real Time Script changes this particular's zone to "Changed", it then executes, and changes the status back to "Unchanged". When the Sonos changes songs, stops, or pauses, it then again changes the status to "Changed" and the cycle begins again.

I use this logic to check if the Sonos has started playing or has been stopped/paused for a given amount of time (at which point the receiver should turn off)

My issue is that there is a good 40+ second delay between the HSPRO log showing the status change to "Changed" and the event being run. There are no delays setup in the event or script so I'm not certain what's causing it.

I've included a small sample of the log to show this effect. The first time the event takes 48 seconds to run, the second 52.

Any help would be greatly appreciated!

Thanks

11/22/2009 9:17:12 PM  Sonos HS virtual device "Sonos Bonus Room Status Change" has been updated.
11/22/2009 9:18:00 PM  Event Event Trigger "Sonos Power State"
11/22/2009 9:18:00 PM  Event Running script in background: SonosPower.vb   
11/22/2009 9:18:08 PM  Sonos Updating virtual device status of Bonus Room
11/22/2009 9:18:08 PM  Sonos All virtual device property monitors for Bonus Room have been updated.
11/22/2009 9:18:08 PM  Sonos HS virtual device "Sonos Bonus Room Status Change" has been updated.
11/22/2009 9:19:00 PM  Event Event Trigger "Sonos Power State"   
11/22/2009 9:19:00 PM  Event Running script in background: SonosPower.vb

[dschoppe]

Manxam,

I don't use Sonos, so I can't answer for certain, but what does your "Sonos Power State" event look like? You don't have any "do not retrigger for xx seconds" options configured do you? Also, are you using a device status change trigger or conditional trigger for this event?

Thanks,
Don

[manxam]

Thanks for your response Don. I do not have any 'do not trigger..." options set (often times there is 4-5 minutes between status changes (avg length of song)).

I have used both device status change and conditional with Status Change is Changed and both are delayed.

Is it possible that while the Sonos script is changing the status to changed/unchanged, the script is not exiting at this time? That HS is waiting for for the script to complete before starting the event?

Call me confused.

Thanks!

[dschoppe]

Originally Posted by manxam

Is it possible that while the Sonos script is changing the status to changed/unchanged, the script is not exiting at this time? That HS is waiting for for the script to complete before starting the event?

Hmmm. How many scripts are involved in this? Are you possibly making multiple calls into the same script from different events and do you possibly have the option enabled to allow only one instance of the script to run?
Just grasping here...

[manxam]

Only two scripts involved. One being the Sonons Real Time Script in question, and the second run by the event that is getting delayed. This "script" has a small case statement looking for STOP, PLAY, PAUSE and then triggers a the appropriate device.

It's written in VB.net and is only a couple of lines. It shouldn't delay anything. Also, as the event that runs this script is getting delayed, I doubt that this is it.

Thanks again for your help.

[Rupp]

What's your CPU level when the "real time" script is running? I wonder if it could be CPU blocking causing delays.