Sonos no longer playing track


#1

1) Give a description of the problem
Last year I created a piston to create a visible (bulb colour change) and audible (Sonos playing a track) when the room temperature exceeds a threshold. This is needed because the gas fire is not thermostatically controlled.

2) What is the expected behaviour?
Bulb colour change and sound file played over Sonos speakers when temperature trigger is reached

3) What is happening/not happening?
Bulb colour changes on trigger condition but sound is no longer played when piston executes on specified condition
Sonos is working in it’s normal way
Sound file still plays from URL

**4) Post a Green Snapshot of the piston![image|45x37]

5) Attach logs after turning logging level to Full
(PASTE YOUR LOGS HERE THEN HIGHLIGHT ALL OF THE LOGS AND CLICK ON THE </> ICON TO FORMAT THEM CORRECTLY)
06/10/2021, 10:02:57 +718ms
+1ms ╔Received event [lounge].temperature = 20.9 with a delay of 42ms
+29ms ║RunTime Analysis CS > 12ms > PS > 4ms > PE > 13ms > CE
+31ms ║Runtime (36874 bytes) successfully initialized in 4ms (v0.3.110.20191009) (29ms)
+32ms ║╔Execution stage started
+40ms ║║Comparison (decimal) 20.9 rises_above (decimal) 20.8 = true (1ms)
+42ms ║║Cancelling condition #2’s schedules…
+43ms ║║Condition #2 evaluated true (5ms)
+44ms ║║Cancelling condition #1’s schedules…
+44ms ║║Condition group #1 evaluated true (state changed) (8ms)
+47ms ║║Cancelling statement #3’s schedules…
+56ms ║║Executed physical command [Kitchen].playTrack([http://www.xxx.org.uk/wp-content/uploads/2020/12/jnglbell.wav]) (4ms)
+57ms ║║Executed [Kitchen].playTrack (6ms)
+62ms ║║Executed physical command [Living room].playTrack([http://www.xxx.org.uk/wp-content/uploads/2020/12/jnglbell.wav]) (3ms)
+63ms ║║Executed [Living room].playTrack (5ms)
+66ms ║║Cancelling statement #5’s schedules…
+72ms ║║Executed physical command [xxx Light].setColor([[hex: #FF0000, hue:0, saturation:100, level:50]]) (2ms)
+73ms ║║Executed [xxx Light].setColor (4ms)
+76ms ║╚Execution stage complete. (44ms)
+77ms ╚Event processed successfully (77ms)

REMOVE BELOW AFTER READING