Announcement

Collapse
No announcement yet.

Boom alarm behaviour changed

Collapse
X
Collapse
 
  • Page of 2
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 template Next
    #1

    Boom alarm behaviour changed

    Hi all,

    Has the behaviour of the Boom alarm clock changed recently?

    What I used to do is this:
    1. Hear alarm go off, hit snooze.button on the top of the boom. Flashing symbol in top right of display showing snooze
    2. Wait for alarm to go off again, hit snooze again. Flashing symbol in top right showing snooze
    3. Finally get up, press the 'power' button on the Boon to wake it up, then turn it off again
    4. Alarm is cancelled, symbol in top right shows steady alarm symbol
    However, more recently (possible since upgrading to '8.3.1 - 1676361197'), this is what I'm seeing:
    1. Hear alarm go off, hit snooze.button on the top of the boom. Flashing symbol in top right of display showing snooze
    2. Wait for alarm to go off again, hit snooze again. Flashing symbol in top right showing snooze
    3. Finally get up, press the 'power' button on the Boon to wake it up, then turn it off again
    4. ​The symbol in the top right is still flashing, and the alarm will go off again after the snooze period
    It seems the only way to disable the alarm when it's in this state is to use the mobile app (Orange Squeeze in this case) to turn the Boom on and off again.

    Any suggestions?

    Thanks

    Andy
    Last edited by adhawkins; 2023-03-17, 10:19.
    Tags: None
    #2
    On my Boom I disabled the alarm clock in LMS settings, so I can't confirm the change in behavior that you have observed.

    The changelog of LMS 8.3.1 mentions following change under Bug Fixes:
    #835 - Improve Alarm reliability - prevent accidental/random alarm stops.

    Maybe the ​change that you have observed is related to this bug fix. Did you check the alarm clock settings under LMS => Settings => Player => SB Boom => Alarm Clock? If you don't see anything obvious in the settings, consider to remove the existing alarm and set a new alarm, and check if you observe a change in behavior.
    | LMS 8.3.2 on Linux Mint | Squeezebox Boom | RPi0W + pCP 8.2.0 + HiFiBerry DAC Zero | ESP Muse Luxe |

    Comment

      #3
      adhawkins could you please enable logging for player.alarmclock, do your thing, then send me the resulting server.log.zip (and turn off logging again)?

      https://www.dropbox.com/request/T3RctyzGgNg0oFDubq6a
      Michael

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

      Comment

        #4
        Hi Michael,

        [QUOTE=mherger;n1634096]adhawkins could you please enable logging for player.alarmclock, do your thing, then send me the resulting server.log.zip (and turn off logging again)?

        I've uploaded a ZIP file containing the log file, and the procedure I followed.

        Annoyingly, with the logging turned up, the issue didn't happen. I then repeated the test with logging back to 'error', and the problem did happen!

        So it's either an intermittent issue, or there is some side effect of the logging code that allows it to work as expected.

        Let me know if you need me to do anything further. I'll see how it goes tomorrow morning when the alarm goes off and report back.

        Thanks

        Andy

        Comment

          #5
          Originally posted by adhawkins View Post
          Has the behaviour of the Boom alarm clock changed recently?

          What I used to do is this:
          1. Hear alarm go off, hit snooze.button on the top of the boom. Flashing symbol in top right of display showing snooze
          2. Wait for alarm to go off again, hit snooze again. Flashing symbol in top right showing snooze
          3. Finally get up, press the 'power' button on the Boom to wake it up, then turn it off again
          4. Alarm is cancelled, symbol in top right shows steady alarm symbol
          Any suggestions?
          Out of curiosity I tested the alarm clock behavior of my Boom. I tested 3 times, and for me the alarm clock works as expected. I did not enable player.alarmclock logging.

          However in step 3, my Boom behaves different from what you describe above. In my case, when I press the power button a single time, it is turned off immediately, snooze is cancelled and steady alarm symbol is shown.

          I am using LMS 8.3.2, but according to the changelog, the behavior of the alarm clock in 8.3.2 is not changed compared to 8.3.1.
          Last edited by CJS; 2023-03-18, 13:40.
          | LMS 8.3.2 on Linux Mint | Squeezebox Boom | RPi0W + pCP 8.2.0 + HiFiBerry DAC Zero | ESP Muse Luxe |

          Comment

            #6
            I'm sorry, haven't found time to look into your issue, yet. But if the behavior indeed is different between various logging modes, then this clearly is a good starting point! I'll hopefully find some time later today.
            Michael

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

            Comment

              #7
              Originally posted by mherger View Post
              I'm sorry, haven't found time to look into your issue, yet. But if the behavior indeed is different between various logging modes, then this clearly is a good starting point! I'll hopefully find some time later today.
              No worries, it's hardly the end of the world. As long as the alarm goes off, that's what's important!

              Let me know if you need me to do any further investigation.

              Andy
              ​​​​​​​

              Comment

                #8
                Originally posted by CJS View Post
                However in step 3, my Boom behaves different from what you describe above. In my case, when I press the power button a single time, it is turned off immediately, snooze is cancelled and steady alarm symbol is shown.
                I think I wrote that bit from memory, so I may well have got the double power button press wrong.

                Thanks for trying it though.

                Andy

                Comment

                  #9
                  Ok, it happened again this morning (had to use Orange Squeeze to fully turn the alarm off).

                  I'll enable the logging again, and see what happens tomorrow morning. Will report back.

                  Andy

                  Comment

                    #10
                    Ok, with logging enabled again, it functioned as expected. I did need to press the power button twice to take it out of snooze though.

                    Andy

                    Comment

                      #11
                      Hmm... I can't reproduce this. I see the same as CJS reported: upon first press of the Power button the alarm is stopped, and the blinking eye goes away.
                      Michael

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

                      Comment

                        #12
                        Originally posted by mherger View Post
                        Hmm... I can't reproduce this. I see the same as CJS reported: upon first press of the Power button the alarm is stopped, and the blinking eye goes away.
                        Were you using the same version I am? I think I'm on the latest 'release', rather than a nightly.

                        I ran again overnight with alarm logging enabled, and it behaved as expected.

                        I wasn't describing the power button action correctly. The first press of the power button brings up the 'alarm stopped' text, then the second is required to put the Boom back into standby.

                        I'll disable the alarm logging again and see what happens tomorrow. Very strange!

                        Andy

                        ​

                        Comment

                          #13
                          Originally posted by adhawkins View Post

                          I wasn't describing the power button action correctly. The first press of the power button brings up the 'alarm stopped' text, then the second is required to put the Boom back into standby.

                          ​
                          Ok, then my experience might have been closer to what I expected. Can you clarify how this is different from older versions?
                          Michael

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

                          Comment

                            #14
                            Originally posted by mherger View Post

                            Can you clarify how this is different from older versions?
                            When I turn off logging, using the power button while it is snoozed does not turn off the alarm. However, for some reason, with alarm logging turned on, it does (which is the behaviour I'd expect).

                            I've disabled the logging again, will see how it goes tomorrow.

                            Andy

                            Comment

                              #15
                              No logging this morning, and it returned to the 'wrong' behaviour, with the power button not cancelling the alarm while in snooze.

                              What is the current 'stable' nightly version? I'll give that a try.

                              Andy

                              Comment

                              Previous 1 2 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