w3wilkes wrote:
> A quick search finds this
> http://forums.slimdevices.com/showthread.php?107328-Dead-Controller=cradle
thank you, yes, I searched and found that thread The controllers are not
my problem, the charging cradle is. My question was specific to the
cradle. My other searched turned
ok, I now understand your point of forwarding the thread. I had read it
before, but I guess I was so focused on either a way of diagnosing the
power supply, or disassembling the cradle, that the fact that the poster
replaced the power supply was completely lost to me when I read it, and
again
I cut and spliced the cable, as you say, anywhere outside the base. Two
wires, soldered, shrink wrap over each solder joint and larger shrink
over the two shrinks. I'll look around and see which controller I fixed
and if I find it, I'll post a picture, although, not allot to see.
One thing, my
26686
nothing special - about 8" from base, but that won't matter unless a
wire is broken.. Like I said, check insure polarity, cut, solder, shrink
over each wire, then bigger shrink over both.
+---+
|Filename: splice.jpg
Interesting info, makes sense, with the receiver, controller, mysb,
links all dependent on stable WIFI, and ISP as well, there's allot to
break if things go bad. Good to know about bridge mode, but until we get
a direct connection, we are stuck with wifi.
I'll be going over there with a radio,
Thank you both,
DRMatt, do I take it from your message that your impression is that the
receivers are the least stable? I remember reading in other threads that
the wifi antenna is not the best performing of the sb's (perhaps due to
form factor). Do you have it hooked up via LAN or wifi?
w3w,
dolodobendan wrote:
> From my experience, the receiver might be less stable with an IP
> provided by DHCP. With a static IP, it's as stable as the other players.
I'll give it a try, thanks for the insight! Jim
Redrum's
Thanks to all;
Regarding tablet or phone, I realize no display is needed, I use squeeze
control, but find I still like the display, rather than pulling
something out of my pocket, or if someone other than myself wants to
operate it. Actually, the radio is a nice front end, and they are going
bpa wrote:
> Net::UDAP is not hard but it is "technical" in that it has a command
> line interface with rigid command structure and produces output which
> looks a bit arcane but it is easy to offer guidance
>
> You have a problem which can be caused by a number of possibilities.
> The output
drmatt wrote:
> I have regular issues with my receivers going blue light locked up and
> requiring restart. And I don't have the duet controller powered up
> anywhere. They just appear to drop connection to their lms instance and
> stay dead sometimes.
>
> -Transcoded from Matt's brain by
bpa wrote:
> One issue with a receiver is that users have tended to hide it away or
> right up beside other kit - unlike radio and touch which are on full
> display.
>
> Signal is never great if a receiver is placed behind an amp or at back
> of a shelf.
agree, but in this test, they were
bpa wrote:
>
> edit:
> If technically minded - you could try using net::UDAP and check a
> "fallen" receiver if it is still on net and check the settings are OK to
> talk to your LMS.
> https://github.com/robinbowes/net-udap
My receivers are at my other location, and one is bound to be
I thought I would post how this concluded, in case the contributors are
subscribing, or a search ends up here.
In summary, at my friend's house, questionable ISP without an ideal Wifi
setup, and he not being very technical - the receiver/controller
configuration of the duet was nothing but
basslover wrote:
> All of the above, either singly or in various combinations. I meant to
> add, my receiver is ethernet wired into the router, so it's not a wifi
> issue in my set up. I did briefly switch to wifi during this episode,
> to make sure it wasn't a short in the cable or
basslover wrote:
> Those are the steps I always do as well, and did about 6 or seven times,
> until this last time, it worked...
Sure, happy to help with the karmacurious, when it failed the
previous times, how did it fail? could not find network, could not
connect to library?, just hang
I have had problems like this, along with other instabilities, that seem
(to me) to be unique to duets, or just receivers. I have always thought
there is something "not as stable" either with the receiver, or the fact
that the receiver and controller communicate via wifi during operation.
I do
basslover wrote:
> I've been wondering, when Tidal streams into my router, does it go into
> my computer before it goes out the router to the receiver via ethernet?
assuming your computer is running LMS, yes. In general, the players are
just players*, you need a "server" which is LMS running
w3wilkes wrote:
> The only time the controller talks directly to the receiver is during
> setup when the receiver has been factory reset. When you pick the
> receiver from the controller (should be referenced by the receivers MAC
> address) the controller gives the receiver your wifi network
I don't think I have a solution for you, perhaps others with more
knowledge of the details will, but I do have allot of experience
struggling to get the receiver and controllers to work. with a PC as LMS
(I now have PiCore). So, I have a few thoughts. It sounds to me like you
have network or
w3wilkes wrote:
> The only time the controller talks directly to the receiver is during
> setup when the receiver has been factory reset. When you pick the
> receiver from the controller (should be referenced by the receivers MAC
> address) the controller gives the receiver your wifi network
basslover wrote:
>
> Some clarifications: I have a bridged connection. I don't have wifi.
> How does that affect your analysis?
>
>
I guess it doesn't. I have never tried to run it bridged, so I don't
know why it would only sometimes ask you. Perhaps (wild guess?) it sees
another wireless
basslover wrote:
> Thanks for all this, I will work my way through.
>
> Some clarifications: I have a bridged connection. I don't have wifi.
> How does that affect your analysis?
>
> Also, I always connect using squeezebox, since I don't have wifi.
>
> All my internet is working well.
w3wilkes wrote:
> I've never done bridge mode as I have no need (and this type connection
> is actually discouraged in the manual, see page 16 of the user guide).
> My guess is that in bridge mode the actual control of the receiver is
> still from LMS or MySB.com and the receiver just works the
wcndave wrote:
> Mine are all ethernet.
>
> Sent from my ONEPLUS A5010 using Tapatalk
then the only thing I can recommend is to bring the rx and controller up
at the same time. I never try to bring up just the rx, but not saying it
wont work.
good luck
Jim
wcndave wrote:
> Stuck on blue...
>
> I have a similar situation, so I tried to reset the player, fast red,
> then slow red, appears on my network as a device, and I can select it in
> the controller.
>
> I get to the connecting to network part, and the light goes yellow,
> green, blue in
mvordeme wrote:
> Thanks for the response. The Receiver is actually located two meters
> away from a WiFi repeater, so the signal strength should not be a
> problem. I tried resetting the Receiver but to no avail. I hate
> resetting the Controller because I will have to re-enter the 63
>
mvordeme wrote:
>
>
> I'll think about wiring, or I'll move a different player to my "office".
> I really like the concept of the Duet, but technically, it is a pain.
I really liked the idea of the small receiver and hand held controller
when I bought the Duet way back. I still like and use
after years of fighting problems with my receivers hanging up, and
battling the get them back on line, I have determined that it was
because of wifi signal stength. I now have 3 receivers on ethernet and
they are rock solid. I have one on wireless that I have improved the
signal strength via a
OppfinnarJocke wrote:
> OK, thanks for the help everyone.
>
> So, it appears that I have to factory reset both the controller and the
> receiver for this to work. I am a bit reluctant to reset the controller,
> since I added some code years ago to make it use a fixed IP address, and
> right
OppfinnarJocke wrote:
> OK, guys, my Duet is up and running again! Thanks for all the help.
>
> Indeed, I had to reset also the controller. How annoying. All my
> customization has to be redone and I have now idea how I did some of
> those long ago...
>
> One strange thing: even though it was
Early on in the thread you mentioned that you could have bought a
repeater with an ethernet connection, but decided not to. Perhaps you
could buy/test/return one? Amazon is good for that here is the USD. Or,
if you have an old router lying around that you could configure as a
repeater? Just
mvordeme wrote:
>
> Anyway, today, a few things have changed. The day started with bad news.
> The Receiver did not play anything without re-buffering. I checked the
> signal strength, and it was 54 % (rather than below 30 % as before). But
> during the night, the router had received a
mvordeme wrote:
> Since I wired the Receiver, it is rock steady. Now I need to decide what
> to do.
good to hear, ethernet may be undesirable, but at least you have an
answer.
You never mentioned, how did it perform after you did the antenna mod?
Jim
If it's at all possible, try the ethernet connection, just to isolate
the problem (wifi - yes/no). Even just temporarily.
one other thought is Phillippe's idea back in the spring on a similar
thread
anglecard48 wrote:
>
> Any other ideas?
I'm sorry I don't have a duet at my current location, otherwise I would
go through the process for you...Are you sure you reset BOTH the
controller and receiver as per my previous post? I have never been able
to properly reset the receiver without the
B1tbull wrote:
> Factory reset for both controller and receiver is a good place to start.
>
> Maybe asking the obvious : can you login to Mysqueezebox.com website
> with your account and password. If so this is the same account/password
> to be used when setting up the Duet after reset.
>
>
I read through the thread and it appears you have not tried factory
reset/startup of receiver and controller. A lot of my "mystery" receiver
issues are fixed this way, worth a shot:
Turn off controller (long press power)
Press and hold button on receiver until LED flashes RED rapidly,
release
garym wrote:
> If you want to connect the receiver and Controller to mysqueezebox.com
> instead, there's a menu item buried somewhere in the CONTROLLER to
> connect the player to mysb.com. Could be under settings > networking or
> somewhere. I forget.
you could also just take LMS offline, the
w3wilkes wrote:
> This could very easily be a failing power supply. I replaced a receiver
> power supply with something like this, set it to 9 volt and picked the
> connector that fit the receiver. Been running fine now for a couple of
> years;
>
agree with w3 and philippe, and I also suspect it's the inability to
supply the needed current. I just replaced a duet controller ps (cut and
splice) where the voltage read fine.
There was a very recent thread where the op could only get a radio to
power up after a factory reset by pressing AND
Happy that you solved your issue!
Rather than low quality, I think a better description of these switching
supplies is inexpensive and adequate when new. Age and heat cycling
causes them to be susceptible to failing as they age. Of course you can
always get a better supply, but isn't it nice
aapthorp wrote:
> I have a Squeezebox Touch and Duet Receiver. At some point in time -
> can't remember when - the Duet Receiver could only be found by LMS when
> it was powered on and off again. LMS has no issue finding the Touch.
> Obviously this is a bit irritating. Any thoughts appreciated.
w3wilkes wrote:
> Yes, I have Duet controllers too which I normally use if I need to do a
> setup which is almost never. I must be lucky, my receivers are both wifi
> and are rock solid! I have used UDAP in the past and find that having
> the receiver wired when setting up with UDAP is more
your sig says you have 2 duets, so do you have a controller handy?
I have always had to bring receivers up from reset with a controller
from reset. Press and hold receiver until fast, then slow flash red.
>From power off, press and hold '+' on controller, while pressing power.
I would use
bvrulez wrote:
>
>
> EDIT: Solved
can you share how you solved it? I have one I am still licking my
fingers with :o:)
Redrum's Profile: http://forums.slimdevices.com/member.php?userid=33806
View this thread:
greywing wrote:
> Thanks, Jim. I will probably stick with the SQ Rcvr for the duration
> but I have only limited knowledge on the "Touch" and "Pi" solutions. Do
> you have any reference recommendations WRT these alternative solutions?
Since your power supply solved the problem, there is no
greywing wrote:
> Actually, my original SB is broke so I'll probably toss it. The used
> one I bought on Ebay is my operable unit and I'll continue using it.
>
> Thanks for the Ref links. Appreciated. I will take a look and assess.
sorry, I misunderstood. I thought you found the ps was the
cathcam wrote:
> Today is squeeebox fix day, started with wlanpoke on a radio which seems
> to be working, on to the controller.
>
> I have two Duets, like many, I bought a spare from ebay.
>
> I have the same problem as everyone. Tried the backup controller(which
> has the original Logitech
If the receiver and power supply are ok, if you press and ho!d the front
button,it should start flashing red, fast at first then slower.
If it does, you have reset the receiver and it us waiting for the
controller to help with setup. If you have a controller (hopefully) from
power off (blank
greywing wrote:
> . It is my understanding the when power is applied to the receiver, the
> button goes red whether it is recognized by the system or not.
> .
I reread your post. I pulled a receiver out of storage and plugged it
in, red light, then white. I then did a factory reset (hold red
greywing wrote:
> Thanks w3wilkes. That looks like a pretty nice power brick and very
> versatile. Turns out it was the power brick that measured 9.03 V but
> apparently couldn't supply sufficient current to power up the Rcvr. And
> thanks to everyone for your responses. The OEM bricks seem
I own allot of receivers, two in use, many in storage, and have reset
them many several times :)
The white does look "light/pale yellow", The yellow is very "vibrant"
yellow. I tried to take a picture, but could not really capture the
color.
I think the receiver is fine as a general purpose
Gregavi wrote:
> Does the Duet Support 16- and 24-bit audio with a sampling rate of up to
> 96 kHz like my Touch does?
> Also, I might purchase a used Duet that does not come with the remote.
> Is the remote necessary if I use IPeng and Logitech Media Server to
> control it?
> Thanks in
whathim wrote:
> Im almost getting to the point where Im tempted to invest in a
> Raspberry Pi solution and ditch the Duet Receiver. Its getting
> ridiculous having a device on my LAN that doesnt have its own web
> interface, as does my router, my printer, my NAS drives.
Might be a good
whathim wrote:
> ...all connections, Receiver, Server, everything in house, is Ethernet
> (i.e., wired and wifi disabled on router). This was working fine via
> the LMS Web Interface (the Duet Controller failed several years back -
> endlessly cycles Logitech'/Free Your Music) with just
I think you are doing it, but just to be sure, you are bringing up the
controller and receiver together, right?
I always do -
power down controller/press and hold receiver until quick red flash,
which then transitions to slower red flash
Press and hold '+' on the controller, then press and
sure, let us know if it stops bugging you :) It seems like it wants you
to update from ~855 to ~862.
funny, I went to settings-advanced-diagnostics-general info and it lists
my firmware as 7.8.0. ??? who knows, maybe there is different gen
hardware.
Jim
slartibartfast wrote:
> This is Community Firmware he is talking about. There is a plugin which
> allows you to install it instead of version 7.8.
>
> Sent from my Pixel 3a using Tapatalk
ah...makes sense. I barely use my controllers and took a "if it aint
broke dont fix it" approach.
slartibartfast wrote:
> .If you have never experienced them you have been very lucky.
or severely frequency limited hearing...:) Thanks
Jim
Redrum's Profile: http://forums.slimdevices.com/member.php?userid=33806
View
w3wilkes wrote:
> I got one of these and it's been working just fine for the last few
> years.
>
When ever I have seen the controller of the duet ask for a software
upgrade, it's for the controller itself, not LMS. But the version number
you list doesn't seem to jive
do this, on your controller go to settings->advanced->software update.
Your current firmware should be listed. Mine is 7.8.0
I don't have a solution, but own quite a few receivers, all but one are
now in storage.
I have never gotten receivers on wifi to work reliably for extended
periods of time, even if the "signal strength" is high (the reading from
the diagnostics menu is not an indicator of quality). The only one
I bought the one that w3w recommended (cheap) and agree, one of the
plugs worked out of the box. And you get a whole lot of other plugs you
may (or may not) need some day! :)
Either way, power supply for the receiver or charging cradle, make sure
to note polarity. SB's are center positive, but
I bought the one that w3w recommended (cheap) and agree, one of the
plugs worked out of the box. And you get a whole lot of other plugs you
may (or may not) need some day! :)
Either way, power supply for the receiver or charging cradle, make sure
to note polarity. SB's are center positive, but
so, since you say duet, and it freezes with the logitech logo, you must
mean the logo on the controller.
Could be a few things, but first try a factory reset of both the
receiver and controller ("duet" is the combo of receiver and
controller):
press and hold button on receiver until it blinks
65 matches
Mail list logo
