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
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
Code:
[COLOR=#000000]11/22/2009 9:17:12 PM [/COLOR] [COLOR=#000000]Sonos [/COLOR][COLOR=#000000]HS virtual device "Sonos Bonus Room Status Change" has been updated.[/COLOR][COLOR=#000000] 11/22/2009 9:18:00 PM [/COLOR] [COLOR=#000000]Event [/COLOR][COLOR=#000000]Event Trigger "Sonos Power State"[/COLOR] [COLOR=#000000]11/22/2009 9:18:00 PM [/COLOR] [COLOR=#000000]Event [/COLOR][COLOR=#000000]Running script in background: SonosPower.vb[/COLOR] [COLOR=#000000]11/22/2009 9:18:08 PM [/COLOR] [COLOR=#000000]Sonos [/COLOR][COLOR=#000000]Updating virtual device status of Bonus Room[/COLOR] [COLOR=#000000]11/22/2009 9:18:08 PM [/COLOR] [COLOR=#000000]Sonos [/COLOR][COLOR=#000000]All virtual device property monitors for Bonus Room have been updated.[/COLOR] [COLOR=#000000]11/22/2009 9:18:08 PM [/COLOR] [COLOR=#000000]Sonos [/COLOR][COLOR=#000000]HS virtual device "Sonos Bonus Room Status Change" has been updated.[/COLOR] [COLOR=#000000]11/22/2009 9:19:00 PM [/COLOR] [COLOR=#000000]Event [/COLOR][COLOR=#000000]Event Trigger "Sonos Power State"[/COLOR] [COLOR=#000000] 11/22/2009 9:19:00 PM [/COLOR] [COLOR=#000000]Event [/COLOR][COLOR=#000000]Running script in background: SonosPower.vb[/COLOR]
Comment