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 6 13 17 template Next
    #31
    Originally posted by mherger View Post
    > 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...
    Had again an issue this morning, I could hear the radio popping, but no stream and nothing displayed on screen. Yesterday I did restart the machine, but I changed an alarm setting later in the day and didn't restart after.

    Have just restarted now. Fingers crossed for tomorrow morning :-).
    Transporter, Touch, SB3, SB2, Duet, Booms, Radios, piCorePlayer --- iPeng & Material --- LMS Version: 8.4.0 - 1676612311 on Pi4 4GB - Max2Play --- Qobuz

    Comment

      #32
      Originally posted by didjean View Post
      Had again an issue this morning, I could hear the radio popping, but no stream and nothing displayed on screen. Yesterday I did restart the machine, but I changed an alarm setting later in the day and didn't restart after.

      Have just restarted now. Fingers crossed for tomorrow morning :-).
      Well no alarm issue today… let’s see tomorrow. If not reporting here anymore, it seems that it means a restart is needed with 8.3 if you add or update an alarm…
      Transporter, Touch, SB3, SB2, Duet, Booms, Radios, piCorePlayer --- iPeng & Material --- LMS Version: 8.4.0 - 1676612311 on Pi4 4GB - Max2Play --- Qobuz

      Comment

        #33
        Originally posted by didjean View Post
        Well no alarm issue today… let’s see tomorrow. If not reporting here anymore, it seems that it means a restart is needed with 8.3 if you add or update an alarm…
        I changed the time of my Radio alarm by one minute and the alarm sounded this morning so it isn't a general issue with 8.3.

        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

          #34
          I'm definitely having issues with alarms in 8.3.. Its bit random sometimes it works sometimes doesn't. Already restarted radio and LMS in docker maybe will reboot NAS next

          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

            #35
            Sorry to be late to the party but I have experienced this.

            It was shortly after I upgraded but to my knowledge has only happen once.

            The alarm failed to play I woke late nothing on Pcp Screen apart from clock (Normal)

            Nothing in log

            Logitech Media Server Version: 8.3.0 - 1661147463 @ Mon 22 Aug 2022 08:23:34 AM CEST

            Server HTTP Port Number: 9000
            Operating system: Red Hat - EN - utf8
            Platform Architecture: x86_64-linux
            Perl Version: 5.26.3 - x86_64-linux-thread-multi
            Audio::Scan: 0.95
            IO::Socket::SSL: 2.066
            Database Version: DBD::SQLite 1.58 (sqlite 3.22.0)
            Total Players Recognized: 10

            On Rocky Linux 8.6 x64

            Jeff
            sigpic
            Want a webapp ? Get SqueezeLite-X ! https://forums.slimdevices.com/showt...l=1#post903953

            Comment

              #36
              Too

              I'm having this too, unfortunately :-(.
              Do I understand correctly that nobody has experienced this with 8.2?
              Then I'm strongly thinking about downgrading
              1x Classic / 2x Radio / 2x Receiver / 1x DAC32 / LMS 8.3.0 - 1630708871 on Docker / Ubuntu 18.04 LTS
              http://www.last.fm/user/rndr

              Comment

                #37
                Originally posted by rlem View Post
                Do I understand correctly that nobody has experienced this with 8.2?
                I have two systems running side by side, the "live" system is running 8.2.1 and is our daily alarm - no failures on that.

                The other system is a test system running 8.3 set to alarm one player twice a day and I've seen one variant of the alarm failing - Just no alarm presented, the player (SB Radio) remains off with clock screensaver showing. Logfile shows alarm is successfully called but then decides act on a request to stop alarm and to turn itself off (in working instances the same request to stop alarm occurs but the logfile shows that request is specifically ignored - logfile posted earlier in this thread).
                Previously LMS had some plugin updates waiting to be installed and a new version of LMS available. I updated the plugins and restarted LMS (but did not update LMS itself) and it seems as others have found the reboot of LMS cleared the problem.
                It's currently back in the failed state, again plugin updates are waiting and as expected the new version of LMS is still being notified, the alarm is being called but the (spurious??) request to stop the alarm is being acted on rather than ignored.

                Kev

                Comment

                  #38
                  Originally posted by KeBul View Post
                  I have two systems running side by side, the "live" system is running 8.2.1 and is our daily alarm - no failures on that.

                  The other system is a test system running 8.3 set to alarm one player twice a day and I've seen one variant of the alarm failing - Just no alarm presented, the player (SB Radio) remains off with clock screensaver showing. Logfile shows alarm is successfully called but then decides act on a request to stop alarm and to turn itself off (in working instances the same request to stop alarm occurs but the logfile shows that request is specifically ignored - logfile posted earlier in this thread).
                  Previously LMS had some plugin updates waiting to be installed and a new version of LMS available. I updated the plugins and restarted LMS (but did not update LMS itself) and it seems as others have found the reboot of LMS cleared the problem.
                  It's currently back in the failed state, again plugin updates are waiting and as expected the new version of LMS is still being notified, the alarm is being called but the (spurious??) request to stop the alarm is being acted on rather than ignored.

                  Kev
                  I suppose people who say the server log contained nothing didn't set alarm logging to info or debug. I must check my log even though my alarm always sounds.

                  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

                    #39
                    Originally posted by KeBul View Post
                    I have two systems running side by side, the "live" system is running 8.2.1 and is our daily alarm - no failures on that.

                    The other system is a test system running 8.3 set to alarm one player twice a day and I've seen one variant of the alarm failing - Just no alarm presented, the player (SB Radio) remains off with clock screensaver showing. Logfile shows alarm is successfully called but then decides act on a request to stop alarm and to turn itself off (in working instances the same request to stop alarm occurs but the logfile shows that request is specifically ignored - logfile posted earlier in this thread).
                    Previously LMS had some plugin updates waiting to be installed and a new version of LMS available. I updated the plugins and restarted LMS (but did not update LMS itself) and it seems as others have found the reboot of LMS cleared the problem.
                    It's currently back in the failed state, again plugin updates are waiting and as expected the new version of LMS is still being notified, the alarm is being called but the (spurious??) request to stop the alarm is being acted on rather than ignored.

                    Kev
                    This is my log from 8.3 after a successful alarm complete with the ignored stop requests.
                    Code:
                    [22-09-11 15:37:02.9781] Slim::Utils::Alarm::save (1017) Saving alarm.
[22-09-11 15:37:02.9796] Slim::Utils::Alarm::save (1037) Alarm saved with id 6ff2539d Rescheduling alarms...
[22-09-11 15:37:02.9804] Slim::Utils::Alarm::scheduleNext (1391) Asked to schedule next alarm for Livingroom
[22-09-11 15:37:02.9811] Slim::Utils::Alarm::scheduleNext (1443) No future alarms found
[22-09-11 15:37:05.9493] Slim::Utils::Alarm::save (1017) Saving alarm.
[22-09-11 15:37:05.9506] Slim::Utils::Alarm::save (1037) Alarm saved with id 6ff2539d Rescheduling alarms...
[22-09-11 15:37:05.9513] Slim::Utils::Alarm::scheduleNext (1391) Asked to schedule next alarm for Livingroom
[22-09-11 15:37:05.9523] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 15:40:0 11/9/2022
[22-09-11 15:37:05.9531] Slim::Utils::Alarm::scheduleNext (1424) Next alarm is at 15:40:0 11/9/2022
[22-09-11 15:37:05.9538] Slim::Utils::Alarm::scheduleNext (1435) Scheduling alarm
[22-09-11 15:37:05.9545] Slim::Utils::Alarm::_startStopTimeCheck (1880) 2 scheduled alarm(s)
[22-09-11 15:40:00.0013] Slim::Utils::Alarm::sound (516) Alarm triggered for Livingroom
[22-09-11 15:40:00.0021] Slim::Utils::Alarm::sound (534) Alarm does not repeat so disabling for next time
[22-09-11 15:40:00.0028] Slim::Utils::Alarm::save (1017) Saving alarm.
[22-09-11 15:40:00.0041] Slim::Utils::Alarm::sound (560) Sounding alarm
[22-09-11 15:40:00.0063] Slim::Utils::Alarm::sound (589) Current Power State: Off
[22-09-11 15:40:00.0106] Slim::Utils::Alarm::pushAlarmScreensaver (1839) Attempting to push into alarm screensaver: . Current mode: INPUT.List
[22-09-11 15:40:00.0115] Slim::Utils::Alarm::sound (609) Current vol: 80 Alarm vol: 50
[22-09-11 15:40:00.0124] Slim::Utils::Alarm::sound (612) Changing volume from 80 to 50
[22-09-11 15:40:00.0148] Slim::Utils::Alarm::sound (622) Alarm playlist shufflemode: 0
[22-09-11 15:40:00.0164] Slim::Utils::Alarm::sound (628) Alarm playlist url: virgin://_LIVE_vir
[22-09-11 15:40:00.0546] Slim::Utils::Alarm::_setAlarmSubscription (1204) Adding alarm subscription
[22-09-11 15:40:00.0562] Slim::Utils::Alarm::sound (697) Scheduling time out in 3600 seconds
[22-09-11 15:40:00.0569] Slim::Utils::Alarm::_startStopTimeCheck (1880) 1 scheduled alarm(s)
[22-09-11 15:40:00.0574] Slim::Utils::Alarm::scheduleNext (1391) Asked to schedule next alarm for Livingroom
[22-09-11 15:40:00.0579] Slim::Utils::Alarm::scheduleNext (1443) No future alarms found
[22-09-11 15:40:00.0630] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: stop
[22-09-11 15:40:00.0635] Slim::Utils::Alarm::_alarmEnd (1981) Ignoring self-created request
[22-09-11 15:40:00.0654] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: power
[22-09-11 15:40:00.0659] Slim::Utils::Alarm::_alarmEnd (1981) Ignoring self-created request
                    Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
                    Bedroom: Radio
                    Bathroom: Radio

                    Comment

                      #40
                      Alarm not working with 8.3?

                      I've had issues with LMS Alarms for ages. I've pretty much given up depending on it.

                      There used to be Alarm volume settings, but now there isn't a setting for alarm volume? If I play some ambient music and fall asleep at night, when the Alarm comes on in the morning it's at a low volume which fails to wake me.

                      Sometimes the Alarm doesn't start in the morning at all.

                      I've always disliked the changes to go into "Alarm Clock mode", displaying just the current time, with no means to switch to the Now Playing screen without stopping the alarm and then restarting the playing track. Often I wake up to something random and think "What is that song?".

                      I do still have an alarm configured, but often I wake via my smart watch buzzing on my wrist, or smart phone. If music starts playing on my SB3 too, it's a bonus! I use my phone to identify the playing tune, and the SB3 is more or less just a clock display.

                      Phil

                      Comment

                        #41
                        Again, an alarm out of 3 radios failed this morning - with no back up.
                        Didn't change any configuration. A restart doesn't seem to help. Only thing that I can point out: a plugin was waiting to be upgraded.
                        Transporter, Touch, SB3, SB2, Duet, Booms, Radios, piCorePlayer --- iPeng & Material --- LMS Version: 8.4.0 - 1676612311 on Pi4 4GB - Max2Play --- Qobuz

                        Comment

                          #42
                          Alarm not working with 8.3?

                          > Again, an alarm out of 3 radios failed this morning - with no back up.

                          That last remark actually is a good point: when mine failed there wasn't
                          any backup either. Which firmware are you using on your Radios?
                          Michael

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

                          Comment

                            #43
                            Originally posted by mherger View Post
                            > Again, an alarm out of 3 radios failed this morning - with no back up.

                            That last remark actually is a good point: when mine failed there wasn't
                            any backup either. Which firmware are you using on your Radios?
                            Latest Community (I believe): 8.0.1 r16881

                            It has been a while since I've heard Fa Fa Fa :-)
                            Last edited by didjean; 2022-09-26, 20:24.
                            Transporter, Touch, SB3, SB2, Duet, Booms, Radios, piCorePlayer --- iPeng & Material --- LMS Version: 8.4.0 - 1676612311 on Pi4 4GB - Max2Play --- Qobuz

                            Comment

                              #44
                              Originally posted by didjean View Post
                              Latest Community (I believe): 8.0.1 r16881

                              It has been a while since I've heard Fa Fa Fa :-)
                              Joining in, that is what got me puzzled about this topic. My wife is a pretty light sleeper and she usually wakes up just from the little `plop` as the Radio starts preparing to play the alarm. My guess would be that if you are someone that never heard that `plop` you are likely to experience failure to play the track and the absence of a built-in backup in the Radio as a missed alarm.

                              Also, how do you all set the alarms? My wife is pretty stubborn and always changes the alarm settings on Radio itself. If you change it on the LMS side instead I suppose a communications issue would lead to Radio keeping its original next alarm and only switch to the new schedule after having fired that one. That appears to be in line with the remark that rebooting Radio causes it to accept the new schedule directly.

                              Comment

                                #45
                                Originally posted by gordonb3 View Post
                                My wife is a pretty light sleeper and she usually wakes up just from the little `plop` as the Radio starts preparing to play the alarm.
                                Couldn't stop laughing after reading about plop.. Thats indeed pretty light sleeping..I though..

                                Turns out my other half also sometimes wakes to that plop.. Lol

                                Anyway alarm didn't work today again.. Was fine yesterday .. STD original firmware..

                                We wonder if the plop was present but as I need about 3 different alarm clocks to wake me up I will never know ;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

                                Previous 1 2 3 4 5 6 13 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