erland;527261 Wrote:
> No, if you can reproduce it I'd suggest that you register a bug at
> bugs.slimdevices.com with detailed information about:
> - What operating system and SBS version and firmware version you are
> using
> - Step by step instruction how to reproduce the problem
> - Which radi
steve0564;527202 Wrote:
> Another mistake / bug:
> Last weekend I switch on my radio. I search my prefered radiostation
> and the display shows that the station is playing. But I can't hear
> anything. Nothing!
> Sbs was running and the server was up, the indicator at the lower right
> corner sho
Another mistake / bug:
Last weekend I switch on my radio. I search my prefered radiostation
and the display shows that the station is playing. But I can't hear
anything. Nothing!
Sbs was running and the server was up, the indicator at the lower right
corner shows a white connection to the server.
PeteCress;526490 Wrote:
>
> That's kind of a relief bc it would seem to imply that if LogiTech
> pulls the plug, my device will still work. Or am I just wishing?
>
Nope, you're correct. We'd lose mysb.com, but you could still run your
SB's from local version of SbS and play all your own musi
flattermann;526476 Wrote:
> Your players should show up on the status page of your SBS:
> http://your_whs_server:9000/settings/server/status.html
That seems to nail it then: I am *not* hooking into mysqueezebox.com.
That's kind of a relief bc it would seem to imply that if LogiTech
pulls the pl
PeteCress;526474 Wrote:
> I have Squeeze box's "Windows Home Server" version installed on my WHS
> box.
>
> Under C:\Program Files\Squeezebox, there is a "server" directory.
>
> MyComputer | Manage | Services and Applications | Services shows a
> service called "Squeezebox Server" running.
>
>
eap;526374 Wrote:
> Are you using a local squeezebox server -- or only mysqueezebox.com.
> Better to use local squeezeboxserver software running on your computer.
I have Squeeze box's "Windows Home Server" version installed on my WHS
box.
Under C:\Program Files\Squeezebox, there is a "server" d
Jake-here;526424 Wrote:
> Just wanted to add my two cents. I'm having a very similar issue.
>
> I'm using my own SB server and setting up the alarm using the buttons
> on the radio. I choose a playlist of my music that is on my server as
> the alarm sound. At the set time the alarm will go off
jmpage2;524897 Wrote:
> Continue to get backup alarm sound instead of my music playlist from SB
> Server 50% of the time on my SB Radio after update to 7.4.2 even after
> disabling nightly rebuild of my music libarary on my SB Radio.
Just wanted to add my two cents. I'm having a very similar iss
eap;526374 Wrote:
> Are you using a local squeezebox server -- or only mysqueezebox.com.
> Better to use local squeezeboxserver software running on your computer.
What nobody said was that "this little toy" really DOES need a 24/7
server working for it to operate as advertised. All I needed wa
PeteCress;526270 Wrote:
> I bought a Squeezebox for the wife after she asked me about a similar
> (but Pandora-centric) product she was interested in.
>
> On Day 1, THREE TIMES I explained to the wife "Here are the presets...
> just press "1" for WHYY, "3" for WRTI, "6" for a German station...
>
eap;519592 Wrote:
> Umm, there really is nothing "wrong" with the radio as is. Mine has
> worked without any glitches from day one. I use it as a bedside alarm
> clock. Never had an alarm not go off or any other alarm issues.
>
> Most people's glitches turn out to be user error, a misunders
erland;525985 Wrote:
> How do you configure the alarm ? On MySB.com web site or in the SBS web
> interface or directly on the Radio ?
> Do you only use MySB.com for alarms ?
> Do you only use your local SBS for alarms ?
Originally was using alarm set on the radio, but I sometimes turned it
off/c
korhojoa;525980 Wrote:
>
> First: alarm is no longer reliable.
>
How do you configure the alarm ? On MySB.com web site or in the SBS web
interface or directly on the Radio ?
Do you only use MySB.com for alarms ?
Do you only use your local SBS for alarms ?
--
erland
Erland Isaksson
'My homep
Urgh.
Just updated to 7.4.2 a few days ago.
Don't know why I did that, now it seems like a really bad idea.
I knew most of the bugs that I had with 7.4.1, and could work with
them, but this is now worse. :(
First: alarm is no longer reliable. On the earlier fw, it worked fine,
as long as my conne
bluegaspode;525897 Wrote:
> Don't know exactly, but I don't think it is respecting any timeout when
> in fallback-mode.
> ...
> Cannot be solved without a big overhaul (which I doubt will happen :( )
That's what I suspected. :( Hopefully they will spend some more
resources on it when the Touch i
Don't know exactly, but I don't think it is respecting any timeout when
in fallback-mode.
The problem is that from what I know there is now special 'timeout'
signal from the server, just a general 'hey there is a new alarm for
tomorrow, you can stop the current'.
Unfortunately this signal is als
bluegaspode;525887 Wrote:
>
> ...
> After that moment the Radio doesn't trust any signals from the server
> anymore until the user stops the backup alarm manually.
> ...
>
It does not even stop after the set timeout interval?
--
copperstate
--
peter.s;525870 Wrote:
> >erland;525746 Wrote:
> > >
> > > Does other people see the same thing, that normal alarm first plays
> and
> > > then switches to backup alarm after a while ? Or do you get the
> backup
> > > alarm immediately ?
>
> In the 'old' days of 7.4.1, the backup would also give
>erland;525746 Wrote:
> >
> > Does other people see the same thing, that normal alarm first plays and
> > then switches to backup alarm after a while ? Or do you get the backup
> > alarm immediately ?
The backup alarm jangle can be first to kick in at the scheduled
alarm time. But it can also, i
erland;525746 Wrote:
>
> Does other people see the same thing, that normal alarm first plays and
> then switches to backup alarm after a while ? Or do you get the backup
> alarm immediately ?
I think I saw that behavior once or twice, but I am not sure (wasn't
quite awake at that time). It does
jmpage2;525794 Wrote:
> That's an interesting find. Can you refresh my memory on enabling ssh
> access on the SBR? I will see if I can catch it in the act myself.
Settings > Advanced > Remote Login
--
aubuti
aubuti's Pr
That's an interesting find. Can you refresh my memory on enabling ssh
access on the SBR? I will see if I can catch it in the act myself.
I don't, however, believe my network is the cause of this. I have seen
the SB Radio go down and lose the wi-fi in 7.4.1 (but not in 7.4.2) even
when the netw
I think I managed to catch a log file when I got the backup alarm this
morning after the normal alarm had played for a while, registered a bug
report for it and included the /var/log/messages file:
https://bugs.slimdevices.com/show_bug.cgi?id=15904
>From the log it looks like there might have bee
Marc;525524 Wrote:
> Why don't you stop complaining about the purported shortcomings in my
> (unwisely discarded) code and instead go fix the problems in 7.4.2 (the
> way that I once did for 7.4.1)...?
Because from your writing it seems you are the only one who ever
understood all implications an
erland;525498 Wrote:
> Marc or bluegaspode, let's focus on the logging. We all know the
> history, there is no point arguing who is right and who is wrong.
>
> Marc, if I understand you correctly, we need some more logging to be
> able to track the problem ?
>
I haven't looked specifically at
bluegaspode;525510 Wrote:
> Why would I feel the need to defend 7.4.2. Every software (be it
> devoloped from you, me or logitech) will always have remaining bugs
> which need to be solved.
> And I keep my oppion. Claiming that the few unknown bugs from now
> wouldn't have happened with your code
> It would make sense for you to defend the now released 7.4.2 code,
> despite its continued instability, I suppose, since perhaps you feel the
> need to take some measure of responsibility for not being convinced of a
> number of the since discarded stability measures I lobbied for.
Why would I f
Marc;525469 Wrote:
>
> If the logs were there then that would be possible...
>
Marc or bluegaspode, let's focus on the logging. We all know the
history, there is no point arguing who is right and who is wrong.
Marc, if I understand you correctly, we need some more logging to be
able to track t
This recent discussion in this thread about the software development
process is enlightening. I feel very comfortable staying back at 7.3.3
with my Transporter, Booms and Duet indefinitely given the approach I
see. I believe that installing a later monolithic version will cause
more problems for m
I will attempt to set up the logging on the radio and collect them but
it will be this weekend at the earliest. I don't have a lot of time to
spend fixing Logitech screwups. :)
--
jmpage2
jmpage2's Profile: http://forums
bluegaspode;525448 Wrote:
> I think its not fair to claim your patch was the best of all and
> everything done later was to the worse.
> Your change was a BIG step towards a very good solution on the given
> architecture, but also with Bens additional changes to your patch we
> have a much more s
> The attempts I made to patch the existing architecture [...] would
> indeed have resulted in a more stable alarm situation for 7.4.2.
I think its not fair to claim your patch was the best of all and
everything done later was to the worse.
Your change was a BIG step towards a very good solution o
erland;525175 Wrote:
> Same thing has happened to me too a couple of times.
>
>
> Your efforts in the past are greatly appreciated, I can understand your
> frustration but I hope you change your mind.
>
> At the moment all Logitech resources are probably busy with the Touch
> release but afte
bluegaspode;525205 Wrote:
> Marc, don't grumble, that's not true.
> I'd say that 95% of your suggestions made it in the final code - and
> the last 5% either didn't look important or you were not able to make
> your point (when at least two people were listening) why some scenarios
> would fail w
Marc;525163 Wrote:
> I spent a great deal of time working toward the resolution of alarm
> problems in 7.4.1, unfortunately a good portion of my implementation
> suggestions were discarded.
Marc, don't grumble, that's not true.
I'd say that 95% of your suggestions made it in the final code - and
Marc;525163 Wrote:
> I also had a 7.4.2 alarm malfunction a couple of days ago. Backup alarm
> audio played even though the station selected for the alarm sound was
> working fine. I turned the alarm off and hit the play button then the
> station played fine. After that the alarm fired again (
jmpage2;524897 Wrote:
> Continue to get backup alarm sound instead of my music playlist from SB
> Server 50% of the time on my SB Radio after update to 7.4.2 even after
> disabling nightly rebuild of my music libarary on my SB Radio.
>
> Interestingly this did not happen on 7.4.1 so obviously so
Continue to get backup alarm sound instead of my music playlist from SB
Server 50% of the time on my SB Radio after update to 7.4.2 even after
disabling nightly rebuild of my music libarary on my SB Radio.
Interestingly this did not happen on 7.4.1 so obviously some "fix" for
alarm reliability ha
The situation improved a lot, but mainly due to the server changes two
weeks or so before the 7.4.2 update. Unfortunately, there are still some
issues with the alarm. E.g. as discussed before, there's a very high
chance that it stops without backup if the router reconnects during the
alarm.
Also m
so many users have posted to this thread already
may words to this is: I love my SBR and would not like to miss it any
more
I was totaly impressed from this streaming-concept right from the
beginning but the devices were much to expensive for me as a student
:-(
of course I also had my troubles w
Tut, tut, now, now, dearie. We mustn't be agist, must we?
--
mpower9
mpower9's Profile: http://forums.slimdevices.com/member.php?userid=33930
View this thread: http://forums.slimdevices.com/showthread.php?t=75541
mpower9;523881 Wrote:
> I bought the Squeezebox Radio to replace a 27 year old conventional
> clock radio that had become unreliable. I bought it with no real
> understanding of what it would do other than play audio streamed by
> radio stations and wake me up in the morning. Reviewers said it ha
I bought the Squeezebox Radio to replace a 27 year old conventional
clock radio that had become unreliable. I bought it with no real
understanding of what it would do other than play audio streamed by
radio stations and wake me up in the morning. Reviewers said it had a
nice sound for a bedside ra
I continue to have issues with my SB Radio not waking me up to the
selected playlist, but instead waking me up to the backup alarm sound.
This is actually more common now in 7.4.2 than it was in 7.4.1 (it
happened one time in 7.4.1 and it's happened over 20 times in 7.4.2).
I will turn off the n
Excellent post Davenva !
I think all your friends have mysqueezebox.com accounts possible more
than one ;)
But they don't now.
The setup wizard is very adamant in that respect it ask for email right
on the screen, I assume that a large quantity of new users do what you
do on some websites "john.
davenva;523261 Wrote:
> erland,
>
> The subject of "average users" is interesting, and certainly most
> relevant to the potential success of squeezebox as a product line.
>
> I agree that this forum attracts perhaps the most demanding users of
> the product. Today this group likely makes up a
I am a bit of a SB junkie/fan and technophile, so I don't consider my
own views representative, but your post does help a lot in bringing a
real-world perspective. I appreciated it a lot.
A company I used to work for had a very good slogan summing up the
aspiration I have for technology products,
erland;523172 Wrote:
>
> I think it's important to remember that what we see on these forums are
> users with problems, but we don't see is the other 95% who are very
> happy with the Radio.
>
> I'm not saying that we should ignore the 5% that have problems, I'm
> just saying that I strongly be
sander;523116 Wrote:
> It does seem to be the crux of the problem with squeezeplay. It's really
> the worst of both worlds. After years of stability at the ip3k level
> they forgot how much work had gone into it, and now 3 years into
> development they're still grappling with fundamental issues l
Phil Leigh;523070 Wrote:
> Erland - I hope they will learn from this. Now that "slim" has become
> "fuller figure", they really need to move on and take advantage of their
> fundamental paradigm shift. "One size fits all" just doesn't work...
It does seem to be the crux of the problem with squee
erland;522953 Wrote:
> I think the problem is that they wanted to use the same alarm logic for
> all Squeezebox devices, after all, the Boom should have the same alarm
> functionality as the Radio. A local alarm is fine on the Radio, Touch
> and Controller but it wouldn't work on Transporter, Boo
davenva;523034 Wrote:
> Phil Leigh
>
> Thanks for the reply.
>
> Good that we agree on poor alarm function design.
>
> I stand by my comments on the rest.
>
> The underfunded QA function supports my comment. Management should fix
> the funding issue.
>
> Citing Sony support is the old "We're
Phil Leigh
Thanks for the reply.
Good that we agree on poor alarm function design.
I stand by my comments on the rest.
The underfunded QA function supports my comment. Management should fix
the funding issue.
Citing Sony support is the old "We're bad, but so is someone else"
defense. The team
davenva;522893 Wrote:
> Just checked in after a long absence, to see if the alarm problems had
> been fixed. I was happy to discover this thread. Sounds like the
> answer is no.
I think this is not true.
A lot of work has been put into the task (though a bit too late), that
for whatever reason
Phil Leigh;522948 Wrote:
> This was the big mistake IMO. The Radio has a computer inside. All alarm
> functionality should have been in firmware with the basic ability to set
> alarms, snooze and beep all managed locally. Then it would have been
> isolated from wi-fi/server/internet issues and co
davenva;522893 Wrote:
> Hi,
>
> Some thoughts:
>
> - Why is the alarm clock function implemented as client-server,
> requiring a 7x24 computer to be running to signal an alarm? (Whether or
> not one should have a server running 7x24 is an irrelevant question - it
> shouldn't be required for an
Hi,
I'm the grumpy old guy who was an early complainer about the alarm
problems.(I believe that I made the original suggestion involving a $5
alarm clock and duct tape...)
Just checked in after a long absence, to see if the alarm problems had
been fixed. I was happy to discover this thread. So
Siduhe;522575 Wrote:
> Do you have an automatic clear and rescan set to run overnight or do you
> use iTunes or MIP autoupdating? I've had problems in the past with
> "current playlist" on alarms when the auto-rescan function has wiped the
> current playlist overnight.
I do have auto rescan goi
jmpage2;522563 Wrote:
> The problem I posted earlier in which the backup sounds instead of my
> regular alarm sound. It must be being caused by the playlist being set
> to "current".
Do you have an automatic clear and rescan set to run overnight or do
you use iTunes or MIP autoupdating? I've h
bluegaspode;522549 Wrote:
> Which one ?
The problem I posted earlier in which the backup sounds instead of my
regular alarm sound. It must be being caused by the playlist being set
to "current".
--
jmpage2
jmpage2's Pro
jmpage2;522546 Wrote:
> Mine had the exact same problem this morning.
Which one ?
--
bluegaspode
1x SB-Controller+Receiver (Duet), 1xSB-Boom. 1xSB-Radio
Server (7.4.1) running on SheevaPlug (Ubuntu) with attached Western
Digital MyBook Essential.
Secondary 7.4 Server on Debianized Buffalo Lin
Mine had the exact same problem this morning. I think it is being
caused by the alarm playlist being set to "current playlist".
I re-set it to a specific playlist and will see if it works correctly
tomorrow morning.
--
jmpage2
--
0xdeadbeef;522294 Wrote:
> The new firmware doesn't really fix all possible alarm issues. E.g. if
> my modem reconnects while the alarm is playing, there is a 50% chance
> that the (extremely loud) backup alarm is played at connection drop, but
> in the other 50%, the alarm just stops.
If you can
the changes in 7.4.2 were just to make the alarm reliable (meaning that
in case of any error you will hear the loud fallback alarm).
Any error means:
- the server was of (and didn't send the actual alarm signal)
- the network had problems
- your internet radio streams has problems.
Once you are in
0xdeadbeef;522294 Wrote:
> Reliability of the alarm got a little better, but mainly due to the
> server fixes some weeks ago. The new firmware doesn't really fix all
> possible alarm issues. E.g. if my modem reconnects while the alarm is
> playing, there is a 50% chance that the (extremely loud)
Reliability of the alarm got a little better, but mainly due to the
server fixes some weeks ago. The new firmware doesn't really fix all
possible alarm issues. E.g. if my modem reconnects while the alarm is
playing, there is a 50% chance that the (extremely loud) backup alarm is
played at connecti
Just wanted to provide an update with some weirdness I saw this morning
with my SB Radio after updating to 7.4.2.
1. Was listening to my own content (on 24/7 WHS box) last night.
2. Powered off the SB Radio after using iPeng to change my alarm time
to 7:00 AM.
3. This morning got a loud burst of
majones;521171 Wrote:
> I think it's very unfair that you people with Radios get a firmware
> update with 7.4.2, but those of us with Duets don't.
Do what I do -- I own a radio AND a duet. So I get the best of both
worlds.
--
eap
--
I keep thinking that MAJONES posts above are all missing the smiley
face.
--
garym
garym's Profile: http://forums.slimdevices.com/member.php?userid=17325
View this thread: http://forums.slimdevices.com/showthread.php?t=755
majones;521171 Wrote:
> I think it's very unfair that you people with Radios get a firmware
> update with 7.4.2, but those of us with Duets don't.
Why? The firmware update for the Radio is to fix specific issues with
that bit of hardware like the preset buttons not working and some
specific ala
I think it's very unfair that you people with Radios get a firmware
update with 7.4.2, but those of us with Duets don't.
--
majones
majones's Profile: http://forums.slimdevices.com/member.php?userid=13029
View this thread:
I meant this bug from you:
http://bugs.slimdevices.com/show_bug.cgi?id=14970
I'll added a link and will discuss the code there.
--
bluegaspode
1x SB-Controller+Receiver (Duet), 1xSB-Boom. 1xSB-Radio
Server (7.4.1) running on SheevaPlug (Ubuntu) with attached Western
Digital MyBook Essential.
S
bluegaspode;521049 Wrote:
> Where do you take the patch from ?
> The one from the bug report for changing alarm windows shouldn't work
> with all the changed code anymore or am I missing anything ?
>
It's not from the bug report, didn't realize there was one already so
I've made my own. Or are y
erland;521025 Wrote:
> If you use 7.5, you can use the "Patch Installer" applet in my testing
> repository to install the "Custom alarm window" patch
Where do you take the patch from ?
The one from the bug report for changing alarm windows shouldn't work
with all the changed code anymore or am I
tcutting;520188 Wrote:
> Maybe erland can figure something out - like allowing one of the custom
> clock screensavers to over-ride the alarm popup (he has a way to replace
> the "now playing" screen). I use the new button setup (volume knob/mute
> for "snooze"; "back" for "let alarm continue"; "
upgrade worked flawless for me.
--
fragfutter
fragfutter's Profile: http://forums.slimdevices.com/member.php?userid=35184
View this thread: http://forums.slimdevices.com/showthread.php?t=75541
eap;520568 Wrote:
> Wow. I guess I'm lucky. My firmware download AND install happened in
> about two minutes total time. No glitches whatsoever. It was a thing
> of beauty.
Same here. Apart from having to re-boot Radio to re-join my wireless
network it was a flawless upgrade from 7.4.1 to 7.4
mlsstl;520510 Wrote:
> I had the same issue last night. The Radio firmware download was very
> slow (about 20 minutes) and then stuck at 99%.
>
> Had to pull the power plug to reboot. The firmware downloaded much more
> quickly the second time (about 2 minutes) and then installed without a
> hi
> This bug was fixed, but only for 7.5.
It's probably fixed in 7.4.2 already: the issue was lack of memory. On Radio
there was a memory leak (which should be fixed now), on Touch there sometimes
were too many services running in the background (TinySBS, Samba). The latter
is fixed in 7.5 only.
If you don't want to risk it, don't try this- but I've been running 7.5
for a while now, and my Radio (as well as duet and touch) have been
solid as a rock for a few weeks now. And yes, I no longer have the
firmware upgrade bug- it was pretty annoying.
--
FredFredrickson
---
mlsstl;520510 Wrote:
> I had the same issue last night. The Radio firmware download was very
> slow (about 20 minutes) and then stuck at 99%.
>
https://bugs.slimdevices.com/show_bug.cgi?id=15522
This bug was fixed, but only for 7.5.
So this could happen again when you upgrade to 7.5 in the f
I'm not sure, so I'd have to look into this, but I've been running my
radio off the TINYSC in my touch- which means I power down my server
more often than not lately..
I haven't even considered if it supports alarms...
I will look tonight, unless somebody knows the answer to this..
--
FredFre
jmpage2;519977 Wrote:
> I just went ahead and downloaded and installed 7.4.2 on my WHS. Sure
> enough my radio was prompting me to update to 7.4.2 firmware.
>
> Started the 7.4.2 firmware download.
>
> An hour ago.
>
> It's stuck on 99% downloaded and not progressing now for 30 minutes.
> Ca
jmpage2;520308 Wrote:
> jump into a time machine and go back about 100 years
I'm a bit busy at work right now, but I'll give this a try at the
weekend.
--
majones
majones's Profile: http://forums.slimdevices.com/member.ph
majones;520292 Wrote:
> Me too. I subsequently bought two more Radios so I now have three. They
> work just fine. For some reason, I didn't decide to start a post on this
> forum with rude words in capitals.
Maybe it hadn't occurred to you that your experiences are not the same
as other users ex
jmpage2;519480 Wrote:
> I installed Squeezebox Server 7.4.1 in October right after getting my
> Squeezebox radio.
Me too. I subsequently bought two more Radios so I now have three. They
work just fine. For some reason, I didn't decide to start a post on this
forum with rude words in capitals.
-
tcutting;520188 Wrote:
> Maybe erland can figure something out - like allowing one of the custom
> clock screensavers to over-ride the alarm popup (he has a way to replace
> the "now playing" screen). I use the new button setup (volume knob/mute
> for "snooze"; "back" for "let alarm continue"; "
bluegaspode;520185 Wrote:
> I don't use the big button anymore with 7.4.2.
> You can hit the volume-button (will act as 'snooze') and the power
> button (will act as 'alarm off').
>
> These shortcuts are not documented though thats why there is still a
> menu :)
>
> As to the possebility for th
Maybe erland can figure something out - like allowing one of the custom
clock screensavers to over-ride the alarm popup (he has a way to replace
the "now playing" screen). I use the new button setup (volume knob/mute
for "snooze"; "back" for "let alarm continue"; "power" for "turn-off
alarm") so
I don't use the big button anymore with 7.4.2.
You can hit the volume-button (will act as 'snooze') and the power
button (will act as 'alarm off').
These shortcuts are not documented though thats why there is still a
menu :)
As to the possebility for third party dev to change the popup-UI:
Actua
jmpage2;519932 Wrote:
> You are continuing to miss the point. No one should need to leave a
> computer on 24X7 for an *alarm clock* to work reliably!
>
>
>
> We personally pay about .09 per kwh for electric and the rates have
> been going up at a faster level than inflation for the past 5 yea
tcutting;519980 Wrote:
> Go ahead and shut down (may have to remove power though)... it downloads
> first before it performs install.
> I've found this happens often on firmware upgrades - but, if you do
> full turn-off, then turn-on before performing upgrade it works fine.
I had this nonsense a
jmpage2;520111 Wrote:
> I thought the alarm default screen was being changed as well to make the
> time actually readable when the alarm is going off...
I wish. Amazing that such a small detail is one of my main annoyances.
There was some talk about allowing 3rd party apps to override the
defaul
Well the loud volume burst prior to alarm fade in is not fixed, guess I
have to wait for 7.5 for that problem.
I thought the alarm default screen was being changed as well to make
the time actually readable when the alarm is going off, but apparently
that's not the case either.
I can only hope t
Ron Olsen;520087 Wrote:
> The list you posted are changes/bug fixes in SqueezeBox Server. There
> are also firmware updates for the SqueezeBox Radio.
>
> As Andy G pointed out in another thread, the Radio release notes are
> here:
> http://wiki.slimdevices.com/index.php/SqueezePlay_7.4.2_Relea
eap;520001 Wrote:
> Where is a definitive and full list of all of the fixes for 7.4.2?
>
> I see this list, but there is not one word of alarms that everyone is
> talking about (so why is it assumed that there are bugfixes regarding
> alarms in this version):
>
> What am I missing?
As Andy G po
> So the radio is dependent on an external server "helping" the radio to
> function properly. Not to mention dependent on a connection to the
> Internet in your home.
You miss the point. Its not about having a server at all.
If you want a reliable (7.4.1) alarm its about if you are able to run a
1
jmpage2;520008 Wrote:
> The SB Radio only "requires" a server at all because of a foolish
> decision that Logitech made to handle this stuff all through My Squeeze
> or SB Server.
>
> I can assure you that having alarms handled completely on the SB Radio
> is totally doable if Logitech so choose
eap;519975 Wrote:
> It is also a radio. The internet radio does not function at all without
> a server somewhere (either in your own home or logitech's data center).
> So the radio is dependent on an external server "helping" the radio to
> function properly. Not to mention dependent on a conn
1 - 100 of 140 matches
Mail list logo
