Not working anymore?

[guschc]

When I open the Pebbos settings from the pebble app, I only get a 404 page.

Even though my speaker is still on the same IP address, Pebbos says it can't find it anymore.

Is Pebbos still working for anyone else with current Sonos?

[jamesfairhurst]

Can you try again please? I moved my website which hosts the settings file, didn't realise this was still in use!

[guschc]

the site is up, but the new IP I enter doesn't get submitted to the app, it keeps searching at the old IP.

Also, the current IP doesn't display in the settings, the field is empty (but that may already have been the case before, I'm not sure).

Yes, I still use my Pebble, all the current smart watches either suck or their batteries last only a day or so :-)

[jamesfairhurst]

I've made a change so if you could try again to test that would be helpful, I no longer have my Pebble so can't check.

[guschc]

Thank you, the settings work now: The current IP gets displayed and the App on the phone gets updated which whatever IP I enter on the settings page.

But the app is still stuck on "trying to find speakers on IP 192.168...." screen, even though the speaker exists on this IP address.

[jamesfairhurst]

Hmm not sure what else to try unfortunately, there have been no changes app wise - just where the settings page was.

[guschc]

Maybe Sonos made a change... But my self-built API based Raspberry Pi Scripts still work flawlessly.
Or it's something about my setup here. Can anyone else reading this please confirm if it still works?

[albertvaka]

I didn't get it to find my Sonos Beam even after setting the IP 😢

[guschc]

It would be great if it could be fixed, I miss Pebbos every day.

[albertvaka]

Can you share the command you use from your Raspberry Pi to control your Sonos? I can try to look into Pebbos' code but I have no idea how to talk to a Sonos device.

[jamesfairhurst]

The main URL the app pings is http://xxx:1400/status/topology which did return a list of all the devices, this doesn't seem to be the case anymore so probably suggests the Sonos api has changed. The app then made various SOAP requests to control the device e.g. volume up/down

Try looking at:

• https://github.com/jishi/node-sonos-http-api
• https://github.com/SoCo/SoCo

See if you can figure out the api. Sorry don't have my Pebble anymore.

[guschc]

I also use node-sonos from my Pi to control Sonos.

[albertvaka]

I've made a fork: https://github.com/albertvaka/Pebbos

So far I've managed to make it compile with a recent version of the Pebble SDK and removed the use of the topology endpoint (since it's no longer available). Unfortunately this means there's no autodiscovery: you have to specify the speaker IP and for now you can only control one speaker.

Next steps would be to add support for specifying more than one IP, or implementing autodiscovery the "brute force way" (testing all the IPs in a range). I might be able to parse the status endpoint to figure out speaker names, groups, etc. but for now I don't do any of that.