Bug 16446 - Alarm switches to backup alarm sound after 1 minute
: Alarm switches to backup alarm sound after 1 minute
Status: CLOSED FIXED
Product: SB Radio
Classification: Unclassified
Component: Alarm
: Include FW version in comment
: PC Windows (legacy)
: P1 normal with 6 votes (vote)
: 7.6.0
Assigned To: Ben Klaas
:
Depends on:
Blocks: 16545
  Show dependency treegraph
 
Reported: 2010-08-10 10:24 UTC by Chris Owens
Modified: 2011-05-16 15:54 UTC (History)
10 users (show)

See Also:
Category: Bug


Attachments
Log for alarm set to 1:38 pm (83.24 KB, text/plain)
2010-08-16 13:49 UTC, Mickey Gee
Details
Log of alarm set for 6.27 (22.72 KB, text/plain)
2010-09-08 04:46 UTC, zarniwoop75
Details
Log of alarm set for 8:00 (200.04 KB, text/plain)
2010-09-21 14:48 UTC, wastl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Owens 2010-08-10 10:24:41 UTC
Maurice reports that after updating to firmware 9009, his alarm played correctly for 20 seconds, then switches to the backup alarm sound even though the stream was playing correctly.

Perhaps we are now being too aggressive on triggering the backup alarm?
Comment 1 Mickey Gee 2010-08-16 13:49:34 UTC
Created attachment 6937 [details]
Log for alarm set to 1:38 pm

Alarm plays stream at 1:38 pm, turns off automatically at 1:39 pm, plays backup alarm a few seconds later.
Comment 2 Mickey Gee 2010-08-16 13:51:29 UTC
For comment 2:

Have log for similar situation with 9009 with Radio connected only to mysqueezebox.com:

1. Set alarm for 1:38 pm.
2. Alarm played radio stream (KQED-FM 88.5) at 1:38 pm.
3. When time on clock turns to 1:39 pm, KQED-FM stops playing.
4. A few seconds later (5 seconds?), backup alarm comes on. 

I did not press snooze button at all.

Log enclosed.
Comment 3 Mickey Gee 2010-08-16 13:58:07 UTC
Breaking up snooze into 2 distinct issues:

Bug 16453: Press button sometimes results in snooze for incorrect interval
Bug 16446: Snooze switches to backup alarm when button not pressed
Comment 4 Mickey Gee 2010-08-16 15:16:51 UTC
Changed title to accurately reflect forum feedback and reproduction scenario.
Comment 5 Ben Klaas 2010-08-23 13:28:02 UTC
While debugging the snooze interval bug 16453, I came upon a situation where the alarm switched to the fallback alarm. Note, however, that the log shows that the connection to mysb.com was severed to trigger this (serverDisconnected notification). IMO, as far as the alarm goes this is working as designed. We haven't gotten any more aggressive with the trigger for the fallback...my guess is that we are hitting more situations where mysb.com connection is severed.

Aug 23 15:17:18 squeezeplay: WARN   applet.AlarmSnooze - AlarmSnoozeApplet.lua:241 alarm_sledgehammerRearm(_pollDecodeState): server alarm in progress - audioState is 1
Aug 23 15:17:28 squeezeplay: WARN   applet.AlarmSnooze - AlarmSnoozeApplet.lua:420 _pollDecodeState(server): audioState is 1
Aug 23 15:17:28 squeezeplay: WARN   applet.AlarmSnooze - AlarmSnoozeApplet.lua:241 alarm_sledgehammerRearm(_pollDecodeState): server alarm in progress - audioState is 1
Aug 23 15:17:34 squeezeplay: INFO   net.comet - Comet.lua:804 Comet {mysqueezebox.com}: _getEventSink error: closed
Aug 23 15:17:34 squeezeplay: INFO   net.comet - Comet.lua:997 Comet {mysqueezebox.com}: handleAdvice state=CONNECTED
Aug 23 15:17:34 squeezeplay: INFO   squeezebox.server - SlimServer.lua:734 disconnected mysqueezebox.com idleTimeoutTriggered: nil
Aug 23 15:17:34 squeezeplay: INFO   applet.AlarmSnooze - AlarmSnoozeApplet.lua:367 notify_serverDisconnected: SlimServer {mysqueezebox.com} is now disconnected
Aug 23 15:17:34 squeezeplay: WARN   applet.AlarmSnooze - AlarmSnoozeApplet.lua:374 notify_serverDisconnected: SlimServer {mysqueezebox.com} - while server alarm in progress! state server triggering fallback alarm!
Aug 23 15:17:34 squeezeplay: WARN   applet.AlarmSnooze - AlarmSnoozeApplet.lua:487 openAlarmWindow()rtc false
Aug 23 15:17:34 squeezeplay: WARN   applet.AlarmSnooze - AlarmSnoozeApplet.lua:537 openAlarmWindow: fallback alarm activation
Aug 23 15:17:34 squeezeplay: WARN   applet.AlarmSnooze - AlarmSnoozeApplet.lua:430 soundFallbackAlarm()
Aug 23 15:17:34 squeezeplay: INFO   audio.decode - Playback.lua:177 loop file applets/AlarmSnooze/alarm.mp3
Aug 23 15:17:34 squeezeplay: INFO   audio.decode - decode_start_handler:277 init decoder mp3
Aug 23 15:17:34 squeezeplay: INFO   applet.AlarmSnooze - AlarmSnoozeApplet.lua:455 Fallback alarm will timeout in 3600 seconds
Comment 6 Ben Klaas 2010-08-23 13:34:08 UTC
additional info:

serverDisconnected notification shows mysb.com goes down at 15:17:34 and client triggers fallback alarm:

Aug 23 15:17:34 squeezeplay: INFO   net.comet - Comet.lua:804 Comet {mysqueezebox.com}: _getEventSink error: closed
Aug 23 15:17:34 squeezeplay: INFO   net.comet - Comet.lua:997 Comet {mysqueezebox.com}: handleAdvice state=CONNECTED
Aug 23 15:17:34 squeezeplay: INFO   squeezebox.server - SlimServer.lua:734 disconnected mysqueezebox.com idleTimeoutTriggered: nil
Aug 23 15:17:34 squeezeplay: INFO   applet.AlarmSnooze - AlarmSnoozeApplet.lua:367 notify_serverDisconnected: SlimServer {mysqueezebox.com} is now disconnected
Aug 23 15:17:34 squeezeplay: WARN   applet.AlarmSnooze - AlarmSnoozeApplet.lua:374 notify_serverDisconnected: SlimServer {mysqueezebox.com} - while server alarm in progress! state server triggering fallback alarm!

comet message at same timestamp shows advice is to retry in 25.621 seconds:

Aug 23 15:17:34 squeezeplay: INFO   net.comet - Comet.lua:1038 Comet {mysqueezebox.com}: advice is retry, connect in 25.621 seconds


25 seconds later, comet attempts reconnection and eventually succeeds:

Aug 23 15:17:59 squeezeplay: WARN   net.comet - Comet.lua:876 Comet {mysqueezebox.com}: _response, /meta/reconnect id=nil failed: invalid clientId
Aug 23 15:17:59 squeezeplay: INFO   net.comet - Comet.lua:997 Comet {mysqueezebox.com}: handleAdvice state=CONNECTING
Aug 23 15:17:59 squeezeplay: INFO   squeezebox.server - SlimServer.lua:734 disconnected mysqueezebox.com idleTimeoutTriggered: nil
Aug 23 15:17:59 squeezeplay: INFO   applet.AlarmSnooze - AlarmSnoozeApplet.lua:367 notify_serverDisconnected: SlimServer {mysqueezebox.com} is now disconnected
Aug 23 15:17:59 squeezeplay: WARN   applet.AlarmSnooze - AlarmSnoozeApplet.lua:380 notify_serverDisconnected: SlimServer {mysqueezebox.com} - disconnected, but no server alarm in progress : nil
Aug 23 15:17:59 squeezeplay: INFO   net.comet - Comet.lua:1038 Comet {mysqueezebox.com}: advice is handshake, connect in 0 seconds
Aug 23 15:18:00 squeezeplay: INFO   squeezebox.server - SlimServer.lua:710 connected mysqueezebox.com
Aug 23 15:18:00 squeezeplay: INFO   applet.AlarmSnooze - AlarmSnoozeApplet.lua:348 notify_serverConnected: SlimServer {mysqueezebox.com} is now connected
Aug 23 15:18:00 squeezeplay: INFO   applet.AlarmSnooze - AlarmSnoozeApplet.lua:351 local player connection status is false
Aug 23 15:18:00 squeezeplay: INFO   squeezebox.server - SlimServer.lua:722 self.mac being set to---->nil
Aug 23 15:18:01 squeezeplay: INFO   applet.SlimDiscovery - SlimDiscoveryApplet.lua:453 connected Squeezebox Radio
Aug 23 15:18:01 squeezeplay: INFO   squeezeplay.applets - AppletManager.lua:708 store settings: SlimDiscovery
Aug 23 15:18:01 squeezeplay: INFO   applet.AlarmSnooze - AlarmSnoozeApplet.lua:296 notify_playerCurrent(LocalPlayer {Squeezebox Radio})
Comment 7 zarniwoop75 2010-09-08 04:46:08 UTC
Created attachment 6951 [details]
Log of alarm set for 6.27
Comment 8 zarniwoop75 2010-09-08 04:53:22 UTC
I am using my controller as an alarm clock to wake up to absolute radio on mysqueezebox.com. Sometimes the alarm fades in correctly to the radio station then after a minute or so sound stops abruptly and I hear a faded in announcement telling me there is a problem with the stream. This is followed by the backup alarm at a barely audible level. After an hour at this level (the alarm timeout period) the volume of the backup alarm suddenly changes to a much higher (more normal) volume and continues indefinitely I suspect. I have attached a log where the alarm goes off at 6.27 and the radio station fades in. At 6.28 the audio stops and I hear the faded in announcement followed by the fallback alarm. I have now updated the controller firmware to 9009 and the issue remains. The same issue occurs when an alarm is set on the receiver.
Comment 9 vendetta_4_v 2010-09-13 23:46:59 UTC
Just tested it on my SB radio

- Both Ethernet connection and Wireless
- Both with Server and without installed
- Both with "Internet radio stations" and with Applets (Tried with Last FM and    Soma. 
- I'm using Acc. pack
- Latest firmware and 7.51 server

Alarm starts on time but after a few seconds the Backup alarm kicks in.
If I press pause on the remote the radio starts playing the music again.

- Will try without acc. pack
- Will check exactly how much today.
- Will check if happens when plays local server music
- Will get the logs tomorrow and attach here
Comment 10 wastl 2010-09-14 14:21:05 UTC
I have the same problem with firmware 9009, the alarm is set at 8:00, my configured radio stream fades in and plays for 20 seconds, then it stops and the fallback alarm fades in. Sometimes I cannot snooze or turn it off, I have to press the power off button to make it stop. Also in the log the fade in of the backup alarm appears twice each time. There is no error other than the SBS not being available, but the Radio is connected to mySB.com, so it should not bother about the SBS. I can attach the log if necessary.

I hope this can be fixed in the next FW, this is really really annoying and since I bought SB radio I have to rely on my iPod to wake up since the radio unreliable. It was much worse a few FW back, but it is still far from what I expect of an alarm clock.
Comment 11 wastl 2010-09-21 14:48:11 UTC
Created attachment 6986 [details]
Log of alarm set for 8:00

One day after I wrote my comment here the radio started with a new behaviour:
* at 8:00 (time of alarm) the radio fades in
* after 20 seconds the radio stops and the fallback alarm fades in
* I turn off the fallback alarm and (this is new) the radio starts to play again!
I attached the log in case it helps resolving the alarm issues.
Comment 12 Nicholas 2010-09-30 11:39:05 UTC
Squeezebox Radio running with mysqueezebox.com r9009.  Every morning without fail, after playing a radio stream for one minute, the radio goes to the annoying fall-back alarm. 

If I edit /usr/share/jive/applets/AlarmSnooze/AlarmSnoozeApplet.lua and remove all the code in the soundFallbackAlarm function the radio stream alarm works perfectly every morning.  

function soundFallbackAlarm(self)
-- all code deleted
end

Perhaps the fall-back alarm is being triggered too easily?
Comment 13 Ben Klaas 2011-01-13 14:53:23 UTC
candidate for 7.6.0
Comment 14 Mickey Gee 2011-01-19 09:19:57 UTC
*** Bug 16545 has been marked as a duplicate of this bug. ***
Comment 15 Graham C 2011-01-19 09:50:21 UTC
(In reply to comment #14)
> *** Bug 16545 has been marked as a duplicate of this bug. ***

Hi, I'm not sure if from a code perspective this is a duplicate of 16545 but as one of the people who reported on that bug, the symptoms recorded on this bug are not the same as I am encountering.

On no occasion have I ever had the alarm start and then it fall back to the backup alarm after one minute.

The issue I reported on 16545 is that after one minute the stream restarts. This happens every morning so is not linked to any loss of MYSB and the backup alarm.
Comment 16 Mickey Gee 2011-01-19 09:58:21 UTC
*** Bug 16644 has been marked as a duplicate of this bug. ***
Comment 17 Steve Smith 2011-01-20 08:47:48 UTC
(In reply to comment #15)
> (In reply to comment #14)
> > *** Bug 16545 has been marked as a duplicate of this bug. ***
> 
> ...the symptoms recorded on this bug are not the same as I am encountering.
> 
> On no occasion have I ever had the alarm start and then it fall back to the
> backup alarm after one minute...

Same here.  Also, Bug 16545 was for the Boom, and this one is for the Radio.
Comment 18 Andy Grundman 2011-04-07 11:05:39 UTC
Are you still seeing this?
Comment 19 Ben Klaas 2011-04-12 12:11:15 UTC
Reading through these comments, they are all over the map and it's not going to be possible to address a focused single issue to get this to a resolved state.

Summary text of the bug when opened: Alarm switches to backup alarm sound after 1 minute

There was a server side issue that has been remedied after this bug was opened. It affected mysb.com users only. Behavior was that a second alarm would fire after exactly 1 minute. This bug says backup alarm after 1 minute, but I'm going to postulate this represents a different flavor of that same bug (16644 and 16545), which is now fixed.

For that reason I'm moving this bug to RESOLVED.

There are several other comments here that describe different issues. If you are tracking this issue for specific resolution of one of those issues, please let me know in a comment here. I think the best route is to open a separate bug for those so as to focus better on those problems.

FYI, the issue described with backup alarm replacing current alarm too aggressively should be remedied by the fix recommended for bug 16663
Comment 20 Paul Chandler 2011-05-16 15:54:38 UTC
Original issue verified fix----Alarm continues and does not go to backup alarm

7.6.0.r 32419