Andronos does not find zones until zones are accessed by Sonos desktop app

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Try to access Sonos after it has been idle for a few hours (say coming home 
from work)
2. Andronos just says "Scanning..." forever and never finds the zones (I have a 
z90 plugged into the network and two s5's which are wireless.)

I have found that if I first access the zones with the Sonos desktop app, then 
Andronos is more likely to be able to find the zones successfully.

My speculation is that there is some sort of additional magic "wake up" message 
that the standard Sonos software knows to send, but Andronos does not.

What version of the product are you using? On what phone?
Andronos beta.44 (44) on T-Mobile G1 (Android 1.6)

Original issue reported on code.google.com by tetron.i...@gmail.com on 24 Sep 2010 at 10:44

• Merged into: #137

[GoogleCodeExporter]

For information
I have the same probleme, impossible to detect my sonos S5.
Have you an idea about this problem?

Original comment by sfoll...@gmail.com on 29 Sep 2010 at 12:16

[GoogleCodeExporter]

Same problem.
Very unstable connection of andronos to my sonos system

I recently updated the sonos system (was promted to do so by the native sonos 
controllers) - since then the connectivity has been unstable.

sonos software is version 3.3

Andronos is version beta.44

Original comment by carsteng...@gmail.com on 2 Oct 2010 at 11:46

[GoogleCodeExporter]

Same problem on my droid x .44 beta, although recently it can't find them at 
all.  Single WiFi, plays normally through the desktop app.

Original comment by SkyWagon...@gmail.com on 10 Oct 2010 at 3:27

[GoogleCodeExporter]

Same issue on an HTC Hero 2.1 and Samsung Apollo 2.1, both running the latest 
Andronos Beta 46. I think carstengaard might be right in that it is related to 
Sonos v3.3 build 14433290. I had to update when I recently added a CR200 
controller. The issue did indeed start around the same time.

Unlike tetron.interreality, I do not see any difference if I use the desktop 
controller to wake the zone players up. Scanning works very rarely, if at all. 
Only manually adding the Zone Player by IP address works and even then, it has 
usually disappeared again when you next go back to the zone list, requiring you 
to manually add it again.

As Ive commented against other issue logs, if a manually added ZP persisted 
between sessions and was immune to scan failures, then the issue would be 
resolved for me. Manually adding ZPs would only be a problem for someone whose 
ZPs regularly change IP address, although I believe most DHCP implementations 
reserve IP addresses for a reasonable period of time, which would make this a 
non-issue 

Original comment by suewoodl...@googlemail.com on 15 Dec 2010 at 1:30

[GoogleCodeExporter]

Just to follow up on this, on my T-Mobile G2 (Android 2.2) scanning for zones 
works almost all the time.

Original comment by tetron.i...@gmail.com on 15 Dec 2010 at 3:19

[GoogleCodeExporter]

Original comment by jre...@gmail.com on 10 Jan 2011 at 12:20

• Changed state: Duplicate