My Flow is not working well. Who can help me?

I have set up my Sonos speakers in the living room as an alarm clock. It starts playing properly every morning, but regularly turns off by itself after 10 minutes. I have already changed several settings, but I am stuck now. Who can help me?

Unfortunately, I cannot upload multiple photos to show my entire flow.

Is the timer “Sonos Wekker Woonkamer” set for 10 minutes? You can upload multiple photos if you place them in separate replies.

Zoom snel uit op uw scherm door de Ctrl-toets(of Cmd op Mac) ingedrukt te houden en op de min-toets (-) te drukken. Herstel de zoom direct naar 100% met Ctrl + 0 . In browsers zoals Chrome/Edge werkt dit direct, en het werkt ook in Windows-toepassingen.

[image]Goog

Some thoughts:

  • Do you perhaps have another conflicting flow that also controls your Sonos speaker?
  • Might there be a maximum number of seconds that can be set in the timer card from the Countdown app? Try using a timer from the Chronograph app instead. You can also set other units in timer cards, like minutes.

Maybe look in the history of the device (sonos woonkamer). It may log what happened and by whom or what.

Thanks for the tip. I try to work whit Chronograph

How can i check the history of a device, I cannot found it.

I think he is referring to this tab in the device tile. It typically shows info on who/what flow turned on/off a device. Not sure whether it is available in a Sonos device tile.

When a device is opened (long press in app) the bottom right symbol (see screenshot). Not all devices show history and not everything is logged. In screenshot an example of a light (i don’t have sonos speakers)

Unfortunately, I cannot see a history on the Sonos speakers, but I just noticed that I can for the lights.

It was worth a try, it could have given some insights of what’s happening with the device.

That said, I think @SunBeech thought about the maximum number for the timer is a decent assumption. Try with Chronograph or Flowbits as alternatives for setting timers, and indeed use a higher “unit” (seconds, minutes, hours, days, …), in this case hours, so you don’t need to enter a high number (2 hours instead of 7200 seconds). Both are the same, but some fields use a maximum number.

Thanks for the tips. I’m going to get started with Chronograph and Flowbits.

The strange thing was, this morning the flow worked perfectly; it started properly, ran smoothly for 2 hours, and then stopped. It has done this before, one morning it did and the next it didn’t. In your opinion, is there an explanation for this?

Well the “history” would be have been a great help in this ;). Since it does work, the problem is not with this flow.
The other thought of Sunbeech could explain, but we are missing logs to verify them. Seems like either a manual intervention or a flow conlict (using same timer elsewhere for example).

Another thought: If I am correct you play online content on your Sonos speaker. Could it be that there sometimes is a hick-up in the WiFi connection? If the Sonos speaker cannot fetch the online music steam anymore, it also stops playing.

As far as I know, I have good Wi-Fi, which isn’t standard anymore. I have an Alta Labs system connected. It is properly configured. And as far as I know, there are no connection fluctuations. Homey is connected via Ethernet, the Sonos via Wi-Fi. Do you have any tips on how I can check if the Sonos has a constant connection or if something is fluctuating?