------------------------------------------------------------------------ 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) ------------------------------------------------------------------------
didjean wrote: > So following my last post, the day after, the same happened. No alarm > was working anymore! I took the time to further test (without restarting > server) and I created a few new alarms based on a radio stream, a > playlist or a Radom mix by year. > > All failed - with no backup sound. please find below a log: > > > [22-11-17 20:45:00.0007] Slim::Utils::Alarm::sound (516) Alarm triggered > for Salle à manger > [22-11-17 20:45:00.0013] Slim::Utils::Alarm::sound (560) Sounding alarm > [22-11-17 20:45:00.0029] Slim::Utils::Alarm::sound (589) Current Power > State: Off > [22-11-17 20:45:00.0096] Slim::Utils::Alarm::pushAlarmScreensaver (1839) > Attempting to push into alarm screensaver: SCREENSAVER.datetime. Current > mode: INPUT.List > [22-11-17 20:45:00.0102] Slim::Utils::Alarm::pushAlarmScreensaver (1845) > Pushing alarm screensaver > [22-11-17 20:45:00.0116] Slim::Utils::Alarm::sound (609) Current vol: 50 > Alarm vol: 50 > [22-11-17 20:45:00.0122] Slim::Utils::Alarm::sound (622) Alarm playlist > shufflemode: 0 > [22-11-17 20:45:00.0133] Slim::Utils::Alarm::sound (628) Alarm playlist > url: randomplay://year > [22-11-17 20:45:01.7219] Slim::Utils::Alarm::_setAlarmSubscription > (1204) Adding alarm subscription > [22-11-17 20:45:01.7238] Slim::Utils::Alarm::sound (697) Scheduling time > out in 3600 seconds > [22-11-17 20:45:01.7246] Slim::Utils::Alarm::_startStopTimeCheck (1880) > 3 scheduled alarm(s) > [22-11-17 20:45:01.7250] Slim::Utils::Alarm::scheduleNext (1391) Asked > to schedule next alarm for Salle à manger > [22-11-17 20:45:01.7255] Slim::Utils::Alarm::findNextTime (461) > Potential next time found: 20:45:0 17/11/2022 > [22-11-17 20:45:01.7260] Slim::Utils::Alarm::findNextTime (466) Last > alarm due: 20:45:0 17/11/2022 > [22-11-17 20:45:01.7264] Slim::Utils::Alarm::findNextTime (471) > Skipping.. > [22-11-17 20:45:01.7268] Slim::Utils::Alarm::findNextTime (461) > Potential next time found: 20:45:0 18/11/2022 > [22-11-17 20:45:01.7273] Slim::Utils::Alarm::findNextTime (466) Last > alarm due: 20:45:0 17/11/2022 > [22-11-17 20:45:01.7278] Slim::Utils::Alarm::scheduleNext (1424) Next > alarm is at 20:45:0 18/11/2022 > [22-11-17 20:45:01.7281] Slim::Utils::Alarm::scheduleNext (1435) > Scheduling alarm > [22-11-17 20:45:01.7286] Slim::Utils::Alarm::_startStopTimeCheck (1880) > 4 scheduled alarm(s) > [22-11-17 20:45:01.7290] Slim::Utils::Alarm::setRTCAlarm (1474) Asked to > set rtc alarm for Salle à manger > [22-11-17 20:45:01.7299] Slim::Utils::Alarm::setRTCAlarm (1503) Setting > RTC alarm to 74700, volume 50 > [22-11-17 20:45:01.7436] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd > called with request: stop > [22-11-17 20:45:01.7442] Slim::Utils::Alarm::_alarmEnd (1992) Stopping > alarm > [22-11-17 20:45:01.7464] Slim::Utils::Alarm::popAlarmScreensaver (1866) > Attempting to pop alarm screensaver. Current mode: SCREENSAVER.datetime > [22-11-17 20:45:01.7469] Slim::Utils::Alarm::popAlarmScreensaver (1868) > Popping alarm screensaver > [22-11-17 20:45:02.7770] Slim::Utils::Alarm::__ANON__ (901) Restoring > pre-alarm shuffle mode: 0 > [22-11-17 20:45:02.7779] Slim::Utils::Alarm::__ANON__ (905) Restoring > pre-alarm power state: off > > After saving that log - I pressed the play button, then I got the stream > the same way the alarm would have been launched - meaning with a fade > in. > > Following all these tests, I restarted the server and alarm worked: > please see the logs for a perfect normal trigger: > > > [22-11-17 21:03:00.0011] Slim::Utils::Alarm::sound (516) Alarm triggered > for Salle à manger > [22-11-17 21:03:00.0019] Slim::Utils::Alarm::sound (560) Sounding alarm > [22-11-17 21:03:00.0039] Slim::Utils::Alarm::sound (589) Current Power > State: Off > [22-11-17 21:03:00.0126] Slim::Utils::Alarm::pushAlarmScreensaver (1839) > Attempting to push into alarm screensaver: SCREENSAVER.datetime. Current > mode: INPUT.List > [22-11-17 21:03:00.0134] Slim::Utils::Alarm::pushAlarmScreensaver (1845) > Pushing alarm screensaver > [22-11-17 21:03:00.0153] Slim::Utils::Alarm::sound (609) Current vol: 50 > Alarm vol: 50 > [22-11-17 21:03:00.0161] Slim::Utils::Alarm::sound (622) Alarm playlist > shufflemode: 0 > [22-11-17 21:03:00.0178] Slim::Utils::Alarm::sound (628) Alarm playlist > url: randomplay://year > [22-11-17 21:03:02.1999] Slim::Utils::Alarm::_setAlarmSubscription > (1204) Adding alarm subscription > [22-11-17 21:03:02.2006] Slim::Utils::Alarm::sound (697) Scheduling time > out in 3600 seconds > [22-11-17 21:03:02.2012] Slim::Utils::Alarm::_startStopTimeCheck (1880) > 3 scheduled alarm(s) > [22-11-17 21:03:02.2015] Slim::Utils::Alarm::scheduleNext (1391) Asked > to schedule next alarm for Salle à manger > [22-11-17 21:03:02.2019] Slim::Utils::Alarm::findNextTime (461) > Potential next time found: 21:3:0 17/11/2022 > [22-11-17 21:03:02.2022] Slim::Utils::Alarm::findNextTime (466) Last > alarm due: 21:3:0 17/11/2022 > [22-11-17 21:03:02.2025] Slim::Utils::Alarm::findNextTime (471) > Skipping.. > [22-11-17 21:03:02.2028] Slim::Utils::Alarm::findNextTime (461) > Potential next time found: 21:3:0 18/11/2022 > [22-11-17 21:03:02.2030] Slim::Utils::Alarm::findNextTime (466) Last > alarm due: 21:3:0 17/11/2022 > [22-11-17 21:03:02.2033] Slim::Utils::Alarm::scheduleNext (1424) Next > alarm is at 21:3:0 18/11/2022 > [22-11-17 21:03:02.2036] Slim::Utils::Alarm::scheduleNext (1435) > Scheduling alarm > [22-11-17 21:03:02.2039] Slim::Utils::Alarm::_startStopTimeCheck (1880) > 4 scheduled alarm(s) > [22-11-17 21:03:02.2042] Slim::Utils::Alarm::setRTCAlarm (1474) Asked to > set rtc alarm for Salle à manger > [22-11-17 21:03:02.2047] Slim::Utils::Alarm::setRTCAlarm (1503) Setting > RTC alarm to 75780, volume 50 > [22-11-17 21:03:02.2268] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd > called with request: stop > [22-11-17 21:03:02.2271] Slim::Utils::Alarm::_alarmEnd (1981) Ignoring > self-created request > [22-11-17 21:03:02.2291] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd > called with request: power > [22-11-17 21:03:02.2294] Slim::Utils::Alarm::_alarmEnd (1981) Ignoring > self-created request > [22-11-17 21:03:02.2405] Slim::Utils::Alarm::_alarmEnd (1966) Ignoring > unwanted notification: playlist stop > [22-11-17 21:03:02.2465] Slim::Utils::Alarm::_alarmEnd (1966) Ignoring > unwanted notification: playlist stop > > > If I compare both logs - last 7 lines are different. > > Really hope we will find the issue soon... Fingers crossed! In the > meantime my 35 years old Philips radio is back on my nightstand :-) You have mentioned before that you don't hear the fallback alarm any more when the alarm fails. If you can get an alarm to work could you try stopping the playback by clicking stop (pause probably works as well) in a control app, I used material skin. The fallback alarm should sound after 1 minute. If nothing else it proves that the fallback alarm can and should sound. Sent from my Pixel 3a using Tapatalk ------------------------------------------------------------------------ slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=116649
_______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
