Bugzilla – Bug 12319
RTC Backup Alarm stops after 1 min if no network connections
Last modified: 2011-05-09 15:20:22 UTC
If no network connection the alarm should be longer than 1 min - see also posted thread: http://forums.slimdevices.com/showthread.php?t=64292 By the way - how do I update firmware on my boom. As I understand current version is 46. My boom has 43 and i do not get a notification regardless if connected to squeezenetwork or squeezecenter. Documentation says that i can press brightness key on the remote to force update - but the boom rempote does not have a brightness key ... /Norbert.
This is by design
My 2c - alarms should never stop unless either a) stopped by the user, or b) a sufficiently long timeout has occurred. Alarms are simply TOO IMPORTANT to many peoples lives. I'd like to see Logitech up the ante re: alarms. Alarms: YES or Alarms: NO, but no Alarms: USUALLY. Either alarms are a *reliably implemented feature*, or they are just toys, not to be trusted.
*** Bug 12401 has been marked as a duplicate of this bug. ***
I agree, it should go for more than 1 minute, it should behave in a loop until either snooze is pressed or the alarm is cancelled. I purchased this device primarily as an alarm clock so it's really important. I've missed two alarms in the last week, I have no idea why, I'd go so far as saying that it didn't go at all, no backup alarm or anything.... until I saw this!
Weldon and Andy note that we should see what other alarm clocks do. Seth, do you have any comments to add?
I did a little digging. It's actually a bit tough to nail down a "typical" alarm duration, but it's certainly longer than one minute... The typical alarm clock _snooze_ duration is 7-9 minutes. The reasoning is that five minutes is deemed too short and 10 minutes is too long. Based on this, we should increase the backup alarm duration to 30 minutes since five minutes is probably the minimum and one hour is probably too long.
Changed title to clarify we are talking about the RTC (real time clock) built in alarm duration.
I'm not sure why the RTC clock behavior should be any/much different than the standard clock.
Changed priority. Reassigned to Felix. Please reassign as appropriate if this one's not for you Felix.
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
For Completeness, another thread discussing this issue: http://forums.slimdevices.com/showthread.php?p=460932
My 2cts on the subject, as I own a Boom and have played a lot with power management on the SC server, making the setup unstable at times. I have been saved more than once by alarm clocks other than the Boom which failed to wake me. My normal setup: - I use alarms on the Boom, volume at 55 or 60%, on a local playlist. The Boom is wired. I've had troubles in wireless mode, and using internet radios (URLs changing or timeouts) - I always keep my phone as a backup. It is self-powered. I use 3 alarms at 5 minutes distance, each lasts about 60 seconds (not my choice). Volume is set to max. It's unpleasant but not extremely loud of course. When I have a plane to catch, I add my old radio clock that I did not remove from the bedroom. It has backup battery power. It plays FM radio -hint- or a buzzer for 60 minutes. Volume is set to max. That's loud. My opinion on the Boom backup alarm: It is fired in emergency situation, so I'd try to make it last as long as possible and gradually go to max volume: generally it takes me a few *minutes* to react in the morning. And at equal volume, some sounds will wake me and others not. I am unclear as if the Boom has any capability of ringing the alarm if network failure is due to power failure. The battery option in Radio is a must-have in this use, i guess.
There are two levels of backup alarm. One is used when there still is a network connection and the desired playlist or radio station fails to play. This bug is not about this situation. This bug (and hence the title RTC - real time clock) talks about the second level of backup alarm (duped RTC alarm) which comes into play in case the network connection is lost when the alarm is due. It is not a playlist nor can the RTC alarm sound be changed by the user. It is a five tone sequence which is programmed fix into firmware. The RTC alarm currently is set to last for one minute. It has been suggested to up this time to the same length a regular alarm is using which is one hour. Seth: you suggested 30 minutes in comment #6. Is that still what you want or should I set it to one hour to make it the same length as the regular alarm time as Dean suggested in comment #8? BTW: Snooze time is set to 9 minutes for the RTC alarm. Thanks Felix
Dean's right. There is no reason it should be different than the standard clock. So, it should be an hour.
== Auto-comment from SVN commit #6492 to the player repo by felix == == https://svn.slimdevices.com/player?view=revision&revision=6492 == Bug: 12319 +1 Description: Extend RTC backup alarm (SBB) from 1 minute to 60 minutes.
This will be available with SBB firmware version 51.
Changed release target since firmware 51 is not targeted for 7.5.0
Boom FW 56 SBS 7.6.0 r 32390 RTC backup alarm (5 tones) continues until snoozed or stopped (60 minutes)