I upgraded the controller to 7.2 r3191 but I now get the red wireless
icon after the controller's been to sleep rather than the blue one.
I'm using this with a Transporter, firmware 63 and SC 7.2.1 73496.
Simon
--
ferraris
Ross L;356842 Wrote:
How is everyone doing with r3191, anyone still seeing BIOD? (Blue Icon
Of Doom)
Mine is much better. Only 1 BIOD since the upgrade but still long time
to re aquire server after sleep.
--
Mushroom_3
Thank you for the feedback, please keep it coming! :-)
How many people noticed this bug while Squeeze Network was your source
(not Squeeze Center)?
--
Ross L
Ross Levine - Slim Devices Quality Assurance
Ross L's
i did.
i'll see if thats still an issue.
one thing i would like to see, is SN be quicker to adopt at least the
same SBC fw that the newest release has.
--
MrSinatra
www.LION-Radio.org
Using:
Squeezebox2 (primary) / SBR (secondary) / SBC - w/SC 7.3b - Win XP Pro
SP3 - 3.2ghz / 2gig ram -
mannekung;356883 Wrote:
As soon as there is a ReadyNas Pro release I'll give it a try. Really
looking forward to it...
Any roadmap for a release of it?
http://bugs.slimdevices.com/show_bug.cgi?id=9909
--
Ross L
Ross Levine - Slim Devices Quality Assurance
Thank you Ross - I'm impressed by your commitment to provide the best
service!
--
mannekung
mannekung's Profile: http://forums.slimdevices.com/member.php?userid=20114
View this thread:
tried SN earlier today, here's what happened:
went to SN, tuned into net radio, put sbc on cradle, waited about a
half hour give or take, picked up the sbc, got the red icon.
in addition the sbc was very slow to react or scroll or do much. i
tried to power down, and the sbc was stuck on
How is everyone doing with r3191, anyone still seeing BIOD? (Blue Icon
Of Doom)
--
Ross L
Ross Levine - Slim Devices Quality Assurance
Ross L's Profile: http://forums.slimdevices.com/member.php?userid=4416
View this
Ross L;356842 Wrote:
How is everyone doing with r3191, anyone still seeing BIOD? (Blue Icon
Of Doom)
As an erstwhile, longtime BIOD sufferer... I upgraded my router to see
if that would change things, and it did. Going from the Linksys
WRT54GX4 with a WRT610 dual band, which was included as
Ross L;356842 Wrote:
How is everyone doing with r3191, anyone still seeing BIOD? (Blue Icon
Of Doom)
As soon as there is a ReadyNas Pro release I'll give it a try. Really
looking forward to it...
Any roadmap for a release of it?
--
mannekung
Jmschnur, what Internet radio stream caused your receiver to turn
itself off? I tested a number of slim picks with r3191 and they played
just fine.
WAMU- see above new duet seems to have fixed problem.
Joel
--
jmschnur
Joel
Hmm I've got my first biod today, some change in 3220 must be for the
worse.
I'm on one of the latest 7.3
The SBC has been working ok since i got it, but with r3220 i got one
freeze so far and one biod both required reboot to get out of.
But i got the biod after i initiated a wol from the sbc in
Ross L;354345 Wrote:
r3191 is now being pushed to 7.2.1 users, so I've removed the custom
files I linked too in my last post. If you're using 7.2.1 your
controller should already be updated to r3191, if not you can simply
restart SqueezeCenter and that should push the update.
Pablolie,
I'd like to thanks Ross and all the people at Slimdevices who worked on
this issue. For me the miracle firmware r3191 brings a tremendous step
in usability.
--
epoch1970
epoch1970's Profile:
Ross L;354676 Wrote:
Joel, if you haven't already, please contact support.
I did- new Duet was sent to me. Interesting issue with non registered
MAC adresses.
I used a direct EHTERNET connection with the new one to make sure I
got the correct updates. I have not yet tried sleep- but all esle
I've had a case open about this for nearly 6 months. At least in my
case, when the controller is blue, it does connect to the SqueezeCenter
computer. It can download album art. It can (try) to download updates.
I've sent Support network traces proving that it isn't about wireless
config, with
Yannzola;350831 Wrote:
Thomas... I love you.
I'm also running DD-WRT (v24-sp1 mini) on a Linksys 54G... all I did
was change the MAC addresses I already had specified in Services (under
Static Leases) to all lower case. Applied changes. Restarted my
Controller and VIOLA! It works! No
Ross L;354345 Wrote:
Kim T. Sounds a lot like
http://bugs.slimdevices.com/show_bug.cgi?id=7153
Yes I have had this problem since I got the Duet back in March, and was
disapointed when I saw that the bug was moved to 7.3. The ZyXEL router
is a wery common router used in Denamrk by
After update it is better but controller disconects from squeeze network
repeatedley and then offers me a new pin to reconnect. I hae now delted
my Duet three times and added it with the new pins but it soon stops
and the process repeats.
Also reconncected to the receiver is still problematic. I
Joel, if you haven't already, please contact support.
--
Ross L
Ross Levine - Slim Devices Quality Assurance
Ross L's Profile: http://forums.slimdevices.com/member.php?userid=4416
View this thread:
I have just upgraded to r3191 FW on the controller and the BIOD has NOT
disapeared! If I place the contrller in a place where there is almost
no signal the controller still gets a BIOD after 15-20min and will not
reconnect to the server.
I took the controller into the room where the router is
i turned the controller off overnight, when starting it this morning it
cant find anything... neither squeezecenter nor the squeezenetwork...
my WLAN works fine otherwise. restarting / factory resetting is not
helping... its seeing a squeezebox player but cant connect or do
anything... what do
r3191 is now being pushed to 7.2.1 users, so I've removed the custom
files I linked too in my last post. If you're using 7.2.1 your
controller should already be updated to r3191, if not you can simply
restart SqueezeCenter and that should push the update.
Pablolie, any update? Contact me in
Refreshed apt-get and loaded 7.2.1 into the Linux VM I'm using. I'm sure
I already had 7.2.1 on there, but I guess this is a fresher one, and apt
can tell the difference.
Sure enough, the new jive FW is in there, and updated. Looks good to
me, but time will tell.
BTW I bought a SB Boom today @
Ross L;353106 Wrote:
We think we have a number of these Blue Icon Of Doom issues resolved.
The fix will be pushed out sometime next week, but if you'd like to try
it now you can download a custom Controller firmware version and a
custom version file here:
http://eng.slimdevices.com/~ross/
OhPinchy;353484 Wrote:
I've been having intermittent problems with my Duet controller
disconnecting, hanging etc. Should I try the 7.2 update posted here or
the 7.3 beta (i.e. does the beta also include that fix)? How do I go
about updating to the beta?
Just bumping to see if anyone has
epoch1970;353700 Wrote:
Update. Nah, my controller refuses to see anything above r3080, sorry.
Ditto.
I loaded the patch jive FW every way I could think of in /cache folder
of my Ubuntu SC and the Controller doesn't know of anything but r3080.
Boo.
--
forddonald
Same problem here.
Have a Boom, which connects wireless without any issue.
The SB receiver works fine and is connected wired, but the SB
controller... that's turning out to be a sad story.
The controller loses connection to the music source after 30 sec of
none use, almost as fast as the screen
Me, too.
Wireless: Apple Time Capsule, latest FW (7.3.2)
SqueezeCenter: 7.2.0, Ubuntu 7.10 in a virtual machine
Players: Transporter, wireless; 2x Receivers, both wireless
Controller: 7.2 r2873, static DHCP entry (router gives it the same IP
every time based on MAC address)
--
forddonald
I brought my receiver down to my router, I took the battery ut of the
controller and then put it back in. I then plugged in the receiver.
This worked after a 5-10 minute wait.
I then unplugged the reciever and put it where it belongs.
I had to turn the receiver on and off and unplug it once
Ross L;353106 Wrote:
We think we have a number of these Blue Icon Of Doom issues resolved.
The fix will be pushed out sometime next week, but if you'd like to try
it now you can download a custom Controller firmware version and a
custom version file here:
http://eng.slimdevices.com/~ross/
After sleep last night my receiver did not work in the morning. After a
reboot of my 7.2.1 the music library works fine but the internet radio
stations do not.
My SB3 is working fine with both internet radio stations and my
library. I am using Vista- would XP be better for the Duet?
Will the
Same here - with the new 7.2.1 all of a sudden my Receiver has gone
dark. When trying to reconnect it with the Controller, the controller
will off me 2 players, one with a cryptic name (which I assume is the
Receiver as it tries to rejoin but has forgotten who he is), and then
the old name of the
pablolie;353423 Wrote:
Same here - with the new 7.2.1 all of a sudden my Receiver has gone
dark. When trying to reconnect it with the Controller, the controller
will off me 2 players, one with a cryptic name (which I assume is the
Receiver as it tries to rejoin but has forgotten who he is),
I am very mad, and shall not post again until I calm down. I'd really
say horrible things about the Duet right now. Why does this crap always
happen on weekends when one wants to listen to music, and why is the
Duet so unreliable cokmpared to the SB3s and Booms I have in the house?
[EMAIL
I've been having intermittent problems with my Duet controller
disconnecting, hanging etc. Should I try the 7.2 update posted here or
the 7.3 beta (i.e. does the beta also include that fix)? How do I go
about updating to the beta?
--
OhPinchy
Same problem here.
I have a Netgear WNDR3300 Router wired connected to a SB receiver
(living room). The Vista 32bit based computer is connected thru a
Netgear WNHDE111 in 5GHz/N bridge mode to the router. This connection
is rock solid and I never encountered a problem. The SB Controller is
We think we have a number of these Blue Icon Of Doom issues resolved.
The fix will be pushed out sometime next week, but if you'd like to try
it now you can download a custom Controller firmware version and a
custom version file here:
http://eng.slimdevices.com/~ross/
Simply put both of those
Hi Ross,
I seem to have similar problems with the controller not connecting to
SqueezeNetwork with the current beta nightlies.
Will this new code also be implemented into the beta firmware?
Thank you
Robert
--
StanByk
StanByk;353112 Wrote:
Hi Ross,
I seem to have similar problems with the controller not connecting to
SqueezeNetwork with the current beta nightlies.
Will this new code also be implemented into the beta firmware?
Thank you
Robert
Hey Robert,
Yes this just went live in beta about 10
Ross L;341127 Wrote:
If you see this please reply to this thread with your wireless router /
access point model number and version, and firmware version. As well
please share your wireless encryption settings, and DHCP status. Also
please let us know if this is a standard wireless setup or
Yannzola;350831 Wrote:
Thomas... I love you.
I'm also running DD-WRT (v24-sp1 mini) on a Linksys 54G... all I did
was change the MAC addresses I already had specified in Services (under
Static Leases) to all lower case. Applied changes. Restarted my
Controller and VIOLA! It works! No
I have a Duet system. I was listening to it fine Thursday night and
returned the controller to the charger station. On Friday, I removed
it from the charger and it would not connect to any music source though
I tried repeatedly and moved around the house. I was able to play music
from my
My Duet is behaving *much* better with a new wireless router.
But it still displays very temperamental behavior under admittedly
unusual circumstances: I have now consolidated all household server
duties on a Vista 64 machine (most silent machine I have built yet) and
have (with a heavy heart)
thhv;349583 Wrote:
I think I'm on to something :-)
I have solved the problem by assign static IP addresses to both the
Controller and the Receiver, by using LOWER CASE MAC DIGITS ONLY!
All I know is that my DUET is now working flawlessly now, and I'm very
happy :-)
Thomas
Thomas... I
After a few weeks of the dreaded blue icon, reboots, resets and
switching my Duet controller on and off several times a day, everything
seemed to settle down (touch wood) after assigning static DHCPs for
Squeezebox and controller. My previously very flaky Linksys WRT54GC is
now behaving itself, I
Ross L;349731 Wrote:
Something to try. Anyone seeing this issue, or if you think you're
seeing this issue it wouldn't hurt to try this.
On your Controller go to Settings - Advanced - Factory Test - Power
management, then uncheck wireless power save.
Let us know what you find. Thanks
Ross L;349731 Wrote:
Something to try. Anyone seeing this issue, or if you think you're
seeing this issue it wouldn't hurt to try this.
On your Controller go to Settings - Advanced - Factory Test - Power
management, then uncheck wireless power save.
Let us know what you find. Thanks
thhv;347941 Wrote:
...
I have also seen it give me the choice between two recievers with
almost the same MAC digits.
#1 ending with 16750F
#2 ending with 16750f
#2 usually works.
I have seen this many times and neither #1 or #2 worked for me.
Hangleton;349683 Wrote:
..
maybe i'm being dense here, but aren't mac addys always supposed to be
in caps? and regardless, why can't the slim clients just be case
insensitive?
are the routers to blame for cap issues?
--
MrSinatra
www.LION-Radio.org
Using:
Squeezebox2 (primary) / SBR (secondary) / SBC - w/SC 7.3b -
Made a change to my Linksys BEFW11S4 config which appears to have
increased stability of my setup so far. I made the change approximately
3 days ago.
I changed the client lease time setting to 5 from 0. Linksys
documentation indicates that 0 means a DHCP lease time of 2 days but I
have to
thhv;349583 Wrote:
I think I'm on to something :-)
I have solved the problem by assign static IP addresses to both the
Controller and the Receiver, by using LOWER CASE MAC DIGITS ONLY!
In my Linksys DD-WRT router, this is done by using the Services section
Additional DNSMasq Options using
Hi all,
Here are my experiences, in case theyre of any interest.
I have had my duet for a couple of weeks, having owned an SB3 for about
a year, which has worked perfectly since I bought it. I have a Draytek
Vigor 2600+ router and am running SC 7.2. All wireless, using WPA.
Seems to me there
Something to try. Anyone seeing this issue, or if you think you're
seeing this issue it wouldn't hurt to try this.
On your Controller go to Settings - Advanced - Factory Test - Power
management, then uncheck wireless power save.
Let us know what you find. Thanks again to everyone for the
Doc_D;349576 Wrote:
I Wonder if thhv is onto something here. Do certain (most?)
implementations of DHCP cop the proverbial spanner in the works by
certain batches of the Duet hardware messing with upper/lower case in
the MAC?
I think I'm on to something :-)
I have solved the problem by
thhv;347941 Wrote:
Same error here. Connecting to Squeezebox
I..
I have also seen it give me the choice between two recievers with
almost the same MAC digits.
#1 ending with 16750F
#2 ending with 16750f
#2 usually works.
Im using static dhcp ip's with Linksys WRT54GL dd-wrt
I hope I am not jinxing myself by writing this.
In the end, I bit the bullet and decided to buy a new wireless router.
I had been looking at the dual band Linksys WRT610N, which had been
listed as tested and trouble free for Duet operation, too.
With some apprehension I plonked down $170. But
pablolie;348501 Wrote:
...
I'll observe it for a longer period of time, and will report.
I can confirm that even after doing all the things that usually would
get the controller to go haywire, with the new router things are
working very well indeed. I am very pleased. Te new router doesn't
Same error here. Connecting to Squeezebox
I only have one DUET. If i restart the controller it let's me choose
between two receivers. A new one with with the same MAC digits. If i
choose the new one I'm not able to connect to SC server (But SC web can
play to the receiver!) If I choose the
Flipper;346672 Wrote:
I turned on the receiver and it connected to SC. Checked the DHCP
client table on my Linksys BEFW11S4 (FW 1.52.02) and I could see the
receiver. I could also see the receiver from SC on my PC.
I'm using a Linksys BEFW11S4, a v4, with the same firmware revision
(now
Ross L;341127 Wrote:
There are a number of network related issues that can occur with Duet
and Controller [...]
If you see this please reply to this thread with your wireless router /
access point model number and version, and firmware version. As well
please share your wireless
New user here.
Brought my Duet last weekend. Had quite a hard time getting it all to
work on Saturday when I brought it home. Not sure what sequence of
events got it working as I was resetting and rebooting in frustration
and it started to work.
Sunday morning I had to repeat this exercise to
I have been frustrated by these symptoms and I am glad that I found this
thread.
I have an incident open [Incident: 080916-002230]
I initially tried the receiver and remote connected wireless to my main
network via a Linksys WAP54G Wireless Access Point (Firmware 3.0.5)
Australian Wireless
My Duet controller also has a red wifi sign sometimes after wake up. It
stays red, but it is working normally..
I have another Duet that doesnt wake up after sleep. Only the buttons
are illuminated. I then have to reboot for it to work.
Probably a hardware default ?
Both on r2873 and SC7.2/SN.
Ross L;345388 Wrote:
Mannekung, Could you please share your networking details asked for in
the original post of this thread?
pablolie, to get to the advanced logging menu on your controller you
must first have an SD card in the Controller with a directory named
log.
Carlandphil,
pablolie;34 Wrote:
Last question: now in logging I see a huge number of options. Just let
it run and write down the time of the issue, and then send you the log
file?
Select SlimServer please.
Remd, this is very interesting. I haven't heard of the red icon and
Controller still works
Mannekung, Could you please share your networking details asked for in
the original post of this thread?
pablolie, to get to the advanced logging menu on your controller you
must first have an SD card in the Controller with a directory named
log.
Carlandphil, thanks for recommending us! Would
As long as DHCP bugs are resolved by the WONTFIX resolution like
here: http://bugs.slimdevices.com/show_bug.cgi?id=462 customers with
some DHCP servers (seems Cisco is picky when SB doesn't observe the
RFC) will have the problems.
However, I don't think that this thread is about DHCP problems
Another problem with my Duet, may be more in line with those of others.
The receiver is wired and connected to an OS X SC7.2 server. The
machine was up all the time and SC wasn't stopped.
Yesterday I was playing music until 8PM on the Duet. At that time I put
the Receiver Off and the Controller
pablolie;343759 Wrote:
will do as soon as i return to California this weekend (on a business
trip right now)...
thanks for helping us out!
I am trying to do this, and can not find the logging option under the
advanced settings in 7.2?
--
pablolie
This is all terribly familiar. Have had the squeezebox for a month
running with no problems (i.e. convincing all my friends to get one).
Updated to latest version last week and since then have had all the
same problems. If I reset modem and wireless router then restart SB all
is well till next
I've had ongoing issues like this since I got my Duet right when they
came out. If I leave it for a few hours or days then come back, I
always have to go through gyrations involving unplugging receivers,
turning off/on the remote, and sometimes rebooting my router to get the
remote/receivers to
I do indeed think I have something going on with my controller. After
going to sleep it does come up with the wrong or nil address. My
router says it keeps sending OFFER's to the Mac Address of the
controller but there are no Acknowledgments in the log the controller
comes up with a random IP
Ross L;344130 Wrote:
Would you be willing to update the firmware of your router and see if
you can still reproduce this?
http://kbserver.netgear.com/products/WGT624v2.asp
I've now updated manually the router firmware to latest version
(V4.2.11_1.0.1) - Something that I would have done
Ross L;343131 Wrote:
Thanks for the specifics, they are helping guide my tests. So far I
still haven't reproduced, please keep sharing details! :)
AV spyder: How are you powering down your Receivers, and how are you
turning them back on? Red light? Please elaborate on the troubles your
I believe I've said me too a couple of times in this forum. But the
description above really goes for me as well. Especially the ethernet
part.
--
mannekung
mannekung's Profile:
I made an earlier post to this thread regarding setting up a dedicated
Wireless B network for the Duet alone. Last night after playing MP3's
for a couple of hours the controller (off the charger) reported that
the players signal strength was 80. Two hours later the controller
(now on the
MY SETUP:
router:
NETGEAR WGT624
Hardware version = V3
Firmware version = V4.2.4_1.0.1
Wireless encryption = WEP 10 digits
I Use DHCP with IP address reservation for each device
Standard Wireless setup: Everything connected Wireless
My SqueezeCenter
7.2 - 22900 @ Tue Aug 26 11:27:23 PDT 2008
Chrobrego, unfortunately I do not have that router here to try to
reproduce. However I do have a question about the router firmware, are
you sure about that version?
http://kbserver.netgear.com/products/WGT624v3.asp
Sailnut, thanks for the details but I'm not sure the inconsistent
wireless
Ross L;344089 Wrote:
Chrobrego, unfortunately I do not have that router here to try to
reproduce. However I do have a question about the router firmware, are
you sure about that version?
http://kbserver.netgear.com/products/WGT624v3.asp
Well I checked the router itself, it is in fact
Chrobrego;344122 Wrote:
Well I checked the router itself, it is in fact written WGT624 V2 not
V3, I wonder why the Web interface indicates Hardware version = V3 in
that case.
You may want to have a word with Netgear about that. Would you be
willing to update the firmware of your router and
my specs are below. fw = 1.20 for the router.
i think there is more than one issue involved here, and the conflation
of factors makes figuring this out very tricky. its not just the dhcp
for the SBC, my sbc has its dhcp IP reserved, (my sb2 uses a static
private ip).
i think a lot of it is
Mr Sinatra,
Sorry, you got me, I linked to the wrong bug. I meant to link to this
one:
http://bugs.slimdevices.com/show_bug.cgi?id=8159
9425 is a receiver bug, and it's also very high on my list.
I'm mostly concerned with the official release of 7.2 which is firmware
r2873. I've managed to
I'm running 7.3 - also been trying the new fireware (using the
SD-method). Problem persists.
My lease time is infinite.
--
mannekung
mannekung's Profile: http://forums.slimdevices.com/member.php?userid=20114
View this
Well you're asking for feedback, and a transaction with support
convinced me my Duet hardware is okay. Here is my latest trip to the
funny farm with my Duet.
I switched from bridged to hybrid mode on my duet to see if using
infrastructure wifi would improve controller receiver interaction. I
Had it happen to me when I left the remote off the charger the other
day. Had to reboot it.
Fortunately I don't leave the remote off the charger very often.
Is there a bug report I can subscribe to on this one?
--
Jeff Flowerday
Ross L;343139 Wrote:
Thats really strange blue means it is connected to the network just not
a music source, in this case it should have some kind of IP. Would you
be willing to email me a log? To get a log from Controller, put an SD
card in it with a directory named log, then go to settings
Ross L;343508 Wrote:
Has anyone experiencing either Controller or Receiver disconnecting/not
reconnecting made changes to their DHCP lease time?
I'm curious if there is a connection to short DHCP lease times. Also,
anyone using 7.3? Thanks again!
I have, and it did not make an
BlueWombat, Do you remember what color the wireless icon was on your
Controller? Could you please share the networking specifics I requested
in the original post?
--
Ross L
Ross Levine - Slim Devices Quality Assurance
I had my Duet connected wirelessly to a WRT54GS running DD-WRT firmware
and I swear I never had this problem. I switched to a WRT600N and now
see it all the time. I've noticed the best solution for me is to reset
my router (sucks!) and the Duet/Controller seem to reconnect without my
help.
--
I may not be seeing the same thing as described in this thread. I let
my controller go to sleep overnight and tried to start it this morning.
I pressed the on button this morning while it took over 5 minutes to
connect to the receiver, it did so without any other problems. I never
saw a blue
I set up a new wireless network using an old Microsoft Access Point
(wireless B) and a Belkin USB adapter (wireless G).
I re-ran setup on my Duet controller and player and within 5 minutes
everything was working perfectly.
That was 12 hours ago and its rock solid.
The original router was the
egg;342435 Wrote:
i have this problem every morning when take it to bed. Want to know a
easy fix? JUST SELL THE CHARGERS... PLEASE
Post the info later.. Love the product.
AMEN BROTHER!
--
Howard Passman
Sorry slow to respond. I don't spend that much time online and God
knows I
Has anyone experiencing either Controller or Receiver disconnecting/not
reconnecting made changes to their DHCP lease time?
I'm curious if there is a connection to short DHCP lease times. Also,
anyone using 7.3? Thanks again!
--
Ross L
Ross Levine - Slim Devices Quality Assurance
pablolie;342711 Wrote:
i am hopeful that we shall get a solution or at least a good workaround
soon, the development team is excellent once they get a critical mass
of people reporting a problem.
...
but based on the urgency this thread displays, i now fully trust that
the developers
NaterGator;343025 Wrote:
... I'd just like to see a bit more communication on the issue (ex: do
the two devices share a common networking API?)
that i have asked for before, and i echo the sentiment. however, it is
not easy for the engineers, who as usual are being whipped to deliver
new
Thanks for the specifics, they are helping guide my tests. So far I
still haven't reproduced, please keep sharing details! :)
AV spyder: How are you powering down your Receivers, and how are you
turning them back on? Red light? Please elaborate on the troubles your
receiver is having connecting
Ross L;343131 Wrote:
The wireless icon is blue and it ssh shows ?.?.?.?, do you happen to
have an SD card? The theory about specific networks seeing this issue
with more frequency than others has not been thrown out. Thats exactly
why I'm asking for network specifics.
That is correct,
pablolie;343138 Wrote:
That is correct, the network icon on the controller is blue and the
address (as displayed by that SSH command) is ?
And yes, I do have SD cards.
Thats really strange blue means it is connected to the network just not
a music source, in this case it should have some
I've only had a Duet for less than a month but both times it went to
sleep, I had a difficult time trying to get it to reconnect. I think
it eventually reconnects on its own but I reboot it several times
before i give up.
My router: SMC2804WBRP-G, Firmware v2.0
Controller: 7.2 r2873
I am
1 - 100 of 111 matches
Mail list logo
