PDA

View Full Version : Squeeze controller losing network connection



Pages : [1] 2

tomlillie
2008-03-19, 18:24
Hi,

I have 3 squeezeboxes and recently added a receiver and a controller. All works well - but the controller spontaneously loses network connectivity every few days - it still says it's connected to the wireless network but cannot find the music server or the players. the players themselves and squeezecenter work fine all the time (even while the controller is throwing a flunky) and always have done on the same network - no changes.

Also the controller permanently believes there is a software update.

any ideas?

thanks

fireupthegrill
2008-03-21, 19:57
Same problem here. My Duet system is terribly flaky. Here are some of the problems:

- The controller frequently decides that it can't get a DHCP lease, so it spontaneously assigns itself a 169.x.x.x address. My home wifi network is pretty good and no other device has this problem.

- If the controller can get a real lease, it often loses connectivity with the SB. Sometimes it blames the SB, saying that the SB can't connect to the SC server. However, that's false; not only is the SB connected by wired Ethernet to the SC, but I can fire up SC from a web browser and happily control the SB from it, at the very same moment that the controller insists that the SB can't communicate with the SC.

- Like yours, my controller always thinks it needs a software update. Unfortunately, it is rarely able to get past the "Copying Update" phase. Most of the time it just hangs there (sometimes displaying the "Try Again..." option faintly in the background), sometimes it starts displaying the x% indicator that advances a percentage point every few seconds, but it almost never reaches 100%, and even if it does, it's a Sisyphean victory, because after the update it still thinks it needs an update.

- Menu operations randomly hang or come up blank.

- Browsing the library is sometimes quite quick but often astonishingly slow, as in minutes before the next screen appears.

- Extra data point: the controller frequently says that it's dropped down to a 2MB or 1MB transfer rate on the 802.11g connection, even when I've placed the controller right next to my AP.

- Extra data point: if I ping the wired SB, travel time is sub-millisecond. But the controller's ping times are spiky, often in the high hundreds of milliseconds.

- Extra data point: ssh'ing to the controller sometimes takes many minutes (or forever) to negotiate the SSH handshake.

My diagnosis is that the remote has trouble with wireless. I don't know whether this is a design defect, a sample defect, or a fixable software problem. I'd consider doing an A/B test at someone else's house to see whether it's a problem with my network, but to be honest I bought this system as a consumer electronics purchase. I didn't intend for it to turn into an exciting hobby; I just wanted a turnkey system that would let me listen to music in different rooms in my house.

slimpy
2008-03-21, 20:47
Dies the controller constantly prompt you to update the firmware or do you navigate to settings - advanced - software update?
If it's the latter you can safely ignore the message that new software is available.
If there is indeed new firmware available the controller will prompt you to update. There's no need to go to the software update section unless you want to reinstall the current firmware.

-s.

fireupthegrill
2008-03-21, 20:49
Dies the controller constantly prompt you to update the firmware or do you navigate to settings - advanced - software update?

Yes, it's the latter; it doesn't interrupt me.

Zaragon
2008-03-22, 03:45
Hi,

I have 3 squeezeboxes and recently added a receiver and a controller. All works well - but the controller spontaneously loses network connectivity every few days - it still says it's connected to the wireless network but cannot find the music server or the players. the players themselves and squeezecenter work fine all the time (even while the controller is throwing a flunky) and always have done on the same network - no changes.

Also the controller permanently believes there is a software update.

any ideas?

thanks
Is the controller the only wireless device? It sounds a little like it is unable to renew the DHCP lease. This could be because of interference.

tomlillie
2008-03-26, 07:12
no, there are other wireless devices - there are 3 squeezeboxes and 1 receiver as well as the controller. but they are all fine - they do not hangup (it's just happened again today). they manage to renew thier DHCP leases without nproblem (and always have). so that makes me suspicious of the controller, not the network.
even when the controller is hung uo - the squeezeboxes are still working and connecting to squeezecentre

cmblissett
2008-03-26, 14:40
I think i have a very similar issue. I have noticed that the Duet works perfectly well when i connect to SqueezeNetwork, but if i select my local NAS as the source the controller displays "Problem Connecting", "Couldn't connect your Squeezebox to your wireless network ..... (Lost Squeezebox)", however when i login to SC7 i can connect to the SB and play my music without any problems.
Having failed to connect it will not reconnect to SqueezeNetwork until i press the button on the front of the receiver (flashes red). It's repeatable everytime.

chrch01
2008-03-29, 16:23
I am having the same issue and figured it was due to poor signal strength which is lower than it should be.

poulsen11
2008-03-30, 07:03
Guys,

I was having all of the same problems you guys were with my SBC showing the same symptoms.

I did absolutely EVERYTHING to try to debug the problem.

Laptop was connecting fine to the internet through wireless.

SBR was connecting fine through wireless and could be controlled flawlessly through Squeezecenter.

Everything was pointing AWAY from my wireless router being the issue.

Turns out the problem was indeed my wireless router. I changed out my wireless router with a new Belkin F5D unit ($40 at Best Buy) and all of my problems went away. The SBC works flawlessly now.

For reference my old router was a refurb from Tiger Direct. A Linksys WRT54GX2.

I dont have any idea whether the issue is actually the fault of the SBC or the router itself, but my stuff is working now and it was WELL worth the $40 to get this thing working.

Jim

fjdebrick
2008-03-30, 10:10
Glad to see others with my problem - the controller can't find the home wireless network despite the fact that other computers find it, and it previously worked fine. I even put a laptop next to the unit to check the network strength and it connected fine. The squeezecenter will connect and play my music, so obviously the network reaches OK. I hate the thought that I have to buy a new router, suggested by one of you, but that may be the way out of this mess. Are there any other solutions anybody has found? I'd appreciate any other suggestions first.

cmblissett
2008-03-30, 13:17
I am not sure that the problem i reported earlier in this thread is the same as what you guys have got, but for what it's worth my connection issues are sorted. The problem was with my ReadyNAS and a new version of firmware has resulted in everything working as nicely.

fireupthegrill
2008-03-30, 17:45
After a couple rounds with Logitech/Slim Devices Support, I'm returning my system under the terms of the 30-day money back guarantee.

I'm sad because I've been looking forward to this device since it was in beta, and I'm already a happy Squeezebox user. But I can't seem to get a replacement device through Support (or even a response to my support requests, lately), so I don't feel I have any choice but to return it.

@lex
2008-03-31, 00:28
After a couple rounds with Logitech/Slim Devices Support, I'm returning my system under the terms of the 30-day money back guarantee.

I'm sad because I've been looking forward to this device since it was in beta, and I'm already a happy Squeezebox user. But I can't seem to get a replacement device through Support (or even a response to my support requests, lately), so I don't feel I have any choice but to return it.

Hello fireupthegrill
I completely agree!.
I have all the same problems with the Controller as you other guys. There is no response from the Slimdevices Support Team to help getting it fixed, no comments, no reply. The only suggestion is "replace your router". Whats going on? Is there mature problems with the product or the software?

mentzler
2008-03-31, 02:45
Hi

I had same type of problem, when I was using SqueezeNetwork and closed down for the night, then I couldn't connect the Controller to the Receiver the next day. Some time it help starting SqueezeCenter and connect to the Receiver from the PC. After a while the Controller again could find both my Reciever and SB ver.3
But today nothing helped, so I took off the power on the wireless router and it helped. Now everything is OK again. The wireless router is a Linksys WRT300N
If anyone have another solution, I would be glad to hear the answer

rtitmuss
2008-03-31, 04:14
I am sorry some of you appear to be having networking problems with the Controller. Please bear with us, it is very important to us that this is fixed as soon as possible.

To help we first need to isolate the problem. If you are having a problem could you please post details of your setup. In particular the following information is important:
- Access point make, model and firmware version
- Are you using having problems using SqueezeCenter, SqueezeNetwork or both
- What OS are you using with SqueezeCenter
- What version of SqueezeCenter are you using

Some people have indicated that changing the router/access point has helped. If you can try a different router/access point does this fix the problem. I am not suggesting this as a long term solution, but to help understand the issue.

It may also be worth you trying SqueezeCenter 7.0.1. Last week I made some changes to the Controller firmware that _may_ help with some connection problems.

Thanks,
Richard

mentzler
2008-03-31, 04:24
OK, I'll try 7.01, where to download/witch file to download for Vista Ultimate?

//Bent

Kim.T
2008-03-31, 09:34
AP : Zyxel 2602HW-D1A (I don't know FW because I don't have the PW for the router)
Only problems with SBC connecting to SC - SBR is wired (I don't use SqueezeNetwork)
SqueezeCenter is running on FreeNAS
Version : squeezecenter-7.0.1-17981-noCPAN.tgz

Update : Upgrading to 18219 doesn't seem to make any diff.

radish
2008-03-31, 09:41
7.0.1 is here: http://www.slimdevices.com/downloads/nightly/latest/trunk/

For Vista use the .exe version.

@lex
2008-03-31, 11:44
I am sorry some of you appear to be having networking problems with the Controller. Please bear with us, it is very important to us that this is fixed as soon as possible.

To help we first need to isolate the problem. If you are having a problem could you please post details of your setup. In particular the following information is important:
- Access point make, model and firmware version
- Are you using having problems using SqueezeCenter, SqueezeNetwork or both
- What OS are you using with SqueezeCenter
- What version of SqueezeCenter are you using

Thanks,
Richard

Hello Richard Titmuss

Thank you for your reply.
Now lets try all together to find out what is wrong and Slimdevices find out how to fix it :-)
I will help you giving all the information I can.
Duet is a great product, but it has to work 100% plug'n'play, stable and reliable as a consumer product on existing standardized network equipment, so I certainly hope problems can be solved.

1 piece SB3 Classic (wireless, 802.11g, 10.0.0.12:40154, Softwareversion: 86, signal=70%)
1 piece SB3 Classic (wireless, 802.11g, 10.0.0.13:55258, Softwareversion: 86, signal=78%)
1 piece SBR(eceiver)(wired, 100 Mbps, 10.0.0.10:50386, Softwareversion: 22)
1 piece SBC(ontroler) (wireless, 802.11g, 10.0.0.16, Softwareversion: 7.0.1 r2158 #28 Sun Mar 30.01:31:09 PDT 2008,signal=?)

After nightly update 26/3 things were running better, but still SBC is loosing connection.

Everything works fine from SC
SBC looses control can't connect to the players for approx. 1-2 minute (wireless indicator turns blue), but reapears and everything goes normal.
All Cover Arts are not always updated in the SBC display when choosing Album List.

SqueezeCenter version: 7.0.1 - 17981 - Windows XP - DA - cp1252 running om my laptop (wireless, 802.11g, 10.0.0.17, 200 CD's in FLAC)

AP is ZyXEL P-2602HW-D1A (router/switch/wireless/ip-telephony)
Firmware is: V3.40(AJQ.2) | 12/06/2006
Channel is 6 (2437MHz)
Wireless encryption disabled
Mac address filtering disabled
SSID broadcast enabled
No signal boost og pre-N specific settings

Best regards

@lex

fjdebrick
2008-03-31, 14:55
In my initial post I said that the squeezecenter could access the receiver. That isn't correct today - nothing works.
1. Using a DLink router, model DI634M
2. Using Vista Home OS on Dell Inspiron.
3. Message on the controller, after finding the Squeezebox, "Couldn't connect your Squeezebox to your wireless network..."
4. Today the message on SqueezeCenter "Your player was not found..."
5 I downloaded SC 7.0.1 with no change in results.
6. I can sit 3 feet from the router and still not get a signal on the controller, so I'm doubtful that it's a network/router weakness.

I appreciate any help you can provide. I really think this is a great system - when it worked.

Thanks... Frank Debrick

PS: After all this, I went into the settings on the controller, found the factory reset, did the reset procedure and now everything works fine. I'll be curious to see if this is a recurring problem.

fireupthegrill
2008-04-01, 11:38
After a couple rounds with Logitech/Slim Devices Support, I'm returning my system under the terms of the 30-day money back guarantee.

Logitech and I both got lucky. They'd already shipped the replacement system to me some time last week, but just didn't notify me of that fact. So Monday afternoon I received a new system, and this one really and truly works, exactly as I'd hoped when I first heard of the Jive product.

In summary: it appears my problems were due to a bad controller -- a sample defect, not a design defect. Whew!

JimC
2008-04-01, 12:23
All:

I ran across a similar issue while I was working with a journalist in Denmark. We had problems with his Linksys WR350N and the SB Controller. By switching from WPA2 to WPA encryption, the problem disappeared.

For those of you experiencing the problem, if you are using WPA2, would it be possible for you to switch to WPA to see if the problem is resolved? Please report your findings here.

Also, if you can run your SB Receiver in a wired configuration, you can use the "bridged" mode (see the Duet User Guide here (http://www.slimdevices.com/su_documentation.html) for details) to test that the Controller is good and that the issue is with connecting to your router/AP. If the Controller works reliably in bridged mode, then we'll need to troubleshoot around the router/AP.


-=> Jim

Jeff Flowerday
2008-04-01, 20:16
All:

I ran across a similar issue while I was working with a journalist in Denmark. We had problems with his Linksys WR350N and the SB Controller. By switching from WPA2 to WPA encryption, the problem disappeared.

For those of you experiencing the problem, if you are using WPA2, would it be possible for you to switch to WPA to see if the problem is resolved? Please report your findings here.

Also, if you can run your SB Receiver in a wired configuration, you can use the "bridged" mode (see the Duet User Guide here (http://www.slimdevices.com/su_documentation.html) for details) to test that the Controller is good and that the issue is with connecting to your router/AP. If the Controller works reliably in bridged mode, then we'll need to troubleshoot around the router/AP.


-=> Jim

I just switched from WPA2 only to WPA only and it hasn't helped me, my Duet remote is still stalling for 30 to 180 seconds every now and then. The > sign just spins when entering an artist or album or any item for that matter. Eventually I back out and try again or a different item and it starts working again.

Running SqueezeCenter 7.0, I've updated the remote once when prompted a week or so ago.

I'm using a Dlink DIR 655 running in ng mode only.

DHCP is on. I've tried both WPA2 only and WPA only.

Wireless strength is 85% or greater.

Jeff Flowerday
2008-04-01, 20:53
I just installed the nightly 7.0.1 build. Will report my findings.

Kim.T
2008-04-01, 22:04
I'm allready using WEP 128 bit - and as mentioned: I don't have the PW for my router - it's preconfigured.

@lex
2008-04-01, 23:50
I just switched from WPA2 only to WPA only and it hasn't helped me, my Duet remote is still stalling for 30 to 180 seconds every now and then. The > sign just spins when entering an artist or album or any item for that matter. Eventually I back out and try again or a different item and it starts working again.
DHCP is on. I've tried both WPA2 only and WPA only.


Exactly same problem here, remote stalling for 30 to 180 seconds. I have no security at all (WPA or WPA2) as long as it doesn't work.

@lex

@lex
2008-04-02, 03:21
Exactly same problem here, remote stalling for 30 to 180 seconds. I have no security at all (WPA or WPA2) as long as it doesn't work.

@lex

We (patient and unhappy users) give feedback to Slimdevices, but nothing comes back. What is going on?. Do you solve anything? What does the nightly beta's fix? Is it specific routers/AP's? Is it hardware failure?

Best regards

@lex

Jeff Flowerday
2008-04-02, 08:52
We (patient and unhappy users) give feedback to Slimdevices, but nothing comes back. What is going on?. Do you solve anything? What does the nightly beta's fix? Is it specific routers/AP's? Is it hardware failure?

Best regards

@lex

I really don't think it's router problem. It's been reported on different models and even brands.

I have too much equipment to go to fixed IP addresses or I would try that. Can any of you confirm if it's still an issue with fixed IP addresses?

Jeff Flowerday
2008-04-02, 10:36
I don't know if a bug has been filed yet or not but I just filed one.

http://bugs.slimdevices.com/show_bug.cgi?id=7697

mowensmd
2008-04-02, 11:44
http://forums.slimdevices.com/showthread.php?t=44311

Router is WRT54GX as well.

MO

forddonald
2008-04-02, 12:25
OK, I'm in the group that received the initial shipments of Duet (a pre-order wait-lister) and my Controller falls squarely into the 'flakey' category.

-- I've seen the spinning > symbol
-- I've seen the wireless icon be white, blue, red and maybe a purple in there as well
-- I've seen the 'no player found' issue where it goes back to three menu choices only
-- I've seen it flake out right in my hand while browsing the menus while attached to a playing Transporter, and have to reconnect it to the WiFi

Like many here, I suspected an aging AP (Apple AP Extreme that's 5+ yrs old), so I run right out and buy a shiny new Time Capsule. Well, that breaks everything (see separate thread; I'm ready for the fix any time). So, I now have to run two APs, one just for the music system.

WiFi for music: D-Link DI-524, latest fw, WPA2 keys
SC 7.0.0 GA, Debian (Ubuntu Server)
All firmwares are GA release
Duet & Transporter

Jeff Flowerday
2008-04-02, 13:21
Everyone else having this issue needs to go into my bug report and vote that it's a problem for you. The more votes the higher priority it will get.

jason3fc
2008-04-02, 13:32
I am also periodically having this problem. It seems to occur after several hours of continuous listening, or if I have not used the controller for sometime. The reciever seems to still be connected and I can control it with SqueezeCenter. The controller however acts like it can no longer find the receiver and or music source. Most of the time, unless I have just 3 choices, I can however still switch to my SB1 on the controller and use it fine and connect to squeezecenter there. The only way to reobtain a connection to the reciever with the controller is to turn off the controller and turn it back on.

Also have seen the exact same things that Forddonald just mentioned above.

SqueezeCenter: 7.01 (tried this in attempt to fix this, but was still having the issue with 7.0 final
SqueezeCenter Server: Standalone XP SP2 box.
Reciever: Wired or Wireless doesnt matter, Wired over CAT6 connected to a gigbit lan switch (Trendnet)
Network: WPA, SSID is not hidden
Router: Buffalo WHR-G54S

xn03296
2008-04-02, 13:48
hello,

I use my Duett in the bridging-mode in a wired LAN. Slimserver 7.01 runs on a qnap-209. The controller very often lost the connection to the receiver. The only help ist to reconfigure the duett completely. What is wrong with the device? If there is no soloution for this problem I will return the duett to my dealer and will buy a sonos.

Regards

Henrik

Jeff Flowerday
2008-04-02, 15:02
Ok it looks like a possible fix is coming with build 18309 and later.

http://bugs.slimdevices.com/show_bug.cgi?id=7376

Unfortunately as of right now 18284 is the latest 7.0.1 build available for download.

rtitmuss
2008-04-02, 15:16
Thanks for your patience, I assure you we are taking this problem very seriously and working to resolve it as soon as possible. So far I think we have isolated two or three networking problems, captured in the following bug reports:

Bug 7376: SBC is sometimes unresponsive
Bug 7153: Poor connectivity with ZyXEL routers
Bug 7489: SBC fails to require wlan after going out of range

I think most of you are probably experiencing the problems in Bug 7376. This appears to be related to running SqueezeCenter on Windows. It has been very difficult to resolve this bug as we have been unable to recreate the problem here, but with help from the community (thanks Steinar!) a fix will be available in tomorrows SqueezeCenter nightly 7.0.1 build. I'll post an update when that build is available to try.

It appears that some routers are not working well with the SBC. So far ZyXEL routers have been confirmed to have problems by our QA team. I suspect the problem is related to the wlan power management, and investigations are continuing. As a work around we recommend you try a different router, or use the Controller and Receiver in bridged mode as described by Jim.

Bug 7489 is an intermittent problem where the SBC fails to reconnect to SqueezeCenter when it moves out of the wlan range. The work around is to reboot your SBC (you should not need to do a factory reset). I will be investigating this in more detail from tomorrow.

These problems are not easy to recreate and resolve, so it will be a while before fixes are available for all these bugs. However it does help a lot to receive reports of these problems, with as much information about your system and symptoms as possible.

Thanks,
Richard

kimbl
2008-04-02, 17:45
Ok - another with what seems to be the same issue. - Controller remote drops connection and has problems reconnecting - reciever and SC fine.

Specifically, remote displays "having problems connecting to zebedee" (SC server)" - then only "choose player" and an empty list. After a few seconds this refreshes with the rotating dot icons - the wifi icon goes to full strength and the two players appear. Generally, signal strength seems to go wildly up and down over the course of a few minutes, even approx 3m from the AP. Needless to say other wifi things (phone, laptops etc) appear fine.

However - to buck the trend - my impression is the problem only came on after an upgrade to 7.01 SC (I've been fiddling with squeezeslave builds) - apparently fine out of the box working with 7.0 SC.

Remote has prompted (I didn't go looking) for software updates on the last two evenings - downloaded, but did seem to struggle - long time starting then intermittent progress indication.

AP: Belkin F5D7130b
Firmware Version 4.05.04
Boot Version 1.03.08

Remote - 7.01r2164
SqueezeCenter Version: 7.0.1 - 17981 - Debian - EN - utf8

Very happy to help trying things to help debug...

Should have said - WEP.

Symptoms confirmed this morning:
Remote comes on from sleep - no player connection, but wireless at 4 bars.
"Select player" - none listed - look at it for a few seconds - try "select music source"
Apparently of it's own accord, flips to
"Connecting to Squeezebox dot circle"
Apparently back to normal

So I'd think 7489, but the range is <3m.

@lex
2008-04-03, 00:15
Thanks for your patience, I assure you we are taking this problem very seriously and working to resolve it as soon as possible. So far I think we have isolated two or three networking problems, captured in the following bug reports:

Bug 7376: SBC is sometimes unresponsive
Bug 7153: Poor connectivity with ZyXEL routers
Bug 7489: SBC fails to require wlan after going out of range

I think most of you are probably experiencing the problems in Bug 7376. This appears to be related to running SqueezeCenter on Windows. It has been very difficult to resolve this bug as we have been unable to recreate the problem here, but with help from the community (thanks Steinar!) a fix will be available in tomorrows SqueezeCenter nightly 7.0.1 build. I'll post an update when that build is available to try.

It appears that some routers are not working well with the SBC. So far ZyXEL routers have been confirmed to have problems by our QA team. I suspect the problem is related to the wlan power management, and investigations are continuing. As a work around we recommend you try a different router, or use the Controller and Receiver in bridged mode as described by Jim.

Bug 7489 is an intermittent problem where the SBC fails to reconnect to SqueezeCenter when it moves out of the wlan range. The work around is to reboot your SBC (you should not need to do a factory reset). I will be investigating this in more detail from tomorrow.

These problems are not easy to recreate and resolve, so it will be a while before fixes are available for all these bugs. However it does help a lot to receive reports of these problems, with as much information about your system and symptoms as possible.

Thanks,
Richard

Hello Richard
Thank you for your status report, looking forward to try nightly release :-)

Some input from here:

Bug 7153: Poor connectivity with ZyXEL routers:
Maybe possible to change some wlan power management settings on the Zyxel Routers? Or upgraded firmware from ZyXEL. (I have ZyXEL).

Bug 7489: SBC fails to require wlan after going out of range:
For the last two days I have kept SBC close (3 feet, always in range) to SBR (bridged) and everything works much better (but still not good enough). In the Album Art list, half of the cover thumbnails is missing and never appears (I have tried to rescan library). SBC sometimes looses connection, but only for 1-2 seconds. Tried to automatical update SBC in room next to SBR (but same room as AP), but it stopped (15% or something). Trying again with SBC 3 feet from SBR and update went smooth to 100%.

Best regards

@lex

Kim.T
2008-04-03, 01:00
Bug 7153: Poor connectivity with ZyXEL routers:
Maybe possible to change some wlan power management settings on the Zyxel Routers? Or upgraded firmware from ZyXEL. (I have ZyXEL).

@lex

Not all users have access for configuring their routers - mine is preconfigured and I don't have the PW. Squeezebox Duet should work "out of the box". And using the Receiver as brigde would in my place not be an optimal solution - I guess that I would loose the signal pretty fast - meaning not being able to control SqueezeCenter in half the house. (I have a B&O stereo where I can listen and control music and TV in the entire house. The Receiver is connected to the stereo in the living room. And the result is that I just have to turn the stereo on in the room I wan't to listen to be able to listen to music from my server).

@lex
2008-04-03, 02:40
Not all users have access for configuring their routers - mine is preconfigured and I don't have the PW. Squeezebox Duet should work "out of the box". And using the Receiver as brigde would in my place not be an optimal solution - I guess that I would loose the signal pretty fast - meaning not being able to control SqueezeCenter in half the house.

Hello Kim, (you are from DK too :-)
I agree Duet should work "out of the box". Anyway I think it should be possible to have your serviceprovider to upgrade and change settings on your preconfigured router if necessary. Not optimal (or acceptabel) but possible.

rtitmuss
2008-04-03, 03:28
The new 7.0.1 nightly build is now available, you can down load this from http://www.slimdevices.com/dev_nightly.html. I am interested on your feedback, on bug 7376.

Richard

rtitmuss
2008-04-03, 03:31
For the last two days I have kept SBC close (3 feet, always in range) to SBR (bridged) and everything works much better (but still not good enough).

A three feet range is wrong. What is the SNR reported in Settings > Advanced Settings > Wireless Network > (Your network name)?

BTW I have ordered a ZyXEL router that should arrive next week (I work remotely from the main office). Hopefully I will have more information about the compatibility problems with the ZyXEL router mid-next week.

Richard

rtitmuss
2008-04-03, 03:34
However - to buck the trend - my impression is the problem only came on after an upgrade to 7.01 SC (I've been fiddling with squeezeslave builds) - apparently fine out of the box working with 7.0 SC.

Can your revert to the 7.0 SC? The 7.0.1 SBC firmware turns the wlan power saving on/off dynamically. This gives better performance when browsing, but it is important to understand if this change has created a new problem.

Thanks,
Richard

@lex
2008-04-03, 04:45
The new 7.0.1 nightly build is now available, you can down load this from http://www.slimdevices.com/dev_nightly.html. I am interested on your feedback, on bug 7376.

Richard

Hello Richard
I will download it now, but cannot test until tomorrow and give feedback.

Best regards

@lex

@lex
2008-04-03, 04:53
A three feet range is wrong. What is the SNR reported in Settings > Advanced Settings > Wireless Network > (Your network name)?

Richard

Hello Richard
Maybe this could be misunderstood. I don't mean, that the range is only 3 feet. I mean that when I test now, only in bedroom :-), the SBC is placed 3 feet away from (bridged) SBR and things seems to be running a little better. This is maybe due to the wlan power management. I run SC 7.0.1

Stormen
2008-04-03, 04:58
Just downloaded it, the remote took ages to update so I had to leave from home after lunchbreak, I'll get back within 4 ours after work to report.

Jeff Flowerday
2008-04-03, 07:09
I just downloaded 18321 and installed it, updated the remote when prompted.

It didn't fix it. I browse to a song, start it playing, sit the remote down for 20-30 seconds, pick it up hit back till I'm back at my artists, try entering an artist and all I get is the spinning >

I then hit back, wait a minute or two and the remote then allows me into that artist. If I don't hit back the spinning > will go on forever.

Kim.T
2008-04-03, 07:34
I have just updated both SqueezeCenter and Jive. It worked for approx 30sec the the blue Icon on the remote apeared. I but now instead of writing connecting to Squeezebox it says connecting to FreeNAS.local After booting the SBC FreeNAS doesn't appear on the list anymore (I can access the server using a browser)!
My SNR is 55-59 (54 mb/s)
NO-go from Denmark ;-)

UPDATE. After rebooting a couple of times the connection is a bit more stable. For the first time I was able to scroll through all 400 albums - showing pictures for all. But I still get "the spinnig arrow"

Stormen
2008-04-03, 08:21
I got it running without any hickups this time, I'll report back if it shows up any more later today.
http://forums.slimdevices.com/showthread.php?t=45328&page=2

JimC
2008-04-03, 19:11
Not all users have access for configuring their routers - mine is preconfigured and I don't have the PW. Squeezebox Duet should work "out of the box".

While we would very much like to have it work "out of the box" the reality of networking is that there are differences--sometimes significant--between routers and devices. We simply can't provide a guarantee that it will work in every single situation. We do our best to test as mnay configurations as possible, and certainly the most common ones, but even that won't predict all possible problems.

We are trying to gather as much information as possible, and are actively working on the problem. As Richard said, we've not been able to reproduce some of these problems in our facilities making it harder to find and fix. We have been making progress and will keep at it. Please continue to provide feedback as to what works and what doesn't so we can try to address the problem.

There's a new firmware build available and we'd appreciate it if you could test it out. Please see this message (http://forums.slimdevices.com/showpost.php?p=287121&postcount=23), which is part of this thread (http://forums.slimdevices.com/showthread.php?t=45168&page=3) for details.

-=> Jim

jason3fc
2008-04-03, 21:26
Trying the latest (2166) build just mentioned has made things much worse for me. I now can isolate this down to some problem with my receiver. I can connect to my wireless network with my controller just fine, and I can even find and control the SB1 in the bedroom fine every time. However the receiver is continually not getting an IP from dhcp every time I try to hold down the button to initiate a new connection. It flashes red, and then on the controller it does its thing when I tell it to set up, but every time it ends up getting a local 169.254 address. This happens with it connected via wired or wireless. Then when I try to find a music source, of course it cant find one, since it has no connection, and then the "Choose Player" disappears from the controller menu, and in order to get it to return I have to restart the controller.

I was by some fluke able to get the receiver connected once tonight, by doing the procedure above and then going to squeezecenter and the receiver showed up, and would even let me control it, even though it wasn't working via the controller. Once I queued something up for it to play via squeezecenter it then proceeded to show up on the controller and I could see it. But as soon as I switched to my bedroom SB1 and switched back to the receiver, sure enough it was gone again, and I couldn't control it or hear it from anywhere.

I was seriously considering putting two of these in the attic for sound into bathrooms, but I'm second guessing this now as it seems it doesn't reliably keep a connection.

This is the second or third time I have had a problem like this since I got it a few weeks back, previously I eventually got it connected again without explanation and it worked for several days straight (albeit with it dropping from the menu from time to time - as my original post stated, but I could always bring it back by rebooting the controller) now I'm back to this same situation with the receiver not getting an ip again.

Besides disabling DHCP on the router as described in the instructions is there a way to force it to use a static IP? I want to leave DHCP turned on for other stuff, but thinking maybe I can force the receiver into a static ip if possible.

jason3fc
2008-04-03, 21:39
Ok - Just an update to my last post. I just held down the button on the receiver and tried to reinitiate a connection via wireless. I was watching the config screen on my router showing DHCP leases, while standing and simultaneously watching the controller. As soon as it was done, I noted that in the DHCP list, the reciever had obtained a legitimate DHCP address: 192.168.1.135 and at the SAME time on the controller it shows that it got 169.254.140.78.. Weird. I then proceeded to try to connect to my squeezecenter and it worked! I unplugged my wired connection to do this, so Im not sure if something is wrong in my network, but I have 3 other devices which are getting IPs over wired DHCP just fine.

Nevertheless, the report of the local IP the controller gave me was wrong, since it really did get a valid IP.

Jeff Flowerday
2008-04-03, 22:47
I just downloaded 18321 and installed it, updated the remote when prompted.

It didn't fix it. I browse to a song, start it playing, sit the remote down for 20-30 seconds, pick it up hit back till I'm back at my artists, try entering an artist and all I get is the spinning >

I then hit back, wait a minute or two and the remote then allows me into that artist. If I don't hit back the spinning > will go on forever.

I just wanted to update my original comment. It seems after rebooting the controller one more time mine has been running much better. Tonight I could get it to stall at all.

Jeff Flowerday
2008-04-03, 23:27
jason3fc, have you tried unplugging the squeeze box and replugging it in and the holding down the button to get the red flashing light? I've had serious connection issues with mine on occasion and recycling the receiver(is that what we call it) solved it for me.

@lex
2008-04-04, 06:04
Hello Richard
I will download it now, but cannot test until tomorrow and give feedback.

Best regards

@lex

Hello Richard
Have now tried SqueezeCenter 7.0.1 - 18321 SBC = 2166
Have reset router, SBR, SBC, SB3's and SC.
It is a no go :-(
- Choose Album or artist and SBC stalling and blue indikator.
- Album list with thumbnails not complete (1/3 missing).

Have checked the router (ZyXEL), all units appear correct and with correct DHCP IP-adresses. Have also tried to change WLAN channel but no improvement.
Maybe I should try to go back to SC 7.0 ?

Best regards

@lex

rtitmuss
2008-04-04, 07:03
Great, it's good to hear that the last patch has fixed the connection issues for some people.

If you are still having problems I have added an option to disable wlan power save in 'Settings > Advanced Settings > Factory Test > Power Management' in 7.0.1 r2170. This can be used for testing, and as a workaround while further investigations into this problem are done. Please note that disabling wlan power save mode will reduce the battery life. This build should be available for testing tomorrow. If you do disable then wlan power save mode then please feedback if this fixed the problems you are seeing.

Thanks,
Richard

@lex
2008-04-04, 07:36
Great, it's good to hear that the last patch has fixed the connection issues for some people.

If you are still having problems I have added an option to disable wlan power save in 'Settings > Advanced Settings > Factory Test > Power Management' in 7.0.1 r2170. This can be used for testing, and as a workaround while further investigations into this problem are done. Please note that disabling wlan power save mode will reduce the battery life. This build should be available for testing tomorrow. If you do disable then wlan power save mode then please feedback if this fixed the problems you are seeing.

Thanks,
Richard

Hello Richard
Please release 7.0.1 r2170 right now :-) so I can test Power Management. Or e-mail release to amj@sj.dk

Best regards

@lex

jrichardson
2008-04-04, 14:13
I need to ask everyone having a Range Issue with their Controller, to please private message me the PID and MAC address of your controller, also the Version information (SC & PLayer) found in SC > Settings > Status

The PID and MAC can be found on a sticker in the battery compartment of your controller.

Thank you.

JimC
2008-04-04, 14:33
Hello Richard
Please release 7.0.1 r2170 right now :-) so I can test Power Management. Or e-mail release to amj@sj.dk

Best regards

@lex

You can always find the latest firmware for the Squeezebox Controller here:

http://www.slimdevices.com/downloads/nightly/latest/trunk/


-=> Jim

jason3fc
2008-04-04, 16:05
Ive tried everything now, and Im about ready to throw in the towel if logitech support is no help. My reciever just WILL NOT get an IP from my DHCP server, I have 5 other devices wired and wireless getting IPs fine via DHCP including another SB1. I have unplugged it, held the button in, to re search for the player, I have done a factory reset and tried that, I have tried plugging the thing directly into the router, no luck. The reciever just refuses now to get anything other than a local 169.254 address and the light on the front always ends up solid blue.

The lights on the back are flashing like there is activity, but still no go. Is there anyway at all to TELL the reciever to get a static IP besides disabling DHCP?

@lex
2008-04-04, 23:12
You can always find the latest firmware for the Squeezebox Controller here:

http://www.slimdevices.com/downloads/nightly/latest/trunk/


-=> Jim

Hello Jim
Yes, I know, but not 2170 today as promised

@lex

davidmac27
2008-04-05, 00:40
Excitement of receiving my Duet quickly faded two days ago after playing with it for about half an hour. This device still needs lots of stability work. The consumer side of me wants to rip Slim Devices a new one. The Product Manager side of me understands the complexity of releasing a device like this. So I will try to be constructive...

I had many of the issues listed in this 7 page posting. I initially connected to my home's wifi router. It is an Actiontec MI424-WR Rev C with the latest firmware from Verizon (FIOS). I had WEP 64 enabled. I now have 7.01 with the latest remote firmware (2167) and it did not seem to help things much.

After reading the posts here, I wired my Duet receiver to my router and setup an adhoc connection to the Duet with the remote. Once the remote is setup for a wifi network, there is no way to go back and tell it to connect via adhoc unless you factory reset the remote and then *also* press and hold the button on the receiver to reset it. The option to do an adhoc connection never appeared for me until I reset the receiver.

Things worked well for most of the evening. I could connect to all of my songs on my Mac Pro upstairs. Then my wife turned off the Mac. I couldn't access the music so I tried to connect to Squeeze Network. No matter what I tried, I could not connect to SN. I had a blue wifi signal on the remote and receiver. Finally, I turned off the remote and reset the receiver and was able to connect to Squeeze Network.

I would recommend you do lots of testing with the above scenario - where the PC or Mac in the home gets turned off - the Duet should be able to gracefully change networks. Maybe have an option in the remote so that when the Mac or PC with the music library gets turned off, the Duet automatically connects to the first internet radio station in the playlist or to some random internet radio pick (one from Staff Picks for example). That way, the music keeps playing.

This device has a lot of promise. It's too bad I feel like I am still beta testing this $432 device.

sapnho
2008-04-05, 03:13
Same "losing connection frequently" problem here. Using a WDS setting of 3 Airport Extreme in our house. No problem whatsoever with other wifi devices. WPA2 enabled.

OS: 10.5.2, SqueezeCenter 7.0.1

Very annoying especially given the comments from better half. Please fix quickly or my life will be miserable! :-))

Otherwise great device, althought the wheel is less responsive than an iPod but I guess that's a patent problem..

denmennis
2008-04-05, 18:56
I have been having similar connectivity issues with the Duet. For the past week, I have had to reset the receiver at least once a day to get the controller and receiver to reconnect. I know just enough about networking, which isn't much, to keep the Duet limping along. My knowledge pales in comparison to everyone who has posted on this tread so you can guess what kind of frustration that I've experienced with this product not to mention the amount of time wasted. This product is far from plug and play and comes no where close to fulfilling my expectations. My wife could never trouble shoot this device which really sort of kills it for me.

Now that I've gotten that off of my chest, I am loathe to give up. There is some sort of sadistic pleasure in digging into the bowels of your system to find the root of your troubles.

Just for the record, I am using a Time Capsule wired to my Intel iMac (OS X 10.5) and have an Airport Express for an access point from which the Duet recieves its wireless signal. And wouldn't you know it. I just went into Airport Utility to see what my settings were and it seems to be hiding from my network. I just love this.

SC 7.0.0

I have had to overcome bandwidth issues...converted to smaller MP3 files and changed channel to 9 to avoid potential interference and this has worked for me as long as the Duet is connected to the system and the controller to the receiver.

I have considered something like the Netgear wireless n access points (WNHDEB111), wiring one to the TC and the other to the SB and losing the AE altogether. I would like to hear what others think of this idea. Of course, if the Duet controller is flawed, there goes another $200.

Sorry to have gone on so long especially since I am technologically challenged
and have next to nothing to offer in the way of help.

dj

Jeff Flowerday
2008-04-05, 21:04
I have had to overcome bandwidth issues...converted to smaller MP3 files and changed channel to 9 to avoid potential interference and this has worked for me as long as the Duet is connected to the system and the controller to the receiver.


dj

When you mention this it makes me want to lay the blame with your wireless infrastructure more than the Duet.

davidmac27
2008-04-05, 23:51
I wish everyone would stop blaming wireless networks. While there may be some issues with some wifi network setups, the Duet has some serious bugs that I think could be the real cause of many of the issues listed here. I too have been having to do a factory reset daily since I bought this. I am now running 2171 and stability has not improved. I am connected adhoc to the receiver which is wired back to my router. Everything was working fine today. I was connected to my Mac upstairs where all of my music lives. Then my wife turned off the Mac and I lost the connection. OK, I thought, the beauty of this thing is that it doesn't require the PC to be on. So I tried to change the music source to SqueezeNetwork. No luck. I rebooted the remote. Tried to connect to SN - No luck. I rebooted the receiver. No luck. I repeated both of these about 3 times. No luck. I went upstairs and turned on the Mac. Finally I was able to connect.

Can the Duet not connect without SqueezeCenter running? When it loses its connection with SqueezeCenter, it seems to require that the unit be setup again (connect to the receiver, choose the music source...)

I would highly recommend doing a lot of testing when the receiver/remote are connected to a PC/Mac and then the computer is turned off. This seems to hose the entire device. It took me over 30 minutes to get everything up and running again. There is no way my wife or any other family member could use this device at this point. Such a shame.

Tiger
2008-04-06, 00:24
Yesterday, I upgraded to 2171 hoping that this Controller connectivity issue could be solved. No luck. Every couple of minutes, the signal strength indicator goes blue and reconnect fails most of the time. Switching the new "WLAN power save mode" on or off doesn't seem to have any effect, except when it's off, the battery drains quicker.
However, this is NOT a router issue, even though Slimdevices seems to indicate so. My Zyxel router/wlan AP works fine with:

- IBM T60 laptop
- Nokia N95 mobile phone
- Playstation 3 (even with worse signal strength)
- Canon MP800R wlan printer
- Duet Receiver (yes, the receiver works quite fine when controlled by SC / laptop FROM THE SAME LOCATION, where the Controller keeps dropping out)

So the suggestion to get another router is just plain ridiculous. I had such high expectations of the Squeezebox Duet system, and now I'm simply just very, very disappointed.

@lex
2008-04-06, 05:53
Upgraded:
SqueezeCenter version: 7.0.1 - 18409 @ Sat Apr 5 00:21:06 PDT 2008 - Windows XP - DA - cp1252, r2171

Choosing Settings/Advanced/Factory Test/Power management/
Sleep Timeout: 60
Suspend Timeout: 3600
Suspend Enabled: No
Suspend Wake: No
Wireless Power Save: No

Now things seems to be running. Have tested all my players for approx. 2 hours now without any stalling :-)

SBR: Wired
SB3-1 : Wireless, SNR=73% (downstairs)
SB3-2 : Wireless, SNR=95% (same room as AP)

Some bugs?
- When choosing Settings/Advanced/About nothing happens (not stalling)
- Album list. Some thumbnail coverarts missing. Choosing "default" thumbnail anyway cover art is shown correct in "Now Playing".
- The wireless indicator on SBC is constant red ! (but everything seems to work)

Best regards

@lex

Kim.T
2008-04-06, 07:16
I can't help ! I upgraded SqueezeCenter and tried to upgrade the controller wireless. Insted of an upgrade it downgraded to version r2097!!
I can't choose danish as language and my SD card is not recogniced anymore (the option to upgraded from SD card is not in the menu only wireless)!

kimbl
2008-04-06, 07:42
OK - I too have been following the upgrade trail on this issue. As yet not got to the bottom of it.
Here's some more data to add to the mix -

SqueezeCenter Version: 7.0.1 - 18409 @ Sat Apr 5 00:41:56 PDT 2008 - Debian - EN - utf8
SC remote 7.01 r2171

Belkin F5D7130 AP

Receiver on same wireless - this has apparently never dropped out - once started playing it's perfect, even after the controller has problems.

After a power-cycle on the remote all is fine, then after a few minutes the remote wireless icon goes blue, and it can't talk to the SqueezeCenter server.

The new "wireless power save off" options don't seem to change anything - other than battery life as you'd expect.

Watching general network connection with ping -t shows some oddities - generally successes are 4-5ms, and go for long periods. I have seen a couple of wierd 1400ms pings. When the screen dims there's no change in ping behaviour. Screen going off sometimes stops ping responses, sometimes not - I haven't properly got to the bottom of that yet.

After the connection icon's gone blue, the network seems ok - or at least reconnects correctly - both ping and SSH still work fine to the remote. But it seems something's wrong above the basic network layer, and the player has given up trying to get through to the SqueezeCenter server (which is itself fine - it's still playing out of the receiver, and web ok). This is even when it tries with the rotating dots and "connecting to..." - no change in icon when I can see the network layer is ok because SSH is still open.

I've been looking in the logs in /var/log/messages, (and can happily post same) but probably need more detail to make useful comment - which process is responsible for the server comms and I'll turn it up to debug level...!

PSSO
2008-04-06, 07:56
I can't help ! I upgraded SqueezeCenter and tried to upgrade the controller wireless. Insted of an upgrade it downgraded to version r2097!!
I can't choose danish as language and my SD card is not recogniced anymore (the option to upgraded from SD card is not in the menu only wireless)!

Try to check the SqueezeCenter Cache folder - is there a jive.version and jive_7.0.1_r2171.bin file ?

denmennis
2008-04-06, 08:50
Here is the latest episode in my saga. I got up this AM and went to check on Duet (this is getting to be as commonplace as feeding my dogs in the morning). Completely disconnected. I think she was out late last night and wanted to sleep in.

I clearly recognize that I need to ramp up my wireless network. That being said, I also realize that I am doing this primarily for my Duet since I can sit in the same room with my laptop without having any problems connecting to the network. I know that the laptop has a more robust antenna etc, etc.....so where is the inherent weakness really? I think it all depends on the way that you look at the problem. Is it the network which otherwise does everything that you expect or is it the wireless client that is the weak link?

If I had read this forum prior to ordering the Duet, I probably would have waited for the bugs to be ironed out or I would have gone in a different direction and not ordered the Duet at all. After coddling, nurturing and swearing at the Duet for almost 3 weeks now, its kind of like an old girlfriend. You may or may not like her, but its hard to let go. Lets face it, when it works , its can bring a smile to your face.

So I'm going to risk screwing up my network altogether and try to hack out a solution which I guess means that I won't be sending the Duet back. I have to agree with rtimuss. Each network is different and one solution does not work for all and I know that the Logitech people are trying to work on this.

Regards
dj

Kim.T
2008-04-06, 09:25
Try to check the SqueezeCenter Cache folder - is there a jive.version and jive_7.0.1_r2171.bin file ?

Which cache folder - I've 3 under SqueezeCenter (CPAN/cache, lib/cache and CPAN/Tie/cache).
I have the 2 mentioed files in the folder slimnas\var\squeezecenter

It would have been nice if there was a step-by-step guide to update JIVE using SSH.

FatClemenza
2008-04-06, 09:31
Same issues as everyone else. I downloaded the latest build which only served to make the controller angry.

Anyhoo, after rebooting the controller about 6 times it finally got a good connection and held it. I had been keeping track of the IP addresses of all my devices and the controller was always getting assigned to 199 until that last time. Once it was assigned to 197 it worked like a charm.

I'm no networking guru so I can't figure why it wasn't cooperating with 199. The only thing at all remarkable about 199 is that it's the last IP in the DHCP range.

I hope this helps.

Router: D-Link DIR-655
Go to: Setup > Network Settings to reserve an IP for the MAC address of the controller.

PSSO
2008-04-06, 10:15
Which cache folder - I've 3 under SqueezeCenter (CPAN/cache, lib/cache and CPAN/Tie/cache).
I have the 2 mentioed files in the folder slimnas\var\squeezecenter


On a Windows Server 2008/Vista machine it's c:\ProgramData\SqueezeCenter\Cache
Try to remove the SD card and then SBC should find the files in the cache folder. My SBC does.

PSSO
2008-04-06, 10:37
It would have been nice if there was a step-by-step guide to update JIVE using SSH.

http://wiki.slimdevices.com/index.cgi?SqueezeboxControllerSoftwareInstall

Kim.T
2008-04-06, 10:46
http://wiki.slimdevices.com/index.cgi?SqueezeboxControllerSoftwareInstallI know that page - but a description saying "you can fly to the moon - just get a rocket" is not good enough for me ;-)

Kim.T
2008-04-06, 10:53
On a Windows Server 2008/Vista machine it's c:\ProgramData\SqueezeCenter\Cache
Try to remove the SD card and then SBC should find the files in the cache folder. My SBC does.Yes but the problem with my setup is that the wireless connection is not stable - therefor I need to upgrade. But I can't upgrade because the wireless is unstable - and therefor I need to upgrade...........
When trying to upgrade the spinning wheel keeps on turning with the text "Coying update" and nothing happens.

PSSO
2008-04-06, 11:10
Yes but the problem with my setup is that the wireless connection is not stable - therefor I need to upgrade. But I can't upgrade because the wireless is unstable - and therefor I need to upgrade...........
When trying to upgrade the spinning wheel keeps on turning with the text "Coying update" and nothing happens.

Can see your problem. Then you have also tried a SBC Factory Reset and Firmware Update with a SD card ?

Kim.T
2008-04-06, 12:15
Yes serveral times. I also found the hint with holding the "volume up" button while booting. I still can't upgrade. Therefor I would like to try SSH, but as mentioned I need i LITTLE more information on how to do it.

sapnho
2008-04-06, 12:23
With yesterday's software update on the controller, things "appear" to be more stable. Let's wait and see. The idea behind the Duet is great and I have no doubt that the problems will be ironed out, it would just be nice if it wouldn't take too long.

BTW, to all people that have problems with the software update. I don't know why, but sometimes it just doesn't work at all, and sometimes it works no problem. It works great in the mornings (European time) but almost never in the evening. Why that is...

egg
2008-04-06, 12:52
I am also periodically having this problem. It seems to occur after several hours of continuous listening, or if I have not used the controller for sometime. The reciever seems to still be connected and I can control it with SqueezeCenter. The controller however acts like it can no longer find the receiver and or music source. Most of the time, unless I have just 3 choices, I can however still switch to my SB1 on the controller and use it fine and connect to squeezecenter there. The only way to reobtain a connection to the reciever with the controller is to turn off the controller and turn it back on.

Also have seen the exact same things that Forddonald just mentioned above.

SqueezeCenter: 7.01 (tried this in attempt to fix this, but was still having the issue with 7.0 final
SqueezeCenter Server: Standalone XP SP2 box.
Reciever: Wired or Wireless doesnt matter, Wired over CAT6 connected to a gigbit lan switch (Trendnet)
Network: WPA, SSID is not hidden
Router: Buffalo WHR-G54S

Same problem here.. If I don't touch the controller for a few hours it has to try and reconnect. It connects back about 50% of the time. Taking 10-45 min sometimes.

kimbl
2008-04-06, 15:03
Aha - further to earlier posts, I've now got a clean logfile from the controller after a reboot through playing and successful operations until it showed the "blue icon, no connection" fault. I'm becomming more convinced it's not actually a network layer fault, but something in the communications with SqueezeCenter after a network blip.

Seems to be normal operations - checking clocks, daily check of firmware etc, then the following - drops off, then errors during the DHCP negotation, which clear,

Apr 6 19:39:22 (none) daemon.notice wpa_supplicant[804]: WPA: Group rekeying completed with 00:30:bd:f2:40:04 [GTK=TKIP]
Apr 6 19:45:30 (none) user.info jive: (SqueezeboxJiveApplet.lua:152) - syncing system clock to hw clock: Sun Apr 6 19:45:30 2008
Apr 6 19:45:32 (none) user.info jive: (SqueezeboxJiveApplet.lua:155) - system clock now synced to hw clock: Sun Apr 6 19:45:32 2008
Apr 6 19:46:26 (none) user.err jive: (NetworkThread.lua:138) - network thread timeout for Task(SocketHttp {zebedee_Chunked}(R))
Apr 6 19:46:26 (none) user.err jive: (SocketHttp.lua:754) - SocketHttp {zebedee_Chunked}:t_rcvResponse.pump() error:inactivity timeout
Apr 6 19:46:26 (none) user.info jive: (Comet.lua:717) - Comet {zebedee}: _getEventSink error: inactivity timeout
Apr 6 19:46:26 (none) user.info jive: (Comet.lua:895) - Comet {zebedee}: handleAdvice state=CONNECTED
Apr 6 19:46:26 (none) daemon.notice wpa_supplicant[804]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Apr 6 19:46:26 (none) user.info jive: (NetworkThread.lua:248) - NOTIFY cometDisconnected: Comet {zebedee}, 0
Apr 6 19:46:26 (none) user.info jive: (SlimServer.lua:421) - SlimServer {zebedee} disconnected
Apr 6 19:46:26 (none) user.info jive: (NetworkThread.lua:248) - NOTIFY serverDisconnected: SlimServer {zebedee}, 0
Apr 6 19:46:26 (none) user.info jive: (Comet.lua:928) - Comet {zebedee}: advice is retry, connect in 3.446 seconds
Apr 6 19:46:26 (none) user.info jive: (SlimServers.lua:275) - Disconnecting from idle servers
Apr 6 19:46:26 (none) user.info jive: (SlimServer.lua:379) - SlimServer {SqueezeNetwork}:disconnect()
Apr 6 19:46:26 (none) user.notice root: wpa_action eth0 DISCONNECTED
Apr 6 19:46:27 (none) daemon.notice wpa_supplicant[804]: Trying to associate with xxx (SSID='AP_Brew' freq=2447 MHz)
Apr 6 19:46:28 (none) daemon.notice wpa_supplicant[804]: Associated with xxx
Apr 6 19:46:28 (none) local0.info udhcpc[992]: Received SIGTERM
Apr 6 19:46:28 (none) local0.info udhcpc[992]: Unicasting a release of 192.168.0.94 to 192.168.0.3
Apr 6 19:46:28 (none) local0.info udhcpc[992]: Sending release...
Apr 6 19:46:28 (none) user.notice root: udhcpc_action eth0 deconfig ip=
Apr 6 19:46:28 (none) local0.info udhcpc[992]: Entering released state
Apr 6 19:46:29 (none) daemon.notice wpa_supplicant[804]: WPA: Key negotiation completed with xxx [PTK=TKIP GTK=TKIP]
Apr 6 19:46:29 (none) daemon.notice wpa_supplicant[804]: CTRL-EVENT-CONNECTED - Connection to xxx completed (reauth) [id=0 id_str=]
Apr 6 19:46:29 (none) user.notice root: wpa_action eth0 CONNECTED
Apr 6 19:46:29 (none) user.err jive: (SocketTcp.lua:96) - SocketTcp:t_connect: Network is unreachable
Apr 6 19:46:29 (none) user.err jive: (SocketHttp.lua:223) - SocketHttp {zebedee_Chunked}:t_sendConnect: Network is unreachable
Apr 6 19:46:29 (none) user.info jive: (Comet.lua:717) - Comet {zebedee}: _getEventSink error: Network is unreachable
Apr 6 19:46:29 (none) user.info jive: (Comet.lua:895) - Comet {zebedee}: handleAdvice state=UNCONNECTED
Apr 6 19:46:29 (none) local0.info udhcpc[7249]: udhcpc (v1.7.1.svn) started
Apr 6 19:46:29 (none) user.notice root: udhcpc_action eth0 deconfig ip=
Apr 6 19:46:29 (none) local0.info udhcpc[7249]: Sending discover...
Apr 6 19:46:31 (none) local0.err udhcpc[7249]: bogus packet, option fields too long
Apr 6 19:46:31 (none) local0.err udhcpc[7249]: bogus packet, option fields too long
Apr 6 19:46:31 (none) local0.err udhcpc[7249]: bogus packet, option fields too long
Apr 6 19:46:31 (none) local0.err udhcpc[7249]: bogus packet, option fields too long
Apr 6 19:46:31 (none) local0.err udhcpc[7249]: bogus packet, option fields too long

<snip> - repeats

Apr 6 19:46:31 (none) local0.err udhcpc[7249]: bogus packet, option fields too long
Apr 6 19:46:31 (none) local0.err udhcpc[7249]: bogus packet, option fields too long
Apr 6 19:46:31 (none) local0.err udhcpc[7249]: bogus packet, option fields too long
Apr 6 19:46:31 (none) local0.err udhcpc[7249]: bogus packet, option fields too long
Apr 6 19:46:31 (none) local0.err udhcpc[7249]: bogus packet, option fields too long
Apr 6 19:46:31 (none) user.notice root: udhcpc_action eth0 zeroconf ip=169.254.136.162
Apr 6 19:46:32 (none) local0.info udhcpc[7249]: Sending discover...
Apr 6 19:46:32 (none) local0.info udhcpc[7249]: Sending select for 192.168.0.94...
Apr 6 19:46:32 (none) local0.info udhcpc[7249]: Lease of 192.168.0.94 obtained, lease time 43200
Apr 6 19:46:32 (none) user.notice root: udhcpc_action eth0 bound ip=192.168.0.94
Apr 6 19:54:12 (none) daemon.notice wpa_supplicant[804]: WPA: Group rekeying completed with xxx [GTK=TKIP]

Then it's on the network (SSH and ping work fine) but blue "no connection" and no ability to reconnect.

jason3fc
2008-04-06, 20:34
I finally figured I could get mine back up and running with a "hard reset" on the receiver.. Holding the button down longer than 12 secs. It came back on, and I was able to reconnect it with wired connection, it got a proper address from DHCP and started working. It worked all night friday, I left for the weekend and came back and sure enough the light was blue and it was disconnected. However, the controller was still connected, and had been the entire time. Im starting to see unlike some of the others here, my controller stays connected fine, its my receiver that keeps losing connection. I did a hard reset on it again, and downloaded the most recent controller firmware, and I was able to reconnect it. Ill see if it still connected in the morning. Unlike a lot of others here, my controller works fine, it definitely the receiver im having problems with.

spence
2008-04-06, 22:57
My latest problem sounds similar to everything here, but it's not quite the same. My SBC has been working fine up until this evening when it lost contact with my SB Duet. I've tried rebooting the SBC, I've tried removing and re-inserting its batteries, I've tried updating the software, but nothing I can do will get it to reconnect.

I've also tried connecting it to the other device in the house (a Squeezebox) and it won't connect to that either.

My SBC, Duet and SB are all connected to the Squeezenetwork, and I almost exclusively play music from Rhapsody, which is what I was playing when the problem occurred this evening. I run Squeezecenter on my (Vista) PC as well, but I cannot get the SBC to connect to that either.

It's not a local network problem. All my devices are connected over WiFi, but I can see from the router's IP tables that they all have IP addresses, and I can in fact ping them all.

The SBC is running version 7.0 r2097, even after downloading a s/w update from the network (yes, it downloads 100%, verifies, and reboots).

What's my next step?

Tiger
2008-04-07, 01:43
Aha - further to earlier posts, I've now got a clean logfile from the controller after a reboot through playing and successful operations until it showed the "blue icon, no connection" fault. I'm becomming more convinced it's not actually a network layer fault, but something in the communications with SqueezeCenter after a network blip.



Hi, can you give details, how you got the log? I'd like to compare my findings.

Tiger
2008-04-07, 02:13
Aha - further to earlier posts, I've now got a clean logfile from the controller after a reboot through playing and successful operations until it showed the "blue icon, no connection" fault. I'm becomming more convinced it's not actually a network layer fault, but something in the communications with SqueezeCenter after a network blip.

Seems to be normal operations - checking clocks, daily check of firmware etc, then the following - drops off, then errors during the DHCP negotation, which clear,

Apr 6 19:39:22 (none) daemon.notice wpa_supplicant[804]: WPA: Group rekeying completed with 00:30:bd:f2:40:04 [GTK=TKIP]
Apr 6 19:45:30 (none) user.info jive: (SqueezeboxJiveApplet.lua:152) - syncing system clock to hw clock: Sun Apr 6 19:45:30 2008
Apr 6 19:45:32 (none) user.info jive: (SqueezeboxJiveApplet.lua:155) - system clock now synced to hw clock: Sun Apr 6 19:45:32 2008
Apr 6 19:46:26 (none) user.err jive: (NetworkThread.lua:138) - network thread timeout for Task(SocketHttp {zebedee_Chunked}(R))
Apr 6 19:46:26 (none) user.err jive: (SocketHttp.lua:754) - SocketHttp {zebedee_Chunked}:t_rcvResponse.pump() error:inactivity timeout
Apr 6 19:46:26 (none) user.info jive: (Comet.lua:717) - Comet {zebedee}: _getEventSink error: inactivity timeout
Apr 6 19:46:26 (none) user.info jive: (Comet.lua:895) - Comet {zebedee}: handleAdvice state=CONNECTED
Apr 6 19:46:26 (none) daemon.notice wpa_supplicant[804]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Apr 6 19:46:26 (none) user.info jive: (NetworkThread.lua:248) - NOTIFY cometDisconnected: Comet {zebedee}, 0
Apr 6 19:46:26 (none) user.info jive: (SlimServer.lua:421) - SlimServer {zebedee} disconnected
Apr 6 19:46:26 (none) user.info jive: (NetworkThread.lua:248) - NOTIFY serverDisconnected: SlimServer {zebedee}, 0
Apr 6 19:46:26 (none) user.info jive: (Comet.lua:928) - Comet {zebedee}: advice is retry, connect in 3.446 seconds
Apr 6 19:46:26 (none) user.info jive: (SlimServers.lua:275) - Disconnecting from idle servers
Apr 6 19:46:26 (none) user.info jive: (SlimServer.lua:379) - SlimServer {SqueezeNetwork}:disconnect()
Apr 6 19:46:26 (none) user.notice root: wpa_action eth0 DISCONNECTED
Apr 6 19:46:27 (none) daemon.notice wpa_supplicant[804]: Trying to associate with xxx (SSID='AP_Brew' freq=2447 MHz)
Apr 6 19:46:28 (none) daemon.notice wpa_supplicant[804]: Associated with xxx
Apr 6 19:46:28 (none) local0.info udhcpc[992]: Received SIGTERM
Apr 6 19:46:28 (none) local0.info udhcpc[992]: Unicasting a release of 192.168.0.94 to 192.168.0.3
Apr 6 19:46:28 (none) local0.info udhcpc[992]: Sending release...
Apr 6 19:46:28 (none) user.notice root: udhcpc_action eth0 deconfig ip=
Apr 6 19:46:28 (none) local0.info udhcpc[992]: Entering released state
Apr 6 19:46:29 (none) daemon.notice wpa_supplicant[804]: WPA: Key negotiation completed with xxx [PTK=TKIP GTK=TKIP]
Apr 6 19:46:29 (none) daemon.notice wpa_supplicant[804]: CTRL-EVENT-CONNECTED - Connection to xxx completed (reauth) [id=0 id_str=]
Apr 6 19:46:29 (none) user.notice root: wpa_action eth0 CONNECTED
Apr 6 19:46:29 (none) user.err jive: (SocketTcp.lua:96) - SocketTcp:t_connect: Network is unreachable
Apr 6 19:46:29 (none) user.err jive: (SocketHttp.lua:223) - SocketHttp {zebedee_Chunked}:t_sendConnect: Network is unreachable
Apr 6 19:46:29 (none) user.info jive: (Comet.lua:717) - Comet {zebedee}: _getEventSink error: Network is unreachable
Apr 6 19:46:29 (none) user.info jive: (Comet.lua:895) - Comet {zebedee}: handleAdvice state=UNCONNECTED
Apr 6 19:46:29 (none) local0.info udhcpc[7249]: udhcpc (v1.7.1.svn) started
Apr 6 19:46:29 (none) user.notice root: udhcpc_action eth0 deconfig ip=
Apr 6 19:46:29 (none) local0.info udhcpc[7249]: Sending discover...
Apr 6 19:46:31 (none) local0.err udhcpc[7249]: bogus packet, option fields too long
Apr 6 19:46:31 (none) local0.err udhcpc[7249]: bogus packet, option fields too long
Apr 6 19:46:31 (none) local0.err udhcpc[7249]: bogus packet, option fields too long
Apr 6 19:46:31 (none) local0.err udhcpc[7249]: bogus packet, option fields too long
Apr 6 19:46:31 (none) local0.err udhcpc[7249]: bogus packet, option fields too long

<snip> - repeats

Apr 6 19:46:31 (none) local0.err udhcpc[7249]: bogus packet, option fields too long
Apr 6 19:46:31 (none) local0.err udhcpc[7249]: bogus packet, option fields too long
Apr 6 19:46:31 (none) local0.err udhcpc[7249]: bogus packet, option fields too long
Apr 6 19:46:31 (none) local0.err udhcpc[7249]: bogus packet, option fields too long
Apr 6 19:46:31 (none) local0.err udhcpc[7249]: bogus packet, option fields too long
Apr 6 19:46:31 (none) user.notice root: udhcpc_action eth0 zeroconf ip=169.254.136.162
Apr 6 19:46:32 (none) local0.info udhcpc[7249]: Sending discover...
Apr 6 19:46:32 (none) local0.info udhcpc[7249]: Sending select for 192.168.0.94...
Apr 6 19:46:32 (none) local0.info udhcpc[7249]: Lease of 192.168.0.94 obtained, lease time 43200
Apr 6 19:46:32 (none) user.notice root: udhcpc_action eth0 bound ip=192.168.0.94
Apr 6 19:54:12 (none) daemon.notice wpa_supplicant[804]: WPA: Group rekeying completed with xxx [GTK=TKIP]

Then it's on the network (SSH and ping work fine) but blue "no connection" and no ability to reconnect.


Obviously, the DHCP process is failing. By the way, is the Controller supposed to release it's DHCP lease like that in the first place? I mean, when it goes into idle mode?

fcm4711
2008-04-07, 02:20
Hi there

I understand you have your SBR connected wired to your network. Is it also correct that your SC7 is running 24/7? Or do you stop your PC over night?
If the next time SBR is stuck with a blue light could you just try to powercycle it to see if it then connects again?

Thanks
Felix



I finally figured I could get mine back up and running with a "hard reset" on the receiver.. Holding the button down longer than 12 secs. It came back on, and I was able to reconnect it with wired connection, it got a proper address from DHCP and started working. It worked all night friday, I left for the weekend and came back and sure enough the light was blue and it was disconnected. However, the controller was still connected, and had been the entire time. Im starting to see unlike some of the others here, my controller stays connected fine, its my receiver that keeps losing connection. I did a hard reset on it again, and downloaded the most recent controller firmware, and I was able to reconnect it. Ill see if it still connected in the morning. Unlike a lot of others here, my controller works fine, it definitely the receiver im having problems with.

jason3fc
2008-04-07, 07:10
My Squeezecenter pc is running 24/7 and has been online for several days at this point. Do you mean cycle the power on the receiver or the squeezecenter server? I have tried this with the receiver each time I got a blue light. This does not work and it comes back on and ends up with a blue light again. I will try this one more time the next time the receiver loses connection just to be sure.

davidmac27
2008-04-07, 07:57
I have tried this with the receiver each time I got a blue light. This does not work and it comes back on and ends up with a blue light again.

I was also having this problem. I finally read that you can hold the center button on the receiver down for 12 seconds to hard reset the receiver. Previously, I would hold it down for about 3-4 seconds before I saw the red light slowly blink. But if you keep holding it in, it will start to blink fast red. Doing this, combined with a factory reset on the remote, allowed me to connect up again.

Kind of reminds me of playing Twister with my kids (;-)

kimbl
2008-04-07, 13:58
@Tiger,
In no particular order: - Yes I think it is supposed to release the DHCP lease - in the deeper sleep the wifi drivers are unloaded, and a DHCP release is the civilised way to start I guess.

Secondly I think it's not a simple DHCP fail - yes there are the errors, but then it succeeds - and the network reconnects - ping and SSH are fine, but it won't reconnect to SqueezeCenter.

Log obtained by logging in to the controller over ssh - I used SCP to copy it off, but you could just copy/paste it from the SSH terminal screen. log is in /var/log/messages

rtitmuss
2008-04-07, 15:17
Obviously, the DHCP process is failing. By the way, is the Controller supposed to release it's DHCP lease like that in the first place? I mean, when it goes into idle mode?

Actually it looks like the wireless connection is failing, the following line in the log shows the disconnection. The Controller will request a new lease after the wlan is reconnected.


Apr 6 19:46:26 (none) daemon.notice wpa_supplicant[804]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

@kimbl did you mention what type of router you have? Can you try disabling wireless power management (instructions are earlier in this thread), does that help.

I made some progress with bug 7489 (Controller does not always reconnect to SqueezeCenter today). Hopefully will have a fix tomorrow.

Richard

kimbl
2008-04-07, 15:52
AP is a Belkin F5D7130b - 802.11g only on channel 8. Other network in the area (not mine) on channel 1).

DHCP and DNS actually run from dnsmasq on another network box not from the AP itself - so I can look at those logs if you like. There's no specific configuration for the controller or receiver it's just in the dynamic range.

Disabling the wifi power managment didn't seem to make any difference - the testing yesterday (and logs) were with that off:
Sleep 60
Suspend timeout 3600
Suspend enabled on
Suspend wake off
Wireless power save off

If there's anything I can log / test to help your bugfixing, let me know...

I thought I was onto something after incidentally rebooting the debain box that runs SqueezeCenter today for the first time in months (new virtualbox kernel modules) and the controller hadn't dropped all afternoon while I was at work - but it's just gone blue while I was typing this - so that wasn't it!

@lex
2008-04-07, 23:21
Hello kimbl

SqueezeCenter version: 7.0.1 - 18409 @ Sat Apr 5 00:21:06 PDT 2008 - Windows XP - DA - cp1252, r2171

When I made the changes in power management my setup startet to work and has been stable since saturday.

Choosing Settings/Advanced/Factory Test/Power management/
Suspend Enabled: No

I don't know what "Suspend Enabled" does, but maybe also try do switch it off.

The wireless indicator on SBC is now constant red ! (but everything seems to work). Maybe Richard could tell if this is correct in r2171 with power management turned off.

You should also try to reset everything (shut down all devices), start router, start AP, start DHCP server, start Squeezecenter, start Squeezeboxes, start Receiver, start Controller etc.

Best regards and good luck.

@lex

fcm4711
2008-04-08, 00:30
Hi jason3fc

I meant power cycling Receiver. Anyhow, I would like you to do the following test if you don't mind. Setup your SBR (with SBC) so it has a dark white light (paused). Now, disconnect power from SBR, wait 10 seconds and reapply power. Does it go to dark white again or is it also stuck on blue?

Thanks
Felix

@lex
2008-04-08, 10:27
SqueezeCenter version: 7.0.1 - 18409 @ Sat Apr 5 00:21:06 PDT 2008 - Windows XP - DA - cp1252, r2171

When I made the changes in power management my setup startet to work and has been stable since saturday.

Choosing Settings/Advanced/Factory Test/Power management/
Suspend Enabled: No

I don't know what "Suspend Enabled" does, but maybe also try do switch it off.

The wireless indicator on SBC is now constant red ! (but everything seems to work). Maybe Richard could tell if this is correct in r2171 with power management turned off.

@lex

Still no response from SlimDevices development team :-) Maybe you are very busy solving bugs :-(
What is happening? Do you find solutions? Some information would be nice :-) I don't dare upgrade now as my system seems to be running (with minor errors), but what about all the other desperate users with no solution and no enjoy

PS: Today wlan indicator is white ! And still running ok, not perfect, but ok :-)

Best regards

@lex

PSSO
2008-04-08, 10:38
Still no response from SlimDevices development team :-) Maybe you are very busy solving bugs :-(
What is happening? Do you find solutions? Some information would be nice :-) I don't dare upgrade now as my system seems to be running (with minor errors), but what about all the other desperate users with no solution and no enjoy

PS: Today wlan indicator is white ! And still running ok, not perfect, but ok :-)

Best regards

@lex

Don't stress the development team. They are doing a great job.

Maybe you should contact technical support - http://www.slimdevices.com/su_tech.html

@lex
2008-04-08, 10:53
Don't stress the development team. They are doing a great job.

Maybe you should contact technical support - http://www.slimdevices.com/su_tech.html

Hmmmm. I don't know ... I'm soon tired of betatesting a consumer product, that should function out off the box, plug''play without major errors and the need to be a Cisco Network Associate Technician to make i work !

Kim.T
2008-04-08, 11:35
I got an answer that they where investigating HW issues.......
And I guese that nerwork errors not are simple to reproduce or predict - they can't test every router before they release a product.

Armand
2008-04-08, 12:13
My story is similar to most previous ones, but maybe it contributes to the solutions:
I've two SB classics working fine, my new SB receiver works fine as well, but the SB controller doesn't. Somehow it can't connect to my computer/server.
I've rebooted the SB receiver, rebooted my computer, rebooted my Belkin router, set the SB controller back to factorty settings, changed the Wireless Channel, but when I try run the SB Controller setup it finds my wireless network and my receiver, but can't connect to the computer as a music source. The message (Couldn't connect your SB to your wireless network) I find rather strange, since it first connects to my network (at least the controller says it does) and then fails to connect to the computer. Furthermore running updates for the controller looks fine (copying updates, verifying and restarting), but the version nummer stays the same: 7.0 r2097. Therefore turning off power management isn't an option.

Suprisingly connecting to the Squeezenetwork does work and the SB receiver is visible (I can turn it off, change Player name, etc.).

So the actual problem appears to be the connection between the SBController to my computer.
I can't think of anything which would be wrong in my computer settings, since both the SBreceiver and controller appear in the router's DHCP Client List and I can ping and trace(rt) it.

My configuration:
OS pc: Windows 2000 professional
Belkin Router
2 classical Squeezeboxes working fine
Wireless mode: 54G-Auto
Security Mode: 128bit WEP

I guess I tried everything possible. Though if anyone still has suggestion, please let me know.

rtitmuss
2008-04-08, 12:25
Still no response from SlimDevices development team :-) Maybe you are very busy solving bugs :-(

Give me a chance, I last posted an update yesterday. And yes today I have been busy fixing bugs, I'll post when I have information to report. The connectivity bugs are our top priority right now, and as I have said before they are not trivial or quick to recreate and fix.

I now think that Bug 7489 is fixed, and will be in tomorrows nightly Controller firmware. This bug would sometimes cause the wireless icon to go blue (that indicates that the connection to SqueezeCenter is lost), and not recover until after the Controller was rebooted.


PS: Today wlan indicator is white ! And still running ok, not perfect, but ok :-)

I am glad that the workaround I added for the Zyxel (and other?) routers is effective. What do you think is still not perfect?

I now have a Zyxel router in my office, and will start investigating the compatibility problems in more detail tomorrow. I am expecting this is a _hard_ problem, so don't expect a quick turnaround on this bug.

Richard

rtitmuss
2008-04-08, 12:27
Suprisingly connecting to the Squeezenetwork does work and the SB receiver is visible (I can turn it off, change Player name, etc.).

That sounds like you may have a firewall or networking problem. I suggest you initially contact support to see if they can help you get your Controller connected.

Richard

rtitmuss
2008-04-08, 12:45
I got an answer that they where investigating HW issues.......

To be clear we are investigating a possible manufacturing fault with a small batch of units, not a hardware design issue.


And I guese that nerwork errors not are simple to reproduce or predict - they can't test every router before they release a product.

This is correct, we did test with lots of routers before shipping but it's impossible to get complete coverage.

Richard

mellie
2008-04-08, 12:45
I am looking in the /latest/trunk dir but i cannot find the lates jive.bin file to update the controller. I also cannot find it in the .tgz archive? Where is the 7.01 rxxxx firmware for the controller located?

Edit: i now see that the version i get to see in the latest/trunk dir is not the one that is talked about here. I get 7.01 r18530 and not the version that is mentioned in this thread.. Any ideas why?

Edit2: Or am I mixing release numbers up? I do know that i cannot find a firmware file for the controllers at all in the current release?

Melle...

Armand
2008-04-08, 13:25
That sounds like you may have a firewall or networking problem. I suggest you initially contact support to see if they can help you get your Controller connected.

Richard,
Thanks for your reply.
I haven't contacted the support desk yet, since I'm looking for updating my controller via SSH first.
SSH works fine: through SSH I can ping all devices including the server. So I guess there's no network issue. Correct?
Only thing now is waiting for a new(er) jive.bin so I can update the controller and hoping that will be the solution to my problem.

@lex
2008-04-08, 14:29
Give me a chance, I last posted an update yesterday. And yes today I have been busy fixing bugs, I'll post when I have information to report. The connectivity bugs are our top priority right now, and as I have said before they are not trivial or quick to recreate and fix. Richard

Sorry Richard, I didn't mean to insult you :-) I know you are working hard on fixing bugs. It's rather frustrating for everyone. I think maybe a 1 or 2 daily status reports like this would be nice? Which problems are solved by which release etc.



I am glad that the workaround I added for the Zyxel (and other?) routers is effective. What do you think is still not perfect? Richard

Yes, it seems that turning of wlan power management according to ZyXEL routers have made my system functional :-)

Still there are a lot of (minor) other bugs in this GREAT system:

- The wlan indicator on the Controller has been red for 4 days and now it is white, why?
- Turning of wlan power managment means less battery capacity.
- All album art thumbnails is not shown in the Album List on the Controller (another bug fix).
- Favorites doesn't include SC content automaticaly, need to change source.
- Album sort by Artist and not only Album Name.
- More Receiver and Controller settings and status in SqueezeCenter.
- Just check out the forum, there are a lot of error messages and improvement suggestions.

Regard this as positive and creative :-)

Best regards (and keep on going)

@lex

JimC
2008-04-08, 15:06
Sorry Richard, I didn't mean to insult you :-) I know you are working hard on fixing bugs. It's rather frustrating for everyone. I think maybe a 1 or 2 daily status reports like this would be nice? Which problems are solved by which release etc.

And, Alex, I don't mean to insult you, but your issue--while very important--may not be the #1 item on someone's to-do list today. We have to balance a huge number of things: bug fixes, new product development, enhancement requests, personal lives, sleep, vacations, etc., in setting priorities.

Also, these forums are not the official avenue for support. We do monitor them, and try to participate in them as much as possible, but that happens only when we can (and not necessarily every day). We try to provide status when it works out from a time and information perspective, but your best bet is to subscribe to the specific bugs you're interested in so you will receive an update when there are changes made or when it is closed. An automated process like bugzilla will beat out a human-made post here almost every single time.


-=> Jim

Kim.T
2008-04-08, 23:06
I now think that Bug 7489 is fixed, and will be in tomorrows nightly Controller firmware. This bug would sometimes cause the wireless icon to go blue (that indicates that the connection to SqueezeCenter is lost), and not recover until after the Controller was rebooted.

Richard

Great - that is the biggets problem I have.

Kim.T
2008-04-09, 03:56
I've just installed r2178 and it looks very good! The controller re-connects after the "blue icon" and played-time and remaining time is updated on the screen.
Just one little issue - I vent into the Factory Test menu to verify the WLAN/power setting and the controller did a complet reset after pressing the "Factory test"!
Go for it......

MrSinatra
2008-04-09, 05:24
yep i see the new ver here:

http://www.slimdevices.com/downloads/nightly/latest/trunk/

but my controller isn't saying there is a new version available for me.

so did yours get it off the website or did you DL the new nightly of SC7 and it got it from there?

Kim.T
2008-04-09, 05:30
yep i see the new ver here:

http://www.slimdevices.com/downloads/nightly/latest/trunk/

but my controller isn't saying there is a new version available for me.

so did yours get it off the website or did you DL the new nightly of SC7 and it got it from there?
No either copy it to an SD card or enable SSH on the SBC and copy the file using the program WinSCP

MrSinatra
2008-04-09, 05:44
very strange...

i had r2171 and it wasn't telling me newer stuff was available, (ie. 2178).

so i downloaded and installed the newest SC7 (18576) and still got no message anything was newer.

so then i did a factory reset, and when it connected to my network, it immediately said newer stuff was available, and this then gave me r2178

but i had to do the reset, and unfortunately i didn't check right after the reset but b4 the update to see what ver it was at that moment.

Jeff Flowerday
2008-04-09, 07:03
very strange...

i had r2171 and it wasn't telling me newer stuff was available, (ie. 2178).

so i downloaded and installed the newest SC7 (18576) and still got no message anything was newer.

so then i did a factory reset, and when it connected to my network, it immediately said newer stuff was available, and this then gave me r2178

but i had to do the reset, and unfortunately i didn't check right after the reset but b4 the update to see what ver it was at that moment.

Installed the latest SC 7.0.1 and just turned off my control. On restart it asked to update.

Kim.T
2008-04-09, 10:23
Just an update: it's still not perfect - but it's getting better. When laying the remote in the Kitchen - 12m from the Router - most of the time it reconnects (after the blue icon). But I've had a few blue icons where the controller didn't reconnect and I had to boot the controller - even if i walked into the studdy where the router is. It seems that the longer the controller lays on the table witout beeing operated - it gets dificulter to get re-connected (I guess that the SBC was laying on the table for 5-10min).

Ben Sandee
2008-04-09, 10:30
On Wed, Apr 9, 2008 at 12:23 PM, Kim. T <
Kim.T.37m1fn1207761901 (AT) no-mx (DOT) forums.slimdevices.com> wrote:

>
> Just an update: it's still not perfect - but it's getting better. When
> laying the remote in the Kitchen - 12m from the Router - most of the
> time it reconnects (after the blue icon). But I've had a few blue icons
> where the controller didn't reconnect and I had to boot the controller -
> even if i walked into the studdy where the router is. It seems that the
> longer the controller lays on the table witout beeing operated - it
> gets dificulter to get re-connected (I guess that the SBC was laying on
> the table for 5-10min).


I had this happen today for the first time ever, was using r2171 I think. I
wasn't sure what the blue icon even meant. Mine was in the charger
overnight -- and maybe coincidentally my SqueezeCenter crashed overnight. I
restarted SqueezeCenter this morning and all my players reconnected fine,
but the controller required a hard reboot (and then it automatically updated
to r2178).

Ben

Tiger
2008-04-09, 14:10
Just upgraded the controller to latest 2178.

Still getting the blue icon occasionally. Perhaps it now is able to reconnect slightly better, but there are still long periods of unresponsiveness.

Couple of questions:

- I'd like to SSH into to controller to look at logs. Seem unable to. What port should I use?

- When pinging the controller, when it does respond (which is not always - when it has lost connection, obviously I get "request time out") I get really big variations in RTT. Up to 3000 ms in some cases. Is this normal?

davidmac27
2008-04-09, 19:45
I am now running firmware 23 and build 2178 on the remote with SC 18576. This has been the worst build for me yet. I have the SBC wired to my home router. I am connecting the remote to the SBC adhoc. After updating the remote this morning, I had my Mac on. I reset the SBC and then factory reset the remote. The remote found the SBC and I chose a wired connection. It completed successfully and I could access the music on my Mac and listen to internet radio. Life was good. I turned off the SBC with the remote and placed the remote in the cradle and went to work. I came home tonight and decided to listen to some music during dinner. I spent the entire dinner trying to connect the remote to the SBC via adhoc connection. This included about 4 factory resets and 4 trips to the SBC to reset it (8 feet away). It would find the controller fine but would error out saying it could not connect wirelessly. Note to developers - you say to hold the SBC button until it blinks red. After a few seconds it blinks red slowly and then if you keep holding for another 3 or so seconds, it starts blinking red quickly. Is there a difference between these two modes? If so, you need to clarify for users or this could be causing problems. I always hold the button until I see a fast blink.

The only difference between my unsuccessful attempts at trying to connect this evening compared to this morning was that my Mac was on this morning. Tonight during dinner, when I just wanted to listen to Internet radio, the Mac (where the MP3's live) was off. That shouldn't matter for initial connection/setup - right???

So I went upstairs and turned on my Mac. Reset remote, reset SBC. Still would not connect. Then I decided to try connecting to my wireless network. I was able to successfully connect and listen to my MP3's and Internet radio. The only problem with this setup is I often run into delays of up to 30 seconds when I change the volume.

Is adhoc mode now broken? What should I try to make it work again?

Note to developers, PMs, marketing, and Slim executives. I have been working as a Product Manager in high tech companies for almost 15 years (Intel, Xircom, and a slew of telephony start-ups). I have been involved in numerous 3rd party software betas (Win95-XP) and hardware betas. I'm even in charge of running beta programs. The Squeezebox Duet is by far the most unstable product I have ever used in my entire life. It reminds me of several Alpha stage devices. It is very disappointing to see such an immature product released. In fact, it is perhaps very telling about the state of affairs at Logitech/Slim Devices. I cannot see any respectable product development team releasing such a bug-ridden product. Was there pressure by upper management to get this thing out the door before the end of the quarter to make the numbers? The Duet has sooo much going for it. It is just a shame that you had to release this thing in the state that it is in.

JimC
2008-04-09, 20:32
After a few seconds it blinks red slowly and then if you keep holding for another 3 or so seconds, it starts blinking red quickly. Is there a difference between these two modes? If so, you need to clarify for users or this could be causing problems. I always hold the button until I see a fast blink.

Slow red is a soft reset; fast red is a factory reset.



Note to developers, PMs, marketing, and Slim executives. I have been working as a Product Manager in high tech companies for almost 15 years (Intel, Xircom, and a slew of telephony start-ups). I have been involved in numerous 3rd party software betas (Win95-XP) and hardware betas. I'm even in charge of running beta programs. The Squeezebox Duet is by far the most unstable product I have ever used in my entire life. It reminds me of several Alpha stage devices. It is very disappointing to see such an immature product released. In fact, it is perhaps very telling about the state of affairs at Logitech/Slim Devices. I cannot see any respectable product development team releasing such a bug-ridden product. Was there pressure by upper management to get this thing out the door before the end of the quarter to make the numbers? The Duet has sooo much going for it. It is just a shame that you had to release this thing in the state that it is in.

I've been at this for a few more years than you and have seen my share of bad products go out the door at several companies. I know enough to know that any short-term gain from rushing a product out is more than offset by the ill-will and expense associated with a bad experience.

While you have no reason to believe me, I can assure you that we did not release a bug-ridden product. You can see all of our reported bugs at bugs.slimdevices.com -- there are 26 open bugs marked with a severity of Major, Critical, or Blocker and only 4 of these are not yet fixed or resolved.

The number of customers with problems posting on our forums is a *fractional* percentage of the installed products. As our 2nd-tier technical support group is under my department, I see their incident reports and there is nothing more than the expected increase in calls that you would have with any new product launch.

That's not to say you're not experiencing a problem, but you are a corner case. With your level of experience you should know that. You should also know that it is literally impossible to test every possible combination of hardware and software that gets used in the field. We use internal and external testing programs to try to minimize the number of problems, but there will always be something unique out there that wreaks havoc with any given product.

Have you contacted our technical support group? It's entirely possible that you have a unit with an intermittent failure on the wireless card, or some other problem. If I were an agent, I would have already provided an RMA for your unit and I know our team would have done the same thing. I'd really like to have your particular product back here for analysis -- please contact me via email (see my profile for my email address) and I will have one of my support agents issue you an RMA.

You're painting the product and the team (both here and in the community) with a very wide brush, when the reality is that the vast majority of customers are not having the same level of difficulty you are. I'm not trying to trivialize the problems you're experiencing, but I can say without equivocation that your experience is far from the norm.


-=> Jim

MrSinatra
2008-04-09, 20:34
i'd suspect that ad hoc mode might be the root of the issue.

not suggesting it shouldn't work, it should, but it might take a while to get it going as its a very small amount of people who use it that way i'd suspect.

can you temporarily set it up via dhcp on a router and see what its like then?

Kim.T
2008-04-09, 23:08
[QUOTE=Tiger;289624]

- I'd like to SSH into to controller to look at logs. Seem unable to. What port should I use?
QUOTE]
Port 22
User: root
Pw: 1234

sapnho
2008-04-09, 23:13
Used to have 2171 and it was working pretty good without a freeze. After the upgrade to 2178 things are back to square one with frequent freezes. Well, I guess that should at least silence the talk about the routers being the problem once and forever.

Better luck, next upgrade. :-((

JimC
2008-04-09, 23:23
Used to have 2171 and it was working pretty good without a freeze. After the upgrade to 2178 things are back to square one with frequent freezes. Well, I guess that should at least silence the talk about the routers being the problem once and forever.

Better luck, next upgrade. :-((

Hmmm... I don't recall anyone stating routers are the problem. I think it was more like we are having problems with some routers and are investigating them with an eye toward fixing the problems. The SBC does not have problems with all routers; I regularly use 4 different routers with all our products and don't have any of the issues that some users are experiencing.

As to your most recent experience, please be aware that the nightly builds are beta and do not undergo the same level of testing (especially regression testing) as a production build. It is possible that fixing one problem creates a new one or even resurrects an old one. It would be great if you could continue to provide constructive feedback on the bug(s) that are affecting you so we can work on finding and addressing the root cause.


-=> Jim

sapnho
2008-04-09, 23:46
Hey Jim, I am one of the avid recommenders of squeezeboxes but compared to the stability of the Sonos, the Duet (at least in my house) has not yet lived up to the standards of connection reliability. And while I will certainly stick with it, the WAF of a device that keeps freezing is less than ideal. And if the device prompts you to update, I would like to think that this is a stable release and not beta. On top of that, 2171 was really reliable for me. But I still trust the duet team to iron out these glitches as soon as feasible.,,

Kim.T
2008-04-10, 00:35
Go back to r2171.
And don't compare the stablity of the Sonos to that of the Duet. The software in Sones is pretty old, and they are not very keen to listen to their customers demands/whishes.

DuetOwner
2008-04-10, 20:21
Hmmm... I don't recall anyone stating routers are the problem. I think it was more like we are having problems with some routers and are investigating them with an eye toward fixing the problems. The SBC does not have problems with all routers; I regularly use 4 different routers with all our products and don't have any of the issues that some users are experiencing.

As to your most recent experience, please be aware that the nightly builds are beta and do not undergo the same level of testing (especially regression testing) as a production build. It is possible that fixing one problem creates a new one or even resurrects an old one. It would be great if you could continue to provide constructive feedback on the bug(s) that are affecting you so we can work on finding and addressing the root cause.


-=> Jim

Dear Jim:

Unfortunately, I have to agree with davidmac27 & sapnho. These are not isolated incidents and you must recognize that.

The controller’s connection reliability problems made me return your product. I was not willing to return it but when it randomly failed fifth time to play a song in the presence of my wife, due to connection reliability, Duet’s fate was sealed. Her stance was that since the day I received Duet, I have bee troubleshooting it.

Support tired to help (they even sent me another Duet) but I believe software glitches can never be countered just by support/troubleshooting, your software team has to do the hard labor of finding and correcting all glitches or write the software again.

Duet controller’s connection reliability problems were there even when I lifted all the barriers (no virus scanner, no firewall, starting Squeeze Center as service…etc whatever I can find at these forums) in newly installed Win XP and Win Vista.

I really liked the concept and I want to buy it again when you’ll have resolved all the issues, when just owning Squeezebox Duet will no longer be an “always troubleshooting” hobby, when it will work as reliably as a consumer product.

I am trying Sonos now. It is reliable only if there is at least one wired connection, if I go 100% wireless then it also drop sound, goes mute, pause….etc. Its controller it bulky and it is twice expense. I believe just because of wireless issues, Sonos recommends at least one wired connection and 100% wireless is neither encouraged nor fully supported.

As I am writing these lines, I can search 34 wireless networks in my Apt., add mine and it becomes 35. I am total novice with respect to wireless technology but I just suspect that wireless space is becoming too congested for audio streaming.

Regards

Haroon

MrSinatra
2008-04-10, 21:08
i have to say i have had some factory resets lately to get the firmware updated...

but all in all, i don't think thats such a big deal. i think the SBC is amazing and i expect these issues to become less and less prevalent.

i guess i don't understand why don't the people with problems use updates and factory resets to get to the newest revision? if worse comes to worse, use the SD card option... i think when u hit r2182 you'll find you love it.

http://www.slimdevices.com/downloads/nightly/latest/trunk/

mkozlows
2008-04-10, 21:18
but all in all, i don't think thats such a big deal. i think the SBC is amazing and i expect these issues to become less and less prevalent.

i guess i don't understand why don't the people with problems use updates and factory resets to get to the newest revision? if worse comes to worse, use the SD card option... i think when u hit r2182 you'll find you love it.


For people like you, who want to track nightlies and be engaged in the dev process, the Duet is great. For people like me, who expected it to be buggy on day one, but are confident that eventually it'll get polished, it's slightly maddening (because it's so close to being great, yet so fatally flawed right now). But for people who bought it expecting it to work as smoothly as an iPod... yeah, not so much.

Tiger
2008-04-11, 02:43
Is there a release note for the nightlies? Some info regarding which bug #'s are addressed?



i have to say i have had some factory resets lately to get the firmware updated...

but all in all, i don't think thats such a big deal. i think the SBC is amazing and i expect these issues to become less and less prevalent.

i guess i don't understand why don't the people with problems use updates and factory resets to get to the newest revision? if worse comes to worse, use the SD card option... i think when u hit r2182 you'll find you love it.

http://www.slimdevices.com/downloads/nightly/latest/trunk/

Yannzola
2008-04-11, 07:11
Looks like I'm suffering from similar symptoms. Receiver connects to Slimserver 7.01 without a hitch, Controller cannot connect reliably. Both are seeing 75-80% signal strength from my Linksys WRT54G router. Worked for a day yesterday, but became flaky again after another update in the eve. I can connect to SqueezeNetwork and listen to radio just fine.... but cannot maintain a reliable connection to SC running on Vista Home edition.

SqueezeCenter Version: 7.0.1 - 18481 @ Mon Apr 7 00:21:40 PDT 2008 - Windows Vista - EN - cp1252
Server IP address: 192.168.1.108
Perl Version: 5.8.8 MSWin32-x86-multi-thread
MySQL Version: 5.0.22-community-nt

Platform Architecture: 586

davidmac27
2008-04-11, 23:58
I am now running 2187 on the remote and fw 23 on the SBC. I think I may be on to something. I had previously been connecting the SBC to a Linksys 8 port switch (model EZXS88W ver 3.1) and then on to my Actiontec MI424-WR Rev C router. I connected the SBC directly to the Actiontec router tonight and the Remote started behaving more like I would expect.

Are others here that are having connection problems connecting through switches?

Yannzola
2008-04-12, 01:11
As of 7.01 r2187.... things are looking good! Fingers crossed. :)

Tiger
2008-04-12, 15:05
Upgraded SBC to 2187. Still connection problems. Perhaps *slightly* improved now. Also, I now get the red field strength icon after inactivity. It seems obvious, that this connection problem is related to some power save / sleep mode; when I had the SBC in the charging cradle, the connection stayed fine over night.

Armand
2008-04-13, 11:49
Still my Controller won't setup.
I upgraded to 7.0.1 r2178, disabled power management, upgraded to r2223, did a factory reset, but still my controller doesn't connect to my computer. The receiver works fine (through my computer), but I can't use the controller.

The controller finds my wireless network, it finds the receiver, it connects to my network ("The Squeezebox is connected to your network"), then I choose my computer as the Music Source to get the message "Problem Connecting; couldn't connect your Squeezebox to your wireless network"... which doen't make sense to me, since it first did connect to the network.

When I choose the option "Skip this step", I return to the Set Up Sqeenzebox.

So I cannot use the Controller and don't see any other option then returning the Controller. Do you?

gboz13
2008-04-13, 16:46
I've also been involved in several wide-scale customer-facing implementations, and I can say that unless you have internal numbers (including real sales/delivery numbers) from Slim Devices/Logitech, then there is no way of being able to make any valid commentary on whether this product was rushed or not. Anyone with real experience in this realm would know this.

Also keep in mind that looking at this particular forum as a litmus test for the scale of an issue is not a good idea. Chances are those with issues are more likely to wander in here to make a post, vs. those who have no issues. If someone were to say "hey, everyone who's posted here has had issues!" my response would be, "well...duh". :)

Anyway, I had some of the same issues. Blue icon, red icon, lost connection to the server, spinning arrow. Upgraded to SC 7.01, and now at remote v 2223. No issues so far, definitely much improved.

Graeme

denmennis
2008-04-14, 13:16
Jim

I agree with your comments that every situation is a little different and it is impossible to troubleshoot every possible problem before rolling out a product.

With regard to the pepole who post on this website, it is clear just by reading these posts that almost every person here has a fairly good working knowledge of networks and connected devices. I have read very, very few posts from someone like me who knows next to nothing and bought the SB with the hope of enjoying the product and not spending night after night on the computer doing nightly builds and upgrading firmware. So now I have to wonder how many people there are out there like me who may view the posts (# of views now exceed 6000 vs # of posts..about 140) but don't or won't post here.

I was given an RMA over a week ago and then had a couple of good days with the SB so I let the opportunity to return it pass. Now it is functionless.

I am at a total loss as to what to do since I simply don't have the time or energy to go through all of these upgrades. I was expecting a product to enhance my listening pleasure and to help releive my stress, not to add to it.

I think I will e-mail Logitech and see if I can send it back so that THEY can fix it.

dj

denmennis
2008-04-14, 13:19
With regard to the pepole who post on this website, it is clear just by reading these posts that almost every person here has a fairly good working knowledge of networks and connected devices. I do not recall many posts from someone like me who knows next to nothing and bought the SB with the hope of enjoying the product and not spending night after night on the computer doing nightly builds and upgrading firmware. A few who claim to be newbies spout out technical jargon like its second nature. So now I have to wonder how many people there are out there like me who may view the posts (# of views now exceed 6000 vs # of posts about 140) but don't or won't post herefor one reason or another. Maybe the problem is more widespread than we know ormaybe it isnt.

I was given an RMA over a week ago and then had a couple of good days with the SB so I let the opportunity to return it pass. Now it is functionless.

I am at a total loss as to what to do since I simply don't have the time or energy to go through all of these upgrades. I was expecting a product to enhance my listening pleasure and to help releive my stress, not to add to it.

I think I will e-mail Logitech and see if I can send it back so that THEY can fix it.

dj

JimC
2008-04-14, 13:58
Jim

I agree with your comments that every situation is a little different and it is impossible to troubleshoot every possible problem before rolling out a product.

With regard to the pepole who post on this website, it is clear just by reading these posts that almost every person here has a fairly good working knowledge of networks and connected devices. I have read very, very few posts from someone like me who knows next to nothing and bought the SB with the hope of enjoying the product and not spending night after night on the computer doing nightly builds and upgrading firmware. So now I have to wonder how many people there are out there like me who may view the posts (# of views now exceed 6000 vs # of posts..about 140) but don't or won't post here.

I was given an RMA over a week ago and then had a couple of good days with the SB so I let the opportunity to return it pass. Now it is functionless.

I am at a total loss as to what to do since I simply don't have the time or energy to go through all of these upgrades. I was expecting a product to enhance my listening pleasure and to help releive my stress, not to add to it.

I think I will e-mail Logitech and see if I can send it back so that THEY can fix it.

dj

Please keep the context of my reply... the poster made the broad suggestion that the product was flawed. I basically replied that I don't believe the product is flawed for every user, but is clearly having problems with his particular configuration.

Having gone through lots of problems like this--most recently with an utterly awful experience with a 2wire residential gateway I got as part of my AT&T U-verse service--I know that it can be frustrating. In the end, though, all networking, and especially wireless networking, is a complex interaction between several devices. Depsite there being "standards" there's always a chance that somewhere in the stack there is an incompatibilty that causes a problem.

Clearly, based on the feedback we've gotten, we've found some issues with certain specific routers. This doesn't indicate a fundamentally flawed design, or rushed development; rather, it indicates a compatibility problem that needs to be addressed. Often these type of problems are very setup-specific, making them difficult to duplicate and as any software engineer can tell you, it is *really* hard to solve a problem you can replicate.

None of this fixes your problem, and for that I am very sorry. I wish there was a simple solution, or that it has simply worked out of the box. The reality is that it didn't but the more information you can share with us, the more likely we are to be able to fix the problem--not just for you, but for all customers in the future that have a setup similar to yours.

You should definitely be in touch with our technical support group. That's the best way for us to be able to gather the data we need. Please feel free to request another RMA -- we'll be happy to swap out the products. If possible, I'd like to make sure the product you return is isolated and checked out specifically for wireless connection problems; would you please make sure to note that if/when you return the device?


-=> Jim

denmennis
2008-04-14, 18:37
Jim

I appreciate your reply and I appreciate what you are having to go through to try to make this product work for everyone. You have been very professional in your replies although I am sure that you have had to bite your tongue on more than one occasion.


dj

denmennis
2008-04-14, 19:11
I'm sorry to waste space here but just one more post. First, every time I threaten to throw the SB back in the box, it kicks back on and starts to work. I am listening to music streaming to the SB, for the 1st time in several days.

Here is the thing I don't understand. Earlier this evening, I did my nightly ritual of going to the controller and trying various methods to try to get it connected to the receiver including a factory reset. It did connect to my network but no choices for music on the controller. I gave up and placed the controller back in the cradle with wheel spinning.

Now 2 hours later, I open up SC on the computer and I'm connected and can play music. I go downstairs to the controller but it acts as if it is still out of the loop. It does not acknowledge that there is music playing. It still says it is connected to my network but I cannot access iTunes or internet radio. If I had to rely on controlling the receiver with SC, I could almost live with that but I have never been able to play music without the controller functioning before so I don't quite understand what is happening.

Thanks in advance to anyone who is willing to shed light on this.

dj

MrSinatra
2008-04-14, 19:23
the controller doesn't route any music signal or music data, it simply acts as a remote to control the software (SC) on the computer that in turn sends the music to the receiver.

are you using the newest firmware for both hardware devices and the newest nightly DL of SC?

i would start there. then i would try making as much of it wired as possible. then i would try to troubleshoot the wireless between the SBC and the router.

also, in my exp, i have often had to unplug and or factory reset all the hardware after a firmware update.

HectorHughMunro
2008-04-14, 19:49
So do we know what routers are rock solid with the Duet?

I've got a Netgear DG834N and unfortunately I am experiencing some of these problems. Currently running the most up to date software on the controller and 7.0/22 on the Squeezecentre and Receiver. Security is WPA-PSK.

I'm probably losing connection every three days of so. Takes me about 40 minutes or so to get a connection again.

Upgrading tonight to 7.01/23 to see if it makes a difference.

denmennis
2008-04-14, 19:50
the controller doesn't route any music signal or music data, it simply acts as a remote to control the software (SC) on the computer that in turn sends the music to the receiver.


MrS

Thanks for answering my question. For some reason, I just assumed that the receiver would not work if the controller was not connected. Like I said, I know next to hothing. I could almost live with a dysfunctional controller if I can control the SB from my computer although inconvenient.

I guess I may just need to suck it up and start the upgrades although I am afraid that I won't have the time for this. I would prefer to have the whole network hard wired but even getting it partly wired would be an undertaking in my house.

dj

Andy8421
2008-04-14, 21:17
Jim,

I would like to pick up on one of Denmennis's points about the number of views vs. the number of posts (over 7000 views now).

It has been suggested elsewhere in the forums that the SBC contoller problems are relatively isolated - the reason given that there are relatively few users posting on the subject. I think it more likely that having checked the site once or twice and having established that the cause is being championed by a vocal few, most owners (myself included) are happy enough to let someone else do the work and wait for the fix.

I don't know (and wouldn't know how to establish) whether this forum supports polls, but it may be useful for your software team to establish what percentage of users are having SBC connection problems.

On behalf of the silent majority, I would like to thank all of the posters who are continuing to bring these issues to Jim's attention, and the professinal response of the slimdevices team in their responses.

Andy.

mbodner
2008-04-14, 23:30
Just a quick question as I have been lurking and on the fence about buying a Duet for the kitchen and a couple receivers for the kids' rooms. I've had a couple SB3s for some time and like the product and familiar with its abilities.

Here's my question. Seeing as the issues appear to be related to the controller, are you able to assign it a static IP? If so has anyone noted an improvement?

In my case, all wireless devices on the LAN are statically assigned and filtered by MAC anyway.

The kids would just control their receivers with laptops, but my wife would require the use of the controller. If I have to spend a lot of time "fixing" her controller issues, she would be frustrated and just not use it.

mb

fakarava2
2008-04-15, 07:12
My own experience, with SB3 and Transporter (brand new...), using squeezecenter 7 :
I have the same problems of Wifi lost connection (only on these products).
Loaded nightlies ....nil, and even worse : key lost.
So it seems they are doing something, at last ;-)
Just downloaded 7.0.1-18767 and upgraded firmwares.
I'll tell you in a few days...

davidmac27
2008-04-15, 08:01
Hello everyone,

Reporting back on my status. I performed about 3 updates on my remote (currently running 2223) since writing here last. I have also ditched running Squeezecenter on my Mac Pro and now run it on a dedicated WinXP box. Everything has been working wonderfully for the last 3 days or so.

I'm not sure if this was Mac related or remote related (I have strong suspicions is was the remote firmware).

But I am happy to report that everything is working as I originally had hoped it would - no need to RMA this product.

As I have said before, I think the Slim team needs to focus on what happens when the PC or Mac running SqueezeCenter gets turned off. When this would happen, the remote would get confused and would not allow me to change to SqueezeNetwork to listen to Internet radio (since my MP3 library was no longer accessible).

I think the Slim team is doing a wonderful job posting frequent updates. They are definitely on top of the issues.

HectorHughMunro
2008-04-15, 09:12
Hello everyone,

Reporting back on my status. I performed about 3 updates on my remote (currently running 2223) since writing here last. I have also ditched running Squeezecenter on my Mac Pro and now run it on a dedicated WinXP box. Everything has been working wonderfully for the last 3 days or so.

I'm not sure if this was Mac related or remote related (I have strong suspicions is was the remote firmware).

But I am happy to report that everything is working as I originally had hoped it would - no need to RMA this product.

As I have said before, I think the Slim team needs to focus on what happens when the PC or Mac running SqueezeCenter gets turned off. When this would happen, the remote would get confused and would not allow me to change to SqueezeNetwork to listed to Internet radio (since my MP3 library was no longer accessible).

I think the Slim team is doing a wonderful job posting frequent updates. They are definitely on top of the issues.

I agree with this. Once it's going, it's fine. I don't have my PC on 24/7 and it's after inactivity that I tend to have problems.

gboz13
2008-04-15, 11:44
Perhaps usage has something to do with it, although from day one my setup has been:

1) Static IP for both the Duet Receiver and Duet Remote (x.x.x.120 and x.x.x.121 respectively).

2) Mac ID filtering for my network, with both MAC IDs put on the "allowed" list.

3) Using D-Link Router with Belkin Wireless Extender, so not a simple wireless setup.

4) Computer on 24/7, but periodic re-boots

I found with SC 7.0 and the last remote firmware allowed with SC 7.0, the common issues found:
1) Spinning Arrow
2) Red icon after a long playing session
3) Blue icon after leaving the remote in the cradle overnight
4) Random power-ons of the receiver
5) No caching of album covers, so looks like covers are being downloaded each time with a delay
6) Random loss of connectivity to SC, where all the menu options disappear
7) Disconnect between remote and receiver (remote shows not playing, receiver is playing)

After upgrading to 7.01 and remote firmware v2223, all the above problems are gone. And I haven't touched any of the usage mentioned above (i.e. no network changes, etc.)

Graeme

geoff
2008-04-15, 20:26
This thread seems to be all about wireless issues with the new duet controller. Is it possible that the problem is more pervasive than this? I have a single SB3 connected with wireless to my server. It worked flawlessly with SC 6.5.4 but since a recent SqueezeCenter upgrade to 7.0 I have had frequent problems with the wireless connection dropping out. It used to show a consistent signal strength of 80%+ at the SB3. But since the upgrade the signal strength seems to wander up and down over time, averages maybe 50-60% and fluctuates up to 70+ and down to 20 something. I can't imagine how the SC software / firmware u/g could do this? But maybe ? I havn't touched the hardware at all, everything is physically just as it was before ... but something has changed somewhere.

Armand
2008-04-16, 00:23
Does anyone have any suggestions?
Thought my previous posts unfortunatelly did't result in any answers yet, I'll give it another shot.
My controller will not connect to my pc / Sqeezecenterserver . It will not connect at all, not just interuptions, it simply does not connect.

After (yet another) factory reset I was able to connect to Sqeezenetwork, in which everything works fine, but connecting to my pc / Sqeezecenterserver afterwards failed.
Connecting to my pc / Sqeezecenterserver after a factory reset doesn't work: "Problem Connecting; couldn't connect your Squeezebox to your wireless network".

It doesn't make sense to me since:
- I can see the controller in the DHCP client list;
- I can connect to the controller throught SSH / putty
- The controller first finds my wireless network, then finds the receiver and connects to my network ("The Squeezebox is connected to your network")
- My receiver and two other classic SqueezeBoxes work fine

I tried changing the Belin router's congfiguration (SSID channel, switching 64 and 128 WEP, etc.)

Can anyone please give me some suggestions?

Kim.T
2008-04-16, 00:57
With my ZyXEL router connection was almost impossible with r2097 (factory default). Update was only possible using a SD card.
But in general I have no problems when the controller is in the charger/cradle but when operated in the hand/laying on the table the controller looses the connection all the time. I'm using r2223 - the only other problem I see is that booting takes ages (when not using English as language)

Moonloop
2008-04-16, 04:03
Ive had my Duet/Receiver for nearly a month now but havent managed to get it usable ( Thank God the SB3 works flawlessly ) . When I do get them to appear on SC the wireless crashes and the SB3 loses its settings so I just leave them largely unused for now as the crashes create problems while ripping .

Equipment : Duet/Receiver , SB3 , Dell Inspiron laptop , HP MediaSmart Server with SC 7 installed , Netopia Cayman router 3347w .

Server is in an upstairs bedroom with the router , SB3 is in the living room working flawlessly after being given a static IP . The Duet Receiver after many different experiments is wired direct to router and connects ( eventually ) , Duet Controller only works with it if in the same room . It has yet to finish 'Copying Update' properly and the whole system crashes in minutes .

Disconnect the Duet duo and reboot and evrything works perfectly with absolutely no crashes .

Baffled and disappointed and waiting on a breakthrough :O)

~M~

dean
2008-04-16, 08:00
Moonloop: Have you tried the latest pre-release version of
SqueezeCenter (7.0.1), which includes a number of connectivity fixes?

http://www.slimdevices.com/dev_nightly.html

fakarava2
2008-04-16, 08:40
Moonloop: Have you tried the latest pre-release version of
SqueezeCenter (7.0.1), which includes a number of connectivity fixes?

http://www.slimdevices.com/dev_nightly.html

For me, this build (that I downloaded yesterday) seems better on this point of view than the previous betas :

"SqueezeCenter: 7.0.1 - 18767 @ Tue Apr 15 00:21:54 PDT 2008 - Windows XP - FR - cp1252"

It needs to be confirmed after a few days, however...

JimC
2008-04-16, 12:13
Does anyone have any suggestions?
Thought my previous posts unfortunatelly did't result in any answers yet, I'll give it another shot.
My controller will not connect to my pc / Sqeezecenterserver . It will not connect at all, not just interuptions, it simply does not connect.

After (yet another) factory reset I was able to connect to Sqeezenetwork, in which everything works fine, but connecting to my pc / Sqeezecenterserver afterwards failed.
Connecting to my pc / Sqeezecenterserver after a factory reset doesn't work: "Problem Connecting; couldn't connect your Squeezebox to your wireless network".

It doesn't make sense to me since:
- I can see the controller in the DHCP client list;
- I can connect to the controller throught SSH / putty
- The controller first finds my wireless network, then finds the receiver and connects to my network ("The Squeezebox is connected to your network")
- My receiver and two other classic SqueezeBoxes work fine

I tried changing the Belin router's congfiguration (SSID channel, switching 64 and 128 WEP, etc.)

Can anyone please give me some suggestions?

The Controller is connected to your wireless network in the same way, regardless of the music source. The connection, assignment of IP address, etc., all occur well before there's an attempt made to find a music source.

If the Controller connects SN and configures the Receiver properly, then the Controller is working. Connecting to SN means that your network is configuring the Controller correctly, and is routing packets to/from the internet to the Controller correctly. This is good.

Not finding a local SqueezeCenter can mean any of the following:

You don't actually have SqueezeCenter 7.0.0 (or higher) running on a computer on your network. Make sure SC is running and, if possible, connect to it from a different computer on your network by opening a web browser and entering http://IP_address_of_computer_running_SC:9000. If the SqueezeCenter interface opens up, then SC is running and available on your network (at least to that computer). Double-check the version number by checking the Status tab under Settings.

One (or more!) software firewalls are blocking the routing of packets to/from the Controller to the computer running SC. Try disabling (as a test!) the firewall and see if you can connect. Be sure to double-check that ALL firewalls are turned off (you might be surprised how many people are running the built-in Windows Firewall and a third-party firewall like Zone Alarm Pro, or Norton Internet Security. If you are able to connect, then you'll need to open the firewall for access (see the Squeezebox Duet Uder Guide for instructions).

The Controller is not on the same network segment as the computer running SqueezeCenter. Check the IP address for the computer and compare it to the IP address for the Controller. They should be very similar (eg., 192.168.1.101 and 192.168.1.106). If they aren't similar, they may not be on the same network segment which means there may not be a route for the data to travel. If this is the case, you'll need to post details about your network set up here (what's connected to what, as in: switch connected to wireless router, PC connected to switch with ethernet cable, Controller and Receiver connected to wireless router). We can try to help you figure out what's happening from that information.


In general, this is stuff our technical support team is really well qualified to help you with... you really should consider contacting them.


-=> Jim

JimC
2008-04-16, 12:18
This thread seems to be all about wireless issues with the new duet controller. Is it possible that the problem is more pervasive than this? I have a single SB3 connected with wireless to my server. It worked flawlessly with SC 6.5.4 but since a recent SqueezeCenter upgrade to 7.0 I have had frequent problems with the wireless connection dropping out. It used to show a consistent signal strength of 80%+ at the SB3. But since the upgrade the signal strength seems to wander up and down over time, averages maybe 50-60% and fluctuates up to 70+ and down to 20 something. I can't imagine how the SC software / firmware u/g could do this? But maybe ? I havn't touched the hardware at all, everything is physically just as it was before ... but something has changed somewhere.

I don't *think* there were significant changes to the networking code on the SB3, but I'm not a software guy so I can't be 100% sure of that.

Is it possible that a neighbor just added a wireless network that uses the same channel as yours? That could cause problems with your network, without you ever having made a single change. If the SB3 is closer neighbor's router than to yours (this does happen: my Transporter is closer to my neighbor's router than mine), it very likely could cause a change in signal strength.

Any other possible changes to the radio environment? Did you add a new 2.4GHz wireless telephone to your house? Any other wireless stuff added recently?


-=> Jim

Armand
2008-04-16, 12:41
Jim, thanks for your reply, but unfortunately nothing new.
I only haven't tried to disable my firewall yet; I'll give it a shot asap. But I already allowed communication through ports3483 (UDP en TCP) and 9000 (TCP).



You don't actually have SqueezeCenter 7.0.0 (or higher) running on a computer on your network. Make sure SC is running and, if possible, connect to it from a different computer on your network by opening a web browser and entering http://IP_address_of_computer_running_SC:9000. If the SqueezeCenter interface opens up, then SC is running and available on your network (at least to that computer). Double-check the version number by checking the Status tab under Settings.

I'm already used to connect to SC from a different computer. It runs 7.0.1 - 18576.


One (or more!) software firewalls are blocking the routing of packets to/from the Controller to the computer running SC. Try disabling (as a test!) the firewall and see if you can connect. Be sure to double-check that ALL firewalls are turned off (you might be surprised how many people are running the built-in Windows Firewall and a third-party firewall like Zone Alarm Pro, or Norton Internet Security. If you are able to connect, then you'll need to open the firewall for access (see the Squeezebox Duet Uder Guide for instructions).

I didn't try that one yet...


The Controller is not on the same network segment as the computer running SqueezeCenter. Check the IP address for the computer and compare it to the IP address for the Controller. They should be very similar (eg., 192.168.1.101 and 192.168.1.106). If they aren't similar, they may not be on the same network segment which means there may not be a route for the data to travel. If this is the case, you'll need to post details about your network set up here (what's connected to what, as in: switch connected to wireless router, PC connected to switch with ethernet cable, Controller and Receiver connected to wireless router). We can try to help you figure out what's happening from that information.

The computers and controllers IP address are on the on the same network segment for sure.

HectorHughMunro
2008-04-16, 13:00
So do we know what routers are rock solid with the Duet?

I've got a Netgear DG834N and unfortunately I am experiencing some of these problems. Currently running the most up to date software on the controller and 7.0/22 on the Squeezecentre and Receiver. Security is WPA-PSK.

I'm probably losing connection every three days of so. Takes me about 40 minutes or so to get a connection again.

Upgrading tonight to 7.01/23 to see if it makes a difference.

Just to report how things are going; Basically, since the latest updates 7.01/23, it's much more stable and I haven't had a crash or had to do a forced restart of any of the Slimdevices kit.

Well done, things definitely improving.

Robin D
2008-04-17, 04:17
Adding my voice - I love the Duet, but it just keeps having Network problems.

I've been following this thread as I have has similar problems:
- Loss of connection to wireless network
- Loss of conection to music source (blue symbol)
- Jittering/stuttering of streamed music despite acceptable signal strength. With no information as to the problem.
- Constant 'Software Updates' loop/failure every time I wanted to use it.
- All of the above unpredictable/at random and resolving/un resolving regardless of my input.

**Im sure that if I had thin walls and 1 access point, I'm sure that things would go swimmingly and this would be an excellent product.**

After many many hours of fiddling reinstalling reorganising testing(...) I've decided to pack the Duet up and send it back for checking. I love a good technical challenge but My wife said I looked sad and tired.

If and when this thing becomes more reliable, will someone tell me as it would have been just perfect for me and I'll buy it again without hesitation. I appreciate the positive efforts of the Slim Team and offer my help if they need more info - just ask.

In summary, the set-up is as follows;
Duet (Infrastructure Mode)
-Wireless 49%-
Netgear WGR614v2
-Ethernet-
dLAN Ethernet Highspeed 85
-Power Cable 40Mbps-
dLAN Ethernet Highspeed 85
-Ethernet-
Netgear WNR834B
-Wireless(30-110Mbps)-
Netgear WN3111/PC Windows XP SP.2

SqueezeCenter Version: 7.0.1 - 18284 - Windows XP - EN - cp1252

(It did not detect the (Home Plug) ethernet initially, so I was forced to use a Netgear AP using the Ethernet as an input, in the same room, providing a 49% reception.)

p.s: I had recently bought a SLIMP3 to complement the Duet, but it may end up replacing it!....

Moonloop
2008-04-17, 05:39
" Moonloop: Have you tried the latest pre-release version of
SqueezeCenter (7.0.1), which includes a number of connectivity fixes?

http://www.slimdevices.com/dev_nightly.html "

Thanks for that Dean , but Customer Services told me that I had the latest version available for my equipment ( HP MediaSmart Server running SC 7.0 - 17793
Windows Home Server 2003 -EN - cp1252 ) Is this not the case ? Is the version slightly tweaked for Servers as opposed to pcs or are they the same ? I have SC set to check for updates automatically but this version number hasnt changed since I installed it a month ago .

Its all very frustrating as SB3 works perfectly so there has to be something different about the Controller as it never connects properly and crashes the system whenever I try.

Any ideas at all considered :)

~M~

consciouspnm
2008-04-17, 06:09
The nightlys refered to here are betas of the next version. You can install them on your HP server. Just download the Windows executable from the link given. SC won't detect the update until they become official.

Moonloop
2008-04-17, 07:18
So the 'Automatic Updates' only reacts to official releases and there hasnt been one of those for a month at least and any benefits or bug fixes in beta versions wont kick in immediately ? Or will they ?

Thanks ,

~M~

slimpy
2008-04-17, 09:14
So the 'Automatic Updates' only reacts to official releases and there hasnt been one of those for a month at least and any benefits or bug fixes in beta versions wont kick in immediately ? Or will they ?

Automatic Updates only notifies you if a new official realease is available.
If you have this enabled and there is new official firmware for the controller available SC will download the file and the controller will prompt you to update.
You won't get any notification whatsoever when there's new beta or nightly software.
You should only install betas/nightlies if you're prepared to update your SC installation every couple of days. The controller will update to the latest firmware whenever there's a new version (could be every day). Because the controller relies on SC you should then also update your SC installation or you might experience incompatibility issues between SC and the controller.

-s.

Moonloop
2008-04-17, 10:00
Thanks !
Ive updated the server to v 18834 and so far , for the first time , managed to update firmware on SB3 and Controller ( I didnt get any notice of firmware updating on Receiver ( is that included with Duet Controller ? )

This is the first time Ive had everything connected for 30 mins without a crash
and Im currently ripping a cd for saving so it'll be interesting to see if the connections hold up !

~M~

rtitmuss
2008-04-17, 10:10
A number of people of reported connectivity problems when using a ZyXEL P-2602HW(L) router with the Squeezebox Controller, both in this thread and in Bug 7153 (http://bugs.slimdevices.com/show_bug.cgi?id=7153).

I have been testing with one of these routers today, and I seems to be working fine. I'll continue using the router for a few days to be sure.

I note that the firmware version on the router I have is "V3.40(AUI.0) | 05/16/2007", where the routers reported previously all have firmware from 2006. Older firmware is not available from the ZyXEL website for testing, however in the release note it mentions that the routers wireless LAN driver was upgraded on 12/14/2006.

If you are experiencing a problem with one of these routers please go to http://www.zyxel.com/web/support_download_list.php and upgrade your router to the latest firmware. I think this is likely to fix the connectivity problems you are seeing, please do report back with any success/failure so we can either close the bug report or investigate further.

I should also stress that anyone with connectivity problems should try the latest SqueezeCenter 7.0.1 beta release (and included Controller firmware) as this includes a number of important bug fixes.

Thanks,
Richard

rtitmuss
2008-04-17, 10:37
Is there a release note for the nightlies? Some info regarding which bug #'s are addressed?

Please see http://mwiki.slimdevices.com/index.php/SqueezeOS#SqueezeOS_Software_Versions.

Richard

davidmac27
2008-04-19, 15:00
This DUET makes me want to SCREAM!!!!

It has been working great all week long. I have upgraded it (or been forced to upgrade it 3 or 4 times). It currently has 2269 on it. This morning, the remote was not connected to the receiver. I tried to connect and ONE HOUR LATER after about 15 factory resets on the remote and receiver - STILL NO LUCK.

If I am lucky, I get to the final screen and it tells me 2287 is available, so I choose to download it. 10 seconds later, the remote spontaneously reboots. I tried it numerous times with the same results. So I grab my memory card and download 2287 off Slim's site. I turn on the remote and it gives me 3 options: download and install 2287, install from SD card, install from SD card. No matter what I do, the damn thing spontaneously reboots after 10 seconds of trying to copy the update.

Now that I have pissed away 90 minutes of my Saturday working on this $428 device, does anyone have any suggestions to get me listening to my music again??? This is getting old. Does anyone test these updates???

xn03296
2008-04-19, 15:32
Now, I am sitting here and I want to hear my music. But my controller told me that a update is waiting. ok, I press the button, the controller tells me that that the update is running. after the restart the conroller tells me a update is waiting. I press the the the button, the controller restarts and ??? the controller tells me a update is waiting....... and so on. No chance to hear music. no reset of the controller helps. everytime the controller wants to make an update.

Helloooo, I payed 400 Euro for this bananaware. The Idea of the sqeezebox duett is great, if it works its a very good peace of hardware...
but the software is a alpha-release. so i will take a cd and put it into my player and hear my music in the "old" way......

davidmac27
2008-04-19, 15:38
I found the solution in another thread. When it prompts you to update, if you hit the back button to get back to Settings. Then goto Advanced and choose Software Update. It worked that way for me.

Sheeesh.

xn03296
2008-04-19, 16:02
if i push the "back" button, nothing happens. Its like a loop. I only can push the OK button for the update, the controller reboots and a only can choose the option "start the update". I restarted the slimserver, I have updatet the slimserver to the newest version. nothing helps. I am an it-professional, I know clusters, solaris, networks and so on. I have a wired 100 MBit CAT5 Lan and I use the Duett in the Bridge Mode. Buts this peace of hardware makes me crazy. sometimes it runs like a charme, but sometimes you cant use it because you have no connection to the receiver, why? its a miracle. You look to your network, to your dhcp server to the mac-adresses, to the slimserver and and and.......
My Network is wired, so it couldnt be a "wireless" problem. I am tired of spending so much time in making this peace of hardware working. I wont to hear music, thats the reason why i bought the duett.

davidmac27
2008-04-19, 16:04
Try doing a reset on the receiver (hold the button in until you see rapid flashes). At the same time, do a factory reset on the remote. Then after setting it up (again), when it says it has a 2287 update, hit the back button.

Hopefully this will work for you.

And I hear ya!

xn03296
2008-04-19, 16:23
Thank you very much for your Tip, I will try it tomorrow. I will give you a feedback.

regards

Henrik

davidmac27
2008-04-19, 16:42
No problem - I am starting to know this product better than the ones that I am Product Manager for...

Cripes! (;-)

breadboxer
2008-04-19, 22:46
A number of people of reported connectivity problems when using a ZyXEL P-2602HW(L) router with the Squeezebox Controller, both in this thread and in Bug 7153 (http://bugs.slimdevices.com/show_bug.cgi?id=7153).

I have been testing with one of these routers today, and I seems to be working fine. I'll continue using the router for a few days to be sure.

I note that the firmware version on the router I have is "V3.40(AUI.0) | 05/16/2007", where the routers reported previously all have firmware from 2006. Older firmware is not available from the ZyXEL website for testing, however in the release note it mentions that the routers wireless LAN driver was upgraded on 12/14/2006.

If you are experiencing a problem with one of these routers please go to http://www.zyxel.com/web/support_download_list.php and upgrade your router to the latest firmware. I think this is likely to fix the connectivity problems you are seeing, please do report back with any success/failure so we can either close the bug report or investigate further.

I should also stress that anyone with connectivity problems should try the latest SqueezeCenter 7.0.1 beta release (and included Controller firmware) as this includes a number of important bug fixes.

Thanks,
Richard

Seems like there's been a lot of focus put on Zylex routers, but I'm having exactly the same connectivity problems (e.g., spinning arrow in the menus, red connectivity icon, lost connections, etc.) with a brand new Netgear WNR3500 on Vista. I would suggest that you broaden your troubleshooting effort, as I doubt very much that the number of posts on this lists even comes close to reflecting the scope of the Duet problem, and the regular customer support channels are falling a bit short.

kimbl
2008-04-20, 14:52
@xn03296
Yup, there's a problem with the current update - not directly related to the network issues in this thread.

See http://forums.slimdevices.com/showthread.php?t=46509&page=3 - for details, and if you're stuck here, upgrade server to 18963 and the controller will update correctly. Certainly that worked for mine just now which had the same problem.

rtitmuss
2008-04-21, 01:42
Seems like there's been a lot of focus put on Zylex routers, but I'm having exactly the same connectivity problems (e.g., spinning arrow in the menus, red connectivity icon, lost connections, etc.) with a brand new Netgear WNR3500 on Vista. I would suggest that you broaden your troubleshooting effort, as I doubt very much that the number of posts on this lists even comes close to reflecting the scope of the Duet problem, and the regular customer support channels are falling a bit short.

Have you tried the 7.0.1 beta release, this includes fixes for a number of connectivity problems.

Richard

Rolo
2008-04-21, 12:20
I'm having some of the same Duet connection problems discussed in this thread.

My set up is a little different than most in that I don't have a computer connected to my network most of the time (long story) and have been listing primarily to Pandora or Internet radio.

Basically, my entire network consist only of a Netgear Rangemax WPNT834 router using WPA2.

Connectivity with both the Duet and my laptop has gotten better doing the following things:

1. Turning off the feature that lets the router switch channels. I now keep things on channel 8.

2. Broadcasting my SSID.

However, I'm still having problems.

1. Often the controller doesn't find the receiver. Am I right in thinking that my WiFi situation is unrelated to this or do they talk to each other through the WiFi network?

2. When I look to see what devices are connected to my router, should I see separate entries for both the controller and receiver? I've only ever seen one SB device connected to the router.

JimC
2008-04-21, 13:09
I'm having some of the same Duet connection problems discussed in this thread.

My set up is a little different than most in that I don't have a computer connected to my network most of the time (long story) and have been listing primarily to Pandora or Internet radio.

Basically, my entire network consist only of a Netgear Rangemax WPNT834 router using WPA2.

Connectivity with both the Duet and my laptop has gotten better doing the following things:

1. Turning off the feature that lets the router switch channels. I now keep things on channel 8.

2. Broadcasting my SSID.


Broadcasting your SSID shouldn't be required, but the auto channel stuff would create issues for both the Receiver and Controller. They would have to timeout their connection before retrying, as opposed to "following" the channel as neither of them implement roaming.



1. Often the controller doesn't find the receiver. Am I right in thinking that my WiFi situation is unrelated to this or do they talk to each other through the WiFi network?

If they are both connected via wireless, then they talk to each other through the router. The only time the Controller is connected directly to the Receiver (via our private ad-hoc connection) is when: 1) the Controller is setting up the Receiver; or 2) when you have the Receiver connected via ethernet and the Controller is bridging to the network through the Receiver.


2. When I look to see what devices are connected to my router, should I see separate entries for both the controller and receiver? I've only ever seen one SB device connected to the router.

See above. Both should have a connection to the router, unless the Receiver is connected via ethernet (and even then it should show up in the router's table, just as a wired device rather than a wireless one).


-=> Jim

browellm
2008-04-21, 14:29
Firstly, apologies as I haven't read the *entire* thread. But I thought I would post my experiences of connectivity with the SB3.

My router is a BT HomeHub (a very common router in the UK based on a Thomson/Alcatel box). I have WPA2 and manual channel selection running.

My SC runs on my home pc, which is not run 24/7 and is therefore subject to normal daily power-downs.

I had *very flaky* DHCP performance between the HomeHub and SB3, and had to regularly go back through guided setup to get the SB3 to renew it's lease (it would often be allocated a private address range 169.x on startup).

Although it doesn't affect other wireless devices on my network (Wii, couple of laptops), I don't think the embedded DHCP server gives stellar performance.

Hacked off with the constant loss of connectivity I shifted the SB3 to a static address outside of the HomeHub's DHCP range. Since then (about 2 weeks and counting), connectivity has been absolutely rock solid.

I am sure many Duet owners have already tried the static address approach, but if not I urge you to give a try.

jefferic
2008-04-21, 15:23
Browellm :

I think I have got the same problem with the Home Hub & would like to try this solution. How do you select wich IP address to use when you shifted it to a static address outside the Home Hub range ?

browellm
2008-04-21, 15:54
Browellm :

I think I have got the same problem with the Home Hub & would like to try this solution. How do you select wich IP address to use when you shifted it to a static address outside the Home Hub range ?

You need to have a look at you router's dhcp range first (from it's admin pages)

E.g. mine is 192.168.1.64 - 192.1.68.1.253

As long as you pick an address on the same subnet 192.168.1.x you will be fine.

I picked 192.168.1.60 for example. x can be anything from 2 to 63. Avoid 0,1,254,255 as are special addresses and/or reserved usually.

Note: if your subnet goes all the way from x.x.x.1 - x.x.x.254, and you are uncomfortable with altering the range just pick a number, say 200, that is unlikely ever to be allocated to a device by your dhcp server.

Your internal address range might be different to mine (10.0.0.x is common) but the principle is the same. Just keep your chosen address on the same subnet (first three dotted number the same)

Sorry if I'm teaching you to suck eggs, I'm not sure of your networking knowledge.

Rolo
2008-04-21, 16:33
If they are both connected via wireless, then they talk to each other through the router. The only time the Controller is connected directly to the Receiver (via our private ad-hoc connection) is when: 1) the Controller is setting up the Receiver; or 2) when you have the Receiver connected via ethernet and the Controller is bridging to the network through the Receiver.



See above. Both should have a connection to the router, unless the Receiver is connected via ethernet (and even then it should show up in the router's table, just as a wired device rather than a wireless one).


-=> Jim

Looking at my attached devices through my router admin utility, at first I only saw one device (the receiver) and now I'm seeing no devices. However, I am streaming music over the net.

When I go to the Squeezebox information utility, the IP address being shown is the IP address assigned to the router and not a number that my router should have been assigning to a connect device. I'm also showing a signal strength of 90.

When I go the wireless information page, the IP address shown is one generated by my router, but I still don't see it (I'm assuming the controller) as a connected device. I also show a SNR between 25 & 40.

Interestingly, while I'm writing this, the controller showed the red icon. I then went to the wireless network option in advanced settings. The controller is trying to find network. This should be easy because I'm in range of 12 different networks. Unfortunately, the display is just showing the spinning dots.

jefferic
2008-04-22, 13:14
[QUOTE=browellm;294097]You need to have a look at you router's dhcp range first (from it's admin pages)

E.g. mine is 192.168.1.64 - 192.1.68.1.253

As long as you pick an address on the same subnet 192.168.1.x you will be fine.

I picked 192.168.1.60 for example. x can be anything from 2 to 63. Avoid 0,1,254,255 as are special addresses and/or reserved usually.

QUOTE]


Thanks - in your first post you said you picked a static address outside the Home Hub's DHCP range, but here are you saying you picked one within the same subnet. Isn't that contradictory ? Forgive my ignorance

Also, do you need to set up the Hoome Hub to run with static IP addresses before you are able to enter the static IP adddress in the SB controller. ?

Thanks for your help

MrSinatra
2008-04-22, 13:21
Thanks - in your first post you said you picked a static address outside the Home Hub's DHCP range, but here are you saying you picked one within the same subnet. Isn't that contradictory ? Forgive my ignorance

no, its not. its good advice.

Zaragon
2008-04-22, 13:52
Just thought I'd mention that I'm using the BT Home hub in one of the networks here and not had any problems with it serving DHCP addresses wirelessly to an SB3, Controller and Receiver and wired to an SB3. It also handles about 10 other devices as well with no issues including the server.

Incidentally it also has an inbuilt DNS responder as well so if you name devices or it picks up their names via the network you can then use URL style names eg http://musicserver.home:9000 as everything on the local network becomes .home

The latest software also has simple shared storage handling, if you plug a USB memory stick into the port it is mounted as a network shared drive. I've not got around to trying it with a real USB disk yet though. It also seems to have a print server built in against the other USB port but I've not tried that at all.

aubuti
2008-04-22, 13:54
Thanks - in your first post you said you picked a static address outside the Home Hub's DHCP range, but here are you saying you picked one within the same subnet. Isn't that contradictory ? Forgive my ignorance


no, its not. its good advice.
To be a bit less laconic, the DHCP range can be a subset of the addresses on the subnet. For example, my home subnet is 192.168.0.1 - 192.168.0.255, but I have set my DHCP server to give out addresses only in the 192.168.0.2 - 192.168.0.16 range.

breadboxer
2008-04-22, 17:28
Have you tried the 7.0.1 beta release, this includes fixes for a number of connectivity problems.

Richard

Yes. I did that before posting, to be certain that I wasn't wasting anyone's time. (Not to be too surly, but I imagine that's something people here appreciate, given how much of theirs has already been dedicated to the Duet.) Often what happens is that the connection icon turns blue after a period and I'm required to reconnect to the music source.

Yannzola
2008-04-23, 08:07
Looks like I'm suffering from similar symptoms. Receiver connects to Slimserver 7.01 without a hitch, Controller cannot connect reliably. Both are seeing 75-80% signal strength from my Linksys WRT54G router. Running on Vista Home edition.


As of SqueezeCenter 7.0.1 - 18932 @ Sat Apr 19 cp1252 (and several Controller updates since) things are looking up! So far I'm managing to connect to SC from my controller consistently, with only a minor amount of lag. Hurrah!

Rolo
2008-04-23, 10:55
As of SqueezeCenter 7.0.1 - 18932 @ Sat Apr 19 cp1252 (and several Controller updates since) things are looking up! So far I'm managing to connect to SC from my controller consistently, with only a minor amount of lag. Hurrah!

I note, however, that some of the problems that people, like myself, are having (I assume) won't be helped by fixes made in SC because we're not using SC.

I can put my controller within 2 feet of my router and I'll still lose the connection. I do need to consider whether switching out my router might be my best option. Anyone have suggestions on routers/APs that are working solidly with the Duet?

Yannzola
2008-04-23, 11:48
I note, however, that some of the problems that people, like myself, are having (I assume) won't be helped by fixes made in SC because we're not using SC.

Pardon my ignorance... but how can you serve any sort of music without running SC (SqueezeCenter)?

Rolo
2008-04-23, 13:53
Pardon my ignorance... but how can you serve any sort of music without running SC (SqueezeCenter)?

At the moment, I don't have a computer hooked up to my wireless network. I'm just streaming from Pandora and Internet radio feeds through Squeeze Network.

Yannzola
2008-04-23, 17:10
At the moment, I don't have a computer hooked up to my wireless network. I'm just streaming from Pandora and Internet radio feeds through Squeeze Network.
Doh! I forgot about the SqueezeNetwork. Got it :)

sfraser
2008-04-24, 12:26
Guys, found a little bug in SqueezeCenter 7.0.1 - 18932. Nothing major, and you may already be aware of it. I have two SC in my home network. One is running an older version of SC. If i try to point an SB from one SC to another SC from the controller, the controller will get caught up in a endless message regarding upgrading the S/W. This does not go away, even after i flash the SB by using the brightness key on the infrared remote of the SB. Only way out of the loop is to remove the batteries on the Controller.

Phil Leigh
2008-04-24, 14:20
why on earth would you want to run 2 instances of SC?

Yannzola
2008-04-24, 15:30
why on earth would you want to run 2 instances of SC?
Maybe for the same reasons I do (I run 6.5 on one rig and 7.01 on another). 7.01 isn't ripe yet, plus all of my favorite plugins haven't been re-written for 7 yet... So I keep 6.5 for the main system and run 7.01 to fool around with my Duet. Biding time until the bugs get ironed out.

mherger
2008-04-24, 22:45
> 7.01 to fool around with my Duet. Biding time until the bugs get ironed
> out.

Bugs which have been reported and not fixed?

Michael

fakarava2
2008-04-24, 23:49
> 7.01 to fool around with my Duet. Biding time until the bugs get ironed
> out.

Bugs which have been reported and not fixed?

Michael
see also:
http://forums.slimdevices.com/showthread.php?t=40091

sfraser
2008-04-25, 04:40
why on earth would you want to run 2 instances of SC?

I have my "original SC" on my windows file server which has a couple TB of hard disk space and approx. 75K songs (flac,wav,mp3). The 2nd SC is a "beta" box, which is a small fanless ITX unit running SlimNAS. I have been having a few issues with the SlimNAS ITX SC recently, so I keep the windows SC up and running as a backup. Plus I can't fit all my music (yet) on the slimNAS unit, so I sometimes jump over to the Windows SC.

I don't believe this is breaking any rules. Again the bug (or what appears to be a bug) is a corner case situation, but it should probably go on the list of things to be fixed.

cheers,

Phil Leigh
2008-04-25, 09:27
I have my "original SC" on my windows file server which has a couple TB of hard disk space and approx. 75K songs (flac,wav,mp3). The 2nd SC is a "beta" box, which is a small fanless ITX unit running SlimNAS. I have been having a few issues with the SlimNAS ITX SC recently, so I keep the windows SC up and running as a backup. Plus I can't fit all my music (yet) on the slimNAS unit, so I sometimes jump over to the Windows SC.

I don't believe this is breaking any rules. Again the bug (or what appears to be a bug) is a corner case situation, but it should probably go on the list of things to be fixed.

cheers,

No - sorry I wasn't being clear...I can see why you would have 2 installations and occasionally switch between them...I meant why would you have 2 active at the same time!
Also, whilst not breaking any rules, I'm sure you can see why that might cause the players to get confused about what IP the SC is on at any time?

I suppose that with static IP everywhere you COULD get this to work reliably. I wouldn't like to try it with DHCP!

sfraser
2008-04-25, 11:55
No - sorry I wasn't being clear...I can see why you would have 2 installations and occasionally switch between them...I meant why would you have 2 active at the same time!
Also, whilst not breaking any rules, I'm sure you can see why that might cause the players to get confused about what IP the SC is on at any time?

I suppose that with static IP everywhere you COULD get this to work reliably. I wouldn't like to try it with DHCP!


I don't see, or there should not be, any problem having multiple SB's and multiple SC's on the same L3 network/broadcast domain. Each SC and SB host has a unique MAC/(DHCP assigned IP) combination.

The controller, in the advanced feature menu , has a "music source" option which lists all SC's currently available on the local network. This allows the controller to point the SB that is currently being managed to anyone of the SC's available (thats how I understand it). Higher level protocols should take care of any session communications between the SB and the chosen SC.

I think where the problem lies, is with the controller, I think it may have a tough time "jumping" between SC's? Particularly if the SC or the end SB requires a S/W upgrade.

Can anyone comment on the communication exchange between the controller and the SC?

Cheers,

Have a great weekend everyone.

PeterDB
2008-04-26, 10:31
Hi,

I have been through the same as most here, i.e. loose connective or just poor reception in general. I have been running the latest nightly builds for quite some time, but it never really seems to get that much better.

As any other wireless device in our household has not issues, I thought it was the Controller, since my Receiver is connected wired and the Controller is connected in wireless mode, not bridged (ie. Controller is connected to the modem/router wireless and the Receiver wired).

I opened up the Controller, and saw that the antenna was really small. So, I modded it - very amateur mod, no less - to make it longer and this really improved my connectivity and the Controllers responsiveness.

Check here: http://forums.slimdevices.com/showthread.php?t=46852

/PeterDB

Zaragon
2008-04-27, 04:12
Not a comment on PeterDB's experience just a general on on antenna length. Small doesn't necessarily mean bad, increasing the length could actually make the signal worse.

Antenna length is determined by wavelength and the circuitry it is connected to. Changing its length changes the balance between the design parameters.

C_Swe
2008-04-29, 11:13
I just wanted to let you know how my connection problem was resolved. I used to have a problem choosing music source from the controller. The screen would show the name of my computer running SqueezeCenter (SC) as well as SqueezeNetwork (SN), but trying to select SC only showed the "connecting" screen for a long time (every time) before finally saying that the connection failed. This issued was solved either by upgrading my Linksys WRT54G router firmware to DD-WRT v23, by the latest software upgrade on the controller, or both (I did not have time to try just the new router firmware because the controller auto-updated). I suspect the problem was the router firmware, since I saw a comment about my old third-party (Satori) firmware causing similar problems with other applications.

My only problem now is that the SC default skin is very slow in Firefox, but selecting the "classic" skin solves that.

SqueezeCenter: 7.0.1 - 19133
Controller software version: 7.1 r2349 root@padbuild #53
Firmware: 23 (as stated on controller when it is connected to receiver)

scottwmackey
2008-04-29, 17:01
Having gone through lots of problems like this--most recently with an utterly awful experience with a 2wire residential gateway I got as part of my AT&T U-verse service--I know that it can be frustrating.-=> Jim

That's what I am using and it is totally hosed. Whenever I am connected to SqueezeCenter, my Squeezebox will completely freeze within minutes. It work flawless, however, through SqueezeNetwork. What did you do to fix whatever your problem was?

jrichardson
2008-04-30, 11:01
That's what I am using and it is totally hosed. Whenever I am connected to SqueezeCenter, my Squeezebox will completely freeze within minutes. It work flawless, however, through SqueezeNetwork. What did you do to fix whatever your problem was?

SqueezeCenter: 7.0.1 - 19133 (or later)
Controller software version: 7.1 r2349 root@padbuild #53 (or later)
Firmware: 23 (as stated on controller when it is connected to receiver)

http://www.slimdevices.com/downloads/nightly/latest/trunk/

Robin D
2008-05-05, 23:42
I have solved my problem and the Duet now works!!

I thought I'd follow up and post my solution to my whole problem for completeness;



- Loss of connection to wireless network
- Loss of conection to music source (blue symbol)
- Jittering/stuttering of streamed music despite acceptable signal strength.
- Constant 'Software Updates' loop/failure every time I wanted to use it.
- All of the above unpredictable/at random and resolving/un resolving regardless of my input.

SqueezeCenter Version: 7.0.1 - 18284 - Windows XP - EN - cp1252


Solution:
- I needed the newest nightly build od SC to overcome the Networking Problems
- I needed to manually load the Controller firmware using a SD card because the newest build had a software update problem
- Not clear in the instructions - I needed to do a factory reset, with the ethernet cable inserted BEFORE resettingn the controller. The Ethernet/Hybrid options were then available

Also relevent may be that I returned the original Duet for test/repair and received a replacement.

Best regards and good luck!
Robin

Kim.T
2008-05-06, 00:24
- Not clear in the instructions - I needed to do a factory reset, with the ethernet cable inserted BEFORE resettingn the controller. The Ethernet/Hybrid options were then available

Robin
Why was that nessesary ? Did you get an replacement for both receiver an Controller - I guess for my version of the Receiver this sould not be nessesary because the FW of the Controller should already be up to date.

Robin D
2008-05-06, 00:54
I had the whole set replaced. I read somewhere (on the forum) that if the Reciever is not re-set first, the Controller does not recognise fully and the options are limited (my interpretation from memory).

As long as the Controller isn't failing to update through the wireless network, don't worry about it.

**Incidentally, after 3 months of waiting, fiddling, exchanging and fiddling, I got the thing to work last night - as reported above. Fantastic!

I then made the mistake of turning it off overnight. When turned on, the reciever works (from the Browser) but the Controller no longer sees the Reciever.

Needless to say I am not very happy.

Anyone have any clues as to what the problem Now is?.... ****

Robin

pablolie
2008-05-11, 15:22
see thread
http://forums.slimdevices.com/showthread.php?p=301063#post301063

i bought the duet a few days ago, installed it, and trouble set in where previously the SB3 had left such great impressions that i own 3 of them.

the SBR works great and sounds great (i use the optical IF to feed an external DAC).

but the SBC is another story altogether.

i have upgraded to the latest nightly, so the controller now has
version 7.0.1 r2409 pad #62...

the rest of the config is quite straightforward...

SqueezeCenter InformationSqueezeCenter Version: 7.0.1 - 19608 @ Sun May 11 00:41:20 PDT 2008 - Debian - EN - utf8
Server IP address: 192.168.1.104
Perl Version: 5.8.8 i486-linux-gnu-thread-multi
MySQL Version: 5.0.45-Debian_1ubuntu3.3

Platform Architecture: i686-linux

Hostname: pablo-linux

Server Port Number: 9000

Total Players Recognized: 1


Player InformationName: elk-livroom

Model: receiver

Firmware: 23

The IP address for this player is: 192.168.1.106:21062

The Ethernet MAC address for this player is: 00:04:20:16:30:f6

Wireless Signal Strength: 97

as mentioned, even with this the controller loses connectivity every few minutes, the improvement now is that it reconnets more readily - but i find the product quite unusable.

pablolie
2008-05-11, 20:10
for the record i have found the Duet so unusable that i have decommissioned it in its original intended place of deployment. i have set up a SB3 instead. the Duet will either get returned or will sit it out in an area of very occasional use, waiting for firmware and software to come up to par.

my opinion: Duet is not ready for primetime. i take ownership for buying a cutting edge product that was basically a beta trial, and will simply watch the development from the sidelines, but i can not recommend ths product to anyone - unlike the SB3, for which i am an effective evangelist.

Ben Sandee
2008-05-11, 20:21
On Sun, May 11, 2008 at 10:10 PM, pablolie <
pablolie.39a22z1210562101 (AT) no-mx (DOT) forums.slimdevices.com> wrote:

> unlike the SB3, for which i am an effective
> evangelist.


If you evangelize anything like you rant then I doubt you are an effective
evangelist. You need to cite specific problems for a rant to be effective.

Ben

pablolie
2008-05-11, 20:37
On Sun, May 11, 2008 at 10:10 PM, pablolie <
pablolie.39a22z1210562101 (AT) no-mx (DOT) forums.slimdevices.com> wrote:

> unlike the SB3, for which i am an effective
> evangelist.


If you evangelize anything like you rant then I doubt you are an effective
evangelist. You need to cite specific problems for a rant to be effective.

Ben


i stated both the issue and posted the configuration. i don't think slim devices needs you to come to their defense, they can talk for themselves.

do *you* own a Duet? does it work flawlessly?

my "rant" was topic related. look at the title. yours wasn't.

zzap
2008-05-14, 12:19
the controller loses connectivity every few minutes

You may want to look at this thread:
http://forums.slimdevices.com/showthread.php?t=47190

The controller went from useless to really-good just by turning off "Wireless Power Save".
It uses a lot of battery power but I don't have connection problems anymore.

pablolie
2008-05-14, 15:21
You may want to look at this thread:
http://forums.slimdevices.com/showthread.php?t=47190

The controller went from useless to really-good just by turning off "Wireless Power Save".
It uses a lot of battery power but I don't have connection problems anymore.


that is an awesome tip - i had not seen a powersaving option (and had looked for it), i did suspect this may have been a wireless power saving issue. i will definitely check this out and report.

PeterDB
2008-05-14, 15:37
You may want to look at this thread:
http://forums.slimdevices.com/showthread.php?t=47190

The controller went from useless to really-good just by turning off "Wireless Power Save".
It uses a lot of battery power but I don't have connection problems anymore.

What is "a lot of battery power"? How much time can you now use the remote without having to charge again?

Rgds, P.

Kim.T
2008-05-15, 00:09
This is an "old" tip.
My romote can operate apporx 3-4 hours in this mode.

zzap
2008-05-15, 12:57
What is "a lot of battery power"? How much time can you now use the remote without having to charge again?

I also get around 3-4 hours worth with WPS off - had hoped for more.
However I cannot say how much of a difference this setting does because the controller never worked properly without disabling it.

The good news is also that 7.0.1 has been released now, so it's not necessary to run beta software anymore in order to access this setting.


This is an "old" tip
Whilst being "old" it was certainly not readily available; neither as information on the forums (probably me primarily targeting the "beginners" forum - seemed like the best option - and/or just not specifying the "correct" search keywords) nor in the official software (needing beta software to even access this setting).

thealmost
2008-05-27, 07:15
Here is my system:

Everything is hardwired via ethernet to Netgear WWGR614 v6 wireless router, firmware V2.0.19_1.0.19NA. The wireless is turned on for connection to my laptop occasionally, but the remote is configured to wirelessly connect via SB, not the router. SB firmware is 23. Remote firmware is the lastest Jive.

Today I can no longer get to SqueezeCenter or SqueezeNetwork. The issue is that the communication between the SB and SqueezeCenter and between remote and SB is inconsistent.

Using OSX v 10.4.11

I'm using the latest version of SqueezeCenter 7.0.2 something although it shows up as 7.0.1 on the applet window.

One thing that happens occassionally that should be noted is that my computer pops up a window telling me that the host name is in conflict. My computer name is OfficeG5 and it will say that there is a host name conflict and that it must rename my computer to OfficeG5-2, etc. It's now up to OfficeG5-5. Maybe this has something to do with it. It seems that when the SB is assigned a different IP address from the DHCP on the router, this is when all hell breaks loose.

I'd try static IP addresses for everything on my network, but I haven't read anywhere about how to assign the remote or SB for that matter, an IP address of my choosing. I can currently ping my SB but I can't get into the settings menu to change anything. I haven't done a factory reset yet because frankly I'm tired of this mess. I've been dealing with it all weekend.

I'll try anything at this point.


Tyler

Ramage
2008-05-27, 07:23
Here is my system:

Everything is hardwired via ethernet to Netgear WWGR614 v6 wireless router, firmware V2.0.19_1.0.19NA. The wireless is turned on for connection to my laptop occasionally, but the remote is configured to wirelessly connect via SB, not the router. SB firmware is 23. Remote firmware is the lastest Jive.

Today I can no longer get to SqueezeCenter or SqueezeNetwork. The issue is that the communication between the SB and SqueezeCenter and between remote and SB is inconsistent.

Using OSX v 10.4.11

I'm using the latest version of SqueezeCenter 7.0.2 something although it shows up as 7.0.1 on the applet window.

One thing that happens occassionally that should be noted is that my computer pops up a window telling me that the host name is in conflict. My computer name is OfficeG5 and it will say that there is a host name conflict and that it must rename my computer to OfficeG5-2, etc. It's now up to OfficeG5-5. Maybe this has something to do with it. It seems that when the SB is assigned a different IP address from the DHCP on the router, this is when all hell breaks loose.

I'd try static IP addresses for everything on my network, but I haven't read anywhere about how to assign the remote or SB for that matter, an IP address of my choosing. I can currently ping my SB but I can't get into the settings menu to change anything. I haven't done a factory reset yet because frankly I'm tired of this mess. I've been dealing with it all weekend.

I'll try anything at this point.


Tyler

Stay cool, Squeezenetwork went down from about 11:30 GMT.

There are lots of posts about this in the forum

thealmost
2008-05-27, 07:35
Hello all,

My SqueezeCenter did not launch automatically on the mac this morning. Thus, the SB would not find the computer. This is why I could ping the SB after a reset of course, but not use it. So, once I started the SC manually and did a factory reset on the SB, remote and made the "wireless timeout" change in the remote menu, all is working again.

I'll let you know for how long.

I must say that when the system is working, I'm thrilled. The sound DAC is decent, although not as good as my low end Rotel CD player. But, hey this is why there is an optical out yes? When the network goes awry, this is when I question the hours and hours of CD ripping and artwork gathering I've done.

Thanks,

Tyler

jezford
2008-05-31, 01:26
Yep, I have the same Controller connection problems as those at the start of this thread -

Squeezebox3 and a receiver both holding connection fine (the former Ethernet, the latter wireless). But the Players regularly disappear from the Controller, or it can't log onto the computer running SC.

Sometimes the Controller does the rotating ball thing and says Please Wait; sometimes it takes forever to connect to one of the players - and if it can't, that player disappears from the player list, to mysteriously reappear minutes, hours or days later.

All firmware updated - if I tell the Controller to firmware update, it tries but gets stuck every time - sometimes saying just 'Copying Update', sometimes with a percentage that eventually jammed (the record is 68%). Once it even changed to 'Verifying', but never finishes, so you have to cancel it to the sad news that the update failed. I gather from other threads that there isn't really an update at all. So a pretty dumb implementation then.

Running OSX 10.4.11 on a PPC Mac G4.

Is it my lovely draft-N Linksys wireless router? I've seen a few threads saying the router's the problem.

ALSO the receiver downstairs (maybe 5m from the WiFi router, with one chipboard ceiling to traverse) doesn't get a solid enough signal to prevent regular breakup. Could that be the ageing Mac I'm serving from?

I'm reviewing this for Geare magazine in Australia, so if you're reading Jim, help me out, otherwise I may have to be rude...

thealmost
2008-06-03, 03:28
This thread is very popular, which is a strong indicator that there are a ton of us out here flopping in the wind with our intermittently functioning duets. Can we have an update on these network issues from someone at Slim? I keep applying the latest SqueezeCenter releases, even the beta versions, in hopes that something will improve. Nothing. I'm tired of the blue light and silence. I'm ready to scratch Duet and downgrade to Slim3 server if that will help or package the whole thing up and send it back.

That said, I'm happy to be the guinea pig if Slim wants to give me a call and run some diagnostics.

What's the word folks?

If it's a router issue, I'll buy a different one. If it's DHCP, I'll go static. If it's a setting I need to change, I'll try it. Just give us some things to try so we can post feedback.

Cheers,

Tyler

thealmost
2008-06-03, 04:05
Mac Server
Squeeze Center Version: 7.3-20424 (I'm trying everything)
Mac G5 PPC Quad processor
OSX 10.4.11

SB Receiver
Firmware 23
Remote: 7.0.1 r2448
Remote connects via SB Receiver

Router
Receiver hardwired to Netgear WGR614v6 with latest firmware: V2.0.19_1.0.19NA
DHCP on
UPnP off
RIP off

Happy to answer any other questions.

I was able to get back on this morning by resetting the router, resetting the receiver and factory resetting the remote.

I mentioned this before, but when I reset my router I get this message on my computer, which doesn't bode well. I believe the receiver can no longer find my computer once this happens.

Attached is an image of the message.

Thanks,

Tyler

radish
2008-06-03, 06:12
I was able to get back on this morning by resetting the router, resetting the receiver and factory resetting the remote.

I mentioned this before, but when I reset my router I get this message on my computer, which doesn't bode well. I believe the receiver can no longer find my computer once this happens.


You have network issues, nothings going to work right until that's resolved. I'd recommend finding someone who knows their way around Mac networks to sort it out for you.

thealmost
2008-06-03, 06:16
Thanks for the tip. The odd part is that my network worked fine before adding the SB system to it. I'll try hard resetting the router and reconfiguring from scratch.

radish
2008-06-03, 06:20
How many computers are on the network? The Mac thinks there are name conflicts going on and it's unlikely the router has anything to do with it, unless there's something wacky going on like one machine with two interfaces but the same name on both?

thealmost
2008-06-03, 06:28
Hi,

There are only two computers on the network hardwired, one PC, one mac. Occasionally my daughter pipes in via wireless with a PC to the Netgear router.

Thanks for helping out. I won't be able to reply until this evening.

Cheers,

Tyler

thealmost
2008-06-03, 20:24
OK, so I scrutinized my router settings. I did a factory reset by pushing the little recessed button on my netgear router. Then I did a restore of the settings and saw that my subnet mask for my internet IP was 255.255.252.0 while the LAN IP was 255.255.255.0. I'm not sure if that is wrong or not as I don't grasp subnet masks very well. I decided to set my LAN IP address to match the internet IP and wallah. All I can tell you is that when I reboot the computer now, squeezecenter starts and finds the SB! I can also now unplug the router and when it comes back on, there is not a second of delay before SB is back on. Sweet. I also found a way to stop those annoying messages that keep coming up on the mac telling me that another host exists with my computer name. I can't find the link but it involves using the Terminal utility to manually add an entry which hard sets the computer to a hostname. HOSTNAME=OFFICEG5, is what I added. You can do a google search on that and should be able to find it without difficulty. Well, let's hope this is the last time you hear from my whiny ass on this thread. I'll be sure to stop back by if my connectivity acts up again.

Sheesh, I just wanted to listen to music. Wrong subnet, who knew?

Cheers all

thealmost
2008-06-04, 05:31
OK, I spoke too soon. This morning when I turned my computer on I was hoping the blue light would turn white on the SB. No. SqueezeCenter was up and running. But the SB simply would not hook in. I power cycled the router and boom. White light. Everything is fine. However, the "same host" issue is not over. There must be an issue with this router releasing connections completely.

Any ideas Slim?

So, while better, at least I can play music, I'm still less than fully functional. Here are my IP settings to improve the picture of my system.

Cheers,

T-

tyler_durden
2008-06-04, 11:43
I'm having the same connection problems between the router and the controller as many have reported here. My set-up is a Linksys WRT54G v5 router with WPA (TKIP) encryption and latest firmware (1.02.5). The router is the DHCP server and assigns all IP addresses. I am running SC 7.0.1-19705 on a dedicated linux server.

The SBR (firmware 23) connection is reliable (once I manage to get it set up) as is my SB3 connection. My other computers have no problem connecting to the network. The SBC (7.0.1 r2448) is the only problem part in the system. When I put the SBC battery into my jive beta controller (MAC address 00:13:E0:A1:78:3B), it works fine, same firmware, though the jive remote now complains about an invalid MAC address when it boots up.

It seems that some hardware change between the jive remote and the SBC is making a difference. The weird thing is that the SBC was working fine for months, then about 2 months ago it started having problems. Nothing in my system has changed during that time. Maybe the wireless modem in the SBC is failing prematurely, or there was some assembly problem.

I have tried clearing the powersave option and it does no good. If the controller is within a few feet of the router, all is well. As soon as I go maybe 20 feet away from the router, the signal strength drops and the connection is lost.

MrSinatra
2008-06-04, 13:09
my friend has your router, v8.

his computer, with vista (and maybe his xp ones too i'll ask) when coming off of hibernate for sure, and maybe sleep, don't reconnect to the internet.

i've been trying to solve the issue for him without much luck.

i wonder if it is some kind of inactivity / sleep / power saving issue though, and perhaps the SBC has the same issue as his laptop does.

grb@aughton.vianw.co.uk
2008-06-04, 13:55
I have the same problem intermittently which is very irritrating. On occasions everythin is fine but next day I am unable to connect to network. Wireless seems fine - works for oter devices (& for SB most of the time). Otre times Iget the spinning circle trying to connect then "try again - missing squeezebox.

I am wihin feet of the router & B light is stuck on yellow.

Tried hard reset etc & turning Firewall off

Should I return the kit as such unreliability is hopeless.

thealmost
2008-06-04, 17:42
Since this thread regarding network flakiness is the highest in this forum, only second to the one announcing the duet release, one would think that slim should be taking this very seriously.

I'm now starting to add other annoying issues to the list. Like, one songs plays while another shows up in the now playing. Took a factory reset to fix that one. Also, stuff I purchased on iTunes used to play back, my latest purchase won't show up in the list.

I'm getting ready to cash in unless we start seeing answers or I at least get an update indicating that there are real issues here that need handling. Keeping us in the dark is not helping. And today I could not get support on the phone. On hold for at least a half hour.

My two cents.

Tyler

aiken
2008-06-04, 18:34
I'm also having a terrible time with the Controller's network connectivity. Right now I've got it sitting a few feet away from the wireless router, and everything else in the house (including this laptop, as I type, about 200ft away) works fine.

But pinging the Controller shows terrible network issues:


Reply from 10.23.17.127: bytes=32 time=5ms TTL=64
Reply from 10.23.17.127: bytes=32 time=3244ms TTL=64
Reply from 10.23.17.127: bytes=32 time=7ms TTL=64
Request timed out.
Request timed out.
Reply from 10.23.17.127: bytes=32 time=883ms TTL=64
Reply from 10.23.17.127: bytes=32 time=2427ms TTL=64
Reply from 10.23.17.127: bytes=32 time=3ms TTL=64
Request timed out.
Request timed out.
Reply from 10.23.17.127: bytes=32 time=1924ms TTL=64
Reply from 10.23.17.127: bytes=32 time=6ms TTL=64
Reply from 10.23.17.127: bytes=32 time=471ms TTL=64
Request timed out.
Reply from 10.23.17.127: bytes=32 time=293ms TTL=64
Request timed out.

And all told, I'm seeing 50% packet loss:

Ping statistics for 10.23.17.127:
Packets: Sent = 89, Received = 44, Lost = 45 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3708ms, Average = 938ms

I've tried turning off wireless power saving, and see no difference. Even when I first boot the Controller, it comes up with high latency and lots of packet loss.

The router is a Linksys WRT54GL running the latest Linksys firmware. I'm really loathe to replace the router, which is working fine for 5 or 6 other wireless devices, just to see if it helps.

Any ideas? The Controller really isn't usable this way. The Receiver works fine wirelessly and I can play music by controlling it from Squeezecenter, but that's small consolation.

pablolie
2008-06-05, 23:21
the power saving config made a huge difference with my Linksys WRT54GX4, even though i am still not using it for main listening room duty and watching it suspiciously after being shocked early. however, let it be known it does seem to work much better (albeit not always) with the power-settings and a Linksys WRT54GX4, which didn't work at *all* initially...

thealmost
2008-06-06, 05:33
Last night I found a tip to move my router IP address range from the standard 198.162.1.1 to something different because it is usually the default. I changed it to 172.16.4.1 and the DHCP range to 50 through 70. Today I fired up my computer and for the first time in a long while the SB simply works!

I had to factory reset everything and power cycle my router and cable modem after I made the IP range change. But man is it more responsive. Go figure.

Anyone?

I'll post if anything else happens.

Letten
2008-06-06, 13:06
Hi,

I got rid of my connection problems by changing WPA-PSK (TKIP) security to WEP 128 bit and MAC-filtering. The problem seemed to be reauthentication, during which the connection was lost.

I'm using a ZyXEL P-660HW router, and my reauthentication timer was set to 3600 seconds (1 hour). SC is running on a Vista laptop also wirelessly connected. First I got rid of some DHCP errors by switching to static ip on the server. But I still got disconnections, then I tried using a ethernet cable to the server to rule out wireless problems on the serverside, still diconnections at 1 hour intervals now, then I tried reducing the reauthentication timer to 5 min, and wow, now the disconnections came at 5 min intervals!.

Unfortunatly my only choices were to increase the timer to max. 9999 seconds (2h45m) or to disable WPA security. First I tried without security and it worked without disconnections for 8 hours straight. Afterwards I tried with WEP and still no problems.

Hopefully my frustrations are over now and I can start enjoying my music :0)

To test whether reauthentication is a problem try to extend or decrease the timer and observe or disable WPA completely for a while.

/Letten

thealmost
2008-06-09, 18:34
Changed to WEP with 128bit, but I doubt this had any real consequence because my SB is hardwired and the remote is connecting via the SB. However, I'm definitely operating better. The switch to something other than 192.168.1.1 for the router IP address and IP range seemed to have to single greatest effect on stability of my system. Been up for a few days now, even after restarting my computer several times, she comes right back up!

Nice.

T-

raffo333
2008-06-20, 00:05
Same problems here, i really cant understand how the remote loses the connection with the box even if is in ad hoc connection and i am in the same room.
Regards

JJD
2008-07-31, 16:14
I have been trying to set up my squeezebox Duet for several days.
I keep losing the connection to my SB (Controller gives all the messages you can read in this Thread. Sometimes I get a connection but that lasts for a few minutes. If I try to play songs during that time I get the blinking > for a longer period of time and then the connection to my computer is lost (then I can play songs on the SB by using Squeezecenter in my Browser).
If it doesn't lose connection inmediately it takes ages to select songs. Getting a list with artists takes like 2 minutes (3800 songs on a network disk).
Even SqueezeCenter in the browser is slow. I play songs via OTSJUke via the same Network and everything works instantly (also with Windows Media Player). The SC Cache directory is like 60+ Mbyte for just 3800 songs... I rebuild it completely a few times to ensure nothing was wrong. If I select another song it takes sometimes 30 seconds before it starts playing.
THis improved a bit by giving the process Real Time Priority! MEmory is enough (1.5 GB on a 3 GHz XP machine).

My setup:
Hybrid
TCP address SB 172.16.134.2
TCP controller 172.16.134.1
Subnetmask 255.255.255.0
Firmware SB 36
Software controller7.1r2722
Software SqueezeCenter-versie: 7.1 - 22170 @ Mon Jul 28 13:36:57 PDT 2008 - Windows XP - NL - cp1252
I got the DUet with the 7.01 software but after the first issues I updated to 7.1

Switching of AVAST Virus scanner and my Firewall doesn't help anything.
All my other equipment (6PC's, 3 Network drives, 2 Network Printers, 5 Network Cameras work great on the network..... I switched of the cameras during working with the Duet to ensure maximun Network Bandwith.
Everything including the SB is wired. The Controller is connected via the Squeezebox. I have tried it via my wireless router however this didn't give any improvements either.

RoonieQ
2008-08-02, 08:40
I have been trying to set up my squeezebox Duet for several days.
I keep losing the connection to my SB (Controller gives all the messages you can read in this Thread. Sometimes I get a connection but that lasts for a few minutes. If I try to play songs during that time I get the blinking > for a longer period of time and then the connection to my computer is lost (then I can play songs on the SB by using Squeezecenter in my Browser).
If it doesn't lose connection inmediately it takes ages to select songs. Getting a list with artists takes like 2 minutes (3800 songs on a network disk).
Even SqueezeCenter in the browser is slow. I play songs via OTSJUke via the same Network and everything works instantly (also with Windows Media Player). The SC Cache directory is like 60+ Mbyte for just 3800 songs... I rebuild it completely a few times to ensure nothing was wrong. If I select another song it takes sometimes 30 seconds before it starts playing.
THis improved a bit by giving the process Real Time Priority! MEmory is enough (1.5 GB on a 3 GHz XP machine)
Does anybody see a solution for these issues or do have to send the .... thing back to Logitech (after browsing through the 25 pages around this issue I am a bit worried if the developpers can solve these issues).

My setup:
Hybrid
TCP address SB 172.16.134.2
TCP controller 172.16.134.1
Subnetmask 255.255.255.0
Firmware SB 36
Software controller7.1r2722
Software SqueezeCenter-versie: 7.1 - 22170 @ Mon Jul 28 13:36:57 PDT 2008 - Windows XP - NL - cp1252
I got the DUet with the 7.01 software but after the first issues I updated to 7.1

Switching of AVAST Virus scanner and my Firewall doesn't help anything.
All my other equipment (6PC's, 3 Network drives, 2 Network Printers, 5 Network Cameras work great on the network..... I switched of the cameras during working with the Duet to ensure maximun Network Bandwith.
Everything including the SB is wired. The Controller is connected via the Squeezebox. I have tried it via my wireless router however this didn't give any improvements either.

Same experience for me when I brought a trial Duet unit home for testing. All of the dropped connections, input response delays, and inconsistent reliability made its use too frustrating and therefore back it went. Defintiely not ready for prime time for me - still way too buggy.

markushk
2008-08-05, 04:39
I wish I'd seen this thread before buying my Duet on Saturday!

I think I have exactly the same issues as described here... too many pages of problems to read all the comments yet.

The Duet takes a long time to connect to both my SB3 & SqueezeCentre. Once it does it loose's connection shortly afterwards (sometimes within a minute). Nothing else on my network is having connectivity issues.

I the same version numbers as above.

Can someone from Logitech confirm that they are able to replicate these issues and are workin on a solution please.

Markus

Letten
2008-08-05, 05:25
What are you using for running Squeezecenter?

Brian Equator
2008-08-05, 12:48
I wish I'd seen this thread before buying my Duet on Saturday!

I think I have exactly the same issues as described here... too many pages of problems to read all the comments yet.

The Duet takes a long time to connect to both my SB3 & SqueezeCentre. Once it does it loose's connection shortly afterwards (sometimes within a minute). Nothing else on my network is having connectivity issues.

I the same version numbers as above.

Can someone from Logitech confirm that they are able to replicate these issues and are workin on a solution please.

Markus

I have the exact same issues, and it's beyond frustrating.

I run Squeezecentre on my main PC with Vista and I use a Netgear WNR834Bv2 router. My PS3 connects without any problems.

Any suggestion as to what to do would be greatly appreciated.

Letten
2008-08-05, 13:11
Hi Brian,

I've had lot's of connection problems and router-crashes and after a lot of experimenting I have come to the conclusion that my Vista Laptop (that I bought to run SC) was the main source of my problems.

I thought my wireless was ok, and I had no problems using the Vista laptop for internet browsing - but a look in the system log of Vista revealed lots of dhcp errors, disconnects and reconnects, not a problem for browsing and email, but not optimal for streaming.

Do You have access to another PC (not Vista) that you could try an run SC on instead? keep Vista completely off, while testing this.

Also try this:

Wireless security if used, try disableling. If that helps try moving to WEP. I've had problems with WPA and reauthentication.

Also try static IP's on the PC with SC.

Good luck

Brian Equator
2008-08-06, 13:21
Hi Brian,

I've had lot's of connection problems and router-crashes and after a lot of experimenting I have come to the conclusion that my Vista Laptop (that I bought to run SC) was the main source of my problems.

I thought my wireless was ok, and I had no problems using the Vista laptop for internet browsing - but a look in the system log of Vista revealed lots of dhcp errors, disconnects and reconnects, not a problem for browsing and email, but not optimal for streaming.

Do You have access to another PC (not Vista) that you could try an run SC on instead? keep Vista completely off, while testing this.

Also try this:

Wireless security if used, try disableling. If that helps try moving to WEP. I've had problems with WPA and reauthentication.

Also try static IP's on the PC with SC.

Good luck

Thank you.

I went through this whole thread and tried the suggestion to change the IP address of the router from the default (192.168.1.1). After this the SB worked perfectly well, but I was unable to connect to the internet. I then changed it back to 192.168.1.1, and so far it all works. I have my doubts though.

I'll be the first to admit, that I'm not very network savvy, but I find these issues unacceptable.

BTW, I haven't got access to an XP PC, and i already use WEP. I'll try the static IP thing, if I encounter problems again.

Cheers,
Brian

Stevan
2008-08-10, 00:46
I also have problems with the SBC not connecting to Squeezecenter unless I remove the battery or reset it by pressing the 'Home' button for several seconds.

There were numerous discussions about Wireless Power Save not being correctly implemented in some WiFi Acces Points. This being said, there should be no problems when using the Duet in bridged mode, right? WRONG!
Even when using the Duet in bridged mode the problem occurs: still a blue icon (the SBC is pingable through the network).

However, I noticed something which might help solving the problem: the problem ony occurs after leaving the SBC on the charger for some hours (e.g. overnight). When I don't put the SBC on the charger the SBC works fine the next morning: after picking it up, it says: 'Be patient' (or something equivalent in Dutch), then the menu shows with a blue icon which turns white after 5 seconds or so. After that everything works as it's supposed to do.

My setup:
Squeezecenter 7.1 (on a QNAP TS-209 NAS), SBC firmware v7.1r2722, SBR Firmware 36 (according to my controller)
Linksys WRT54G, with DD-WRT v24-sp1 (07/27/08)

Hope this helps in solving the problem.

chemirocha
2008-08-12, 03:49
I have a similar situation to Stevan in that the controller will lose connection to the SC server overnight whilst in the cradle and not reconnect without restarting the controller.

The wireless power saving makes no difference.

I am also running SC on a QNAP TS-209 Pro which is set up to do a scan for new music overnight, during which time it becomes un-responsive. So I tried running a scan this morning manually, after reconnecting the controller, and lo and behold the controller has lost its connection and cannot re-connect, even though the scan has completed and the server is now responding normally.

I will try disabling the scan tonight and leave the controller in the cradle to see if it loses the connection again.

BTW I can ping the controller successfully even though it can't connect, in fact I can even log in using SSH so it is not a wireless or network issue.

So, it seems to me that the real problem is the controller and SC being unable to re-establish a dialogue once interrupted. However, it is odd, since I can move the controller out of wireless range (and get the blue icon) yet it will reconnect perfectly once within range again.

I hope this helps someone sort this problem, because it is really annoying!



EDIT: My details are:

SqueezeCenter Version: 7.2 - 22440 @ Fri Aug 8 02:00:32 PDT 2008 - Linux - EN - utf8
Server IP address: 10.0.1.10
Perl Version: 5.8.8 armv5tejl-linux-thread-multi
MySQL Version: 5.0.27

Platform Architecture: armv5tejl-linux

Hostname: NAS-1

Server Port Number: 9001

Total Players Recognized: 1

Player Information
Name: Main Squeezebox
Model: receiver
Firmware: 42
The IP address for this player is: 10.0.1.100:43672
The Ethernet MAC address for this player is: 00:04:20:16:7b:9d
Wireless Signal Strength: 62

Controller Version: 7.2r2826 (Aug 9 02:17:21)


From the controller messages log, after the scan has been started and completed and I pick up the controller to re-establish a connection;



Aug 12 11:29:32 SqueezeboxController user.info jive: (NetworkThread.lua:249) - NOTIFY: serverRescanning(SlimServer {NAS-1})
Aug 12 11:30:43 SqueezeboxController user.err jive: (NetworkThread.lua:139) - network thread timeout for Task(SocketHttp {NAS-1_Chunked}(R))
Aug 12 11:30:43 SqueezeboxController user.err jive: (SocketHttp.lua:781) - SocketHttp {NAS-1_Chunked}:t_rcvResponse.pump() error:inactivity timeout
Aug 12 11:30:43 SqueezeboxController user.info jive: (Comet.lua:745) - Comet {NAS-1}: _getEventSink error: inactivity timeout
Aug 12 11:30:43 SqueezeboxController user.info jive: (Comet.lua:913) - Comet {NAS-1}: handleAdvice state=CONNECTED
Aug 12 11:30:43 SqueezeboxController user.info jive: (NetworkThread.lua:249) - NOTIFY: cometDisconnected(Comet {NAS-1})
Aug 12 11:30:43 SqueezeboxController user.info jive: (SlimServer.lua:541) - SlimServer {NAS-1} disconnected
Aug 12 11:30:43 SqueezeboxController user.info jive: (NetworkThread.lua:249) - NOTIFY: serverDisconnected(SlimServer {NAS-1}, 0)
Aug 12 11:30:43 SqueezeboxController user.info jive: (SlimDiscoveryApplet.lua:422) - serverDisconnected SlimServer {NAS-1}
Aug 12 11:30:43 SqueezeboxController user.info jive: (SlimServer.lua:476) - SlimServer {SqueezeNetwork}:connect
Aug 12 11:30:43 SqueezeboxController user.info jive: (Comet.lua:954) - Comet {NAS-1}: advice is retry, connect in 1.615 seconds
Aug 12 11:30:53 SqueezeboxController user.info jive: (NetworkThread.lua:249) - NOTIFY: cometConnected(Comet {SqueezeNetwork})
Aug 12 11:30:53 SqueezeboxController user.info jive: (SlimServer.lua:518) - SlimServer {SqueezeNetwork} connected
Aug 12 11:30:53 SqueezeboxController user.info jive: (NetworkThread.lua:249) - NOTIFY: serverConnected(SlimServer {SqueezeNetwork})
Aug 12 11:30:53 SqueezeboxController user.info jive: (SlimDiscoveryApplet.lua:436) - serverConnected
Aug 12 11:30:53 SqueezeboxController user.info jive: (SlimServer.lua:201) - SlimServer {SqueezeNetwork}: has no players!
Aug 12 11:31:33 SqueezeboxController user.info jive: (SlimDiscoveryApplet.lua:171) - Removing server SlimServer {NAS-1}
Aug 12 11:31:33 SqueezeboxController user.info jive: (NetworkThread.lua:249) - NOTIFY: serverDelete(SlimServer {NAS-1})
Aug 12 11:31:44 SqueezeboxController user.info jive: (SlimDiscoveryApplet.lua:171) - Removing server SlimServer {NAS-1}
Aug 12 11:31:44 SqueezeboxController user.info jive: (NetworkThread.lua:249) - NOTIFY: serverDelete(SlimServer {NAS-1})
Aug 12 11:31:52 SqueezeboxController user.info jive: (SlimServer.lua:201) - SlimServer {SqueezeNetwork}: has no players!
Aug 12 11:31:54 SqueezeboxController user.info jive: (SlimDiscoveryApplet.lua:171) - Removing server SlimServer {NAS-1}
Aug 12 11:31:54 SqueezeboxController user.info jive: (NetworkThread.lua:249) - NOTIFY: serverDelete(SlimServer {NAS-1})
Aug 12 11:31:55 SqueezeboxController user.err jive: (NetworkThread.lua:139) - network thread timeout for Task(SocketHttp {NAS-1_Chunked}(R))
Aug 12 11:31:55 SqueezeboxController user.err jive: (SocketHttp.lua:471) - SocketHttp {NAS-1_Chunked}:t_rcvHeaders.pump:nil
Aug 12 11:31:55 SqueezeboxController user.info jive: (SqueezeboxJiveApplet.lua:584) - setPowerState=active acpower=false
Aug 12 11:31:55 SqueezeboxController user.info jive: (SqueezeboxJiveApplet.lua:997) - Set CPU speed 200000
Aug 12 11:31:55 SqueezeboxController user.info jive: (SqueezeboxJiveApplet.lua:630) - Restore effect volume 42
Aug 12 11:31:55 SqueezeboxController user.debug kernel: 256fs: div 4 => result 48828, deviation 4728
Aug 12 11:31:55 SqueezeboxController user.debug kernel: 512fs: div 2 => result 48828, deviation 4728
Aug 12 11:31:55 SqueezeboxController user.debug kernel: 384fs: div 3 => result 43402, deviation -698
Aug 12 11:31:55 SqueezeboxController user.debug kernel: best: fs=384, div=3, rate=43402
Aug 12 11:31:55 SqueezeboxController user.warn kernel: mapped channel 10 to 2
Aug 12 11:31:57 SqueezeboxController user.info jive: (SlimServer.lua:457) - Sending WOL to 00:08:9B:AC:94:23
Aug 12 11:31:57 SqueezeboxController user.info jive: (NetworkThread.lua:249) - NOTIFY: cometDisconnected(Comet {NAS-1})
Aug 12 11:31:57 SqueezeboxController user.info jive: (NetworkThread.lua:249) - NOTIFY: serverDisconnected(SlimServer {NAS-1}, 1)
Aug 12 11:31:57 SqueezeboxController user.info jive: (SlimServer.lua:457) - Sending WOL to 00:08:9B:AC:94:23
Aug 12 11:31:58 SqueezeboxController user.info jive: (SlimDiscoveryApplet.lua:422) - serverDisconnected SlimServer {NAS-1}
Aug 12 11:32:04 SqueezeboxController user.info jive: (SlimDiscoveryApplet.lua:171) - Removing server SlimServer {NAS-1}
Aug 12 11:32:04 SqueezeboxController user.info jive: (NetworkThread.lua:249) - NOTIFY: serverDelete(SlimServer {NAS-1})
Aug 12 11:32:14 SqueezeboxController user.info jive: (SlimDiscoveryApplet.lua:171) - Removing server SlimServer {NAS-1}
Aug 12 11:32:14 SqueezeboxController user.info jive: (NetworkThread.lua:249) - NOTIFY: serverDelete(SlimServer {NAS-1})
Aug 12 11:32:24 SqueezeboxController user.info jive: (SlimDiscoveryApplet.lua:171) - Removing server SlimServer {NAS-1}
Aug 12 11:32:24 SqueezeboxController user.info jive: (NetworkThread.lua:249) - NOTIFY: serverDelete(SlimServer {NAS-1})
Aug 12 11:32:34 SqueezeboxController user.info jive: (SlimDiscoveryApplet.lua:171) - Removing server SlimServer {NAS-1}
Aug 12 11:32:34 SqueezeboxController user.info jive: (NetworkThread.lua:249) - NOTIFY: serverDelete(SlimServer {NAS-1})
Aug 12 11:32:44 SqueezeboxController user.info jive: (SlimDiscoveryApplet.lua:171) - Removing server SlimServer {NAS-1}
Aug 12 11:32:44 SqueezeboxController user.info jive: (NetworkThread.lua:249) - NOTIFY: serverDelete(SlimServer {NAS-1})
Aug 12 11:32:48 SqueezeboxController user.info jive: (ClockApplet.lua:528) - Type: analog
Aug 12 11:32:48 SqueezeboxController user.info jive: (ClockApplet.lua:154) - Init Analog Clock
Aug 12 11:32:48 SqueezeboxController user.info jive: (ClockApplet.lua:117) - Init Clock
Aug 12 11:32:49 SqueezeboxController user.info jive: (ClockApplet.lua:154) - Init Analog Clock
Aug 12 11:32:49 SqueezeboxController user.info jive: (ClockApplet.lua:117) - Init Clock
Aug 12 11:32:49 SqueezeboxController user.info jive: (SqueezeboxJiveApplet.lua:584) - setPowerState=dimmed acpower=false
Aug 12 11:32:49 SqueezeboxController user.info jive: (SqueezeboxJiveApplet.lua:997) - Set CPU speed 200000
Aug 12 11:32:51 SqueezeboxController user.info jive: (SlimServer.lua:201) - SlimServer {SqueezeNetwork}: has no players!
Aug 12 11:32:54 SqueezeboxController user.info jive: (SlimDiscoveryApplet.lua:171) - Removing server SlimServer {NAS-1}
Aug 12 11:32:54 SqueezeboxController user.info jive: (NetworkThread.lua:249) - NOTIFY: serverDelete(SlimServer {NAS-1})
Aug 12 11:33:04 SqueezeboxController user.info jive: (SlimDiscoveryApplet.lua:171) - Removing server SlimServer {NAS-1}
Aug 12 11:33:04 SqueezeboxController user.info jive: (NetworkThread.lua:249) - NOTIFY: serverDelete(SlimServer {NAS-1})
Aug 12 11:33:14 SqueezeboxController user.info jive: (SlimDiscoveryApplet.lua:171) - Removing server SlimServer {NAS-1}
Aug 12 11:33:14 SqueezeboxController user.info jive: (NetworkThread.lua:249) - NOTIFY: serverDelete(SlimServer {NAS-1})
Aug 12 11:33:24 SqueezeboxController user.info jive: (SlimDiscoveryApplet.lua:171) - Removing server SlimServer {NAS-1}
Aug 12 11:33:24 SqueezeboxController user.info jive: (NetworkThread.lua:249) - NOTIFY: serverDelete(SlimServer {NAS-1})

and so on.

Stevan
2008-08-16, 02:39
I also tried disableing the auto-refresh option in Squeezecenter. And since disabling it, I never had a blue icon anymore!

I have disabled it for three days now and everything works as a charm. After updating the library the blue icon shows up again!

ollymbln
2008-08-17, 03:14
Just wanted to let you know, that I am experiencing the same problems already mentioned here before, but with some other hardware on the network/computer side:

I have to different networks - one contains an AVM Fritzbox 3170 (Firmware 49.04.57) running in 802.11b/g compatible mode with a WPA 2 encryption and a second one running an Apple TimeCapsule 1TB (Firmware 7.3.2) also WPA2 encryption. I used the Timecapsule only to negotiate if it makes the same problems like the AVM Fritzbox, as I am normally running TC as a 5GHz 802.11n only device, but I can approve that the same problems appear with the TC instead of the Fritzbox. On the computers side it is an Apple iMac running Mac OS X 10.5.4 (Built 9E17) using the iTunes library (iTunes 7.7.1).

As the Fritzbox (which ist quite popular in Germany as it is supplied with several DSL line contracts by many telcos) has a better webinterface to figure out the problem, let me tell you what happens. If I take a look into the webinterface I can see that the controller as well as the player have been assigned an IP adresse. The iMac has a fixed IP address. When I try to configure the Squeezebox it connects to the WLAN supplied by the Fritzbox and when it comes to the point to connect to the music library the SB controller says something like "Squeezebox (169.168...) can not connect..." - that means that the SB has got an invalid IP adresse while the router (Fritzbox) still states an valid one for the squeezebox controller and says that it is connected. A bit strange in my oppinion.

So I reseted the SB again and now it detects the network again, I can enter the password and the the controller says that the network connection can not be established. Doing the same procedure again a few times it worked after serveral tries but only for a few minutes. After that the connection dropped again and I experienced either the problem, that the commands I gave with controller was only executed after a few seconds or even minutes (while the music started/stopped playing in between several times) or even says again, that there is no connection.

On the Mac I tried Squeezecenter 7.0.1, 7.1 and at last the nightly build of 7.2 -no difference.

As I am running several other devices on the network (an Apple TV, a Sonos system, an HP WLAN Printer, a Sony PS3 etc.) and no one has got connection problems with the WLAN that definately seems to be a problem between the SB and the Fritzbox or WLAN in general. It does not even matter if there are about 3-4 meters between the WLAN base and the SB or about 12-13 meters (last one would be the usual setup for me).

As a last note from my side, I gave a second SB Duet to a friend of mine, running also a Fritzbox but with an QNAP209 as the server and he experienced similar problems. In the company I am working for we also set up a SB Duet and treid to connect it to a WLAN and an Mac as the server - not sucess running Apple Airport Base stations as WLAN access points. Last try was to give another SB Duett to another friend using a Netgear WLAN router as well as a ReadyNas as the server - that works flawlessly (as you see sometimes it is quite usefull to have access to several Squeezeboxes ;).

From my point of view, after all those tries the SB Duett controller seems to have problems with some kind of WLAN hardware and maybe a hugher ammount of other WLAN devices in the network (interferencies?).

So for me I am going on to use my Sonos system that works flawlessly and will try to use the Duett from time to time again while hopeing that it will work some day.

Oliver