(In reply to comment #0)
> I have an alarm at 6:50 set to a radio stream, and another at 7:01 set to the
> Sub-Alert Sound Effect. Snooze at 5 minutes. Alarm Timeout set to 10 minutes
> (so that Alarm 1 times-out before Alarm 2 sounds.) I only use mysqueezebox.com 
> 
> Alarm 2 does not sound if Snooze is hit. (This was not the case with 7.4.1) 
> 
> Another Bug: If you have Alarm Timeout at 10, Snooze at 5, and hit Snooze after
> 8 minutes of play, the Alarm Times out at 10min, BUT at 13min the Radio turns
> on but without the Alarm Function (i.e., no Snooze/Turn off option)

I'd go farther: I had it working for a day (new radio), and now I cannot get any alarm to work: turn off all alarms, set to music, etc.

This is pretty crucial for an alarm clock.

This bug is easily reproducd on the Boom.

e.g. 1st alarm 0722, 2nd alarm 0728

1st alarm goes off, snooze (9 min), 6 mins later 2nd alarm fires. Very briefly an "alarm cancelled" (or something similar, too quick to read properly) message appears on the display, and then nothing.  The 2nd alarm does not initiate, and the 1st alarm does not come back from snooze.

Why have two alarms set?  On the Boom remote it is easy to press Off instead of Snooze.  Get this wrong and you snooze for 24hrs.  A second alarm should protect against this, obviously not as it stands though.

Keith

Sorry, should have said Vista Home Premium, SBS 7.4.2, alarm set on Boom direct.

Keith

Regarding my issue: I've discovered (I think) what the problem was on my squeezebox: apparently the squeezebox radio and the web account can end up disagreeing on the timezone, with the on-line account having priority for the alarm and the local timezone having priority for the clock.

In my case, I set the timezone on the Radio to EST (later MST) successfully. But when I looked online the timezone was PST.

The snooze on my boom, which worked fine for over a year, now works only sporatically or not at all. I have been late for work bcause of it. The device is now useless so far as the reason I purchased it. Logitech has given no time frame as to a fix. This thing cost $300.00. I feel used.

There is a new wrinkle to this behaviour. The same problem now occurs after any stream is paused rather than stopped... and it appears that the sleep function, the pause button, and the stopping of one alarm so that another can go off all involve pausing rather than stopping a feed.

Here are some use cases that show the behaviour:

1) Start a feed. Push but don't hold pause. Start a different feed. The old station information will still display on the screen (i.e. logo etc.), and the status will indicate that the (first) feed is paused rather than stopped or playing, even though you can hear the second feed. Then at an arbitrary interval (sometimes a few seconds sometimes a couple of minutes) the new feed will stop and you will hear nothing. Touching any button will start the (second) feed up again for an arbitrary short interval. And so on.

2) Start a feed, set the sleep timer. After the feed stops, start a different feed by hand or using alarm. Same behaviour as under 1. Sometimes, with the alarm, the second feed will start and then after a second or two go to the backup music or stop entirely to silence.

3) Set two alarms. When the second alarm goes off, the behaviour is as in 1) and 2).

You can prevent this behaviour happening if you push and hold pause between the first and second feeds (this changes the pause symbol to stop, and when the new feed comes up the graphics related to the second feed). Once a second feed starts, the only way of stopping the behaviour seems to be to reboot.

This is all on the SB Radio.