Bugzilla – Bug 16545
alarm runs twice and does not turn SB to standby after timeout
Last modified: 2011-01-31 11:12:22 UTC
Sceduled alarms do start two times. First in time and second one minute later. After Thema given timeout the SB does not switch to standby, the menu is shown. By turning the on off button the SB will restart - Shows the SB logo, think a warm restart cause no screen showing the connection to mysb or the router getting the ip. The problem occurs on SB classic and SB boom.
See also topic in forum: http://forums.slimdevices.com/showthread.php?t=81529
Ist schon unglaublich wie ernst man hier die Fehlermeldungen nimmt.
When I switch the alarm off and then on again it seems to be working ok for one wakeup call. The next time it's messed up again.
*** This bug has been confirmed by popular vote. ***
Using a Boom on MSB.com waking to an internet radio stream with Fade In Alarm set to "Yes". Alarm comes on at 5:30am and starts to fade in. I press Power Off after perhaps 5 seconds and it turns off. At 5:31am it comes on and starts to fade in again. I press Power Off and it stays off. About 10% of the time it will correctly not come on the second time. (This happens the same for several alarms set at 5:30am, 5:40am and 7:30am, depending on the day of the week.)
I'm also seeing this issue. On a regular basis the alarm will sound on a BBC Radio 4 feed from mySB.com as required at 6.00am but at 6.01am it then fades back in again. At 7.00am the radio will stop but then goes to Now Playing rather than standby. This is on a Boom with firmware 50.
Same here. I use mysqueezebox.com for alarming (mo-fr: 05:45am). Alarm starts with an internet-radio-station (klassic radio hamburg). If I switch the alarm off, one minute later the alarm starts a second time.
Same as comment #7. This issue also seems to be covered by bugs: 16453 Second snooze period only 1 minute long if button pressed during first snooze period 16644 Alarm turns itself again after 1 min I found this one while searching for other open bugs that cover my other issues with radio/mysb.
I see that the real time is not up to date. The minutes are on delay between one and two minutes. Maybe this is the reason for getting the alarm a second time. I use a radio controlled clock nearby my Boom. So I can see this delay. Boom is connected with wireless lan.
Are you still seeing this issue? I was never able to reproduce it.
(In reply to comment #10) > Are you still seeing this issue? I was never able to reproduce it. The only problem with this bug is it happens at 6.00am when I'm not at my sharpest! I'm not sure if it is still happening... I'll try and do some tests at a more reasonable time of day and see if I can reproduce the issue again.
Reseted my Boom yesterday (power off, hold donw "add" (+) button, power on). Deleted all alarms. Sceduled a new serial alarm: Mo-Fr @ 5:45h, radiostation RockAntenne, timeout 20 minutes, default preferences. Same behavior this morning. Alarm started. After a minute alarm fades in second time. After 20 minutes + one alarm stops, Boom shows menu, not going back to standby mode.
(In reply to comment #12) > Reseted my Boom yesterday (power off, hold donw "add" (+) button, power on). > Deleted all alarms. > Sceduled a new serial alarm: Mo-Fr @ 5:45h, radiostation RockAntenne, timeout > 20 minutes, default preferences. > > Same behavior this morning. Alarm started. After a minute alarm fades in second > time. After 20 minutes + one alarm stops, Boom shows menu, not going back to > standby mode. I can also confirm the same. Alarm set for 6.00am for BBC R4, went off at 6.00 faded out at 6.01 and restarted then after the 1 hour timeout it stopped at 7.01am. Again as described above my boom also then sits scrolling the programme name, as though I had just stopped play, rather than switching off and displaying the time as I'm sure it used to.
*** This bug has been marked as a duplicate of bug 16446 ***
Please reopen this bug; it does not appear to be a duplicate of 16446. This has occurred pretty regularly on my Boom (running via MySB) since ~8/2010. I haven't reported it as I was (and am still) waiting for y'all to fix the general alarm foo that's been prevalent since then. The behavior I'm seeing is exactly that reported in the OP. -Don
This ist not a DUPLICATE!
The last five days (Mo-Fr) the alarm failed two times, behavior described above. I did no restarts, nor switched the Boom to my local Squeezebox-Server.
I'm fine with this bug staying open, but it is in fact a duplicate. There is one issue, server-side, that is causing doubling up of a single alarm. It only affects players connected to mysqueezebox.com, but it _does_ affect both Squeezeplay-based (Radio/Touch) and ip3k-based (Boom/Classic/Receiver) players. Leaving open, but making it dependent on 16645. The relevant debug from the client-side that demonstrates that both bugs are server-side is in that bug.
sorry, it's dependent on bug 16646
third time's a charm :) -- dependent on bug 16446
Issue is not solved after yesterday's firmware update (52) and mysqueezebox at r: 31832. (But I see the taget milestone is 7.6.0. So keep on working on it!)
I confirm, that the issue still exists in Firmware #52. I defined a alarm on weekdays. If the option "repeat alarm" is set, the alarm fades in at the given time and after a minute fades in again. Then it plays until the timeout. If the option "repeat alarm" is not set, the alarm starts at the given time, doesn't fade in a second time, plays until the timeout but will not repeat at the next day.
Thanks Juergen! I was finally able to reproduce this bug with your info. Should have a fix very soon.
== Auto-comment from SVN commit #10002 to the network repo by agrundman == == http://svn.slimdevices.com/network?view=revision&revision=10002 == Fixed bug 16545, SN alarm could repeat after 1 minute due to a bug with the timezone handling
I tested this defect on Radio, Boom, Duet, and Touch while connected to Mysqueezebox.com and was unable to reproduce.
Verified fixed, closing bug.