Announcement

Collapse
No announcement yet.

Alarm not working with 8.3?

Collapse
X
Collapse
 
  • Page of 17
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 4 5 12 17 template Next
    #16
    OK I think I can confirm I also experience some random problem as you described.. I wasn't sure and when tested few times during day it seem to work. But now I had 2 alarms within 30min ..1st went off ok and 2nd one stopped first one, changed alarm on display but no audio at all. Just silence.

    Version: 8.3.0 - 1654547000 @ Mon Jun 6 22:52:44 CEST 2022


    Sent from my Moto Z3 Play using Tapatalk
    3x Squeezebox Touch, 4x Squeezebox Radio, Squeezelite (RPi 3B with HiFiBerry DAC+Pro on OSMC), Material Skin Apk, Squeeze Commander, Logitech Media Server Version: 8.2.0 with Material Skin (Docker in DS218+)

    Comment

      #17
      Originally posted by Jaca View Post
      OK I think I can confirm I also experience some random problem as you described.. I wasn't sure and when tested few times during day it seem to work. But now I had 2 alarms within 30min ..1st went off ok and 2nd one stopped first one, changed alarm on display but no audio at all. Just silence.

      Version: 8.3.0 - 1654547000 @ Mon Jun 6 22:52:44 CEST 2022


      Sent from my Moto Z3 Play using Tapatalk
      I think that has been a "feature" for a long time, well before 8.3 [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

        #18
        Same problem overhere.. but with a twist..
        I wanted to change the windows server for a docker container.
        In the windows settings and server version all works as intended and alarm functions.
        When i replaced the windows server for the synology docker container the alarm stopped working.
        Same nightly versions!
        Going back to windows solved the problem, but of course thats not the intention.
        So is there a difference between the two codes that can explain this behavior?

        Versons:
        Logitech Media Server Versie: 8.3.0 - 1659590348 @ Thu Aug 4 07:20:03 WEDT 2022
        Hostnaam: HPserver
        IP-adres van server: 192.168.1.130
        HTTP-poortnummer van server: 9000
        Besturingssysteem: Windows 10 - NL - cp1252
        Platformarchitectuur: 8664
        Perl versie: 5.14.1 - MSWin32-x86-multi-thread
        Audio::Scan: 1.05
        IO::Socket::SSL: 2.068
        Database versie: DBD::SQLite 1.58 (sqlite 3.22.0)
        Totaal aantal herkende muziekspelers: 3

        Logitech Media Server Version: 8.3.0 - 1659590348 @ Fri Aug 5 16:37:15 CEST 2022
        Hostname: lmscommunity-logitechmediaserver2
        Server IP Address: 192.168.1.150
        Server HTTP Port Number: 9000
        Operating system: Debian (Docker) - EN - utf8
        Platform Architecture: x86_64-linux
        Perl Version: 5.32.1 - x86_64-linux-gnu-thread-multi
        Audio::Scan: 1.05
        IO::Socket::SSL: 2.069
        Database Version: DBD::SQLite 1.58 (sqlite 3.22.0)
        Total Players Recognized: 2
        Last edited by seth_space; 2022-08-12, 12:37.

        Comment

          #19
          Originally posted by slartibartfast View Post
          I think that has been a "feature" for a long time, well before 8.3 [emoji2]

          Sent from my Pixel 3a using Tapatalk
          Ohh lol.. Wasn't aware of that. Well, in this case I'm back to " not so sure" position. Maybe I've not experienced Michael's alarm problem ;p

          Sent from my Moto Z3 Play using Tapatalk
          3x Squeezebox Touch, 4x Squeezebox Radio, Squeezelite (RPi 3B with HiFiBerry DAC+Pro on OSMC), Material Skin Apk, Squeeze Commander, Logitech Media Server Version: 8.2.0 with Material Skin (Docker in DS218+)

          Comment

            #20
            This is really weird. I'm not even on v8.3 (but 8.2.0 - 1627922070) and my alarm has also started failing on my Squeezebox Boom, where it has been working reliably for years. I wouldn't say it fails randomly, rather it works randomly. During my about 15 (or so) tries this morning, three worked and in the other 12 (or so) failed. By failed I mean that the song is "loaded" (cover art shows up in the webUI) but it never starts playing. If I manually click play on that song, it starts playing no problem.

            Just did another test and here is the log:

            Code:
            [22-08-14 16:35:01.6099] Slim::Utils::Alarm::save (1017) Saving alarm.
[22-08-14 16:35:01.6102] Slim::Utils::Alarm::save (1037) Alarm saved with id 41cf9152 Rescheduling alarms...
[22-08-14 16:35:01.6103] Slim::Utils::Alarm::scheduleNext (1391) Asked to schedule next alarm for Boom Bedroom 
[22-08-14 16:35:01.6104] Slim::Utils::Alarm::scheduleNext (1397) Previous scheduled alarm wasn't triggered.  Clearing nextAlarm and killing timer
[22-08-14 16:35:01.6148] Slim::Utils::Alarm::_startStopTimeCheck (1880) 0 scheduled alarm(s)
[22-08-14 16:35:01.6149] Slim::Utils::Alarm::_startStopTimeCheck (1889) Stopping time checker task
[22-08-14 16:35:01.6170] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 6:30:0 15/8/2022
[22-08-14 16:35:01.6171] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 16:34:0 14/8/2022
[22-08-14 16:35:01.6172] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 16:36:0 14/8/2022
[22-08-14 16:35:01.6173] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 16:34:0 14/8/2022
[22-08-14 16:35:01.6174] Slim::Utils::Alarm::scheduleNext (1424) Next alarm is at 16:36:0 14/8/2022
[22-08-14 16:35:01.6175] Slim::Utils::Alarm::scheduleNext (1435) Scheduling alarm
[22-08-14 16:35:01.6176] Slim::Utils::Alarm::_startStopTimeCheck (1880) 1 scheduled alarm(s)
[22-08-14 16:35:01.6177] Slim::Utils::Alarm::_startStopTimeCheck (1884) Starting time checker task
[22-08-14 16:35:01.6178] Slim::Utils::Alarm::setRTCAlarm (1474) Asked to set rtc alarm for Boom Bedroom 
[22-08-14 16:35:01.6229] Slim::Utils::Alarm::setRTCAlarm (1503) Setting RTC alarm to 59760, volume 50
[22-08-14 16:36:00.0358] Slim::Utils::Alarm::sound (516) Alarm triggered for Boom Bedroom 
[22-08-14 16:36:00.0360] Slim::Utils::Alarm::sound (560) Sounding alarm
[22-08-14 16:36:00.0366] Slim::Utils::Alarm::sound (589) Current Power State: Off
[22-08-14 16:36:00.0395] Slim::Utils::Alarm::pushAlarmScreensaver (1839) Attempting to push into alarm screensaver: SCREENSAVER.musicinfo. Current mode: INPUT.List
[22-08-14 16:36:00.0397] Slim::Utils::Alarm::pushAlarmScreensaver (1845) Pushing alarm screensaver
[22-08-14 16:36:00.0416] Slim::Utils::Alarm::sound (609) Current vol: 50 Alarm vol: 50
[22-08-14 16:36:00.0417] Slim::Utils::Alarm::sound (622) Alarm playlist shufflemode: 0
[22-08-14 16:36:00.0422] Slim::Utils::Alarm::sound (628) Alarm playlist url: sugarcube:track
[22-08-14 16:36:00.0556] Slim::Utils::Alarm::_setAlarmSubscription (1204) Adding alarm subscription
[22-08-14 16:36:00.0559] Slim::Utils::Alarm::sound (697) Scheduling time out in 3600 seconds
[22-08-14 16:36:00.0656] Slim::Utils::Alarm::_startStopTimeCheck (1880) 0 scheduled alarm(s)
[22-08-14 16:36:00.0657] Slim::Utils::Alarm::_startStopTimeCheck (1889) Stopping time checker task
[22-08-14 16:36:00.0684] Slim::Utils::Alarm::scheduleNext (1391) Asked to schedule next alarm for Boom Bedroom 
[22-08-14 16:36:00.0687] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 6:30:0 15/8/2022
[22-08-14 16:36:00.0704] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 16:36:0 14/8/2022
[22-08-14 16:36:00.0710] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 16:36:0 14/8/2022
[22-08-14 16:36:00.0713] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 16:36:0 14/8/2022
[22-08-14 16:36:00.0715] Slim::Utils::Alarm::findNextTime (471) Skipping..
[22-08-14 16:36:00.0718] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 16:36:0 20/8/2022
[22-08-14 16:36:00.0720] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 16:36:0 14/8/2022
[22-08-14 16:36:00.0723] Slim::Utils::Alarm::scheduleNext (1424) Next alarm is at 6:30:0 15/8/2022
[22-08-14 16:36:00.0725] Slim::Utils::Alarm::scheduleNext (1435) Scheduling alarm
[22-08-14 16:36:00.0733] Slim::Utils::Alarm::_startStopTimeCheck (1880) 1 scheduled alarm(s)
[22-08-14 16:36:00.0737] Slim::Utils::Alarm::_startStopTimeCheck (1884) Starting time checker task
[22-08-14 16:36:00.0742] Slim::Utils::Alarm::setRTCAlarm (1474) Asked to set rtc alarm for Boom Bedroom 
[22-08-14 16:36:00.0808] Slim::Utils::Alarm::setRTCAlarm (1503) Setting RTC alarm to 23400, volume 50
[22-08-14 16:36:00.4320] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: stop
[22-08-14 16:36:00.4321] Slim::Utils::Alarm::_alarmEnd (1992) Stopping alarm
[22-08-14 16:36:00.4362] Slim::Utils::Alarm::popAlarmScreensaver (1866) Attempting to pop alarm screensaver.  Current mode: SCREENSAVER.musicinfo
[22-08-14 16:36:00.4364] Slim::Utils::Alarm::popAlarmScreensaver (1868) Popping alarm screensaver
[22-08-14 16:36:04.1118] Slim::Utils::Misc::msg (1341) Warning: [16:36:04.1116] EV: error in callback (ignoring): Can't use an undefined value as a symbol reference at /usr/share/perl5/Slim/Utils/PerlRunTime.pm line 116.
[22-08-14 16:36:04.1166] Slim::Utils::Alarm::__ANON__ (901) Restoring pre-alarm shuffle mode: 0
[22-08-14 16:36:04.1170] Slim::Utils::Alarm::__ANON__ (905) Restoring pre-alarm power state: off
            At 16:36:00.4320 it says: "_alarmEnd called with request: stop" Where might that be coming from?

            Notice also 16:36:00.0358 where it says that the previous alarm wasn't triggered.

            The warning at 16:36:04.1118 also occurs when the alarm triggers correctly, so I assume we can ignore that.
            Server: LMS 8.2 on an Ubuntu 18.04 virtual machine
            Players: Radio, Touch, Duet (Receiver & Controller), 2 Booms, Google Nest Hub (via chromecast plugin)
            Remote control apps: Material Skin (Web UI), but also SqueezePad (iOS), Squeezecontroller (Android)
            Important plugins: Trackstat, Spicefly Sugarcube, Lazy Search Music, Custom Browse, Multi Library

            Comment

              #21
              After restarting the virtual machine (Ubuntu 18.04) on which LMS is running, I can't seem to reproduce the issue anymore. I assume that you guys have already tried restarting and it didn't go away? So I expect the issue to return... We'll see.

              One thing I can say from the logs of the successful tries is that when I stop the alarm manually (on the web-ui), then it says `Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: pause` instead of `stop` at the end.
              Server: LMS 8.2 on an Ubuntu 18.04 virtual machine
              Players: Radio, Touch, Duet (Receiver & Controller), 2 Booms, Google Nest Hub (via chromecast plugin)
              Remote control apps: Material Skin (Web UI), but also SqueezePad (iOS), Squeezecontroller (Android)
              Important plugins: Trackstat, Spicefly Sugarcube, Lazy Search Music, Custom Browse, Multi Library

              Comment

                #22
                Alarm not working with 8.3?

                Hehe... I should never have started this thread :-).

                > After restarting the virtual machine (Ubuntu 18.04) on which LMS is
                > running, I can't seem to reproduce the issue anymore. I assume that you
                > guys have already tried restarting and it didn't go away? So I expect
                > the issue to return... We'll see.

                Similar experience here: I posted here because I experienced exactly
                what you describe. The track would seemingly be started, but actual
                playback wouldn't happen.

                And then I had to indeed restart my LMS system, too - and haven't had a
                single failure since (which is a week).
                Michael

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

                Comment

                  #23
                  Originally posted by mherger View Post
                  Hehe... I should never have started this thread :-).

                  > After restarting the virtual machine (Ubuntu 18.04) on which LMS is
                  > running, I can't seem to reproduce the issue anymore. I assume that you
                  > guys have already tried restarting and it didn't go away? So I expect
                  > the issue to return... We'll see.

                  Similar experience here: I posted here because I experienced exactly
                  what you describe. The track would seemingly be started, but actual
                  playback wouldn't happen.

                  And then I had to indeed restart my LMS system, too - and haven't had a
                  single failure since (which is a week).
                  Ahhhh... I was just going to report no failures in the last 4 days of testing, but I also restarted my 8.3 server after updating the plugins on the morning of the 11th.

                  Just as another reference point, I'll leave that SB Radio on my 8.3 setup with 2 alarms a day configured, see if the issue comes back.

                  Originally posted by chaug View Post
                  One thing I can say from the logs of the successful tries is that when I stop the alarm manually (on the web-ui), then it says `Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: pause` instead of `stop` at the end.
                  I see this as well, I thought it might be because my players are set to pause at power off in player audio settings

                  Kev

                  Comment

                    #24
                    Originally posted by mherger View Post
                    Hehe... I should never have started this thread :-).
                    [color=blue]
                    Oh no, it was good you did. It's important to have this place where people find that they have the same problem.

                    And unless we find what caused this strange issue, we have to expect it to reoccur...

                    Not sure whether I prefer it to reoccur (because then we can figure it out) or it to be a once in a lifetime failure (in which case we'll never know for sure)... Luckily my preference doesn't matter at all.
                    Server: LMS 8.2 on an Ubuntu 18.04 virtual machine
                    Players: Radio, Touch, Duet (Receiver & Controller), 2 Booms, Google Nest Hub (via chromecast plugin)
                    Remote control apps: Material Skin (Web UI), but also SqueezePad (iOS), Squeezecontroller (Android)
                    Important plugins: Trackstat, Spicefly Sugarcube, Lazy Search Music, Custom Browse, Multi Library

                    Comment

                      #25
                      starting and restarting the dockerized LMS does not solve the problem.
                      The windows install works without a hitch.
                      Very strange..
                      Are there ports involved with the alamr? Maybe thats something to test in dockerized apps.

                      Comment

                        #26
                        So what kindof stuff can fix itself by rebooting on "normal" machines but not in docker containers?

                        I have no idea but my first guess would be that it has something to do with environment variables (in docker). Like the timezone or something, which might be set statically in a container or "mirrored" into the container from the host. If the timezone becomes corrupted on the host, the container also gets it wrong and restarting the container should not change that.

                        Have you tried restating the whole machine?
                        Server: LMS 8.2 on an Ubuntu 18.04 virtual machine
                        Players: Radio, Touch, Duet (Receiver & Controller), 2 Booms, Google Nest Hub (via chromecast plugin)
                        Remote control apps: Material Skin (Web UI), but also SqueezePad (iOS), Squeezecontroller (Android)
                        Important plugins: Trackstat, Spicefly Sugarcube, Lazy Search Music, Custom Browse, Multi Library

                        Comment

                          #27
                          Yes, tried all kind of things.. docker container as host ( same ipnumber and all ports ( as far as i know) and as bridged network.
                          Tried older Logitech versions in docker ( the advantage to run several LMS sessions with a simple restart)

                          None of them seems to safely run the alarm.

                          Interesting.. when i set an alarm under the windows version and switch of the server the radio just uses its standard musictune but still works.
                          If i do the same under linux the radio does not start the alarm on the set time.
                          I can see the alamrs in the interface of the radios though, they are there but do not work.. very strange.

                          I see differences in Perl versions between windows and Linux ( see posting above with details)
                          So it seems Windows version is working better then the Linux version.. what can be the main cause of this?

                          Comment

                            #28
                            Unfortunately I've also experienced a failed alarm this morning - running 8.3.0 - 1661147463 on a pi4. The stream didn't start as fas as I could see.
                            Also, 2 days ago - did modify some alarms (did set up 4 different for the same radio) directly from the server interface but player didn't get updated. Had to restart the Radio.
                            Transporter, Touch, SB3, SB2, Duet, Booms, Radios, piCorePlayer --- iPeng & Material --- LMS Version: 8.4.0 - 1676612311 on Pi4 4GB - Max2Play --- Qobuz

                            Comment

                              #29
                              Originally posted by didjean View Post
                              Unfortunately I've also experienced a failed alarm this morning - running 8.3.0 - 1661147463 on a pi4. The stream didn't start as fas as I could see.
                              Also, 2 days ago - did modify some alarms (did set up 4 different for the same radio) directly from the server interface but player didn't get updated. Had to restart the Radio.
                              Again today, no alarm on 1 radio out of 3. And no fallback. Will restart my set up. If still an issue by end of week, will revert back to 8.2
                              Transporter, Touch, SB3, SB2, Duet, Booms, Radios, piCorePlayer --- iPeng & Material --- LMS Version: 8.4.0 - 1676612311 on Pi4 4GB - Max2Play --- Qobuz

                              Comment

                                #30
                                Alarm not working with 8.3?

                                > Again today, no alarm on 1 radio out of 3. And no fallback. Will restart
                                > my set up. If still an issue by end of week, will revert back to 8.2

                                When I started this thread I was definitely seeing an issue. I then did
                                as you suggest: restart the LMS machine. And I haven't had a hiccup since...
                                Michael

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

                                Comment

                                Previous 1 2 3 4 5 12 17 template Next
                                Working...
                                X

                                We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

                                By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.

                                I Agree