Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) Hello all, I had the fallback alarm this morning :o( Which log will be useful now ? Vincent vhenninot's Profile: http://forums.slimdevices.com/member.php?userid=45315 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) Here are my LMS infos : Logitech Media Server Version : *8.3.0*- 1667251155 @ Fri 04 Nov 2022 09:16:39 AM CET Nom d'hôte : raspberrypi IP : 192.168.1.28 Port HTTP : 9000 SE : Debian - FR - utf8 Plate-forme : armv7l-linux Version de Perl : 5.24.1 - arm-linux-gnueabihf-thread-multi-64int Audio::Scan : 1.02 IO::Socket::SSL : 2.044 Version de la base de données : DBD::SQLite 1.58 (sqlite 3.22.0) vhenninot's Profile: http://forums.slimdevices.com/member.php?userid=45315 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] 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. ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) Hello all, Many thanks for all tests and work LMS is running on a raspberry, and I upgraded all radios with latest community firmware. Im using LMS alarm since 10 years and never had problems until i upgraded to 8.3. I also confirm that i did not use material skin when the alarm bug started to occur. Im streaming from Deezer, I will try to use local music files only for next alarm to be sure that there is no network timeout Vincent vhenninot's Profile: http://forums.slimdevices.com/member.php?userid=45315 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the
results, please visit http://forums.slimdevices.com/showthread.php?t=116649
Question: On what player types does the alarm fail for you?
- Squeezebox Radio (official firmware 7.x)
- Squeezebox Radio (community firmware 8.x)
- Squeezebox Touch (official firmware 7.x)
- Squeezebox Touch (community firmware 8.x)
- SB Classic/Boom/Receiver/Transporter
- Other (eg. Raspberry Pi based)
I had my first confirmed occurrence this morning of Michael's recent LMS
change saving me from a missed alarm due to a "playerprefs" stop
command, which originated from an Android instance of Material Skin
running on my phone. Running LMS 8.3.1 Nov 28 build and Material Skin
4.0.1. Here is the log:
Code:
[22-12-06 08:30:00.0052] Slim::Utils::Alarm::sound (516) Alarm triggered for
Bedroom pair
[22-12-06 08:30:00.0061] Slim::Utils::Alarm::sound (560) Sounding alarm
[22-12-06 08:30:00.0148] Slim::Utils::Alarm::sound (589) Current Power State:
On
[22-12-06 08:30:00.0190] Slim::Utils::Alarm::pushAlarmScreensaver (1839)
Attempting to push into alarm screensaver: . Current mode: INPUT.List
[22-12-06 08:30:00.0203] Slim::Utils::Alarm::sound (609) Current vol: 26
Alarm vol: 30
[22-12-06 08:30:00.0206] Slim::Utils::Alarm::sound (612) Changing volume from
26 to 30
[22-12-06 08:30:00.0250] Slim::Utils::Alarm::sound (622) Alarm playlist
shufflemode: 0
[22-12-06 08:30:00.0280] Slim::Utils::Alarm::sound (628) Alarm playlist url:
http://www.folkalley.com/membership.pls
[22-12-06 08:30:00.0809] Slim::Utils::Alarm::_setAlarmSubscription (1204)
Adding alarm subscription
[22-12-06 08:30:00.0825] Slim::Utils::Alarm::sound (697) Scheduling time out
in 3600 seconds
[22-12-06 08:30:00.0839] Slim::Utils::Alarm::_startStopTimeCheck (1880) 0
scheduled alarm(s)
[22-12-06 08:30:00.0842] Slim::Utils::Alarm::_startStopTimeCheck (1889)
Stopping time checker task
[22-12-06 08:30:00.0846] Slim::Utils::Alarm::scheduleNext (1391) Asked to
schedule next alarm for Bedroom pair
[22-12-06 08:30:00.0855] Slim::Utils::Alarm::findNextTime (461) Potential
next time found: 8:30:0 6/12/2022
[22-12-06 08:30:00.0857] Slim::Utils::Alarm::findNextTime (466) Last alarm
due: 8:30:0 6/12/2022
[22-12-06 08:30:00.0859] Slim::Utils::Alarm::findNextTime (471) Skipping..
[22-12-06 08:30:00.0861] Slim::Utils::Alarm::findNextTime (461) Potential
next time found: 8:30:0 7/12/2022
[22-12-06 08:30:00.0863] Slim::Utils::Alarm::findNextTime (466) Last alarm
due: 8:30:0 6/12/2022
[22-12-06 08:30:00.0866] Slim::Utils::Alarm::scheduleNext (1424) Next alarm
is at 8:30:0 7/12/2022
[22-12-06 08:30:00.0868] Slim::Utils::Alarm::scheduleNext (1435) Scheduling
alarm
[22-12-06 08:30:00.0870] Slim::Utils::Alarm::_startStopTimeCheck (1880) 1
scheduled alarm(s)
[22-12-06 08:30:00.0872] Slim::Utils::Alarm::_startStopTimeCheck (1884)
Starting time checker task
[22-12-06 08:30:00.0910] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd
called with request: stop
[22-12-06 08:30:00.1038] Slim::Utils::Misc::msg (1325) Warning:
[08:30:00.1012] (
bless({
_cb_args => undef,
_cb_enable=> 1,
_cb_func => undef,
_clientid => "cc:cc:4c:51:85:cb",
_func => sub { "???" },
_isQuery => 0,
_langoverride => undef,
_needClient => 1,
_params => {},
_request => ["stop"],
_requeststr => "stop",
_results => {},
_source =>
"/93e24c28/slim/playerprefs/cc:cc:4c:51:85:cb|274||93e24c28|Mozilla/5.0 (Linux;
Android 7.1.1; ZTE A2017U Build/NMF26V; wv) AppleWebKit/537.36 (KHTML, like
Gecko) Version/4.0 Chrome/107.0.5304.141 Mobile Safari/537.36",
_status => 10,
_useixhash=> 0,
}, "Slim::Control::Request"),
"Alarm: ignored event",
) at /Slim/Utils/Alarm.pm line 1986.
[22-12-06 08:30:00.1041] Slim::Utils::Alarm::_alarmEnd (1987) Ignoring
notification to subscriber
Sam
SamY's Profile: http://forums.slimdevices.com/member.php?userid=63495
View this thread: http://forums.slimdevices.com/showthread.php?t=116649
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) mherger wrote: > > When registering a notification callback for a particular player > > ($client), e.g. > > Code: > > > > Slim::Control::Request::subscribe( \, [['power', > 'play', 'playlist', 'pause', 'mixer']], $client); > > > > is it expected/intended that the callback should also be invoked > for > > other players that are synched with that player? > > I don't think it is. But I'm not too familiar with that code. If you > check the client in your callback, would it be called for _all_ synched > > players or only ever one, but not always the one to be expected? The latter, it seems. The name of the player using the plugin is "Max2Play". The two other synced players are "DAC32" and "Bedroom pair". Here is a portion of the plugin's debug log when initiating playback from the DAC32 player. Note that none of the callback calls are from the plugin client itself. Code: [22-12-04 20:53:43.6701] Plugins::DenonAvpControl::Plugin::commandCallback (2172) *** DenonAvpControl: commandCallback() p0: playlist [22-12-04 20:53:43.6704] Plugins::DenonAvpControl::Plugin::commandCallback (2173) *** DenonAvpControl: commandCallback() p1: jump [22-12-04 20:53:43.6706] Plugins::DenonAvpControl::Plugin::commandCallback (2174) *** DenonAvpControl: commandCallback() p2: [22-12-04 20:53:43.6707] Plugins::DenonAvpControl::Plugin::commandCallback (2184) *** DenonAvpControl: commandCallback() Player: DAC32 [22-12-04 20:53:43.6709] Plugins::DenonAvpControl::Plugin::commandCallback (2187) *** DenonAvpControl: commandCallback() Unregistered player - bypassing [22-12-04 20:53:43.7314] Plugins::DenonAvpControl::Plugin::commandCallback (2172) *** DenonAvpControl: commandCallback() p0: playlist [22-12-04 20:53:43.7316] Plugins::DenonAvpControl::Plugin::commandCallback (2173) *** DenonAvpControl: commandCallback() p1: open [22-12-04 20:53:43.7318] Plugins::DenonAvpControl::Plugin::commandCallback (2174) *** DenonAvpControl: commandCallback() p2: [22-12-04 20:53:43.7320] Plugins::DenonAvpControl::Plugin::commandCallback (2184) *** DenonAvpControl: commandCallback() Player: Bedroom pair [22-12-04 20:53:43.7322] Plugins::DenonAvpControl::Plugin::commandCallback (2187) *** DenonAvpControl: commandCallback() Unregistered player - bypassing [22-12-04 20:53:43.7471] Plugins::DenonAvpControl::Plugin::commandCallback (2172) *** DenonAvpControl: commandCallback() p0: playlist [22-12-04 20:53:43.7474] Plugins::DenonAvpControl::Plugin::commandCallback (2173) *** DenonAvpControl: commandCallback() p1: open [22-12-04 20:53:43.7476] Plugins::DenonAvpControl::Plugin::commandCallback (2174) *** DenonAvpControl: commandCallback() p2: [22-12-04 20:53:43.7478] Plugins::DenonAvpControl::Plugin::commandCallback (2184) *** DenonAvpControl: commandCallback() Player: Bedroom pair [22-12-04 20:53:43.7479] Plugins::DenonAvpControl::Plugin::commandCallback (2187) *** DenonAvpControl: commandCallback() Unregistered player - bypassing [22-12-04 20:53:44.3219] Plugins::DenonAvpControl::Plugin::commandCallback (2172) *** DenonAvpControl: commandCallback() p0: playlist [22-12-04 20:53:44.3228] Plugins::DenonAvpControl::Plugin::commandCallback (2173) *** DenonAvpControl: commandCallback() p1: newsong [22-12-04 20:53:44.3233] Plugins::DenonAvpControl::Plugin::commandCallback (2174) *** DenonAvpControl: commandCallback() p2: [22-12-04 20:53:44.3239] Plugins::DenonAvpControl::Plugin::commandCallback (2184) *** DenonAvpControl: commandCallback() Player: Bedroom pair [22-12-04 20:53:44.3243] Plugins::DenonAvpControl::Plugin::commandCallback (2187) *** DenonAvpControl: commandCallback() Unregistered player - bypassing [22-12-04 20:58:52.2127] Plugins::DenonAvpControl::Plugin::commandCallback (2172) *** DenonAvpControl: commandCallback() p0: playlist [22-12-04 20:58:52.2130] Plugins::DenonAvpControl::Plugin::commandCallback (2173) *** DenonAvpControl: commandCallback() p1: open [22-12-04 20:58:52.2131] Plugins::DenonAvpControl::Plugin::commandCallback (2174) *** DenonAvpControl: commandCallback() p2: [22-12-04 20:58:52.2133] Plugins::DenonAvpControl::Plugin::commandCallback (2184) *** DenonAvpControl: commandCallback() Player: Bedroom pair [22-12-04
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) KeBul wrote: > Well somewhat disappointing news today... > > This morning my 7am Back Bedroom alarm failed to trigger... > > [22-12-04 07:00:37.4903] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd > called with request: pause > > _source => > "/5cf52aae/slim/request|100||5cf52aae|SqueezePlay-baby/8.0.1-r16855 > (armv5tejl)", > > So this was a "request" from the player itself (I know that because it's > the only player with firmware 16855), even though the player was not > touched (I slept through till 9:30), but possibly relevant the last > thing done on the player was to turn it off by it's power button and the > player is configured to pause on power off. > The Radio in my bedroom is always operated locally. My GF actually even programs the alarms on the thing itself even after I showed her that it is much easier to do using the web frontend. She never missed any alarm but I can't really state that the issue discussed here never occurred. Over the years we have had several occurrences of the fallback alarm sounding but I always figured it was a WiFi issue and I can in fact state that after inspection later I did see a red WiFi icon but I don't really know if that was always the case. As I mentioned before my GF is a fairly light sleeper and she often responses to nothing more than the power on 'plop' sound, which I know because sometimes the paperboy wakes me about an hour earlier and I have not fully dozed back but even then I often miss the 'plop' but it is the 'bleep' from the poweroff button pressed without having heard any music prior to that. What I found during testing is that sometimes the Radio would turn on, then the alarmOff signal was logged and executed, and after that the backup alarm sounded. Intriguing as it is I really have no clue how many times that may have happened if she hadn't killed it just from hearing the device powering on. gordonb3's Profile: http://forums.slimdevices.com/member.php?userid=71050 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) Well somewhat disappointing news today... This morning my 7am Back Bedroom alarm failed to trigger... [22-12-04 07:00:37.4903] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: pause _source => "/5cf52aae/slim/request|100||5cf52aae|SqueezePlay-baby/8.0.1-r16855 (armv5tejl)", So this was a "request" from the player itself (I know that because it's the only player with firmware 16855), even though the player was not touched (I slept through till 9:30), but possibly relevant the last thing done on the player was to turn it off by it's power button and the player is configured to pause on power off. There was a nice block of "ignoring self-created request" and "Ignoring unwanted notifications" - so handling of those seemed to be working fine [22-12-04 07:00:00.0625] Slim::Utils::Alarm::_alarmEnd (1982) Ignoring self-created request [22-12-04 07:00:00.0811] Slim::Utils::Alarm::_alarmEnd (1966) Ignoring unwanted notification: playlist stop [22-12-04 07:00:10.2100] Slim::Utils::Alarm::_alarmEnd (1966) Ignoring unwanted notification: playlist pause [22-12-04 07:00:37.2776] Slim::Utils::Alarm::_alarmEnd (1966) Ignoring unwanted notification: mode stop [22-12-04 07:00:37.2836] Slim::Utils::Alarm::_alarmEnd (1966) Ignoring unwanted notification: playlist stop So unlike my testing scenarios this wasn't a failure with a 'playerprefs' source directly involved, the system had not been restarted after Friday's testing, so I guess still had all the elements for trigger and failure embedded in there somewhere. I've tried to put MaterialSkin vTest back on, but fails to load with "Can't locate Plugins/MaterialSkin/Plugin.pm in @INC", I think I'm doing the same as before for a manual plugin zip install, but I must be missing something because it's not having it. Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
When registering a notification callback for a particular player ($client), e.g. Code: Slim::Control::Request::subscribe( \, [['power', 'play', 'playlist', 'pause', 'mixer']], $client); is it expected/intended that the callback should also be invoked for other players that are synched with that player? I don't think it is. But I'm not too familiar with that code. If you check the client in your callback, would it be called for _all_ synched players or only ever one, but not always the one to be expected? ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) I apologize if this post is off-topic but there is a chance that it might be related in a tangential way. About 3 months ago, a user of the Denon AVR plugin that I co-maintain reported strange behavior and provided a debug log illustrating it. It appeared that the problem was caused by the notification callback in the plugin being called for events from players other than those for which the plugin had registered (subscribed) the callback --- a condition that the code was completely unprepared to handle. Upon further research, it was discovered that the players in questions were ones that had been synched with a player that WAS registered for the events. I was able to easily recreate the situation and coded a fix (workaround?) that was fairly simple but added some cpu overhead --- add and maintain an array of player id's that are currently registered for the notifications and ignore any event callbacks from unregistered players. However, it seemed strange to me at the time that a problem with as common a use case as this should suddenly appear in a plugin that had been in fairly widespread use for over 10 years. I also had doubts about whether or not the behavior was intentional/correct after looking at the LMS doc pages. So here's my question: When registering a notification callback for a particular player ($client), e.g. Code: Slim::Control::Request::subscribe( \, [['power', 'play', 'playlist', 'pause', 'mixer']], $client); is it expected/intended that the callback should also be invoked for other players that are synched with that player? Sam SamY's Profile: http://forums.slimdevices.com/member.php?userid=63495 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
Michael doesn't seem to believe Material is to blame - however, I have tested several times without Material installed and not had any alarm failures, but there's a caveat to that - the only way I can "reliably" induce failures during testing is by playing around and changing between players in Material - with no Material installed I can't do that. Yes, I believe Material is only triggering an issue in LMS. But to ignore _notifications_ in the alarm code seems the right thing to me. They usually echo an action taken elsewhere. And we should only act on actual input, not on notification (unless we subscribe to them, of course). Why that introduces another issue, I have no clue. I remember Felix, and old Squeezebox buddie of the time, who had to work on Alarm code at a later stage, once mentioned he would never use it. The Alarm code combined (LMS & firmware) was just too complicated, dealing with too many possible failures... I think it's also worth noting that Michael started this thread and first reported he was having strange alarm issues early Aug, about 2 weeks after your unsubscribe change. ~Insert smoking gun emoji here~ :D It was the return to school time - we hadn't used the alarm for several weeks :-). ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) cpd73 wrote: > Mainly to cleanup - I believe if you subscribe to a message you should > unsubscribe when you no longer want to be informed. I -think- it was > missing before due to a simple oversight. > Yeah sure, makes sense - wish I had a better understanding of all this (and a better capability to understand all this :o. ) cpd73 wrote: > Probably none, as Material has worked for years before this change. > So although not as tidy as you would like, a very low risk to revert that change. cpd73 wrote: > I don't 100% believe Material is wrong, just that its behaviour triggers > this issue in LMS. > Same place I've got to on this one. There's been some good work done investigating though by yourself, Michael and gordonb3, but seems to be quite a few unanswered questions floating around, like yours on correct method to unsubscribe and gordon's on why the alarms always seem to start with an ignored self request "Stop" Must say as well, while conversing with you - amazing job you've done on Material it's a lovely modern interface for LMS Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) KeBul wrote: > Checking back on your posts you say you introduced this method of > unsubscribe in July 22 - what was the reason for that introduction? Mainly to cleanup - I believe if you subscribe to a message you should unsubscribe when you no longer want to be informed. I -think- it was missing before due to a simple oversight. KeBul wrote: > What would be the potential impact of removing the unsubscribe (apart > from maybe a fix for the alarm problem)? Probably none, as Material has worked for years before this change. KeBul wrote: > Michael doesn't seem to believe Material is to blame - however, I have > tested several times without Material installed and not had any alarm > failures, but there's a caveat to that - the only way I can "reliably" > induce failures during testing is by playing around and changing between > players in Material - with no Material installed I can't do that. > Having said that, the testing I did with your MaterialSkin vTest, which > had the unsubscribe removed, was quite extensive with lots of changing > between players but no alarm failures were seen. I don't 100% believe Material is wrong, just that its behavior triggers this issue in LMS. *Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here. cpd73's Profile: http://forums.slimdevices.com/member.php?userid=66686 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) cpd73 wrote: > I'm going to release an update to Material soon. Should I remove the > unsubscribe? Will that work-around the issue? Or should I leave Material > as is and wait for the fix in LMS itself? Hi Craig, Checking back on your posts you say you introduced this method of unsubscribe in July 22 - what was the reason for that introduction? What would be the potential impact of removing the unsubscribe (apart from maybe a fix for the alarm problem)? Michael doesn't seem to believe Material is to blame - however, I have tested several times without Material installed and not had any alarm failures, but there's a caveat to that - the only way I can "reliably" induce failures during testing is by playing around and changing between players in Material - with no Material installed I can't do that. Having said that, the testing I did with your MaterialSkin vTest, which had the unsubscribe removed, was quite extensive with lots of changing between players but no alarm failures were seen. Michaels ignore 'playerprefs' fix in Alarm.pm resolves or at least drastically improves the problem where an alarm fails to trigger, but seems to have made another issue worse - "using a remote device to pause or stop an alarm". Although I agree with him this is considerably less of an issue than an alarm failing to trigger, so we are in a better place at the moment. My testing also seems to indicate, without Material installed pause works every time, i.e. the alarm is successfully shutdown, once Material is installed the issue for me becomes prevalent, pause regularly fails to completely shutdown an alarm. I haven't tested MaterialSkin vTest against this issue, if you would like me to do so let me know, but from what I'm seeing in the logs I would be surprised if removing the unsubscribe didn't also help with this. In short, albeit from a pure testing evidential standpoint rather than in-depth knowledge of Material and LMS and the protocols/code/interactions between them etc.. I think that Material currently is a trigger for whatever is going wrong within the player and alarm handling, from the testing with MaterialSkin vtest, it looks like removing the unsubscribe either stops that trigger or greatly reduces it. I think it's also worth noting that Michael started this thread and first reported he was having strange alarm issues early Aug, about 2 weeks after your unsubscribe change. ~Insert smoking gun emoji here~ :D Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) KeBul wrote: > Yep seriously, worked for the first couple of alarms but then started > failing each time. Just set up another test - failed 3 out of 4. > > Not as reliable to fail as pause on a Radio, but definitely still > happening. > > KevI wonder why we don't see the same behaviour... Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) I'm going to release an update to Material soon. Should I remove the unsubscribe? Will that work-around the issue? Or should I leave Material as is and wait for the fix in LMS itself? *Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here. cpd73's Profile: http://forums.slimdevices.com/member.php?userid=66686 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) slartibartfast wrote: > Seriously [emoji1787]. How consistent were your results? I tried four > times in a row and each time the alarm screen closed down. Even with > pause and that never works on the Radio. > slartibartfast wrote: > I just tried seven alarms on the Touch and every time the alarm was > cancelled correctly with three "Stops" and four "Pauses". > Yep seriously, worked for the first couple of alarms but then started fail each time. Just set up another test - failed 3 out of 4. Not as reliable to fail as pause on a Radio, but definitely still happening. Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) slartibartfast wrote: > I suppose this could be the culprit > https://github.com/Logitech/squeezeplay/commit/d5d4e0590a1b962395f00535453276b3baa429b4 > > Sent from my Pixel 3a using TapatalkAlthough that code is in Squeezeplay for > Windows and that also has the issue where the alarm screen does not close down when stopped or paused remotely. Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) mherger wrote: > > @mherger Any thoughts on why the Radio and the Touch behave > differently > > when the alarm is paused or stopped from a remote source? I wonder if > > I don't know... some of the very last changes were indeed related to the > > Alarm. But I've lost track of what is in which firmware version. > > https://github.com/Logitech/squeezeplay/commits/public/7.8I suppose this > could be the culprit https://github.com/Logitech/squeezeplay/commit/d5d4e0590a1b962395f00535453276b3baa429b4 Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
@mherger Any thoughts on why the Radio and the Touch behave differently when the alarm is paused or stopped from a remote source? I wonder if I don't know... some of the very last changes were indeed related to the Alarm. But I've lost track of what is in which firmware version. https://github.com/Logitech/squeezeplay/commits/public/7.8 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) KeBul wrote: > I can reproduce the pause and stop not closing down an alarm completely > problem on my SB Touch > > KevI just tried seven alarms on the Touch and every time the alarm was cancelled correctly with three "Stops" and four "Pauses". Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) KeBul wrote: > I can reproduce the pause and stop not closing down an alarm completely > problem on my SB Touch > > KevSeriously [emoji1787]. How consistent were your results? I tried four times in a row and each time the alarm screen closed down. Even with pause and that never works on the Radio. Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) slartibartfast wrote: > So far all my alarm testing has been on a Radio where pausing an alarm > remotely doesn't cancel the alarm correctly and stopping an alarm > remotely sometimes cancels the alarm correctly. > So I tried setting alarms on a Touch and so far both pausing and > stopping an alarm remotely has worked correctly every time. So what is > the difference? > slartibartfast wrote: > @mherger Any thoughts on why the Radio and the Touch behave differently > when the alarm is paused or stopped from a remote source? I wonder if > the last official firmware of the Touch contained any changes related to > this which were not in the Radio firmware. > I can reproduce the pause and stop not closing down an alarm completely problem on my SB Touch Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) @mherger Any thoughts on why the Radio and the Touch behave differently when the alarm is paused or stopped from a remote source? I wonder if the last official firmware of the Touch contained any changes related to this which were not in the Radio firmware. Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
Just to add another usage case, my morning alarm is set up for a stereo pair of Google Nest Minis using Philippe's Castbridge plugin. The alarm had become unreliable in recent months but has not failed since applying the most recent updates to Material Skin and LMS. Following is a debug log of this morning's successful alarm trigger and subsequent successful pause/stop, which was achieved by saying "Google, stop the music". Note that the source for the pause request is "CLI". Ok, ok. There's a use case for other control points :-). Nice one! ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) slartibartfast wrote: > The ending of my alarm log looks very similar to yours. In my case > though although the log says the alarm has been stopped the alarm screen > did not close on the player. > Do we know what > "Attempting to pop alarm screensaver" means? > > Push and Pop are stack related terms. Push means to save the current state and replace it with something new, Pop is the reverse and restores that earlier state. gordonb3's Profile: http://forums.slimdevices.com/member.php?userid=71050 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) So far all my alarm testing has been on a Radio where pausing an alarm remotely doesn't cancel the alarm correctly and stopping an alarm remotely sometimes cancels the alarm correctly. So I tried setting alarms on a Touch and so far both pausing and stopping an alarm remotely has worked correctly every time. So what is the difference? Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the
results, please visit http://forums.slimdevices.com/showthread.php?t=116649
Question: On what player types does the alarm fail for you?
- Squeezebox Radio (official firmware 7.x)
- Squeezebox Radio (community firmware 8.x)
- Squeezebox Touch (official firmware 7.x)
- Squeezebox Touch (community firmware 8.x)
- SB Classic/Boom/Receiver/Transporter
- Other (eg. Raspberry Pi based)
SamY wrote:
> Just to add another usage case, my morning alarm is set up for a stereo
> pair of Google Nest Minis using Philippe's Castbridge plugin. The alarm
> had become unreliable in recent months but has not failed since applying
> the most recent updates to Material Skin and LMS. Following is a debug
> log of this morning's successful alarm trigger and subsequent successful
> pause/stop, which was achieved by saying "Google, stop the music". Note
> that the source for the pause request is "CLI".
>
> >
Code:
> > [22-12-01 08:30:00.0162] Slim::Utils::Alarm::sound (516) Alarm
triggered for Bedroom pair
> [22-12-01 08:30:00.0175] Slim::Utils::Alarm::sound (560) Sounding alarm
> [22-12-01 08:30:00.0200] Slim::Utils::Alarm::sound (589) Current Power
State: On
> [22-12-01 08:30:00.0210] Slim::Utils::Alarm::pushAlarmScreensaver (1839)
Attempting to push into alarm screensaver: . Current mode: INPUT.List
> [22-12-01 08:30:00.0215] Slim::Utils::Alarm::sound (609) Current vol: 32
Alarm vol: 30
> [22-12-01 08:30:00.0220] Slim::Utils::Alarm::sound (612) Changing volume
from 32 to 30
> [22-12-01 08:30:00.0236] Slim::Utils::Alarm::sound (622) Alarm playlist
shufflemode: 0
> [22-12-01 08:30:00.0249] Slim::Utils::Alarm::sound (628) Alarm playlist
url: http://www.folkalley.com/membership.pls
> [22-12-01 08:30:00.0366] Slim::Utils::Alarm::_setAlarmSubscription (1204)
Adding alarm subscription
> [22-12-01 08:30:00.0374] Slim::Utils::Alarm::sound (697) Scheduling time
out in 3600 seconds
> [22-12-01 08:30:00.0379] Slim::Utils::Alarm::_startStopTimeCheck (1880) 0
scheduled alarm(s)
> [22-12-01 08:30:00.0382] Slim::Utils::Alarm::_startStopTimeCheck (1889)
Stopping time checker task
> [22-12-01 08:30:00.0387] Slim::Utils::Alarm::scheduleNext (1391) Asked to
schedule next alarm for Bedroom pair
> [22-12-01 08:30:00.0391] Slim::Utils::Alarm::findNextTime (461) Potential
next time found: 8:30:0 1/12/2022
> [22-12-01 08:30:00.0394] Slim::Utils::Alarm::findNextTime (466) Last alarm
due: 8:30:0 1/12/2022
> [22-12-01 08:30:00.0396] Slim::Utils::Alarm::findNextTime (471) Skipping..
> [22-12-01 08:30:00.0399] Slim::Utils::Alarm::findNextTime (461) Potential
next time found: 8:30:0 2/12/2022
> [22-12-01 08:30:00.0402] Slim::Utils::Alarm::findNextTime (466) Last alarm
due: 8:30:0 1/12/2022
> [22-12-01 08:30:00.0405] Slim::Utils::Alarm::scheduleNext (1424) Next alarm
is at 8:30:0 2/12/2022
> [22-12-01 08:30:00.0408] Slim::Utils::Alarm::scheduleNext (1435) Scheduling
alarm
> [22-12-01 08:30:00.0411] Slim::Utils::Alarm::_startStopTimeCheck (1880) 1
scheduled alarm(s)
> [22-12-01 08:30:00.0413] Slim::Utils::Alarm::_startStopTimeCheck (1884)
Starting time checker task
> [22-12-01 08:30:00.0430] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd
called with request: stop
> [22-12-01 08:30:00.0445] Slim::Utils::Misc::msg (1325) Warning:
[08:30:00.0442] (
> bless({
> _cb_args => undef,
> _cb_enable=> 1,
> _cb_func => undef,
> _clientid => "cc:cc:4c:51:85:cb",
> _func => sub { "???" },
> _isQuery => 0,
> _langoverride => undef,
> _needClient => 1,
> _params => {},
> _request => ["stop"],
> _requeststr => "stop",
> _results => {},
> _source => "ALARM",
> _status => 10,
> _useixhash=> 0,
> }, "Slim::Control::Request"),
> "Alarm: ignored event",
> ) at /Slim/Utils/Alarm.pm line 1981.
> [22-12-01 08:30:00.0448] Slim::Utils::Alarm::_alarmEnd (1982) Ignoring
self-created request
> [22-12-01 08:31:30.0468] Slim::Utils::Alarm::_checkPlaying (1115) Checking
whether client is playing for alarm 36ec2f69
> [22-12-01 08:31:30.0475] Slim::Utils::Alarm::_checkPlaying (1122) Current
playmode: play
> [22-12-01 09:12:03.2180] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd
called with request: pause
> [22-12-01 09:12:03.2200] Slim::Utils::Misc::msg (1325) Warning:
[09:12:03.2198] do {
> require MIME::Base64;
> require Symbol;
> my $a = bless({
> _ae_callback => sub { "???" },
> _cb_enable=> 1,
> _clientid => "cc:cc:4c:51:85:cb",
> _connectionid => bless(Symbol::gensym(), "IO::Socket::INET"),
> _func => sub { "???" },
> _isQuery => 0,
>
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the
results, please visit http://forums.slimdevices.com/showthread.php?t=116649
Question: On what player types does the alarm fail for you?
- Squeezebox Radio (official firmware 7.x)
- Squeezebox Radio (community firmware 8.x)
- Squeezebox Touch (official firmware 7.x)
- Squeezebox Touch (community firmware 8.x)
- SB Classic/Boom/Receiver/Transporter
- Other (eg. Raspberry Pi based)
Just to add another usage case, my morning alarm is set up for a stereo
pair of Google Nest Minis using Philippe's Castbridge plugin. The alarm
had become unreliable in recent months but has not failed since applying
the most recent updates to Material Skin and LMS. Following is a debug
log of this morning's successful alarm trigger and subsequent successful
pause/stop, which was achieved by saying "Google, stop the music". Note
that the source for the pause request is "CLI".
Code:
[22-12-01 08:30:00.0162] Slim::Utils::Alarm::sound (516) Alarm triggered
for Bedroom pair
[22-12-01 08:30:00.0175] Slim::Utils::Alarm::sound (560) Sounding alarm
[22-12-01 08:30:00.0200] Slim::Utils::Alarm::sound (589) Current Power State:
On
[22-12-01 08:30:00.0210] Slim::Utils::Alarm::pushAlarmScreensaver (1839)
Attempting to push into alarm screensaver: . Current mode: INPUT.List
[22-12-01 08:30:00.0215] Slim::Utils::Alarm::sound (609) Current vol: 32
Alarm vol: 30
[22-12-01 08:30:00.0220] Slim::Utils::Alarm::sound (612) Changing volume from
32 to 30
[22-12-01 08:30:00.0236] Slim::Utils::Alarm::sound (622) Alarm playlist
shufflemode: 0
[22-12-01 08:30:00.0249] Slim::Utils::Alarm::sound (628) Alarm playlist url:
http://www.folkalley.com/membership.pls
[22-12-01 08:30:00.0366] Slim::Utils::Alarm::_setAlarmSubscription (1204)
Adding alarm subscription
[22-12-01 08:30:00.0374] Slim::Utils::Alarm::sound (697) Scheduling time out
in 3600 seconds
[22-12-01 08:30:00.0379] Slim::Utils::Alarm::_startStopTimeCheck (1880) 0
scheduled alarm(s)
[22-12-01 08:30:00.0382] Slim::Utils::Alarm::_startStopTimeCheck (1889)
Stopping time checker task
[22-12-01 08:30:00.0387] Slim::Utils::Alarm::scheduleNext (1391) Asked to
schedule next alarm for Bedroom pair
[22-12-01 08:30:00.0391] Slim::Utils::Alarm::findNextTime (461) Potential
next time found: 8:30:0 1/12/2022
[22-12-01 08:30:00.0394] Slim::Utils::Alarm::findNextTime (466) Last alarm
due: 8:30:0 1/12/2022
[22-12-01 08:30:00.0396] Slim::Utils::Alarm::findNextTime (471) Skipping..
[22-12-01 08:30:00.0399] Slim::Utils::Alarm::findNextTime (461) Potential
next time found: 8:30:0 2/12/2022
[22-12-01 08:30:00.0402] Slim::Utils::Alarm::findNextTime (466) Last alarm
due: 8:30:0 1/12/2022
[22-12-01 08:30:00.0405] Slim::Utils::Alarm::scheduleNext (1424) Next alarm
is at 8:30:0 2/12/2022
[22-12-01 08:30:00.0408] Slim::Utils::Alarm::scheduleNext (1435) Scheduling
alarm
[22-12-01 08:30:00.0411] Slim::Utils::Alarm::_startStopTimeCheck (1880) 1
scheduled alarm(s)
[22-12-01 08:30:00.0413] Slim::Utils::Alarm::_startStopTimeCheck (1884)
Starting time checker task
[22-12-01 08:30:00.0430] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd
called with request: stop
[22-12-01 08:30:00.0445] Slim::Utils::Misc::msg (1325) Warning:
[08:30:00.0442] (
bless({
_cb_args => undef,
_cb_enable=> 1,
_cb_func => undef,
_clientid => "cc:cc:4c:51:85:cb",
_func => sub { "???" },
_isQuery => 0,
_langoverride => undef,
_needClient => 1,
_params => {},
_request => ["stop"],
_requeststr => "stop",
_results => {},
_source => "ALARM",
_status => 10,
_useixhash=> 0,
}, "Slim::Control::Request"),
"Alarm: ignored event",
) at /Slim/Utils/Alarm.pm line 1981.
[22-12-01 08:30:00.0448] Slim::Utils::Alarm::_alarmEnd (1982) Ignoring
self-created request
[22-12-01 08:31:30.0468] Slim::Utils::Alarm::_checkPlaying (1115) Checking
whether client is playing for alarm 36ec2f69
[22-12-01 08:31:30.0475] Slim::Utils::Alarm::_checkPlaying (1122) Current
playmode: play
[22-12-01 09:12:03.2180] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd
called with request: pause
[22-12-01 09:12:03.2200] Slim::Utils::Misc::msg (1325) Warning:
[09:12:03.2198] do {
require MIME::Base64;
require Symbol;
my $a = bless({
_ae_callback => sub { "???" },
_cb_enable=> 1,
_clientid => "cc:cc:4c:51:85:cb",
_connectionid => bless(Symbol::gensym(), "IO::Socket::INET"),
_func => sub { "???" },
_isQuery => 0,
_langoverride => undef,
_needClient => 1,
_params => {
# tied Tie::IxHash
_fadein => undef,
_newvalue => undef,
_suppressShowBriefly =>
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) KeBul wrote: > In this instance maybe slightly different, although I've not tested > thoroughly with Stop, in my case, on the 29th Nov nightly, so far > _every_ pause from default WebUI, Material, iPeng or jive fails to > properly stop the alarm. > > > Exactly, and that completely unpredictable behaviour is what is making > it so difficult to test and resolve. > > KevIt would be nice to get consistent behaviour with pause and stop but like Michael says most times the alarm will be cancelled on the device. I just tried pausing an alarm from the default skin and heard a snippet of the fallback alarm as the clock reached 10:21 followed by a full fallback alarm at 10:22. That matches your description in an earlier post today. Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) mherger wrote: > > I'd rate the "don't miss an alarm" much more important than pausing an > alarm from another device. As I would assume most people using an alarm > > a.) are using it on a Radio and b.) would use the device's UI to end an > > alarm. So overall we got an improvement over 8.3.0? Absolutely, on the 29th Nov nightly I'm certain I've not seen a fail to trigger in several days of testing - must be getting on for over 60 successful alarms now. If stopping the alarm needs to be done remotely - powering off the player still works fine. Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) slartibartfast wrote: > In my system pressing "Stop" in Material does cancel the alarm which it > never did before the latest changes so are we still seeing different > behaviour? > In this instance maybe slightly different, although I've not tested thoroughly with Stop, in my case, on the 29th Nov nightly, so far _every_ pause from default WebUI, Material, iPeng or jive fails to properly stop the alarm. slartibartfast wrote: > Having said that I tried cancelling the alarm this morning by pressing > "Stop" in Material and the alarm didn't cancel and the fallback alarm > sounded a little later. > Exactly, and that completely unpredictable behaviour is what is making it so difficult to test and resolve. Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) Does anyone actually have even a start of a clue why 'stop' is called directly after alarm is registered as its handler? It seems more reliable to stop that unwanted behavior rather than maintaining a list of exceptions to which calls should be processed. gordonb3's Profile: http://forums.slimdevices.com/member.php?userid=71050 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) slartibartfast wrote: > In my system pressing "Stop" in Material does cancel the alarm which it > never did before the latest changes so are we still seeing different > behaviour? > > Sent from my Pixel 3a using TapatalkHaving said that I tried cancelling the > alarm this morning by pressing "Stop" in Material and the alarm didn't cancel and the fallback alarm sounded a little later. Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) KeBul wrote: > > > At the moment I would say the change in code fixes or at least > drastically improves the problem where an alarm fails to trigger, but > completely breaks stopping the alarm with a pause or stop from a remote > controlling device. > > Kev In my system pressing "Stop" in Material does cancel the alarm which it never did before the latest changes so are we still seeing different behaviour? Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
At the moment I would say the change in code fixes or at least drastically improves the problem where an alarm fails to trigger, but completely breaks stopping the alarm with a pause or stop from a remote controlling device. Thank you very much for all the work you've done on this subject! This pretty much is the summary I wanted to ask for after seeing all the other postings (yours and those of the others involved here). I'd rate the "don't miss an alarm" much more important than pausing an alarm from another device. As I would assume most people using an alarm a.) are using it on a Radio and b.) would use the device's UI to end an alarm. So overall we got an improvement over 8.3.0? ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) mherger wrote: > > So it looks like the behaviour of pressing pause from a remote > control > > device has changed. > > But the change would be in 8.3.0, too? First of all apologies to anyone who read my previous response to this - I jumped the gun somewhat and the information in that post was not correct. The testing I'd done and results I had got very much made it look like the pause issue was purely due to the 'playerprefs" fix in the 29th Nov nightly, however, I'd forgotten it can take a while of playing around in Material to start producing failures and during more extensive testing looking at Slarti's "Stop" failures, I've reproduced the pause issue in the 21st Nov nightly as well. I've been back on 8.3.0 for a while and have just managed to get a pause failure to occur on that, so the answer to Michael's question above is yes such failure can occur in 8.3.0!! What was odd was it was failing every time with a remote device pause when I was testing the 29th Nov nightly this morning, but has been difficult to get it to fail this evening on the previous versions. However, I've just gone back to 8.3.1 29th Nov nightly - and straight away pause from a remote controller fails to shut of the alarm, so I feel there's definitely something about the 'playerprefs' fix that makes that failure more permanent - I'm pretty sure I've not seen it work, as stated in my testing report. At the moment I would say the change in code fixes or at least drastically improves the problem where an alarm fails to trigger, but completely breaks stopping the alarm with a pause or stop from a remote controlling device. Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the
results, please visit http://forums.slimdevices.com/showthread.php?t=116649
Question: On what player types does the alarm fail for you?
- Squeezebox Radio (official firmware 7.x)
- Squeezebox Radio (community firmware 8.x)
- Squeezebox Touch (official firmware 7.x)
- Squeezebox Touch (community firmware 8.x)
- SB Classic/Boom/Receiver/Transporter
- Other (eg. Raspberry Pi based)
I think Slarti's initial "Stop" problem is another bug;
The behaviour of the stop button has now changed with the 'playerprefs'
fix and is very similar to the "pause" failure in that the stop command
is issued with a playerprefs source:
_request => ["stop"],
_requeststr => "stop",
_results => {},
_source =>
"/09f6cf6e/slim/playerprefs/00:04:20:26:1d:b9|214||09f6cf6e|Mozilla/5.0
(Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like
Gecko) Version/16.1 Safari/605.1.15",
_status => 10,
and as per the 'playerprefs' fix is ignored
[22-11-30 20:40:52.8919] Slim::Utils::Alarm::_alarmEnd (1966) Ignoring
unwanted notification: playlist stop
So I reckon fix the 'pause' issue in the 'playerprefs' fix code and
you'll get his original stop issue back.
Attached is a logfile from a Stop in Material UI whilst alarm is playing
8.3.1 29th Nov nightly
Kev
+---+
|Filename: 831_playerprefs_fix_29Nov_stopfail.txt |
|Download: http://forums.slimdevices.com/attachment.php?attachmentid=39269|
+---+
KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883
View this thread: http://forums.slimdevices.com/showthread.php?t=116649
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the
results, please visit http://forums.slimdevices.com/showthread.php?t=116649
Question: On what player types does the alarm fail for you?
- Squeezebox Radio (official firmware 7.x)
- Squeezebox Radio (community firmware 8.x)
- Squeezebox Touch (official firmware 7.x)
- Squeezebox Touch (community firmware 8.x)
- SB Classic/Boom/Receiver/Transporter
- Other (eg. Raspberry Pi based)
mherger wrote:
> > So it looks like the behaviour of pressing pause from a remote
> control
> > device has changed.
>
> But the change would be in 8.3.0, too?
No this change for me is only apparent after the playerprefs code fix...
i.e. this elseif
Code:
elsif ($source && $source !~ m|^/[a-z0-9]+/slim/request| && $source =~
m|^/[a-z0-9]+/slim/\w+/(?:[0-9a-f]+:){5}[0-9a-f]+|i) {
warn Data::Dump::dump($request, 'Alarm: ignored event');
main::DEBUGLOG && $isDebug && $log->debug('Ignoring notification to
subscriber');
return;
If I put the original Alarm.pm from Nov 21 nightly in then pause in
WebUI pauses the alarm and turns off player
If I roll back to 8.3.0 then pause in WebUI pauses the alarm and turns
off player
With 29th Nov nightly then pause in WebUI pauses the stream but leaves
the alarm "running" alarm screensaver is still on and then the fallback
alarm starts.
Attached are log files for the above 3 instances
I wasn't aware there could be a stop button added in Material, so
haven't tested behaviour with that under any version.
Kev
+---+
|Filename: 831_playerprefs_fix_29Nov_pausefail.txt |
|Download: http://forums.slimdevices.com/attachment.php?attachmentid=39268|
+---+
KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883
View this thread: http://forums.slimdevices.com/showthread.php?t=116649
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) didjean wrote: > You asked me to try this a week ago and it did cancel the alarm, I > couldnt get the fallback. So at least the behaviour was already like > this on 8.3.1 before the Alarm fix was appliedDid you try pausing the alarm. > I get the fallback after 2 minutes now [emoji3] Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) didjean wrote: > You asked me to try this a week ago and it did cancel the alarm, I > couldnt get the fallback. So at least the behaviour was already like > this on 8.3.1 before the Alarm fix was appliedFor you but not for me. Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) slartibartfast wrote: > My tests were all on 8.3/8.4. > Before the latest changes, pressing Stop in Material Skin would leave > the alarm screen active and the fallback alarm would sound after 60 > seconds. > After the latest changes, pressing Stop in Material Skin cancels the > alarm. > I didn't try pressing pause in Material before the changes but now the > fallback alarm sounds after 120 seconds. > Bear in mind I didn't have the alarm issue before the changes. > > Sent from my Pixel 3a using Tapatalk You asked me to try this a week ago and it did cancel the alarm, I couldnt get the fallback. So at least the behaviour was already like this on 8.3.1 before the Alarm fix was applied Transporter, Touch, SB3, SB2, Duet, Booms, Radios, piCorePlayer --- iPeng & Material --- LMS Version: 8.3.1 - 1668787267 on Pi4 4GB - Max2Play --- Qobuz didjean's Profile: http://forums.slimdevices.com/member.php?userid=2900 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) mherger wrote: > > If I pause now then the alarm screen continues to be displayed but I > do > > not hear the fallback alarm after 60 seconds. If I stop playback with > > the optional Stop button then I get my clock screensaver and the alarm > > screen disappears. This is definitely different to previous behaviour > > and I wonder if the fallback alarm will fire if required. > > Could you please confirm behaviour in v8.3.0? I'd like to understand > whether this is a side-effect of the recent change to Alarm, or > something introduced in 8.3.0 (there was a change around pause/stop > behaviour).My tests were all on 8.3/8.4. Before the latest changes, pressing Stop in Material Skin would leave the alarm screen active and the fallback alarm would sound after 60 seconds. After the latest changes, pressing Stop in Material Skin cancels the alarm. I didn't try pressing pause in Material before the changes but now the fallback alarm sounds after 120 seconds. Bear in mind I didn't have the alarm issue before the changes. Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) I tested the fallback alarm by restarting the server after the alarm was triggered and it does sound after 60 seconds. Having decided the fallback alarm should sound if the playback is paused from Material skin I tried again and the fallback alarm did sound but after 120 seconds. Maybe this new behaviour is actually preferred, after all when I first tried stopping the alarm from Material I was surprised to hear the fallback alarm. Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
If I pause now then the alarm screen continues to be displayed but I do not hear the fallback alarm after 60 seconds. If I stop playback with the optional Stop button then I get my clock screensaver and the alarm screen disappears. This is definitely different to previous behaviour and I wonder if the fallback alarm will fire if required. Could you please confirm behaviour in v8.3.0? I'd like to understand whether this is a side-effect of the recent change to Alarm, or something introduced in 8.3.0 (there was a change around pause/stop behaviour). ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) KeBul wrote: > How do you stop playback? > > KevIf I pause now then the alarm screen continues to be displayed but I do not hear the fallback alarm after 60 seconds. If I stop playback with the optional Stop button then I get my clock screensaver and the alarm screen disappears. This is definitely different to previous behaviour and I wonder if the fallback alarm will fire if required. Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) KeBul wrote: > How do you stop playback? > > Kev You can enable this in Material skin interface settings. Transporter, Touch, SB3, SB2, Duet, Booms, Radios, piCorePlayer --- iPeng & Material --- LMS Version: 8.3.1 - 1668787267 on Pi4 4GB - Max2Play --- Qobuz didjean's Profile: http://forums.slimdevices.com/member.php?userid=2900 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) slartibartfast wrote: > Previously if I stopped playback in Material skin the fallback alarm > would sound after 60 seconds. I haven't tried with the new build. > > Sent from my Pixel 3a using Tapatalk How do you stop playback? Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) KeBul wrote: > Alarm paused/stopped player turned off, in my case back to clock > screensaver. > > Same as pressing pause on player itself during alarm. > > KevPreviously if I stopped playback in Material skin the fallback alarm would sound after 60 seconds. I haven't tried with the new build. Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) slartibartfast wrote: > What was the old behaviour after pressing pause? > > Sent from my Pixel 3a using Tapatalk Alarm paused/stopped player turned off, in my case back to clock screensaver. Same as pressing pause on player itself during alarm. Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) mherger wrote: > > So it looks like the behaviour of pressing pause from a remote > control > > device has changed. > > But the change would be in 8.3.0, too? Not sure, I'd have to roll back and re-test... only compared it to 8.2.1, bear with me. I'll retest under 8.3.0 Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) KeBul wrote: > :D > > Testing Michaels fix... ending alarms using various control methods... > > Leaving to alarm timeout setting - OK > > From Player (SB Radio) front panel > > > > - Snooze alarm menu on screensaver - OK, although surprised to see > it leave the now playing screen on the display during snooze period > (same on LMS 8.2.1) - Turn off alarm menu on screensaver - OK, turned off alarm/player - Pause - OK, turned off alarm/player - Select and play something else - cant be done on player front > panel (because of alarm screensaver?) - Player on/off button - OK, turned off alarm/player > > > > > > Standard Web UI > > > > - Pause - This paused play of stream but didnt stop alarm, player > remained on alarm screensaver, then got a very brief burst of > fallback alarm, then a very short while after went into fallback > alarm until timeout ended alarm - Repeatable. - Play something else - Changed to a local track which started to > play, but Alarm screensaver remained and debug didnt show end of > alarm, player turned off at end of timeout, so playing something > else doesnt stop the alarm. - power off - OK, turned off alarm/player > > > > > > MaterialSkin > > > > - pause - Same behaviour as default Web UI - play something else - same behaviour as default Web UI - power off - OK, turned off alarm/player > > > > > > ipeng > > > > - pause - Same behaviour as default Web UI - play something else - Same behaviour as default Web UI - power off - OK, turned off alarm/player > > > > > > Jive - Control alarm test device from another player (SB Touch) > > > > - pause - Same behaviour as default Web UI - play something else - Same behaviour as default Web UI - power off - OK, turned off alarm/player > > > > > > Ran same tests from Web UI LMS 8.2.1 > > > > - pause - OK, turned off alarm/player - play something else - Same behaviour as default Web UI - power off - OK, turned off alarm/player > > > > > > So it looks like the behaviour of pressing pause, whilst alarm is on, > from a remote control device has changed. > > Kev What was the old behaviour after pressing pause? Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
So it looks like the behaviour of pressing pause from a remote control device has changed. But the change would be in 8.3.0, too? ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) didjean wrote: > > Just installed and will report if any failure (or Covid) :D Testing Michaels fix... ending alarms using various control methods... Leaving to alarm timeout setting - OK >From Player (SB Radio) front panel - Snooze alarm menu on screensaver - OK, although surprised to see it leave the now playing screen on the display during snooze period (same on LMS 8.2.1) - Turn off alarm menu on screensaver - OK, turned off alarm/player - Pause - OK, turned off alarm/player - Select and play something else - cant be done on player front panel (because of alarm screensaver?) - Player on/off button - OK, turned off alarm/player Standard Web UI - Pause - This paused play of stream but didnt stop alarm, player remained on alarm screensaver, then got a very brief burst of fallback alarm, then a very short while after went into fallback alarm until timeout ended alarm - Repeatable. - Play something else - Changed to a local track which started to play, but Alarm screensaver remained and debug didnt show end of alarm, player turned off at end of timeout, so playing something else doesnt stop the alarm. - power off - OK, turned off alarm/player MaterialSkin - pause - Same behaviour as default Web UI - play something else - same behaviour as default Web UI - power off - OK, turned off alarm/player ipeng - pause - Same behaviour as default Web UI - play something else - Same behaviour as default Web UI - power off - OK, turned off alarm/player Jive - Control alarm test device from another player (SB Touch) - pause - Same behaviour as default Web UI - play something else - Same behaviour as default Web UI - power off - OK, turned off alarm/player Ran same tests from Web UI LMS 8.2.1 - pause - OK, turned off alarm/player - play something else - Same behaviour as default Web UI - power off - OK, turned off alarm/player So it looks like the behaviour of pressing pause from a remote control device has changed. Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) mherger wrote: > > Thanks! You got my blessing :-D You're welcome. The only thing better would be a blessing from the Pope but I understand he's pretty busy this time of year. :cool: Sam SamY's Profile: http://forums.slimdevices.com/member.php?userid=63495 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) Wow indeed! Thanks! You are all amazing. I love this community. Just installed and will report if any failure (or Covid) Transporter, Touch, SB3, SB2, Duet, Booms, Radios, piCorePlayer --- iPeng & Material --- LMS Version: 8.3.1 - 1668787267 on Pi4 4GB - Max2Play --- Qobuz didjean's Profile: http://forums.slimdevices.com/member.php?userid=2900 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) mherger wrote: > New 8.3.1/8.4 builds should be available with this additional check on > the source. Thanks Michael, I've been testing this since late morning - 35 successful alarms triggered, no failures, plenty of debug reports of source = blahblah'playerprefs' so we are looking good on the fix for that specific cause of alarm failures. I've started some adhoc functional testing just to check the fix doesn't seem to have broken anything in alarm use - will continue that to completion tomorrow, had enough tonight - Mrs B has been kind enough to share her covid-19 infection and that has now won for the day, time hopefully for some sleep. Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) wow, thank you all, would be great if this fixes it. just updated, and now hoping I will wake up tomorrow morning. Wake up with music that is...instead of stressed out kids :) cheers Dennis cortegedusage's Profile: http://forums.slimdevices.com/member.php?userid=69028 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
New 8.3.1/8.4 builds should be available with this additional check on the source. ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
I actually think that the MAC address is included in the source string when the associated session is controlling a different device, i.e. In that case it would be a /slim/request - which is excluded explicitly. ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the
results, please visit http://forums.slimdevices.com/showthread.php?t=116649
Question: On what player types does the alarm fail for you?
- Squeezebox Radio (official firmware 7.x)
- Squeezebox Radio (community firmware 8.x)
- Squeezebox Touch (official firmware 7.x)
- Squeezebox Touch (community firmware 8.x)
- SB Classic/Boom/Receiver/Transporter
- Other (eg. Raspberry Pi based)
mherger wrote:
> Rather than just blocking player-refs notifications we should probably
> just ignore any player specific notification:
>
> >
Code:
> > diff --git a/Slim/Utils/Alarm.pm b/Slim/Utils/Alarm.pm
> index e6acade08..abf4be8a6 100644
> --- a/Slim/Utils/Alarm.pm
> +++ b/Slim/Utils/Alarm.pm
> @@ -1982,6 +1982,11 @@ sub _alarmEnd {
> main::DEBUGLOG && $isDebug && $log->debug('Ignoring self-created request');
> return;
> }
> + elsif ($source && $source !~ m|^/[a-z0-9]+/slim/request| && $source
=~ m|^/[a-z0-9]+/slim/\w+/(?:[0-9a-f]:){5}[0-9a-f]|i) {
> + warn Data::Dump::dump($request, 'Alarm: ignored event');
> + main::DEBUGLOG && $isDebug && $log->debug('Ignoring
notification to subscriber');
> + return;
> + }
> elsif ($source) {
> warn Data::Dump::dump($request, 'Alarm: fired event');
> $log->error("Unknown source: $source");
>
> >
>
> Would anybody be able to apply this and test? I think that (most)
> interactive actions taken by a user would be `/abc213/slim/request`,
> whereas notification come with a MAC address in the source element. As
> notifications already are in response to some action we should ignore
> them.
I actually think that the MAC address is included in the source string
when the associated session is controlling a different device, i.e.
other than itself. This regex might thus block legit actions to stop the
alarm from e.g. Controller.
Also not completely unimportant, `index()` is more CPU friendly than
regex, even if the latter is applied with fixed strings.
gordonb3's Profile: http://forums.slimdevices.com/member.php?userid=71050
View this thread: http://forums.slimdevices.com/showthread.php?t=116649
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
Okay. I've got it this time. No, REALLY!!! :o (I verified it with a regex testing utility.) The problem is missing quantifiers after the components of the MAC You're correct! Hopefully this post will redeem my technical credibility to at least a minor extent. In any case, the change should allow Michael's solution to function as intended. Thanks! You got my blessing :-D ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the
results, please visit http://forums.slimdevices.com/showthread.php?t=116649
Question: On what player types does the alarm fail for you?
- Squeezebox Radio (official firmware 7.x)
- Squeezebox Radio (community firmware 8.x)
- Squeezebox Touch (official firmware 7.x)
- Squeezebox Touch (community firmware 8.x)
- SB Classic/Boom/Receiver/Transporter
- Other (eg. Raspberry Pi based)
SamY wrote:
> I stand exposed... :D
Okay. I've got it this time. No, REALLY!!! :o
(I verified it with a regex testing utility.)
The problem is missing quantifiers after the components of the MAC
address so the solution is to change:
Code:
m|^/[a-z0-9]+/slim/\w+/(?:[0-9a-f]:){5}[0-9a-f]|
To:
Code:
m|^/[a-z0-9]+/slim/\w+/(?:[0-9a-f]+:){5}[0-9a-f]+|
Or, to be more strict:
Code:
m|^/[a-z0-9]+/slim/\w+/(?:[0-9a-f]{2}:){5}[0-9a-f]{2}|
Hopefully this post will redeem my technical credibility to at least a
minor extent. In any case, the change should allow Michael's solution to
function as intended.
Sam
SamY's Profile: http://forums.slimdevices.com/member.php?userid=63495
View this thread: http://forums.slimdevices.com/showthread.php?t=116649
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) Really interesting thread and thanks for tirelessly chasing the bug. This morning I had it again - faulty/non-triggered alarm with my 8.3.1 setup and the whole family overslept - the interesting thing about it, I hadn't touched the setup for the past few weeks and I hadn't adjusted the alarm either and it was reliable over this weeks. In my view, material was not really involved and the alarm was always acknowledged over the radios - anyway, I'm really happy that the issue has been recognized and will be fixed soon. Best regards and thank you so much! lms: 8.3.1 - 1667914563 on rpi4/ raspbian buster 10 points to musiclibrary on qnap ts212 (nfs) 1x duet - cntrl-fw: 8.0.1-r16907/ receiver-fw: 77 2x sb radio - fw: 8.0.1-r16907 1x squeezebox boom - fw 57 1x transporter - fw: 87 rpi 2b - pcp 8.0.1/ squeezelite v1.9.9-1391-pcp softsqueeze 3.9.2 on win 10 / squeezeplay 8.0.1r1343 on win 10 squeeze player 1.3.21 on s22/android 13.0.0 controller: android phone - squeezer 2.3.0/ material skin 3.0.1 MichaelPr's Profile: http://forums.slimdevices.com/member.php?userid=68465 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) Paul Webster wrote: > The trailing i is to indicate that the text matching should be > case-insensitive. I stand exposed... :D Sam SamY's Profile: http://forums.slimdevices.com/member.php?userid=63495 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) The trailing i is to indicate that the text matching should be case-insensitive. Paul Webster author of \"now playing\" plugins covering radio france (fip etc), planetradio (bauer - kiss, absolute, scala, jazzfm etc), kcrw, abc australia and cbc/radio-canada and, via the extra \"radio now playing\" plugin lots more - see https://forums.slimdevices.com/showthread.php?115201-announce-radio-now-playing-plugin Paul Webster's Profile: http://forums.slimdevices.com/member.php?userid=105 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the
results, please visit http://forums.slimdevices.com/showthread.php?t=116649
Question: On what player types does the alarm fail for you?
- Squeezebox Radio (official firmware 7.x)
- Squeezebox Radio (community firmware 8.x)
- Squeezebox Touch (official firmware 7.x)
- Squeezebox Touch (community firmware 8.x)
- SB Classic/Boom/Receiver/Transporter
- Other (eg. Raspberry Pi based)
SamY wrote:
> I suspect a typo in Michael's second regex, checking for a MAC address
> in the source but I don't see it offhand.
At the risk of exposing my limited knowledge of the intricacies of
regular expressions, I believe the problem could be the trailing 'i'
after the pattern in the last regex. I would replace:
Code:
m|^/[a-z0-9]+/slim/\w+/(?:[0-9a-f]:){5}[0-9a-f]|i
with:
Code:
m|^/[a-z0-9]+/slim/\w+/(?:[0-9a-f]:){5}[0-9a-f]|
i.e. No trailing 'i'
Sam
SamY's Profile: http://forums.slimdevices.com/member.php?userid=63495
View this thread: http://forums.slimdevices.com/showthread.php?t=116649
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) KeBul wrote: > Testing this change today, I'm still getting alarm failures, first a > sanity check... I suspect a typo in Michael's second regex, checking for a MAC ID in the source but I don't see it offhand. Sam SamY's Profile: http://forums.slimdevices.com/member.php?userid=63495 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the
results, please visit http://forums.slimdevices.com/showthread.php?t=116649
Question: On what player types does the alarm fail for you?
- Squeezebox Radio (official firmware 7.x)
- Squeezebox Radio (community firmware 8.x)
- Squeezebox Touch (official firmware 7.x)
- Squeezebox Touch (community firmware 8.x)
- SB Classic/Boom/Receiver/Transporter
- Other (eg. Raspberry Pi based)
gordonb3 wrote:
> If you could I would appreciate you verifying the patch for the LMS side
> I posted earlier (with the 'bad' MaterialSkin). Obviously it is good
> when the current issue gets solved from whatever side but I think the
> objective should be to stop this forever rather than rely on Craig
> fixing it all.
I tested this last night and it seemed to work...
Code:
# Don't respond to requests that we created ourselves
my $source = $request->source;
if ($source && (($source eq 'ALARM') || ($source eq
'PLUGIN_RANDOMPLAY') || (index($source,'playerprefs') != -1))) {
warn Data::Dump::dump($request, 'Alarm: ignored event');
main::DEBUGLOG && $isDebug && $log->debug('Ignoring
self-created request');
return;
}
elsif ($source) {
warn Data::Dump::dump($request, 'Alarm: fired event');
$log->error("Unknown source: $source");
}
Here's my test actions/results log:
21:25 - Alarm OK - timeout to end, log file shows source=ALARM
21:40 - Alarm OK - timeout to end, log file shows source=ALARM
Opened Material MacOS/Safari, swapped players from BB to SR2 and then to
Lounge - left monitoring Lounge
21:55 - Alarm OK - timeout to end, log file shows
source=blahblah'playerprefs
22:10 - Alarm OK - Turned of Material player dropdown, log file shows
source=ALARM
22:30 - Alarm OK - timeout to end, log file shows
source=blahblahplayerprefs
22:40 - Alarm OK - timeout to end, log file shows source=ALARM, changed
to SR2 and then back to Lounge in Material
22:50 - Alarm OK - timeout to end, log file shows
source=blahblahplayerprefs, changed to SR2 and then back to Lounge in
Material
23:00 - Alarm OK - timeout to end, log file shows
source=blahblahplayerprefs
Here's a debug extract from 21:55 alarm which showed a source of
'playerprefs' but the Alarm still worked:
[22-11-26 21:55:00.0011] Slim::Utils::Alarm::sound (516) Alarm triggered
for Spare Radio 2
[22-11-26 21:55:00.0020] Slim::Utils::Alarm::sound (560) Sounding alarm
[22-11-26 21:55:00.0045] Slim::Utils::Alarm::sound (589) Current Power
State: Off
[22-11-26 21:55:00.0091] Slim::Utils::Alarm::pushAlarmScreensaver (1839)
Attempting to push into alarm screensaver: . Current mode: INPUT.List
[22-11-26 21:55:00.0100] Slim::Utils::Alarm::sound (609) Current vol: 18
Alarm vol: 18
[22-11-26 21:55:00.0109] Slim::Utils::Alarm::sound (622) Alarm playlist
shufflemode: 0
[22-11-26 21:55:00.0124] Slim::Utils::Alarm::sound (628) Alarm playlist
url: sounds://_LIVE_bbc_radio_two
[22-11-26 21:55:00.0317] Slim::Utils::Alarm::_setAlarmSubscription
(1204) Adding alarm subscription
[22-11-26 21:55:00.0329] Slim::Utils::Alarm::sound (697) Scheduling time
out in 300 seconds
[22-11-26 21:55:00.0338] Slim::Utils::Alarm::_startStopTimeCheck (1880)
0 scheduled alarm(s)
[22-11-26 21:55:00.0341] Slim::Utils::Alarm::_startStopTimeCheck (1889)
Stopping time checker task
[22-11-26 21:55:00.0348] Slim::Utils::Alarm::scheduleNext (1391) Asked
to schedule next alarm for Spare Radio 2
[22-11-26 21:55:00.0353] Slim::Utils::Alarm::findNextTime (461)
Potential next time found: 14:0:0 27/11/2022
[22-11-26 21:55:00.0356] Slim::Utils::Alarm::findNextTime (466) Last
alarm due: 21:55:0 26/11/2022
~KeBul - removed lots of findNextTime entries~
[22-11-26 21:55:00.0680] Slim::Utils::Alarm::findNextTime (461)
Potential next time found: 16:15:0 27/11/2022
[22-11-26 21:55:00.0684] Slim::Utils::Alarm::findNextTime (466) Last
alarm due: 21:55:0 26/11/2022
[22-11-26 21:55:00.0688] Slim::Utils::Alarm::scheduleNext (1424) Next
alarm is at 22:10:0 26/11/2022
[22-11-26 21:55:00.0692] Slim::Utils::Alarm::scheduleNext (1435)
Scheduling alarm
[22-11-26 21:55:00.0696] Slim::Utils::Alarm::_startStopTimeCheck (1880)
1 scheduled alarm(s)
[22-11-26 21:55:00.0700] Slim::Utils::Alarm::_startStopTimeCheck (1884)
Starting time checker task
[22-11-26 21:55:00.0785] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd
called with request: stop
[22-11-26 21:55:00.0805] Slim::Utils::Misc::msg (1325) Warning:
[21:55:00.0800] (
bless({
_cb_args => undef,
_cb_enable=> 1,
_cb_func => undef,
_clientid => "00:04:20:26:1d:b9",
_func => sub { "???" },
_isQuery => 0,
_langoverride =>
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the
results, please visit http://forums.slimdevices.com/showthread.php?t=116649
Question: On what player types does the alarm fail for you?
- Squeezebox Radio (official firmware 7.x)
- Squeezebox Radio (community firmware 8.x)
- Squeezebox Touch (official firmware 7.x)
- Squeezebox Touch (community firmware 8.x)
- SB Classic/Boom/Receiver/Transporter
- Other (eg. Raspberry Pi based)
mherger wrote:
> Rather than just blocking player-refs notifications we should probably
> just ignore any player specific notification:
>
> >
Code:
> > diff --git a/Slim/Utils/Alarm.pm b/Slim/Utils/Alarm.pm
> index e6acade08..abf4be8a6 100644
> --- a/Slim/Utils/Alarm.pm
> +++ b/Slim/Utils/Alarm.pm
> @@ -1982,6 +1982,11 @@ sub _alarmEnd {
> main::DEBUGLOG && $isDebug && $log->debug('Ignoring self-created request');
> return;
> }
> + elsif ($source && $source !~ m|^/[a-z0-9]+/slim/request| && $source
=~ m|^/[a-z0-9]+/slim/\w+/(?:[0-9a-f]:){5}[0-9a-f]|i) {
> + warn Data::Dump::dump($request, 'Alarm: ignored event');
> + main::DEBUGLOG && $isDebug && $log->debug('Ignoring
notification to subscriber');
> + return;
> + }
> elsif ($source) {
> warn Data::Dump::dump($request, 'Alarm: fired event');
> $log->error("Unknown source: $source");
>
> >
>
> Would anybody be able to apply this and test? I think that (most)
> interactive actions taken by a user would be `/abc213/slim/request`,
> whereas notification come with a MAC address in the source element. As
> notifications already are in response to some action we should ignore
> them.
Testing this change today, I'm still getting alarm failures, first a
sanity check... here's the code changes I copied into
/usr/local/slimserver/Slim/Utils/Alarm.pm
39250
and here's a BBEdit differences between the original Alarm.pm (left) and
the modified Alarm.pm (right)
39251
Logfile extract of one of the failures:
[22-11-27 10:30:00.0016] Slim::Utils::Alarm::sound (516) Alarm triggered
for Spare Radio 2
[22-11-27 10:30:00.0025] Slim::Utils::Alarm::sound (560) Sounding alarm
[22-11-27 10:30:00.0054] Slim::Utils::Alarm::sound (589) Current Power
State: Off
[22-11-27 10:30:00.0105] Slim::Utils::Alarm::pushAlarmScreensaver (1839)
Attempting to push into alarm screensaver: . Current mode: INPUT.List
[22-11-27 10:30:00.0117] Slim::Utils::Alarm::sound (609) Current vol: 18
Alarm vol: 18
[22-11-27 10:30:00.0126] Slim::Utils::Alarm::sound (622) Alarm playlist
shufflemode: 0
[22-11-27 10:30:00.0143] Slim::Utils::Alarm::sound (628) Alarm playlist
url: sounds://_LIVE_bbc_radio_two
[22-11-27 10:30:00.0293] Slim::Utils::Alarm::_setAlarmSubscription
(1204) Adding alarm subscription
[22-11-27 10:30:00.0304] Slim::Utils::Alarm::sound (697) Scheduling time
out in 300 seconds
[22-11-27 10:30:00.0311] Slim::Utils::Alarm::_startStopTimeCheck (1880)
0 scheduled alarm(s)
[22-11-27 10:30:00.0316] Slim::Utils::Alarm::_startStopTimeCheck (1889)
Stopping time checker task
[22-11-27 10:30:00.0321] Slim::Utils::Alarm::scheduleNext (1391) Asked
to schedule next alarm for Spare Radio 2
[22-11-27 10:30:00.0326] Slim::Utils::Alarm::findNextTime (461)
Potential next time found: 18:0:0 27/11/2022
[22-11-27 10:30:00.0330] Slim::Utils::Alarm::findNextTime (466) Last
alarm due: 10:30:0 27/11/2022
~KeBul - removed lots of findNextTime entries~
[22-11-27 10:30:00.0708] Slim::Utils::Alarm::findNextTime (461)
Potential next time found: 9:45:0 28/11/2022
[22-11-27 10:30:00.0713] Slim::Utils::Alarm::findNextTime (466) Last
alarm due: 10:30:0 27/11/2022
[22-11-27 10:30:00.0717] Slim::Utils::Alarm::scheduleNext (1424) Next
alarm is at 10:45:0 27/11/2022
[22-11-27 10:30:00.0721] Slim::Utils::Alarm::scheduleNext (1435)
Scheduling alarm
[22-11-27 10:30:00.0725] Slim::Utils::Alarm::_startStopTimeCheck (1880)
1 scheduled alarm(s)
[22-11-27 10:30:00.0728] Slim::Utils::Alarm::_startStopTimeCheck (1884)
Starting time checker task
[22-11-27 10:30:00.0813] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd
called with request: stop
[22-11-27 10:30:00.0833] Slim::Utils::Misc::msg (1325) Warning:
[10:30:00.0828] (
bless({
_cb_args => undef,
_cb_enable=> 1,
_cb_func => undef,
_clientid => "00:04:20:26:1d:b9",
_func => sub { "???" },
_isQuery => 0,
_langoverride => undef,
_needClient => 1,
_params => {},
_request => ["stop"],
_requeststr => "stop",
_results => {},
_source =>
"/c6aad791/slim/playerprefs/00:04:20:26:1d:b9|20||c6aad791|Mozilla/5.0
(Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like
Gecko) Version/16.1 Safari/605.1.15",
_status => 10,
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) Alrighty, editing finished - back to testing. I've put gordonb3's fix from post #154 into Alarm.pm and am currently testing that. Michael's code from post #173 is in Alarm_MH.pm waiting in the wings for its turn to be tested. I'll report back Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) Paul Webster wrote: > That is the one - see the first line of mherger's "diff". Cheers Paul - was multi-tasking with cooking dinner, so didn't spot that. :o Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) KeBul wrote: > > /usr/local/slimserver/Slim/Utils > That is the one - see the first line of mherger's "diff". Paul Webster author of \"now playing\" plugins covering radio france (fip etc), planetradio (bauer - kiss, absolute, scala, jazzfm etc), kcrw, abc australia and cbc/radio-canada and, via the extra \"radio now playing\" plugin lots more - see https://forums.slimdevices.com/showthread.php?115201-announce-radio-now-playing-plugin Paul Webster's Profile: http://forums.slimdevices.com/member.php?userid=105 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) gordonb3 wrote: > If you could I would appreciate you verifying the patch for the LMS side > I posted earlier (with the 'bad' MaterialSkin). Obviously it is good > when the current issue gets solved from whatever side but I think the > objective should be to stop this forever rather than rely on Craig > fixing it all. Sorry Gordon (?), been testing all day - just got to this... mherger wrote: > Rather than just blocking player-refs notifications we should probably > just ignore any player specific notification: > > "code removed by KeBul" > > Would anybody be able to apply this and test? I think that (most) > interactive actions taken by a user would be `/abc213/slim/request`, > whereas notification come with a MAC address in the source element. As > notifications already are in response to some action we should ignore > them. Happy to do both of these, but just want to confirm how I've struggled to find Alarm.pm in my LMS install, but have now found one in: /usr/local/slimserver/Slim/Utils But a search is also showing Alarm.pm in other places are these all the same file? is it just a case of editing your changes into that file? I'm using pCP with LMS installed and Filezilla to view/search for the files. Cheers Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) Results of Michael's request for me to test under 8.2 is posted above... But prior to that first thing today on my 8.3 system I removed Craig's MaterialSkin vTest version and re-installed v3.0.1 standard release, then started testing again Here's my actions/results log for that series: More alarm testing Sat 26th Put released material back on system 9:30 - Alarm OK - timeout to end Opened Material, usual switch between players, started music on lounge and left monitoring 9:45 - Alarm OK - Turned off in Material from player drop down, left monitoring Lounge (i.e. didnt actually switch to SR2) 10:00 - Alarm OK - timeout to end, switched to player in Material, then back to Lounge 10:15 - Alarm fail - no screen pop, no fallback, source playerprefs/Safari 10:30 - Alarm fail - no screen pop, no fallback, source playerprefs/Safari 10:45 - Alarm fail - no screen pop, no fallback, source playerprefs/Safari Failures started on the 3rd Alarm after starting to use Material, unlike the previous two days of testing with no MaterialSkin and then MaterialSkin vTest which produced 69 successful alarms and no failures. I wanted to try prove my thoughts it could be MacOS/IOS/Safari specific, so I removed my Mac from the network, re-started LMS and continued to test using a Windows 8 machine with Chromium base MS Edge browser, here's my actions/results log for that: Restart LMS 11:00 - Alarm OK - timeout to end 11:15 - Alarm OK - timeout to end 11:30 - Alarm OK - timeout to end 11:45 - Alarm OK - timeout to end 12:00 - Alarm OK - Opened Material Win8 MS edge - selected SR2, then player pulldown power off, then select Lounge and play 12:15 - 12:30 - Alarm OK - Turned off in Material from player drop down, left monitoring Lounge (i.e. didnt actually switch to SR2) 12:45 - Alarm OK - timeout to end, switched to player in Material, then back to Lounge 13:00 - Alarm OK - timeout to end, switch to SR2 in M, in drop down turn player on/off, went back to Lounge 13:15 - Alarm OK - Turned off in Material from player drop down, left monitoring Lounge (i.e. didnt actually switch to SR2) 13:30 - Alarm OK - timeout to end, switched to player in Material, then back to Lounge 13:45 - Alarm triggered to Fallback, turned off on player front panel, on Material switch to SR2 and hit play to play stream - worked OK turned off SR2 from Material dropdown and change to monitoring Lounge BUT logfile showed a stop request from source playerprefs" 14:00 - Alarm triggered to Fallback, turned off on player in Material dropdown, logfile showed a stop request from source playerprefs. Closed Material web browser. 14:15 - Alarm fail - source playerprefs/MSEdge So that's that sorted, definitely not OS/Browser specific. Cheers Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) mherger wrote: > > Thank you very much for all your effort! If I may ask for another favor: > > would 8.2 really not be impacted by this issue? Can you confirm this > with the added log line somebody suggested? Honestly it's a pleasure to be able to help. So thinking about how I've managed to reproduce the issue under 8.3 has made me realise that any claim of it not happening on 8.2 is potentially false because my day to day use of my 8.2 system is nothing like the 8.3 system... mainly because most my players are now on the 8.3 system - it's only the 2 bedroom players that remained on 8.2... and these are very rarely controlled by Material. Late this afternoon I set up my test player (Spare Radio 2 or SR2) on the 8.2.1 system, Version of material is 3.0.1 same as on the 8.3 system. SB Radio "Back Bedroom" replaces the Lounge player as the in use player that I go back to in Material. Same alarm setup every 15 minutes to play for 5 minutes (timeout). LMS had been restarted earlier this morning when I'd updated MaterialSkin, the system had been unused since so took that as a decent fresh start. I let the test run through 4 successful alarms starting at 15:45 - then opened Material and did the usual stuff... here's my test actions/results log... Moved SR2 to LMS 8.2.1 system Added 15 minute alarms till 10:30pm tonight using default Web UI 15:45 - Alarm OK - timeout to end 16:00 - Alarm OK - timeout to end 16:15 - Alarm OK - timeout to end 16:30 - Alarm OK - timeout to end Start Material, v3.0.1 (same as LMS 8.3 system) MacOS/Safari 16 Select SR2 from drop down, then select Back Bedroom which is playing a long playlist 16:45 - Alarm fail, no stream no fallback alarm 17:00 - Alarm fail, no stream no fallback alarm 17:15 - Alarm fail, no stream no fallback alarm 17:30 - Alarm fail, no stream no fallback alarm 17:45 - Alarm OK - timeout to end So there you have it, as gordonb3 has found it fails in 8.2 as well. Here's the failure log file - no extra debug stuff as per Michael's 21 Nov nightly of 8.3 as I have no idea how to add that code to 8.2.1 I've removed most of the lines of searching for next available alarm to make it more readable [22-11-26 16:45:00.0026] Slim::Utils::Alarm::sound (516) Alarm triggered for Spare Radio 2 [22-11-26 16:45:00.0033] Slim::Utils::Alarm::sound (560) Sounding alarm [22-11-26 16:45:00.0053] Slim::Utils::Alarm::sound (589) Current Power State: Off [22-11-26 16:45:00.0092] Slim::Utils::Alarm::pushAlarmScreensaver (1839) Attempting to push into alarm screensaver: . Current mode: INPUT.List [22-11-26 16:45:00.0100] Slim::Utils::Alarm::sound (609) Current vol: 18 Alarm vol: 18 [22-11-26 16:45:00.0106] Slim::Utils::Alarm::sound (622) Alarm playlist shufflemode: 0 [22-11-26 16:45:00.0119] Slim::Utils::Alarm::sound (628) Alarm playlist url: sounds://_LIVE_bbc_radio_two [22-11-26 16:45:00.0250] Slim::Utils::Alarm::_setAlarmSubscription (1204) Adding alarm subscription [22-11-26 16:45:00.0257] Slim::Utils::Alarm::sound (697) Scheduling time out in 300 seconds [22-11-26 16:45:00.0262] Slim::Utils::Alarm::_startStopTimeCheck (1880) 1 scheduled alarm(s) [22-11-26 16:45:00.0264] Slim::Utils::Alarm::scheduleNext (1391) Asked to schedule next alarm for Spare Radio 2 [22-11-26 16:45:00.0407] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 16:45:0 26/11/2022 [22-11-26 16:45:00.0409] Slim::Utils::Alarm::scheduleNext (1424) Next alarm is at 17:0:0 26/11/2022 [22-11-26 16:45:00.0411] Slim::Utils::Alarm::scheduleNext (1435) Scheduling alarm [22-11-26 16:45:00.0414] Slim::Utils::Alarm::_startStopTimeCheck (1880) 2 scheduled alarm(s) [22-11-26 16:45:00.0469] Slim::Control::Request::renderAsArray (2233) Error: request should set useIxHashes in Slim::Control::Request->new() [22-11-26 16:45:00.0473] Slim::Control::Request::renderAsArray (2233) Backtrace: frame 0: Slim::Utils::Log::logBacktrace (/usr/local/slimserver/Slim/Control/Request.pm line 2233) frame 1: Slim::Control::Request::renderAsArray (/usr/local/slimserver/Slim/Web/Cometd.pm line 940) frame 2: Slim::Web::Cometd::requestCallback (/usr/local/slimserver/Slim/Web/Cometd.pm line 791) frame 3: Slim::Web::Cometd::__ANON__ (/usr/local/slimserver/Slim/Control/Request.pm line 2058) frame 4: (eval) (/usr/local/slimserver/Slim/Control/Request.pm line 2058) frame
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the
results, please visit http://forums.slimdevices.com/showthread.php?t=116649
Question: On what player types does the alarm fail for you?
- Squeezebox Radio (official firmware 7.x)
- Squeezebox Radio (community firmware 8.x)
- Squeezebox Touch (official firmware 7.x)
- Squeezebox Touch (community firmware 8.x)
- SB Classic/Boom/Receiver/Transporter
- Other (eg. Raspberry Pi based)
Rather than just blocking player-refs notifications we should probably
just ignore any player specific notification:
Code:
diff --git a/Slim/Utils/Alarm.pm b/Slim/Utils/Alarm.pm
index e6acade08..abf4be8a6 100644
--- a/Slim/Utils/Alarm.pm
+++ b/Slim/Utils/Alarm.pm
@@ -1982,6 +1982,11 @@ sub _alarmEnd {
main::DEBUGLOG && $isDebug && $log->debug('Ignoring self-created request');
return;
}
+ elsif ($source && $source !~ m|^/[a-z0-9]+/slim/request| && $source
=~ m|^/[a-z0-9]+/slim/\w+/(?:[0-9a-f]:){5}[0-9a-f]|i) {
+ warn Data::Dump::dump($request, 'Alarm: ignored event');
+ main::DEBUGLOG && $isDebug && $log->debug('Ignoring
notification to subscriber');
+ return;
+ }
elsif ($source) {
warn Data::Dump::dump($request, 'Alarm: fired event');
$log->error("Unknown source: $source");
Would anybody be able to apply this and test? I think that (most)
interactive actions taken by a user would be `/abc213/slim/request`,
whereas notification come with a MAC address in the source element. As
notifications already are in response to some action we should ignore
them.
Michael
"It doesn't work - what shall I do?" - "Please check your server.log
and/or scanner.log file!"
(LMS: Settings/Information)
mherger's Profile: http://forums.slimdevices.com/member.php?userid=50
View this thread: http://forums.slimdevices.com/showthread.php?t=116649
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) KeBul wrote: > Another day of alarms... no changes to the set up, just alarms set every > 15 minutes and some use of MaterialSkin. > > 41 alarms, no failures, so looking like Craig's proposed tweak in > MaterialSkin has helped the situation. > > I don't think I can do any more with this current setup, depending how I > feel tomorrow I may go back to the released version of Material and see > if I can break it again and then try with a different OS/Browser. > > Kev If you could I would appreciate you verifying the patch for the LMS side I posted earlier (with the 'bad' MaterialSkin). Obviously it is good when the current issue gets solved from whatever side but I think the objective should be to stop this forever rather than rely on Craig fixing it all. gordonb3's Profile: http://forums.slimdevices.com/member.php?userid=71050 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
41 alarms, no failures, so looking like Craig's proposed tweak in MaterialSkin has helped the situation. I don't think I can do any more with this current setup, depending how I feel tomorrow I may go back to the released version of Material and see if I can break it again and then try with a different OS/Browser. Thank you very much for all your effort! If I may ask for another favor: would 8.2 really not be impacted by this issue? Can you confirm this with the added log line somebody suggested? ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) Another day of alarms... no changes to the set up, just alarms set every 15 minutes and some use of MaterialSkin. 41 alarms, no failures, so looking like Craig's proposed tweak in MaterialSkin has helped the situation. I don't think I can do any more with this current setup, depending how I feel tomorrow I may go back to the released version of Material and see if I can break it again and then try with a different OS/Browser. Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) I wasn't expecting to do much on this today with other plans afoot, but my wife tested positive for Covid-19 this morning so we are isolating at home. I decided to short cut my testing plans as well... I'd run almost a day without Material installed, 28 alarms triggered successfully during that period and no failures seen and as Craig had taken the time to produce a MaterialSkin-Test build without the "playprefs unsubscribe" I decided to drop that in and test that. So far it's looking good, MaterialSkin Test was installed just after 3pm and the first alarm scheduled for 3:15, 14 alarm triggers later still no failures and I've been adhoc testing all sorts of scenarios around use of Material, including many attempts at how I managed to get it to fail previously. Alarms are due to start again soon, I've gradually increased the alarms configured - I'm amazed, it's up to 33 now!! I'll carry on testing and then continue tomorrow - there's no guarantee because the failure is so unpredictable, but so far, including the run without Material installed, this must be the most alarms in sequence without a failure I've had since I started testing. I'll report back again tomorrow. Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) mherger wrote: > > Shows the Material client shutting down the alarm 99% of the time in > all > > 8.x versions. > Does it really _fail_ the alarm, or just log that one statement? Because > > we still believe this was a 8.3 only issue... mherger wrote: > > Do note that the SB devices themselves appear to use cometd as well > as > > indicated by this log snippet: > > But that's ok, isn't it? If you hit power off on the device then the > alarm is expected to stop. > > > So it isn't strictly necessary to be using Material, it may also be > e.g. > > The difference here is that the above is an interaction between the user > > and the system, whereas in the case of Material it's an automated > reaction to some state change (a subscription). See my reaction to Kev. In my view this is simply unfortunate timing of parallel developments and yes it does require a fairly specific environment so the majority of users will not be affected by the bug. As for the randomness like I mentioned earlier there does appear to be a time factor involved as well. Can't really pinpoint it, but yesterday I couldn't make the alarm fail until I subscribed to a third player in my Material session. The logs are also somewhat puzzling as for every alarm that is being triggered there is an _alarmEnd response but there is always only one, i.e. if the Material client pops up issuing this request 'ALARM' which is expected to show up there doesn't. I mentioned earlier that I suspected this to be a logging issue but in hindsight I think LMS may be blocking multiple prefsync requests issued simultaneously and only serving the one that is first in queue. This makes it plausible that you could never replicate this if you run LMS on a workstation class machine where LMS is likely to win that election every time. gordonb3's Profile: http://forums.slimdevices.com/member.php?userid=71050 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) KeBul wrote: > But are these cometd "playerprefs"?.. I can get various sources reported > rather than "ALARM", such as the player itself - pressing pause, > If I try and emulate what I was doing in Material By taking control of > the SB Radio under test from a Touch and then release control again I do > not see an unknown source with "playerprefs" reported by the alarm. > If I leave the Touch controlling the SB Radio and turn off the Radio > after the alarm has succeeded then I see a power request with source > reported as "Squeezeplay-fab4" > > All the failures I have seen have been with a Stop request and a source > including "Playerprefs" and Safari > I don't think it is specific to cometd. The ignore routine inside _alarmEnd is already there so there is a known bug (although the person that knows may have left Logitech a long time ago) with the state change that causes a response that shuts down the alarm. The only thing different here is that we are now seeing an external source accessing this bug and the ignore routine failing to block that auto created request. > > When you say occurrences - do you mean actual alarm failures but no > cometd shown as the source... > No, my aim was to see a failed alarm so what I meant here is that the alarm did in fact sound and the log showed that the attempt to stop it was successfully blocked by the ignore routine. gordonb3's Profile: http://forums.slimdevices.com/member.php?userid=71050 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
Do note that the SB devices themselves appear to use cometd as well as indicated by this log snippet: But that's ok, isn't it? If you hit power off on the device then the alarm is expected to stop. So it isn't strictly necessary to be using Material, it may also be e.g. The difference here is that the above is an interaction between the user and the system, whereas in the case of Material it's an automated reaction to some state change (a subscription). ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
Shows the Material client shutting down the alarm 99% of the time in all 8.x versions. Does it really _fail_ the alarm, or just log that one statement? Because we still believe this was a 8.3 only issue... ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) cpd73 wrote: > Can someone please try using the attached Material version? I've remove > the playerprefs "unsubscribe" > > 39220 Thanks Craig I've downloaded and will install it soon, just running a test with Material removed from the system at the moment, want to give that a day or so and then wanted to test with current released Material but with a non MacOS/IOS/Safari device/browser. gordonb3 wrote: > Do note that the SB devices themselves appear to use cometd as well as > indicated by this log snippet: > > Code: > > [22-11-22 17:01:44.4157] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: pause > [22-11-22 17:01:44.4178] Slim::Utils::Alarm::_alarmEnd (1980) stop requested by '/338b2cbb/slim/request|649||338b2cbb|SqueezePlay-baby/8.0.1-r16907 (armv5tejl)' > > > > > So it isn't strictly necessary to be using Material, it may also be > e.g. SB controller or (uncommon but possible) a player with a > graphical interface that is used to control a second player. Regarding > the comment about needing to remove the skin, as far as I'm aware the > skin itself doesn't do anything on its own. It merely allows a browser > to subscribe to notifications prompting it to perform certain actions > like displaying the active song name, volume level, or as turns out to > be happening here resync preferences. The whole point here is that you > must have an active client and it must have subscribed to > notifications concerning the player that is to play the alarm. If > there is no active client then there will be no response and > subsequently no request to resync preferences. > But are these cometd "playerprefs"?.. I can get various sources reported rather than "ALARM", such as the player itself - pressing pause, If I try and emulate what I was doing in Material By taking control of the SB Radio under test from a Touch and then release control again I do not see an unknown source with "playerprefs" reported by the alarm. If I leave the Touch controlling the SB Radio and turn off the Radio after the alarm has succeeded then I see a power request with source reported as "Squeezeplay-fab4" All the failures I have seen have been with a Stop request and a source including "Playerprefs" and Safari gordonb3 wrote: > > BTW the "fool proof" method I described did for some reason not work out > as fool proof for me today. I had several occurrences where no cometd > client intervened with the alarm and so it does seem pretty random. I'm > quite certain however that the fix posted above works, ugly as it is. When you say occurrences - do you mean actual alarm failures but no cometd shown as the source... Cheers Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) Can someone please try using the attached Material version? I've remove the playerprefs "unsubscribe" 39220 +---+ |Filename: lms-material-test.zip| |Download: http://forums.slimdevices.com/attachment.php?attachmentid=39220| +---+ *Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here. cpd73's Profile: http://forums.slimdevices.com/member.php?userid=66686 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) Do note that the SB devices themselves appear to use cometd as well as indicated by this log snippet: Code: [22-11-22 17:01:44.4157] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: pause [22-11-22 17:01:44.4178] Slim::Utils::Alarm::_alarmEnd (1980) stop requested by '/338b2cbb/slim/request|649||338b2cbb|SqueezePlay-baby/8.0.1-r16907 (armv5tejl)' So it isn't strictly necessary to be using Material, it may also be e.g. SB controller or (uncommon but possible) a player with a graphical interface that is used to control a second player. Regarding the comment about needing to remove the skin, as far as I'm aware the skin itself doesn't do anything on its own. It merely allows a browser to subscribe to notifications prompting it to perform certain actions like displaying the active song name, volume level, or as turns out to be happening here resync preferences. The whole point here is that you must have an active client and it must have subscribed to notifications concerning the player that is to play the alarm. If there is no active client then there will be response and subsequently no request to resync preferences. BTW the "fool proof" method I described did for some reason not work out as fool proof for me today. I had several occurrences where no cometd client intervened with the alarm and so it does seem pretty random. I'm quite certain that the fix posted above works, ugly as it is. gordonb3's Profile: http://forums.slimdevices.com/member.php?userid=71050 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) This is the most interesting forum thread I've followed in a long time. It reads like a mystery novel. Each day I come here to read the next chapter. Like Michael, though, my alarms have been working without fail for weeks now after a period where they were failing fairly often. I'm running with the new source debug change though and will post if I see anything unusual. Btw, I also am a Material Skin user and had just begun using it regularly when my alarm failures started showing up a few months ago. Sam SamY's Profile: http://forums.slimdevices.com/member.php?userid=63495 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
So despite Michaels feeling that the "playerprefs" source is a red herring, I'm still only seeing failures when such a source is presented, That could very well be true. But I do not always see failure when those calls are logged. I had a whole series of cases where the alarm worked as expected, despite the source being that "playerprefs" thing. This whole thing is crazy!! I fully agree :-). After having started this thread I've probably only seen one single failure. Despite using the alarm feature on a daily basis on multiple Radios... ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) slartibartfast wrote: > I followed your instructions in Firefox on Windows 10 and my Radio alarm > set for more than 10 minutes in the future still fired normally. I seem > to be immune to this issue [emoji3] > Interesting, the only logs, showing the "playerprefs" source, I can find here are from myself and didjean... but both using Apple devices and Safari web browser. Kev KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the
results, please visit http://forums.slimdevices.com/showthread.php?t=116649
Question: On what player types does the alarm fail for you?
- Squeezebox Radio (official firmware 7.x)
- Squeezebox Radio (community firmware 8.x)
- Squeezebox Touch (official firmware 7.x)
- Squeezebox Touch (community firmware 8.x)
- SB Classic/Boom/Receiver/Transporter
- Other (eg. Raspberry Pi based)
KeBul wrote:
> gordonb3 - thanks for all your efforts on this, I can't comment on
> specifics as most of it is way beyond me, spaghetti code fix is
> interesting though.
>
> This morning, I changed my alarm settings to run a sequence of alarms
> from 11:30, I used the default web UI and can categorically state I have
> not used Material, yesterday or today... But so far today both the 11:30
> and 11:45 alarms have failed in the usual way, no alarm screensaver pop
> and no stream or fallback sound.
>
> Logfile shows the usual:
>
> [22-11-23 11:30:00.0627] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd
> called with request: stop
> [22-11-23 11:30:00.0647] Slim::Utils::Misc::msg (1325) Warning:
> [11:30:00.0642] (
> bless({
> _cb_args => undef,
> _cb_enable=> 1,
> _cb_func => undef,
> _clientid => "00:04:20:26:1d:b9",
> _func => sub { "???" },
> _isQuery => 0,
> _langoverride => undef,
> _needClient => 1,
> _params => {},
> _request => ["stop"],
> _requeststr => "stop",
> _results => {},
> _source =>
> "/5e4ba0d7/slim/playerprefs/00:04:20:26:1d:b9|31||5e4ba0d7|Mozilla/5.0
> (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like
> Gecko) Version/16.1 Safari/605.1.15",
> _status => 10,
> _useixhash=> 0,
> }, "Slim::Control::Request"),
> "Alarm: fired event",
> ) at /usr/local/slimserver/Slim/Utils/Alarm.pm line 1986.
> [22-11-23 11:30:00.0653] Slim::Utils::Alarm::_alarmEnd (1987) Unknown
> source:
> /5e4ba0d7/slim/playerprefs/00:04:20:26:1d:b9|31||5e4ba0d7|Mozilla/5.0
> (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like
> Gecko) Version/16.1 Safari/605.1.15
> [22-11-23 11:30:00.0657] Slim::Utils::Alarm::_alarmEnd (1997) Stopping
> alarm
> [22-11-23 11:30:00.0670] Slim::Utils::Alarm::popAlarmScreensaver (1866)
> Attempting to pop alarm screensaver. Current mode: INPUT.List
> [22-11-23 11:30:01.0740] Slim::Utils::Alarm::__ANON__ (901) Restoring
> pre-alarm shuffle mode: 0
> [22-11-23 11:30:01.0750] Slim::Utils::Alarm::__ANON__ (905) Restoring
> pre-alarm power state: off
>
> So despite Michaels feeling that the "playerprefs" source is a red
> herring, I'm still only seeing failures when such a source is presented,
> in todays case though, no Material involvement only use of the default
> Web UI to change the alarm times, not player swapping either - the ui
> was on "spare Radio 2" when it opened (and still is) I clicked on
> Settings, then the player tab which had "Spare Radio 2" selected and
> changed the drop down to Alarm Clock.
>
> And now as I type with no further action taken the 12:00 alarm has
> successfully gone off...
>
> _source => "ALARM",
>
> I wonder what produced that brief period of "playerprefs" source
> (default web ui? ) and does it as Michael now believes make no
> difference.
>
> This whole thing is crazy!!
>
> Kev
You might have to remove the Material skin plugin before testing. Not
using is one thing, but it is still installed on your server isnt it?
Transporter, Touch, SB3, SB2, Duet, Booms, Radios, piCorePlayer ---
iPeng & Material --- LMS Version: 8.3.1 - 1668787267 on Pi4 4GB -
Max2Play --- Qobuz
didjean's Profile: http://forums.slimdevices.com/member.php?userid=2900
View this thread: http://forums.slimdevices.com/showthread.php?t=116649
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the
results, please visit http://forums.slimdevices.com/showthread.php?t=116649
Question: On what player types does the alarm fail for you?
- Squeezebox Radio (official firmware 7.x)
- Squeezebox Radio (community firmware 8.x)
- Squeezebox Touch (official firmware 7.x)
- Squeezebox Touch (community firmware 8.x)
- SB Classic/Boom/Receiver/Transporter
- Other (eg. Raspberry Pi based)
gordonb3 - thanks for all your efforts on this, I can't comment on
specifics as most of it is way beyond me, spaghetti code fix is
interesting though.
This morning, I changed my alarm settings to run a sequence of alarms
from 11:30, I used the default web UI and can categorically state I have
not used Material, yesterday or today... But so far today both the 11:30
and 11:45 alarms have failed in the usual way, no alarm screensaver pop
and no stream or fallback sound.
Logfile shows the usual:
[22-11-23 11:30:00.0627] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd
called with request: stop
[22-11-23 11:30:00.0647] Slim::Utils::Misc::msg (1325) Warning:
[11:30:00.0642] (
bless({
_cb_args => undef,
_cb_enable=> 1,
_cb_func => undef,
_clientid => "00:04:20:26:1d:b9",
_func => sub { "???" },
_isQuery => 0,
_langoverride => undef,
_needClient => 1,
_params => {},
_request => ["stop"],
_requeststr => "stop",
_results => {},
_source =>
"/5e4ba0d7/slim/playerprefs/00:04:20:26:1d:b9|31||5e4ba0d7|Mozilla/5.0
(Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like
Gecko) Version/16.1 Safari/605.1.15",
_status => 10,
_useixhash=> 0,
}, "Slim::Control::Request"),
"Alarm: fired event",
) at /usr/local/slimserver/Slim/Utils/Alarm.pm line 1986.
[22-11-23 11:30:00.0653] Slim::Utils::Alarm::_alarmEnd (1987) Unknown
source:
/5e4ba0d7/slim/playerprefs/00:04:20:26:1d:b9|31||5e4ba0d7|Mozilla/5.0
(Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like
Gecko) Version/16.1 Safari/605.1.15
[22-11-23 11:30:00.0657] Slim::Utils::Alarm::_alarmEnd (1997) Stopping
alarm
[22-11-23 11:30:00.0670] Slim::Utils::Alarm::popAlarmScreensaver (1866)
Attempting to pop alarm screensaver. Current mode: INPUT.List
[22-11-23 11:30:01.0740] Slim::Utils::Alarm::__ANON__ (901) Restoring
pre-alarm shuffle mode: 0
[22-11-23 11:30:01.0750] Slim::Utils::Alarm::__ANON__ (905) Restoring
pre-alarm power state: off
So despite Michaels feeling that the "playerprefs" source is a red
herring, I'm still only seeing failures when such a source is presented,
in todays case though, no Material involvement only use of the default
Web UI to change the alarm times, not player swapping either - the ui
was on "spare Radio 2" when it opened (and still is) I clicked on
Settings, then the player tab which had "Spare Radio 2" selected and
changed the drop down to Alarm Clock.
And now as I type with no further action taken the 12:00 alarm has
successfully gone off...
_source => "ALARM",
I wonder what produced that brief period of "playerprefs" source
(default web ui? ) and does it as Michael now believes make no
difference.
This whole thing is crazy!!
Kev
KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883
View this thread: http://forums.slimdevices.com/showthread.php?t=116649
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the
results, please visit http://forums.slimdevices.com/showthread.php?t=116649
Question: On what player types does the alarm fail for you?
- Squeezebox Radio (official firmware 7.x)
- Squeezebox Radio (community firmware 8.x)
- Squeezebox Touch (official firmware 7.x)
- Squeezebox Touch (community firmware 8.x)
- SB Classic/Boom/Receiver/Transporter
- Other (eg. Raspberry Pi based)
gordonb3 wrote:
> > >
- (if testing with older version) Apply patch to log the source of
> the alarmEnd call:
> >
Code:
> > diff -ru a/Slim/Utils/Alarm.pm b/Slim/Utils/Alarm.pm
> --- a/Slim/Utils/Alarm.pm2022-11-20 11:56:59.616851242 +0100
> +++ b/Slim/Utils/Alarm.pm2020-10-22 20:50:03.0 +0200
> @@ -1977,6 +1977,7 @@
>
> # Don't respond to requests that we created ourselves
> my $source = $request->source;
> +main::DEBUGLOG && $isDebug && $log->debug("stop requested by '$source'");
> if ($source && ($source eq 'ALARM' || $source eq 'PLUGIN_RANDOMPLAY')) {
> main::DEBUGLOG && $isDebug && $log->debug('Ignoring self-created
request');
> return;
> >
- Open a browser into Material and select the player on which you
> want to test the alarm
- go to the `settings - player` page and set the alarm 5 minutes (or
> more) away from current
> note: if you set the time say 2 minutes away the Alarm will usually
> fire correctly - made that mistake several times
- return to main page and select a different player
- keep Material open on that second player
> > >
>
> Shows the Material client shutting down the alarm 99% of the time in
> all 8.x versions. Have not been able to trace back further because I
> used a different installer back then and it would cost me several
> hours to run through all the involved compile actions.I followed your
> instructions in Firefox on Windows 10 and my Radio alarm
set for more than 10 minutes in the future still fired normally. I seem
to be immune to this issue [emoji3]
Sent from my Pixel 3a using Tapatalk
slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609
View this thread: http://forums.slimdevices.com/showthread.php?t=116649
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) Tested the above and it works: Code: [22-11-23 12:26:00.0034] Slim::Utils::Alarm::sound (516) Alarm triggered for Assurancetourix [22-11-23 12:26:00.0084] Slim::Utils::Alarm::sound (560) Sounding alarm [22-11-23 12:26:00.0177] Slim::Utils::Alarm::sound (589) Current Power State: Off [22-11-23 12:26:00.0309] Slim::Utils::Alarm::pushAlarmScreensaver (1839) Attempting to push into alarm screensaver: . Current mode: INPUT.List [22-11-23 12:26:00.0340] Slim::Utils::Alarm::sound (609) Current vol: 17 Alarm vol: 32 [22-11-23 12:26:00.0372] Slim::Utils::Alarm::sound (612) Changing volume from 17 to 32 [22-11-23 12:26:00.0445] Slim::Utils::Alarm::sound (622) Alarm playlist shufflemode: 0 [22-11-23 12:26:00.0487] Slim::Utils::Alarm::sound (628) Alarm playlist url: http://opml.radiotime.com/Tune.ashx?id=s124134=aac,ogg,mp3,wmpro,wma,wmvoice=16=88beeb0eb03dde47915d999c774f56c9 [22-11-23 12:26:00.1609] Slim::Utils::Alarm::_setAlarmSubscription (1204) Adding alarm subscription [22-11-23 12:26:00.1658] Slim::Utils::Alarm::sound (697) Scheduling time out in 3600 seconds [22-11-23 12:26:00.1695] Slim::Utils::Alarm::_startStopTimeCheck (1880) 1 scheduled alarm(s) [22-11-23 12:26:00.1725] Slim::Utils::Alarm::scheduleNext (1391) Asked to schedule next alarm for Assurancetourix [22-11-23 12:26:00.1757] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 6:30:0 24/11/2022 [22-11-23 12:26:00.1797] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 12:26:0 23/11/2022 [22-11-23 12:26:00.1827] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 12:26:0 23/11/2022 [22-11-23 12:26:00.1856] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 12:26:0 23/11/2022 [22-11-23 12:26:00.1882] Slim::Utils::Alarm::findNextTime (471) Skipping.. [22-11-23 12:26:00.1910] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 12:26:0 24/11/2022 [22-11-23 12:26:00.1938] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 12:26:0 23/11/2022 [22-11-23 12:26:00.1967] Slim::Utils::Alarm::scheduleNext (1424) Next alarm is at 6:30:0 24/11/2022 [22-11-23 12:26:00.1993] Slim::Utils::Alarm::scheduleNext (1435) Scheduling alarm [22-11-23 12:26:00.2023] Slim::Utils::Alarm::_startStopTimeCheck (1880) 2 scheduled alarm(s) [22-11-23 12:26:00.2212] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: stop [22-11-23 12:26:00.2240] Slim::Utils::Alarm::_alarmEnd (1980) stop requested by '/6edd4328/slim/playerprefs/00:04:20:12:34:56|467||6edd4328|Mozilla/5.0 (X11; Linux x86_64; rv:105.0) Gecko/20100101 Firefox/105.0' [22-11-23 12:26:00.2340] Slim::Utils::Alarm::_alarmEnd (1982) Ignoring self-created request [22-11-23 12:26:00.2450] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: power [22-11-23 12:26:00.2478] Slim::Utils::Alarm::_alarmEnd (1980) stop requested by '/6edd4328/slim/playerprefs/00:04:20:12:34:56|467||6edd4328|Mozilla/5.0 (X11; Linux x86_64; rv:105.0) Gecko/20100101 Firefox/105.0' [22-11-23 12:26:00.2504] Slim::Utils::Alarm::_alarmEnd (1982) Ignoring self-created request [22-11-23 12:26:42.7089] Slim::Utils::Alarm::_alarmEnd (1966) Ignoring unwanted notification: mode stop [22-11-23 12:26:42.7250] Slim::Utils::Alarm::_alarmEnd (1966) Ignoring unwanted notification: playlist stop [22-11-23 12:26:42.8223] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd called with request: pause [22-11-23 12:26:42.8264] Slim::Utils::Alarm::_alarmEnd (1980) stop requested by '/6edd4328/slim/playerprefs/00:04:20:12:34:56|467||6edd4328|Mozilla/5.0 (X11; Linux x86_64; rv:105.0) Gecko/20100101 Firefox/105.0' [22-11-23 12:26:42.8291] Slim::Utils::Alarm::_alarmEnd (1982) Ignoring self-created request [22-11-23 12:26:42.9313] Slim::Utils::Alarm::popAlarmScreensaver (1866) Attempting to pop alarm screensaver. Current mode: INPUT.List [22-11-23 12:26:43.9346] Slim::Utils::Alarm::__ANON__ (901) Restoring pre-alarm shuffle mode: 0 [22-11-23 12:26:43.9419] Slim::Utils::Alarm::__ANON__ (905) Restoring pre-alarm power state: off There does appear to be some race condition active though because the log does not show me switching off the alarm on the device itself at 12:26:42 but
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the
results, please visit http://forums.slimdevices.com/showthread.php?t=116649
Question: On what player types does the alarm fail for you?
- Squeezebox Radio (official firmware 7.x)
- Squeezebox Radio (community firmware 8.x)
- Squeezebox Touch (official firmware 7.x)
- Squeezebox Touch (community firmware 8.x)
- SB Classic/Boom/Receiver/Transporter
- Other (eg. Raspberry Pi based)
i.e. like so:
Code:
--- a/Slim/Utils/Alarm.pm 2020-10-22 20:50:03.0 +0200
+++ b/Slim/Utils/Alarm.pm 2022-11-23 10:42:16.695338858 +0100
@@ -1977,7 +1977,7 @@
# Don't respond to requests that we created ourselves
my $source = $request->source;
- if ($source && ($source eq 'ALARM' || $source eq 'PLUGIN_RANDOMPLAY')) {
+ if ($source && (($source eq 'ALARM') || ($source eq
'PLUGIN_RANDOMPLAY') || (index($source,'playerprefs') != -1))) {
main::DEBUGLOG && $isDebug && $log->debug('Ignoring
self-created request');
return;
}
gordonb3's Profile: http://forums.slimdevices.com/member.php?userid=71050
View this thread: http://forums.slimdevices.com/showthread.php?t=116649
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) Log: (dump entries removed) Code: [22-11-22 15:59:00.0158] Slim::Utils::Alarm::sound (516) Alarm triggered for Maestria [22-11-22 15:59:00.0256] Slim::Utils::Alarm::sound (560) Sounding alarm ... [22-11-22 15:59:00.3429] Slim::Control::Request::executeDone (1919) 0 [22-11-22 15:59:00.3472] Slim::Control::Request::__updateListenerSuperRE (2438) updated listener superRE: (?^:library|favorites|notification|changed|menustatus|client|rescan|playlist|prefset) [22-11-22 15:59:00.3533] Slim::Control::Request::unsubscribe (824) Request from: Slim::Utils::Alarm::_alarmEnd - (36 listeners) [22-11-22 15:59:00.3656] Slim::Utils::Alarm::_setAlarmSubscription (1204) Adding alarm subscription [22-11-22 15:59:00.3702] Slim::Control::Request::__updateListenerSuperRE (2438) updated listener superRE: (?^:stop|pause|library|prefset|playlist|power|rescan|client|changed|menustatus|notification|favorites) [22-11-22 15:59:00.3730] Slim::Control::Request::subscribe (800) Request from: Slim::Utils::Alarm::_alarmEnd - (37 listeners) [22-11-22 15:59:00.3826] Slim::Utils::Alarm::sound (697) Scheduling time out in 3600 seconds [22-11-22 15:59:00.3864] Slim::Utils::Alarm::_startStopTimeCheck (1880) 0 scheduled alarm(s) [22-11-22 15:59:00.3909] Slim::Utils::Alarm::_startStopTimeCheck (1889) Stopping time checker task [22-11-22 15:59:00.4026] Slim::Utils::Alarm::scheduleNext (1391) Asked to schedule next alarm for Maestria [22-11-22 15:59:00.4060] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 6:30:0 23/11/2022 [22-11-22 15:59:00.4158] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 15:59:0 22/11/2022 [22-11-22 15:59:00.4360] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 15:59:0 22/11/2022 [22-11-22 15:59:00.4388] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 15:59:0 22/11/2022 [22-11-22 15:59:00.4454] Slim::Utils::Alarm::findNextTime (471) Skipping.. [22-11-22 15:59:00.4482] Slim::Utils::Alarm::findNextTime (461) Potential next time found: 15:59:0 23/11/2022 [22-11-22 15:59:00.4656] Slim::Utils::Alarm::findNextTime (466) Last alarm due: 15:59:0 22/11/2022 [22-11-22 15:59:00.4684] Slim::Utils::Alarm::scheduleNext (1424) Next alarm is at 6:30:0 23/11/2022 [22-11-22 15:59:00.4711] Slim::Utils::Alarm::scheduleNext (1435) Scheduling alarm [22-11-22 15:59:00.4750] Slim::Utils::Alarm::_startStopTimeCheck (1880) 1 scheduled alarm(s) [22-11-22 15:59:00.4836] Slim::Utils::Alarm::_startStopTimeCheck (1884) Starting time checker task [22-11-22 15:59:00.4923] Slim::Control::Request::notifyFromArray (839) (alarm _cmd) [22-11-22 15:59:00.4960] Slim::Control::Request::notify (2011) Notifying randomplay [22-11-22 15:59:00.5315] Slim::Control::Request::notify (2011) Notifying alarm sound ... [22-11-22 15:59:00.6066] Slim::Control::Queries::statusQuery (3522) statusQuery() [22-11-22 15:59:00.6453] Slim::Control::Queries::statusQuery (3817) statusQuery(): setup non-zero player response [22-11-22 15:59:00.6814] Slim::Control::Request::dump (2337) Request: Query [00:04:20:12:34:56->status] from JSONRPC (Done) ... [22-11-22 15:59:00.8660] Slim::Control::Request::executeDone (1919) 0 [22-11-22 15:59:00.8798] Slim::Control::Request::notify (2011) Notifying stop [22-11-22 15:59:00.8920] Slim::Control::Request::notify (2049) Notifying Slim::Web::Cometd::__ANON__ of stop =~ [[]] [22-11-22 15:59:00.8950] Slim::Web::Cometd::requestCallback (935) requestCallback got results for /c205f7ee/slim/playerprefs/00:04:20:12:34:56 / 2006 [22-11-22 15:59:00.9114] Slim::Control::Request::renderAsArray (2231) Error: request should set useIxHashes in Slim::Control::Request->new() [22-11-22 15:59:00.9149] Slim::Control::Request::renderAsArray (2231) Backtrace: [22-11-22 15:59:00.9261] Slim::Control::Request::notify (2049) Notifying Slim::Web::Cometd::__ANON__ of stop =~ [[]] [22-11-22 15:59:00.9356] Slim::Web::Cometd::requestCallback (935) requestCallback got results for /c205f7ee/slim/playerprefs/00:04:20:12:34:56 / 1970 [22-11-22 15:59:00.9454] Slim::Control::Request::renderAsArray (2231) Error: request should set useIxHashes in Slim::Control::Request->new() [22-11-22 15:59:00.9555]
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the
results, please visit http://forums.slimdevices.com/showthread.php?t=116649
Question: On what player types does the alarm fail for you?
- Squeezebox Radio (official firmware 7.x)
- Squeezebox Radio (community firmware 8.x)
- Squeezebox Touch (official firmware 7.x)
- Squeezebox Touch (community firmware 8.x)
- SB Classic/Boom/Receiver/Transporter
- Other (eg. Raspberry Pi based)
- (if testing with older version) Apply patch to log the source of the
alarmEnd call:
Code:
diff -ru a/Slim/Utils/Alarm.pm b/Slim/Utils/Alarm.pm
--- a/Slim/Utils/Alarm.pm 2022-11-20 11:56:59.616851242 +0100
+++ b/Slim/Utils/Alarm.pm 2020-10-22 20:50:03.0 +0200
@@ -1977,6 +1977,7 @@
# Don't respond to requests that we created ourselves
my $source = $request->source;
+ main::DEBUGLOG && $isDebug && $log->debug("stop requested by
'$source'");
if ($source && ($source eq 'ALARM' || $source eq 'PLUGIN_RANDOMPLAY')) {
main::DEBUGLOG && $isDebug && $log->debug('Ignoring
self-created request');
return;
- Open a browser into Material and select the player on which you want
to test the alarm
- go to the `settings - player` page and set the alarm 5 minutes (or
more) away from current
note: if you set the time say 2 minutes away the Alarm will usually
fire correctly - made that mistake several times
- return to main page and select a different player
- keep Material open on that second player
Shows the Material client shutting down the alarm 99% of the time in all
8.x versions. Have not been able to trace back further because I used a
different installer back then and it would cost me several hours to run
through all the involved compile actions.
gordonb3's Profile: http://forums.slimdevices.com/member.php?userid=71050
View this thread: http://forums.slimdevices.com/showthread.php?t=116649
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
Need to note that I patched Alarm.pm in both 8.2.0 and 8.0.0 to report the source of the _alarmEnd signal. Using the scheme I reported earlier the logs show it is the Material client that shuts down the alarm. Thus Please note that I believe that message is a red hering: yesterday I've seen cases where there was that "wrong" source, but the alarm fired as expected. gordonb3 - could you please summarize for me the exact steps you take to reproduce the failure? Idiotproof, please? ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
Re: [SlimDevices: Beta] Alarm not working with 8.3?
A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) Need to note that I patched Alarm.pm in both 8.2.0 and 8.0.0 to report the source of the _alarmEnd signal. Using the scheme I reported earlier the logs show it is the Material client that shuts down the alarm. Thus the change that caused didn't happen in the LMS code but was in fact in the Material code. Of course the whole point is that LMS should not have permitted this to happen in the first place but as this has been dangling over our heads for quite a number of years solving it could take some time and may likely involve redesigning the whole alarm system from the ground up. gordonb3's Profile: http://forums.slimdevices.com/member.php?userid=71050 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 ___ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
