Squeezebox Booms don´t not start alarm clocks

[duedeldu]

[22-11-07 07:08:44.6027] Slim::Plugin::Extensions::Plugin::_parseXML
(517) entry CustomClock does not match, bad target version [0.1.0
outside 7.4, *]

Hmm... is jivelite reporting a version 0.1.0?

[duedeldu]

Squeezebox Booms do not start alarm clocks

Since a few days i have a very strange behaviour regarding the alarm clock on my 3 SB Booms in my network.
The are some alarms set, one for my girlfriend, one for me.
Mosty we play some radio streams, or something from our local library to wake up.
Until now...
The alarm on every device i tried seems to start for half a second, and then stops, like it is switched off.
All my booms do that. I tried deleting alarms and recreating them, tested local music and radio streams, alarm sounds also.
All Booms were resetted to factory defaults.
Even a total new installation of my LMS (Community Edition on a Synology NAS as Docker container) did not help.
Has anyone a clue, what triggers this?
It has worked for 12 years, and since some days there is absolutely no chance to get the alarm clocks working on my Booms. On all my other SB devices (Radio/Touch), there is no problem.

[mherger]

=?utf-8?q?Squeezebox_Booms_don=EF=BF=BDt_not_?==?utf-8?q?start_alarm_clocks?=

> Since a few days i have a very strange behaviour regarding the alarm
> clock on my 3 SB Booms in my network.
> The are some alarms set, one for my girlfriend, one for me.
> Mosty we play some radio streams, or something from our local library to
> wake up.
> Until now...

Did you install to LMS 8.3 recently?

[duedeldu]

Geht auch auf deutsch. :-)
Läuft aktuell V8.3, ganz frisches Docker Image von gestern.

[mherger]

=?utf-8?q?Squeezebox_Booms_don=EF=BF=BDt_not_?==?utf-8?q?start_alarm_clocks?=

> Geht auch auf deutsch. :-)
> Läuft aktuell V8.3, ganz frisches Docker Image von gestern.

So was habe ich befürchtet :-(. Ich befürchte, wir haben tatsächlich ein
Weckerproblem in 8.3. Siehe
http://forums.slimdevices.com/showthread.php?t=116649. Allerdings habe
ich noch kein Muster erkennen können, wann das passiert. Ich kann es
nicht gewollt nachvollziehen. Es ist mir zwei, drei mal passiert. Doch
dann läuft der Wecker über Wochen wieder zuverlässig...

[duedeldu]

Morgen!
Exakt. Das Verhalten ist wie in dem von Dir beschriebenen Thread.
Ich dachte schon ich bin verrückt.

[duedeldu]

[22-11-07 07:08:44.6027] Slim::Plugin::Extensions::Plugin::_parseXML
(517) entry CustomClock does not match, bad target version [0.1.0
outside 7.4, *]

Hmm... is jivelite reporting a version 0.1.0?

Werd ich heute Abend checken.

[duedeldu]

Die von Dir genannte Fehlermeldung ist leider nicht im Log.
Das einzige was im Log steht, wenn einer der Wecker nicht spielt ist z.B. das hier (mehrere Beispiele):

[22-11-06 20:32:01.4340] Plugins::BookmarkHistory::Plugin::newsongCallback (1561) Trigger for newsong exists but is to old (to be expected when you press play after reconnect). client:Slim::Player::Boom=ARRAY(0x55a67f16b1f8) time: 1667763121 trigger value:1667746956 requestlaylist newsong url:http://opml.radiotime.com/Tune.ashx?...a37627bb33ee8d

[22-11-06 20:36:00.8262] Plugins::BookmarkHistory::Plugin::newsongCallback (1561) Trigger for newsong exists but is to old (to be expected when you press play after reconnect). client:Slim::Player::Boom=ARRAY(0x55a67ee0bc68) time: 1667763360 trigger value:1667746956 requestlaylist newsong url:loop://content.mysqueezebox.com/static/sounds/natural/lapping_waves.mp3

Es ist übrigens egal, ob man Webradiostreams, lokalen Content aus der eigenen Bibliothek oder Wecktöne abspielt.