Hi
I have the saem issue since the app update...I cannot use my local airsonic server.
Will airsonic will be supported again? When?
Thanks
Hi,
same for me, since this update (catastrophic, the word is not an exaggeration) no more access to airsonic type libraries.
Sonos has made no response on this disappearance of service, and therefore no announcement is made on a return.
This is really terrible.
Update : I wrote to the “CEO” (read the support of Sonos) on the 18th of May and asked a few questions (the same as up above) and I got… a standard boilerplate email that hasn’t answered any of my questions.
It has been one month… we start to believe it will never be supported again and the silence from Sonos slowly makes me angry.
The sonos app on my PC is still working with bonob.
On my mobile phone, the service is gone WHY please give us the bonob service back AND update the app on our mobile phones, the new a is a disaster
a lot of people complain about the new app why don't
you do anything about it
We haven't even gotten an answer yet
These services are all missing from the new mobile app because they use http: endpoints, and Sonos announced that support for those has gone away: they now require https endpoints.
All of the services listed use local addresses, which makes it really hard (maybe impossible?) to use a real https address (I doubt a self-signed certificate will work but its worth a try).
Unless/until add an option for http SMAPI endpoints, your only choices remain the Desktop apps (until they are deprecated) or third-party apps that support SMAPI (eg SonoPhone, SonoPad, Phonos Universal).
These services are all missing from the new mobile app because they use http: endpoints, and Sonos announced that support for those has gone away: they now require https endpoints.
All of the services listed use local addresses, which makes it really hard (maybe impossible?) to use a real https address (I doubt a self-signed certificate will work but its worth a try).
Unless/until add an option for http SMAPI endpoints, your only choices remain the Desktop apps (until they are deprecated) or third-party apps that support SMAPI (eg SonoPhone, SonoPad, Phonos Universal).
I tried to put bonob behind a https reverse proxy with a valid Let’s Encrypt certificate and then manually add it on port 1400 of a sonos device but that doesn’t work either…
I tried to put bonob behind a https reverse proxy with a valid Let’s Encrypt certificate and then manually add it on port 1400 of a sonos device but that doesn’t work either…
Yes, that would have been my attempt as well. Thanks for trying this. I wonder if there is a way to retrieve some logs or debugging info.
b.t.w. after you put it behind the reverse proxy, did it still work (with the desktop app)? Also, I assume you need to put both bonob & navidrome behind a reverse proxy, enabling SSL for both.
I tried to put bonob behind a https reverse proxy with a valid Let’s Encrypt certificate and then manually add it on port 1400 of a sonos device but that doesn’t work either…
Yes, that would have been my attempt as well. Thanks for trying this. I wonder if there is a way to retrieve some logs or debugging info.
b.t.w. after you put it behind the reverse proxy, did it still work (with the desktop app)? Also, I assume you need to put both bonob & navidrome behind a reverse proxy, enabling SSL for both.
I don’t think that I have asked bonob to use gonic per HTTPS, but it doesn’t matter, since bonob even with HTTPS wasn’t even proposed as service on the first place…
“Downgrading” to S1 solves my issues, and it’s also much faster to use !
The Sonos Environment will NOT accept self signed certificates -
e.g. python (with SoCo installed)
Python
from soco.music_services import MusicService
print(MusicService.get_all_music_services_names())
--- lists my regiistered navidrome
navid = MusicService('navidrome')
print (navid.get_metadata())
--- hm
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='192.168.1.234', port=444): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1007)')))
I have set up my own root CA for use in my home network but it made no difference.
Sonos needs to provide a way for you to register you own CA (like browsers do).
Ciao
Tom
I finally move to plex server instead of Airsonic to have my local Librery on Sonos..
The new app is not appreciate by many of us.
They tried something without success this time, Hope they will do better next time.
Best Regards
Guillaume
I finally move to plex server instead of Airsonic to have my local Librery on Sonos..
The new app is not appreciate by many of us.
They tried something without success this time, Hope they will do better next time.
The reason I moved away from Plex in the first place was its complex networking requirements.
I wouldn’t want to go back. But I also don’t want to downgrade to S1.
Sonos have said they don’t support “customsd” type services any more, so I don’t think it matters what cert is used, or path, it can’t work.The music service has to be callable from their Cloud, and customsd services are not.
Pity there is no phonos for Android %-(
