Time zone changed in 80.00.08 update

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