------------------------------------------------------------------------ A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 ------------------------------------------------------------------------ Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) ------------------------------------------------------------------------
This sequence looks pretty fishy: didjean wrote: > [22-11-18 15:40:00.6249] Slim::Utils::Alarm::_startStopTimeCheck (1880) > 4 scheduled alarm(s) > [22-11-18 15:40:00.6253] Slim::Utils::Alarm::setRTCAlarm (1474) Asked to > set rtc alarm for Salle à manger > [22-11-18 15:40:00.6259] Slim::Utils::Alarm::setRTCAlarm (1513) Clearing > RTC alarm > [22-11-18 15:40:00.6398] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd > called with request: stop > [22-11-18 15:40:00.6403] Slim::Utils::Alarm::_alarmEnd (1992) Stopping > alarm > So what happens here is that the alarm is in fact fired but is instantly stopped before the associated track even starts playing. But the strangest thing is that in this log snippet the same sequence of commands is given, only this time the software appears to identify the instant 'stop' command as a bad request and allows the sounding of the alarm to continue. > > [22-11-18 15:47:00.7284] Slim::Utils::Alarm::_startStopTimeCheck (1880) > 4 scheduled alarm(s) > [22-11-18 15:47:00.7287] Slim::Utils::Alarm::setRTCAlarm (1474) Asked to > set rtc alarm for Salle à manger > [22-11-18 15:47:00.7292] Slim::Utils::Alarm::setRTCAlarm (1513) Clearing > RTC alarm > [22-11-18 15:47:00.7392] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd > called with request: stop > [22-11-18 15:47:00.7396] Slim::Utils::Alarm::_alarmEnd (1981) Ignoring > self-created request > [22-11-18 15:47:00.7417] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd > called with request: power > [22-11-18 15:47:00.7420] Slim::Utils::Alarm::_alarmEnd (1981) Ignoring > self-created request > [22-11-18 15:47:00.7546] Slim::Utils::Alarm::_alarmEnd (1966) Ignoring > unwanted notification: playlist stop > [22-11-18 15:47:00.7633] Slim::Utils::Alarm::_alarmEnd (1966) Ignoring > unwanted notification: playlist stop > [22-11-18 15:47:48.5053] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd > called with request: stop > [22-11-18 15:47:48.5062] Slim::Utils::Alarm::_alarmEnd (1992) Stopping > alarm > Two questions: - Why does the alarm routine issue a 'stop' directly after 'start'? - Why does _alarmEnd respond inconsistently to this incorrect 'stop' command? ------------------------------------------------------------------------ gordonb3's Profile: http://forums.slimdevices.com/member.php?userid=71050 View this thread: http://forums.slimdevices.com/showthread.php?t=116649
_______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
