Alarms "hidden" in System Settings with 10.4

Pissed off at having to google where to set the alarm - this is not a 'system' function. SONOS fail. Fix ASAP pls.

As enveryone said, the alarm is an every day function for us. Even set twice per day when we have to get up at différent times.
I would love to have it as accessible as My Sonos, and or through an Android widget and see the next alarm on the lock screen notification...

This update made the Sonos system unusable for one of our primary use case (at least in bedrooms)

Thanks for the future update !!!

Just to demonstrate the difference between the design of the old and new screens, I’ve attached before/after FULL SCREEN images from my phone.

BEFORE: (clean lines, attractive to look at, great use of available screen space, 10 alarms visible on one screen, nice large on/off buttons to aid selection, green button ‘on’ colour provides a nice and attractive visual aid to show at a glance which are switched off/on).

AFTER: (I’ll leave you to judge for yourself but I dislike this new version of the same screen intensely, and my dislike is increasing each time that I use it).

What I’ve also noticed is that (on my admittedly older iPad) the redesigned ‘Settings’ screens have become much more sluggish than the old. e.g. When I select ‘Alarms’ from the previous screen it takes almost 2 seconds before the Alarms screen actually appears. And just as long (if not longer) between selecting an alarm to actually see the Alarm details. I’m sometimes pressing the screen twice thinking that my first press hasn’t been registered. This is ok for accessing Settings which don’t change very often, but I access and use Alarms every day. The new screens certainly seem to be more resource hungry for some reason.

I’m very sorry Sonos designers/coders. I know that you must have put a lot of time and effort into the new ‘Settings’ redesign, but I’m afraid that I just see it as a big backwards step. From my perspective I can’t see what gains it brings, it looks ugly, performs sluggishly (at least on my older iPad) and gives me, as an end user, a poor and frustrating user experience. Please think again.

The alarm issue needs fixing and quickly! What happened to user testing?

I've posted separately under Troubleshooting, but I've just had one of my regular wake up alarms fail to go off. Not even the chime. I've never had this happen to me before and I've been using alarms for years. It's easy to jump to conclusions...

I just responded to your troubleshooting thread. Please don't jump to conclusions, the UI changes are unrelated to alarms that don't work alarms are stored on the players, not on the apps.

Hi Ryan - sorry I’ll try not jump to conclusions. I don’t want to set a hare running for you/Sonos. it just seemed a bit co-incidental.

In my defence I mentioned in an earlier post that the Alarm buttons in the new GUI were a bit ‘sticky’ but this didn’t really articulate clearly what I meant. I had the scenario when switching an alarm that the button got stuck half way between on and off for a while. So (purely from an end-user perspective) I guess that I was thinking this might have somehow confused the system or corrupted something.

That sounds a lot more like an issue in your local wifi environment, as the button push on the controller would be communicating with and getting a response from the software on your speaker(s). You may want to check the wifi interference FAQ, and see if there's something there that might be causing an issue in your local LAN. Which actually would be an excellent reason why the alarm might fail, too. If the speaker can't reach the indicated location, it falls back to the chime.

That sounds a lot more like an issue in your local wifi environment, as the button push on the controller would be communicating with and getting a response from the software on your speaker(s). You may want to check the wifi interference FAQ, and see if there's something there that might be causing an issue in your local LAN. Which actually would be an excellent reason why the alarm might fail, too. If the speaker can't reach the indicated location, it falls back to the chime.

Don't want to take this thread off at a tangent (my fault for posting here about the failed alarm). Thanks very much for this suggestion. I'll take a look.

Been using Sonos since the earlies days, all the way back to having a separate physical controller. Many of us use alarms, 'cause, well, we don't want a cheap battery operated alarm clock when we've invested $$$ in a fantastic music system.

Anyone willing to THINK about how people use alarms realizes that they are absolutely positively not a set-it-and-forget-it feature. An early meeting = an early alarm, etcetera. And when does a user change alarm settings? Yup, just before bedtime … when poking around deep in the menu structure is NOT APPRECIATED.

Burying the alarm control demonstrates an approach to UI design with little empathy for the users. I'm sorry to say, this approach has been evident for the past couple of years.

I realize this post is harsh, but this particular deeply flawed change with the alarm controls needs to garner enough attention to get fixed.