Say on Sonos creates delay in rule

Setup, Configuration and Use Scripts & Rules
1

Hi everybody,
I have a problem with my sonos speaker. In my rule I want to make an announcement over my speakers and let some lights blink.
The say command on my Sonos delays the residual execution of the rule about 20 seconds.

when 
    Item Klingel received command ON
then   
    sendBroadcastNotification("Es hat gerade jemand geklingelt")
    say("Achtung, es hat jemand geklingelt.", "picotts:deDE", "chromecast:chromecast:77066852f54e39fb60633a668d726f83")
    // say("Achtung, es hat jemand geklingelt.", "picotts:deDE", "sonos:SYMFONISK:RINCON_347E5CF0AE6A01400")
    LightStates = storeStates(BellLights)
    BellLights.members.forEach[item | sendCommand(item,ON)]
    Thread::sleep(1500)
    BellLights.members.forEach[item | sendCommand(item,OFF)]
    Thread::sleep(1500)
    BellLights.members.forEach[item | sendCommand(item,ON)]
    Thread::sleep(1500)
    BellLights.members.forEach[item | sendCommand(item,OFF)]
    Thread::sleep(1500)
    BellLights.members.forEach[item | sendCommand(item,ON)]
    Thread::sleep(1500)
    BellLights.members.forEach[item | sendCommand(item,OFF)]
    Thread::sleep(1500)
    restoreStates(BellLights) 
end

When I execute the rule like this all is fine. Blinking and announcement on the google home happen pretty much instantly. As soon as I uncomment the “say” on the sonos speaker. The blinking is delayed for 20 seconds after start of rule execution.
Anyone experienced something simular before?
Best regards
Daniel

2

So, if you already have a task in the “say” queue, and try to add another, it stops further rule execution until it gets the chance to begin?
I suppose that’s not too surprising, I don’t know if it is documented.

A workaround would be to spin off the second say action into it’s own thread using a short duration createTimer()