Bugzilla – Bug 11225
Alarm failing to go off couple times since last SNetwork or SBB upgrade
Last modified: 2009-09-16 06:10:55 UTC
A couple times over the last couple weeks, the SBB failed to sound an alarm. The time came and went and nothing played, and nothing showed on the screen. When looking at the SBB subsequently, the main menu had options that had disappeared: the first time, the last two options (MP3Tunes and Settings), and this morning the last three option (Last.fm, MP3Tunes, and Settings). The only way to get them back was to turn off the SBB, then hold the power button in for several seconds (which appears to reboot it). At that point, the main menu was restored to what had been configured in SqueezeNetwork, and the alarm worked the next day. The only thing I can *think* of that might be correlated is that I'd made an alarm change via SqueezeNetwork vs. the SBB UI the prior day/night. I'm not totally sure of that the first time, but am the second time. This used to work fine (and is far more convenient than using the SBB UI to set up alarms) -- but was something broken in that area, perhaps, when you enhanced the SqueezeNetwork player UI recently? As a related comment, for something as critical as an alarm clock, which is how I'd assume a lot of your SBB customers use it, please take care with changes to that; and, you may wish to add the Alarm as a specifically-named "Component" choice within the SBB for these bug reports.
Robert: The alarm is a function of SN or SC, not the player. I have changed the product/component to reflect this
Robert: are you able to reproduce this error? if so, please turn player.alarm to debug and attach a log file.
James - My apologies for delay in responding. Couple notes: 1) I only use SN, not SC 2) Re: reproducing it, I haven't yet. I'm leery to try it on a regular alarm time -- don't want to risk oversleeping -- and haven't focused on it to try at an e.g. afternoon time on a day when I'm home. I did see the following related issue: (a) changed an alarm to "Off" on the player (b) later that day, turned it back "On" via SN (c) checked the player a couple hours later and it was still "Off". Unlike the originally-reported issue, the player hadn't lost several main-menu options, so I didn't have to reboot it, but the change wasn't applied. 3) I will try the afternoon-alarm test this weekend. Thanks.
I'm unable to reproduce this on cue, but it did happen again -- I set an alarm using SqueezeNetwork, and the next day the "Settings" option had been deleted from my SqueezeBox boom, and the alarm didn't go off normally (this last time, thankfully, it beeped as it had no connectivity vs. not going off at all as it did the first two times). So, sorry, I'm not able to help in debugging much. It does seem that SN doesn't work. I have to switch to use the player UI for any alarm updates.
Robert: Please email me the mac address of your Boom
Robert: we will be releasing a new version of SqueezeNetwork "soon" that has new alarm code. When that happens please re-test this alarm issue. Re-open the bug after that if you still see the issue.