Closed dineshbhoopathy closed 9 years ago
Hmm OK, so just the Bridge appears in the app list on the Pebble, nothing else?
Also are you specifying a speaker IP or the bridge IP in the settings?
Yes, I specify the speaker IP and I can see it's trying to look for it but then lists the bridge ( to which the controls wouldn't work anyway )
What's the source code when you visit the below URL in your browser? Replacing the IP with your speaker's IP.
http://192.168.1.84:1400/status/topology
That is used to loop through the speakers and grab their name & IP.
Hmm, it's confusing really. About the setup, there are 3 sonos players (.18/.19/.20) in a group over a sonos bridge (.2). But .20 is the IP I use to control ( for instance from my socos client on my fedora box, the other IPs are not responsive ). The mediaservers are basically a registered sonos client with it's local media which is no use for us here I guess.
Maybe you could loop through zoneplayers, run a command to identify if the controls work and then add it to the pebble list ? Too bad I can't test things and submit a patch quickly. Just got my pebble 3 days ago :)
Feel free to ask if you need more information and thanks for your time mate!
It should be grabbing the "TV Room" ZonePlayer as it's not a Bridge and it's marked as a coordinator. Strange that it's not really. If you've time I'd suggest installing the Pebble SDK and try compiling & running the app locally. You'll then be able to log why it's not picking up the player.
Yes, planning on doing exactly that. Thanks for your help!
Hmm, I just noticed something weird. Like it 'did' detect TV Room as the coordinator but the IP for it is pointing to .2 instead of .20 ( I'm using the app to hard set it to .20 of course) and click on the label takes me to the menu but the controls just wouldn't work.
Interestingly I noticed in pebble settings that it has the option to select sonos and many many devices to control using the inbuilt music app and it works too
unable to connect to paired speakers as the sonos bridge is being detected as a speaker.
Sadly, specifying the IP address from settings doesn't help either.