After updating to 80.00.08 (iOS) and updating the system to 16.2 I was able to create new alarms (the old ones were still missing). Alarm didn’t start at the set time and it looks like they are delayed by two hours.
I think there is currently no way to change the system‘s default time, either.
So I might set up all alarms two hours too early and hope that it’s not automatically changed
Time zone changed in 80.00.08 update
Show first post
This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.
The ‘golden’ App does have Time Zone option, Settings » System » Date & Time » Time Zone. If you still have access to golden App, could be worth checking.
I still suspect Sonos is now using some kind of geolocation detection, based on IP address and/or DNS lookups, and in few cases this is not resolving correctly. I have seen incorrect DNS geolocation before (Microsoft not Sonos), when proxy DNS servers are used.
Alarms were not available in initial release due to some ‘corruption’, maybe this was Time Zone data?
5 hour difference for me here (Houston, TX)
Woke up at 3:00 am this morning instead of 8. Pretty pissed lol.
Dear All,
is there any possibility to assign some additionall funcitonality to buttons avaible on the voicespeaker?
Not currently, no.
I can confirm that on my system in eastern Australia. I have now set my alarm at what looks like 10 hours early and that works.
can Sonos developers please look at fixing this?
Update version 80.04.04 - It's really exasperating. Now it is finally possible to set a time zone for the alarm clock function, but unfortunately daylight saving time has not been taken into account. It's exasperating, these are absolute basics that are not taken into account during app development.
+9Sam_hh wrote:
Update version 80.04.04 - It's really exasperating. Now it is finally possible to set a time zone for the alarm clock function, but unfortunately daylight saving time has not been taken into account. It's exasperating, these are absolute basics that are not taken into account during app development.
This has the hallmarks of a poor specification/requirement being given to either an overloaded/tired development team and/or an outsourced team.
I wouldn’t be surprised to find an overloaded team making silly mistakes, fighting deadlines and doing the minimum to meet requirements and reduce the backlog against internal pressures from above. Whereas previously they might have questioned requirements, now I expect they’re struggling to keep on top of things with how long this has been going on given the state of the May release.
An outsourced team will generally code to the client requirements. If the client ticket didn’t ask for daylight savings, the work doesn’t included it.
What seems even stranger, these days, is a user needs to even think about having to enter the time/timezone. It’s an internet connected system with an app that runs on a computer/phone/tablet. Except in edge cases there should be no reason a user needs to manual set the timezone or summertime. 🙄
Los Angeles, California here and my alarm turns on 7 hours ahead. Seems like we are all waiting for this bug to be fixed.
Thank you Sonos,
I can confirm that you have fixed the alarm, by adding a time zone setting under manage.
That works well, thank you
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.