Bugzilla – Bug 8538
alarm clock functionality (not working with SuperCap)
Last modified: 2008-12-15 12:39:18 UTC
CAT PR-0066 ------------ Description * the alarm clock works fine as long as there is internet. if the device looses wireless or even the internet connection (or serving computer if using local streams), the device will cease to function thus disabling the alarm clock. the user guide says this will not happen and the device will alarm in local mode just using an internal sound to wake you up. this is FALSE and would be a very bad thing for the device. the alarm issue needs to be addressed since the device seems to want to be sold as an alarm clock replacement. (snooze button means alarm clock in my opinion). Steps to Duplicate * 1. set alarm (this includes sedtting all alarm related functions) 2. disable the internet source the device is using thats it. the alarm will not function reguardless of alarm audio source. as another bug, if you press the power button while there is no internet, the device will power cycle and require that you set up the device, like out of the box, when the internet comes back. (the device seems to go into a continuous"reconnect" state while internet is gone. though it will come back online without issue if there is no user intervention, the latter basically requires a complete setup again. all automation is lost)
SC is currently not sending alarm settings to the player, this needs to be implemented first. I left an example in Player/Boom.pm how to set an alarm when a player connects but it is commented out.
(In reply to comment #1) > SC is currently not sending alarm settings to the player, this needs to be > implemented first. I left an example in Player/Boom.pm how to set an alarm when > a player connects but it is commented out. Max, would you be interested in implementing this functionality?
I'll take a look.
R21145 in the boom-new-alarm branch adds code that should sort this out. However, I haven't tested it on the boom itself. Whenever the next alarm is scheduled, it checks if it's due in the next 24 hours and sets the RTC alarm if so. Otherwise, the RTC alarm is cleared. It checks every 24 hours to see if the next alarm is due in the next 24 hours and sets it if so. Alarms are scheduled every time an alarm is added, deleted or edited or when a client connects, so this should cover all cases.
RTC alarm is now set correctly. Internal sound is indeed issued. My, what a sound!
Tested with FW 17 and 7.2-21271 and still can not get this to function properly. Steps to reproduce 1) attach a boom to SC 2) using either boom or SC set an alarm 3) stop server 4) wait for alarm time to pass, note: nothing happens on boom
Hmm, I haven't been testing this by stopping the server - merely by holding left to disconnect. Apart from that it definitely works for me.
Confirming that nothing happens for the given test case. It never displayed the clock and the alarm didn't sound. I think this is a problem with the fw. I managed to get it to display the clock by pushing power, waiting for it to try waking up the server and failing then, once I'd got to the setup menu, pressing power. This showed that the rtc alarm had been set correctly by showing the alarm time (now passed) when the seconds hit 30. Basically, I think we're ahead of the implementation here.
Firmware rev 4447 contains: - Added bell sign to rtc clock if alarm is set - Bell sign blinks during alarm - Alarm can be stopped by pushing wheel, or snoozed by pressing snooze button - Alarm tone still needs to be improved/changed (currently main volume dependent) The display going dark and not showing the clock is covered in bug 8592
Firmware rev 4448 adds power and pause button as possibilities to stop an alarm to be more consistent with when connected to SC/SN.
How about when not connected to either SN/SC? Will the alarm still go off? The display is blank when not connected, so I don't know what happens as the alarm/clock is not shown
Clock and alarm not showing when loosing connection to SC/SN is fixed in fw rev 4474. (The alarm bell is flashing during an alarm.) Alarm sound still needs to be improved.
Change 22076 passes the alarm volume to the Slim::Player::Boom::setRTCAlarm. This needs fw 19 to test that the rtc alarm uses the appropriate volume.
James to verify fix
Moving to 7.2 to ensure visibility.
Verified fixed with r19
This bug has been fixed in the 7.3.0 release version of SqueezeCenter! Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.