Announcement

Collapse
No announcement yet.

Alarm not working with 8.3?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Alarm not working with 8.3?

    > I’m using LMS alarm since 10 years and never had problems until i
    > upgraded to 8.3.


    Are you on 8.3.0 or 8.3.1? The latter should be behaving much better.
    24
    Squeezebox Radio (official firmware 7.x)
    12.50%
    3
    Squeezebox Radio (community firmware 8.x)
    58.33%
    14
    Squeezebox Touch (official firmware 7.x)
    0%
    0
    Squeezebox Touch (community firmware 8.x)
    0%
    0
    SB Classic/Boom/Receiver/Transporter
    20.83%
    5
    Other (eg. Raspberry Pi based)
    16.67%
    4
    Michael

    "It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
    (LMS: Settings/Information)

    #2
    Alarm not working with 8.3?

    Am I the only one experiencing issues with the Alarm in LMS 8.3? I'm getting random behavior trying to use alarms. Most of the time they would change the player state to show the alarm sound as the currently playing track. But playback would not start. No error in the logs, no fallback alarm, no nothing. Just silence.

    I'm only seeing it on one of my systems (the one where we've been relying on alarms for years!), can't reproduce it on my dev machine. And the fact that nobody else has reported this makes me wonder whether we really have the shortest summer vacation on the globe, or whether we're the only ones using the alarm :-).
    Michael

    "It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
    (LMS: Settings/Information)

    Comment


      #3
      Originally posted by mherger View Post
      Am I the only one experiencing issues with the Alarm in LMS 8.3? I'm getting random behavior trying to use alarms. Most of the time they would change the player state to show the alarm sound as the currently playing track. But playback would not start. No error in the logs, no fallback alarm, no nothing. Just silence.

      I'm only seeing it on one of my systems (the one where we've been relying on alarms for years!), can't reproduce it on my dev machine. And the fact that nobody else has reported this makes me wonder whether we really have the shortest summer vacation on the globe, or whether we're the only ones using the alarm :-).
      I just stumbled across your post. My alarm in the morning is set to stop after 60 minutes. It worked reliably until some weeks ago. The alarm/radio does not stop anymore. I checked the logs but found nothing. Tbh I did not dig deeper. Is there a log setting I need to change?
      8.4.0 Nightly on Intel NUC
      Control: Web-GUI/MaterialSkin

      Living Room: RPi4, HifiBerry DIGI+ Pro, wavemaster TWO NEO
      Kitchen: RPi4, HifiBerry DIGI+ Pro, wavemaster CUBE MINI NEO
      Bedroom: RPi4, HifiBerry DIGI+ Pro, wavemaster CUBE MINI NEO

      Comment


        #4
        Alarm not working with 8.3?

        > I just stumbled across your post. My alarm in the morning is set to stop
        > after 60 minutes. It worked reliably until some weeks ago. The
        > alarm/radio does not stop anymore. I checked the logs but found nothing.


        That would be a different topic... our alarms refuse to play. Can't even
        say about the automatic stopping :-)

        > Tbh I did not dig deeper. Is there a log setting I need to change?


        You can enable logging for player.alarmclock (Settings/Advanced/Logging).
        Michael

        "It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
        (LMS: Settings/Information)

        Comment


          #5
          Just to add another data point, my one alarm triggers reliably each morning at 8:30 and turns off after 45 minutes. I am running the latest 8.3 nightly build. The player is a stereo pair of Google Nest Minis using the Castbridge plugin.
          Sam

          Comment


            #6
            My alarm on a Radio always works although it is a Favourite rather than current playlist. Presumably you have tried turning it off and on again [emoji2]

            Sent from my Pixel 3a using Tapatalk
            Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
            Bedroom: Radio
            Bathroom: Radio

            Comment


              #7
              The alarm didn't go off on my 8.3 system this morning...

              I set it up yesterday after reading this thread... two alarm instances per day one at 12:30pm which I forgot to check yesterday and one at 8:30am.

              The Radio playlist is displaying the favourite which is a radio stream I normally use for alarms that hasn't been played on that device for quite some time, so something happened for one or both of the alarms but the Radio itself has remained off this morning.

              Just going to set up the logging.

              System details

              Logitech Media Server Version: 8.3.0 - 1655802730 @ Tue 21 Jun 2022 11:28:50 AM CEST
              Hostname:
              Server IP Address:
              Server HTTP Port Number: 9000
              Operating system: piCore - EN - utf8
              Platform Architecture: armv7l-linux
              Perl Version: 5.32.1 - arm-linux-gnueabihf-thread-multi-64int
              Audio::Scan: 1.05
              IO::Socket::SSL: 2.071
              Database Version: DBD::SQLite 1.58 (sqlite 3.22.0)
              Total Players Recognized: 4

              and interestingly that SB Radio is on Community Firmware:

              Player Model: Squeezebox Radio
              Player Type: baby
              Firmware: 8.0.1-r16855

              Whereas on my "live" system which we use for a daily alarm the SB Radio is on the last official release 7.7.3-r16676
              and LMS is Version: 8.2.1 - 1644703015 @ Sun 13 Feb 2022 01:08:32 AM CET

              So before I set up logging I've moved that player back to my 8.2 setup and configured an alarm to go off at 09:20


              Kev
              Last edited by KeBul; 2022-08-10, 11:28.

              Comment


                #8
                Tested alarm twice with the SB Radio v8.0.1-r16855 on LMS v8.2.1 and it came on with fallback first time and successfully streamed radio station the second time.

                So moved it back to 8.3 and will leave it setup on there to see how it behaves.

                I've turned on player.alarmclock logging, but now realise that was mhergers response to the post about the alarm not stopping at 60 minutes, which of course makes sense, Michael H being more than capable of getting logs out of his failing setup

                Kev

                Comment


                  #9
                  Originally posted by KeBul View Post
                  Tested alarm twice with the SB Radio v8.0.1-r16855 on LMS v8.2.1 and it came on with fallback first time and successfully streamed radio station the second time.

                  So moved it back to 8.3 and will leave it setup on there to see how it behaves.

                  I've turned on player.alarmclock logging, but now realise that was mhergers response to the post about the alarm not stopping at 60 minutes, which of course makes sense, Michael H being more than capable of getting logs out of his failing setup

                  Kev
                  Is your Radio plugged into the mains. Battery powered Radios behave differently when it comes to alarms. They need to wake up before the alarm time and I am not sure if that works.

                  Sent from my Pixel 3a using Tapatalk
                  Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
                  Bedroom: Radio
                  Bathroom: Radio

                  Comment


                    #10
                    Originally posted by mherger View Post
                    > I just stumbled across your post. My alarm in the morning is set to stop
                    > after 60 minutes. It worked reliably until some weeks ago. The
                    > alarm/radio does not stop anymore. I checked the logs but found nothing.


                    That would be a different topic... our alarms refuse to play. Can't even
                    say about the automatic stopping :-)

                    > Tbh I did not dig deeper. Is there a log setting I need to change?


                    You can enable logging for player.alarmclock (Settings/Advanced/Logging).
                    Thank you! The ridiculous thing is: It has not been working for weeks, then I posted about it and yesterday and today it worked. I have no issues with starting the alarm though.
                    8.4.0 Nightly on Intel NUC
                    Control: Web-GUI/MaterialSkin

                    Living Room: RPi4, HifiBerry DIGI+ Pro, wavemaster TWO NEO
                    Kitchen: RPi4, HifiBerry DIGI+ Pro, wavemaster CUBE MINI NEO
                    Bedroom: RPi4, HifiBerry DIGI+ Pro, wavemaster CUBE MINI NEO

                    Comment


                      #11
                      Originally posted by slartibartfast View Post
                      Is your Radio plugged into the mains.
                      Yeah, mains powered and hard wired, so although batteries are installed, those players don't really get used as portable as they are tied to the network cable.

                      When I started out using Squeeze stuff back in 2009, a Boom was in the main bedroom and used as the alarm, in those days wireless (in general) was pretty unreliable, which affected the reliability of the alarm so I ran an ethernet cable back to the router - that was the start of wiring up the whole house with Cat5, so now I run players that are capable hard-wired rather than wifi, except in the Kitchen because I couldn't get Cat5 out to there.
                      Wifi is much improved these days, but still not as good as hard-wired.

                      When I changed the bedroom players to SB Radios, we went back into the world of unreliable alarms whilst Logitech sorted all the bugs in the code of those early Baby releases, however for many years now the alarm function has been very reliable and used at least 5 days a week.
                      As we rely on the alarm working, I constantly run at least two instances of LMS, one "live" which only gets upgraded or changed after one of the test systems shows there are no issues in newer version for my every day use. I used to avoid the nightlies, like the plague, but luckily those days of Michael H and his mates breaking something with just about every release seem to be long gone (no offence intended Michael H ).

                      The multiple servers and plenty of players arrangement allows me, if I have time, to play and test issues when they crop up here without affecting my day to day use.

                      Kev

                      PS As would be the way, the alarm has triggered fine twice since moving the player back to 8.3 I've now set it for 12:30pm and 8am each day, logs currently show next instance as 12:30pm.
                      Last edited by KeBul; 2022-08-10, 11:26.

                      Comment


                        #12
                        Another failed alarm...

                        Time for alarm was set for 12:30pm, timeout is 90 minutes, but when I checked it after 75 minutes SB Radio was off.

                        I've configured the alarm settings to use a different favourite radio station for each of the two alarms.
                        The SB Radio queue/now playing showed the correct radio station for the 12:30pm alarm

                        Here's the log, from setting the alarm to it's failed end state:
                        [22-08-10 10:41:45.2269] Slim::Utils::Alarm::save (1037) Alarm saved with id e277575b Rescheduling alarms...
                        [22-08-10 10:41:45.2273] Slim::Utils::Alarm::scheduleNext (1391) Asked to schedule next alarm for Back Bedroom
                        [22-08-10 10:41:45.2277] Slim::Utils::Alarm::scheduleNext (1397) Previous scheduled alarm wasn't triggered. Clearing nextAlarm and killing timer
                        [22-08-10 10:41:45.2283] Slim::Utils::Alarm::_startStopTimeCheck (1880) 0 scheduled alarm(s)
                        [22-08-10 10:41:45.2287] Slim::Utils::Alarm::_startStopTimeCheck (1889) Stopping time checker task
                        [22-08-10 10:41:45.2295] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 8:0:0 11/8/2022
                        [22-08-10 10:41:45.2299] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 10:30:0 10/8/2022
                        [22-08-10 10:41:45.2303] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 12:30:0 10/8/2022
                        [22-08-10 10:41:45.2307] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 10:30:0 10/8/2022
                        [22-08-10 10:41:45.2311] Slim::Utils::Alarm::scheduleNext (1424) Next alarm is at 12:30:0 10/8/2022
                        [22-08-10 10:41:45.2315] Slim::Utils::Alarm::scheduleNext (1435) Scheduling alarm
                        [22-08-10 10:41:45.2319] Slim::Utils::Alarm::_startStopTimeCheck (1880) 1 scheduled alarm(s)
                        [22-08-10 10:41:45.2323] Slim::Utils::Alarm::_startStopTimeCheck (1884) Starting time checker task
                        [22-08-10 12:30:00.0023] Slim::Utils::Alarm::sound (516) Alarm triggered for Back Bedroom
                        [22-08-10 12:30:00.0032] Slim::Utils::Alarm::sound (560) Sounding alarm
                        [22-08-10 12:30:00.0059] Slim::Utils::Alarm::sound (589) Current Power State: Off
                        [22-08-10 12:30:00.0114] Slim::Utils::Alarm:ushAlarmScreensaver (1839) Attempting to push into alarm screensaver: . Current mode: INPUT.List
                        [22-08-10 12:30:00.0125] Slim::Utils::Alarm::sound (609) Current vol: 28 Alarm vol: 25
                        [22-08-10 12:30:00.0135] Slim::Utils::Alarm::sound (612) Changing volume from 28 to 25
                        [22-08-10 12:30:00.0169] Slim::Utils::Alarm::sound (622) Alarm playlist shufflemode: 0
                        [22-08-10 12:30:00.0186] Slim::Utils::Alarm::sound (628) Alarm playlist url: http://opml.radiotime.com/Tune.ashx?...02a97946a187c2
                        [22-08-10 12:30:00.0485] Slim::Utils::Alarm::_setAlarmSubscription (1204) Adding alarm subscription
                        [22-08-10 12:30:00.0497] Slim::Utils::Alarm::sound (697) Scheduling time out in 5400 seconds
                        [22-08-10 12:30:00.0504] Slim::Utils::Alarm::_startStopTimeCheck (1880) 0 scheduled alarm(s)
                        [22-08-10 12:30:00.0507] Slim::Utils::Alarm::_startStopTimeCheck (1889) Stopping time checker task
                        [22-08-10 12:30:00.0513] Slim::Utils::Alarm::scheduleNext (1391) Asked to schedule next alarm for Back Bedroom
                        [22-08-10 12:30:00.0518] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 8:0:0 11/8/2022
                        [22-08-10 12:30:00.0522] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 12:30:0 10/8/2022
                        [22-08-10 12:30:00.0526] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 12:30:0 10/8/2022
                        [22-08-10 12:30:00.0530] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 12:30:0 10/8/2022
                        [22-08-10 12:30:00.0534] Slim::Utils::Alarm::findNextTime (471) Skipping..
                        [22-08-10 12:30:00.0537] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 12:30:0 11/8/2022
                        [22-08-10 12:30:00.0541] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 12:30:0 10/8/2022
                        [22-08-10 12:30:00.0545] Slim::Utils::Alarm::scheduleNext (1424) Next alarm is at 8:0:0 11/8/2022
                        [22-08-10 12:30:00.0549] Slim::Utils::Alarm::scheduleNext (1435) Scheduling alarm
                        [22-08-10 12:30:00.0553] Slim::Utils::Alarm::_startStopTimeCheck (1880) 1 scheduled alarm(s)
                        [22-08-10 12:30:00.0556] Slim::Utils::Alarm::_startStopTimeCheck (1884) Starting time checker task
                        [22-08-10 12:30:00.0594] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: stop
                        [22-08-10 12:30:00.0599] Slim::Utils::Alarm::_alarmEnd (1992) Stopping alarm
                        [22-08-10 12:30:00.0612] Slim::Utils::Alarm:opAlarmScreensaver (1866) Attempting to pop alarm screensaver. Current mode: INPUT.List
                        [22-08-10 12:30:01.0628] Slim::Utils::Alarm::__ANON__ (901) Restoring pre-alarm shuffle mode: 0
                        [22-08-10 12:30:01.0644] Slim::Utils::Alarm::__ANON__ (905) Restoring pre-alarm power state: off

                        End of part one...

                        Part two in next post

                        Kev

                        Comment


                          #13
                          Part two...

                          Compare this to the previous 10:30am alarm which worked fine and I turned off the SB Radio at 10:35
                          [22-08-10 10:30:00.0210] Slim::Utils::Alarm::sound (628) Alarm playlist url: http://opml.radiotime.com/Tune.ashx?...02a97946a187c2
                          [22-08-10 10:30:00.0491] Slim::Utils::Alarm::_setAlarmSubscription (1204) Adding alarm subscription
                          [22-08-10 10:30:00.0504] Slim::Utils::Alarm::sound (697) Scheduling time out in 5400 seconds
                          [22-08-10 10:30:00.0511] Slim::Utils::Alarm::_startStopTimeCheck (1880) 0 scheduled alarm(s)
                          [22-08-10 10:30:00.0515] Slim::Utils::Alarm::_startStopTimeCheck (1889) Stopping time checker task
                          [22-08-10 10:30:00.0520] Slim::Utils::Alarm::scheduleNext (1391) Asked to schedule next alarm for Back Bedroom
                          [22-08-10 10:30:00.0525] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 8:0:0 11/8/2022
                          [22-08-10 10:30:00.0529] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 10:30:0 10/8/2022
                          [22-08-10 10:30:00.0534] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 10:30:0 10/8/2022
                          [22-08-10 10:30:00.0537] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 10:30:0 10/8/2022
                          [22-08-10 10:30:00.0541] Slim::Utils::Alarm::findNextTime (471) Skipping..
                          [22-08-10 10:30:00.0545] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 10:30:0 11/8/2022
                          [22-08-10 10:30:00.0549] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 10:30:0 10/8/2022
                          [22-08-10 10:30:00.0553] Slim::Utils::Alarm::scheduleNext (1424) Next alarm is at 8:0:0 11/8/2022
                          [22-08-10 10:30:00.0557] Slim::Utils::Alarm::scheduleNext (1435) Scheduling alarm
                          [22-08-10 10:30:00.0561] Slim::Utils::Alarm::_startStopTimeCheck (1880) 1 scheduled alarm(s)
                          [22-08-10 10:30:00.0564] Slim::Utils::Alarm::_startStopTimeCheck (1884) Starting time checker task
                          [22-08-10 10:30:00.0649] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: stop
                          [22-08-10 10:30:00.0654] Slim::Utils::Alarm::_alarmEnd (1981) Ignoring self-created request
                          [22-08-10 10:30:00.0686] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: power
                          [22-08-10 10:30:00.0691] Slim::Utils::Alarm::_alarmEnd (1981) Ignoring self-created request
                          [22-08-10 10:30:00.0851] Slim::Utils::Alarm::_alarmEnd (1966) Ignoring unwanted notification: playlist stop
                          [22-08-10 10:35:27.9464] Slim::Utils::Alarm::_alarmEnd (1966) Ignoring unwanted notification: mode stop
                          [22-08-10 10:35:27.9526] Slim::Utils::Alarm::_alarmEnd (1966) Ignoring unwanted notification: playlist stop
                          [22-08-10 10:35:28.0081] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: pause
                          [22-08-10 10:35:28.0089] Slim::Utils::Alarm::_alarmEnd (1992) Stopping alarm
                          [22-08-10 10:35:28.0117] Slim::Utils::Alarm:opAlarmScreensaver (1866) Attempting to pop alarm screensaver. Current mode: INPUT.List
                          [22-08-10 10:35:29.0129] Slim::Utils::Alarm::__ANON__ (896) Restoring pre-alarm volume level: 28
                          [22-08-10 10:35:29.0157] Slim::Utils::Alarm::__ANON__ (901) Restoring pre-alarm shuffle mode: 0
                          [22-08-10 10:35:29.0176] Slim::Utils::Alarm::__ANON__ (905) Restoring pre-alarm power state: off

                          Comparing the two, after scheduling the next alarm and starting the time checker task (1884) on the alarm that worked the next two (spurious??) alarmEnd (1970) commands are ignored (1981's), with a further ignore of a playlist stop (1966)
                          [22-08-10 10:30:00.0564] Slim::Utils::Alarm::_startStopTimeCheck (1884) Starting time checker task
                          [22-08-10 10:30:00.0649] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: stop
                          [22-08-10 10:30:00.0654] Slim::Utils::Alarm::_alarmEnd (1981) Ignoring self-created request
                          [22-08-10 10:30:00.0686] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: power
                          [22-08-10 10:30:00.0691] Slim::Utils::Alarm::_alarmEnd (1981) Ignoring self-created request
                          [22-08-10 10:30:00.0851] Slim::Utils::Alarm::_alarmEnd (1966) Ignoring unwanted notification: playlist stop

                          But on the failed one, the alarmEnd (1970) is not ignored and the alarm is stopped and the device shutdown within two seconds of the alarm being triggered.
                          [22-08-10 12:30:00.0556] Slim::Utils::Alarm::_startStopTimeCheck (1884) Starting time checker task
                          [22-08-10 12:30:00.0594] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: stop
                          [22-08-10 12:30:00.0599] Slim::Utils::Alarm::_alarmEnd (1992) Stopping alarm
                          [22-08-10 12:30:00.0612] Slim::Utils::Alarm:opAlarmScreensaver (1866) Attempting to pop alarm screensaver. Current mode: INPUT.List
                          [22-08-10 12:30:01.0628] Slim::Utils::Alarm::__ANON__ (901) Restoring pre-alarm shuffle mode: 0
                          [22-08-10 12:30:01.0644] Slim::Utils::Alarm::__ANON__ (905) Restoring pre-alarm power state: off

                          The shutdown is slightly different from from the one at 10:35 when I turned off the SB Radio using a short press of the power button (Pause at power off set in player audio settings), which would have caused the alarmEnd called with request: pause
                          Also note that the genuine stop of the alarm saw the restoration of the volume level.
                          [22-08-10 10:35:27.9464] Slim::Utils::Alarm::_alarmEnd (1966) Ignoring unwanted notification: mode stop
                          [22-08-10 10:35:27.9526] Slim::Utils::Alarm::_alarmEnd (1966) Ignoring unwanted notification: playlist stop
                          [22-08-10 10:35:28.0081] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: pause
                          [22-08-10 10:35:28.0089] Slim::Utils::Alarm::_alarmEnd (1992) Stopping alarm
                          [22-08-10 10:35:28.0117] Slim::Utils::Alarm:opAlarmScreensaver (1866) Attempting to pop alarm screensaver. Current mode: INPUT.List
                          [22-08-10 10:35:29.0129] Slim::Utils::Alarm::__ANON__ (896) Restoring pre-alarm volume level: 28
                          [22-08-10 10:35:29.0157] Slim::Utils::Alarm::__ANON__ (901) Restoring pre-alarm shuffle mode: 0
                          [22-08-10 10:35:29.0176] Slim::Utils::Alarm::__ANON__ (905) Restoring pre-alarm power state: off

                          I'll enable player.alarmclock debug on the 8.2.1 system and see what that shows.

                          Kev

                          Comment


                            #14
                            Here's the debug from a working alarm on

                            LMS v8.2.1 - 1644703015 @ Sun 13 Feb 2022 01:08:32 AM CET
                            SB Radio v7.7.3-r16676

                            [22-08-11 06:30:00.0027] Slim::Utils::Alarm::sound (516) Alarm triggered for Main Bedroom
                            [22-08-11 06:30:00.0034] Slim::Utils::Alarm::sound (560) Sounding alarm
                            [22-08-11 06:30:00.0056] Slim::Utils::Alarm::sound (589) Current Power State: Off
                            [22-08-11 06:30:00.0094] Slim::Utils::Alarm:ushAlarmScreensaver (1839) Attempting to push into alarm screensaver: . Current mode: INPUT.List
                            [22-08-11 06:30:00.0102] Slim::Utils::Alarm::sound (609) Current vol: 31 Alarm vol: 24
                            [22-08-11 06:30:00.0108] Slim::Utils::Alarm::sound (612) Changing volume from 31 to 24
                            [22-08-11 06:30:00.0129] Slim::Utils::Alarm::sound (622) Alarm playlist shufflemode: 0
                            [22-08-11 06:30:00.0142] Slim::Utils::Alarm::sound (628) Alarm playlist url: pr://planetradio?n=MellowMagic
                            [22-08-11 06:30:00.0538] Slim::Utils::Alarm::_setAlarmSubscription (1204) Adding alarm subscription
                            [22-08-11 06:30:00.0545] Slim::Utils::Alarm::sound (697) Scheduling time out in 14400 seconds
                            [22-08-11 06:30:00.0549] Slim::Utils::Alarm::_startStopTimeCheck (1880) 0 scheduled alarm(s)
                            [22-08-11 06:30:00.0551] Slim::Utils::Alarm::_startStopTimeCheck (1889) Stopping time checker task
                            [22-08-11 06:30:00.0554] Slim::Utils::Alarm::scheduleNext (1391) Asked to schedule next alarm for Main Bedroom
                            [22-08-11 06:30:00.0558] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 6:30:0 11/8/2022
                            [22-08-11 06:30:00.0561] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 6:30:0 11/8/2022
                            [22-08-11 06:30:00.0563] Slim::Utils::Alarm::findNextTime (471) Skipping..
                            [22-08-11 06:30:00.0566] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 6:30:0 12/8/2022
                            [22-08-11 06:30:00.0568] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 6:30:0 11/8/2022
                            [22-08-11 06:30:00.0570] Slim::Utils::Alarm::scheduleNext (1424) Next alarm is at 6:30:0 12/8/2022
                            [22-08-11 06:30:00.0572] Slim::Utils::Alarm::scheduleNext (1435) Scheduling alarm
                            [22-08-11 06:30:00.0575] Slim::Utils::Alarm::_startStopTimeCheck (1880) 1 scheduled alarm(s)
                            [22-08-11 06:30:00.0577] Slim::Utils::Alarm::_startStopTimeCheck (1884) Starting time checker task
                            [22-08-11 06:30:00.0596] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: stop
                            [22-08-11 06:30:00.0599] Slim::Utils::Alarm::_alarmEnd (1981) Ignoring self-created request
                            [22-08-11 06:30:00.0607] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: power
                            [22-08-11 06:30:00.0609] Slim::Utils::Alarm::_alarmEnd (1981) Ignoring self-created request
                            [22-08-11 06:30:00.0694] Slim::Utils::Alarm::_alarmEnd (1966) Ignoring unwanted notification: playlist stop
                            [22-08-11 07:14:28.3057] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: pause
                            [22-08-11 07:14:28.3064] Slim::Utils::Alarm::_alarmEnd (1992) Stopping alarm
                            [22-08-11 07:14:28.3084] Slim::Utils::Alarm:opAlarmScreensaver (1866) Attempting to pop alarm screensaver. Current mode: INPUT.List
                            [22-08-11 07:14:29.3086] Slim::Utils::Alarm::__ANON__ (896) Restoring pre-alarm volume level: 31
                            [22-08-11 07:14:29.3107] Slim::Utils::Alarm::__ANON__ (901) Restoring pre-alarm shuffle mode: 0
                            [22-08-11 07:14:29.3120] Slim::Utils::Alarm::__ANON__ (905) Restoring pre-alarm power state: off

                            It looks pretty much the same as the working example on LMS 8.3 in my post #12

                            I'll continue to monitor the test alarm setup on 8.3 and report back.

                            Kev

                            Comment


                              #15
                              Till today I had no issues with the alarm on my SB3 in the bedroom. Version 8.3.0 version from June 21th.
                              Last edited by wbree; 2022-08-13, 06:54.
                              __________________________________________________ _______________________________________
                              Logitech Media Server Versie: 8.3.0 - 1663737210 @ Wed Sep 21 07:16:54 WEDT 2022
                              Platform: Windows Server 2022 NL
                              Plug-ins: Spotty v4.8.3 (M. Herger)
                              3x Squeezebox Classic, 1x Touch, 1x Boom
                              Spotify Premium Account (NL)

                              Comment

                              Working...
                              X