Update on the Sonos App from Patrick Spence

Thanks @Rhonny and @Ken_Griffiths for trying to help. I’ve just checked and both the iOS app and the Sonos system are up to date (both are set to auto update as well). All the speakers are on 16.3.1 build 80.1-55240.
 

if the issue is to do with the timezone data not being available for the speaker, do you know how I might be able to resolve this please?

Thanks a lot for your support

If you are on 16.1 app and firmware I wouldn’t download it unless you are going to buy new products like the ace

So its been 2.5 weeks since the mea culpa and the app is still slow and just overall uggh…

Any chance we can just go back to the old app? 

This release might be a pivotal point in the future of the company….

You can set the time zone in Settings>Manage>Date and Time 

I’d be very surprised if most consumer routers had an ntp server service in them.

The router itself will have an ntp client to update its own time, but for home/smb use it’s a server package and config that would be an unnecessary thing for the manufacturer to include and provide.

Devices inside the network that need ntp will more likely have an internet ntp pool address in their default config because it is accurate enough and its unrealistic to expect a home user have their own ntp server. Devices could even ignore any dhcp time server options they receive depending on manufacturer setup.

I’m not sure how Sonos sets the time on new devices, at a guess, as part of initial setup, the controller app uses the tablet/mobile time to set the Sonos device time, then once it’s connected to the WiFi network it may perform an ntp sync with an external pool at intervals. Future manual time/timezone changes probably get set in the speakers when changed in app.

For enterprise usage, it would be odd having the router provide it rather than it being distributed from a separate server.

Confirmed @sigh, I’ve never seen a consumer Wi-Fi router serve as an in-house NTP server. Also worth noting that clients/devices will not ‘inherit’ their NTP server from a Wi-Fi router, so if you want everything under your roof to sync with the same NTP server (a nice-to-have, not a must-have) you’ll need to make that assignment across all your devices.

As an aside, I recently discovered that my Windows machine was not performing scheduled NTP syncs. Appears that the requisite “Windows Time” service is not necessarily started by default. Quick fix …

https://helpdeskgeek.com/how-to/how-to-fix-time-synchronization-failed-in-windows/

My Technicolor DGA4135 router has the following - access to NTP servers, it’s not an NTP server in itself. But my understanding (and experience from device fails) was that the router requires access to the NTP server to establish the time on certain devices. My question was whether the OP re. alarms was missing access and so the Sonos wasn’t able to determine the time... But if that is not the case then I will be on my way. (Not sure how this thread became so off-track!)

Hi @Rhonny, I think Sonos devices are “hardcoded” to a specific NTP server. I suppose it is possible that privacy filtering (see below) could prevent that synchronization. And then there is the separate matter of setting the correct timezone.

Ah, I think I know what you mean.

The router could be an indicator that there is a problem between your ISP connection and time servers. If it has ntp servers set but the router can’t keep the correct time it potentially means anything on your network that is also needing to connect to the internet ntp servers are likely to have a hard time.

Thanks , how do find which version you are on skullc ?