Home of the Squeezebox™ & Transporter® network music players.

View Poll Results: On what player types does the alarm fail for you?

Voters
20. You may not vote on this poll
  • Squeezebox Radio (official firmware 7.x)

    3 15.00%
  • Squeezebox Radio (community firmware 8.x)

    12 60.00%
  • Squeezebox Touch (official firmware 7.x)

    0 0%
  • Squeezebox Touch (community firmware 8.x)

    0 0%
  • SB Classic/Boom/Receiver/Transporter

    3 15.00%
  • Other (eg. Raspberry Pi based)

    4 20.00%
Multiple Choice Poll.
Page 1 of 19 12311 ... LastLast
Results 1 to 10 of 182
  1. #1
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,775

    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)

  2. #2
    Junior Member
    Join Date
    Aug 2020
    Posts
    19
    Quote 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.3.0 Nightly on RPi4
    Control: Web-GUI/MaterialSkin

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

  3. #3
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,775

    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).

  4. #4
    Senior Member
    Join Date
    Oct 2014
    Location
    Pittsburgh PA
    Posts
    481
    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

  5. #5
    Senior Member
    Join Date
    Jan 2010
    Location
    Hertfordshire
    Posts
    9,628
    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

    Sent from my Pixel 3a using Tapatalk

  6. #6
    Senior Member KeBul's Avatar
    Join Date
    Sep 2009
    Location
    London
    Posts
    450
    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 at 03:28.

  7. #7
    Senior Member KeBul's Avatar
    Join Date
    Sep 2009
    Location
    London
    Posts
    450
    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

  8. #8
    Senior Member
    Join Date
    Jan 2010
    Location
    Hertfordshire
    Posts
    9,628
    Quote 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

  9. #9
    Junior Member
    Join Date
    Aug 2020
    Posts
    19
    Quote 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.3.0 Nightly on RPi4
    Control: Web-GUI/MaterialSkin

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

  10. #10
    Senior Member KeBul's Avatar
    Join Date
    Sep 2009
    Location
    London
    Posts
    450
    Quote 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 at 03:26.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •