TUNEIN / internet radio support

[julius-d]

Hi 👋 !

Looks like I am working on something similar like you :)
(See https://github.com/julius-d/ueberboese-api)

The main difference is maybe the approach to change the bose api server url.
My approach is to use

nc 192.168.178.2 17000
envswitch boseurls set https://ueberboese.your-example-host.org https://ueberboese-downloads.your-example-host.org/updates/soundtouch
exit

Until the start of the year my setup worked quite well.
But now the TUNEIN support disappeared and I do not understand why/how.

How is it going with you server + devices are still able to play internet radio?

[gmuth]

When they detect too many requests their services start behaving strange:
e.g. by slowing responses down artificially or silently removing results from queries.
Maybe a VPN helps to pretend another location.

[akpdw]

@julius-d Hi! Sorry I didn't actually set up a follow on this repository until a week or so ago, and github's UI has no indication on it at all that there is any activity in Discussions unless you actually click on the tab. So I had no idea that this post was here!

Looking at https://github.com/julius-d/ueberboese-api I see you have some TuneIn support written in now so I'm guessing that you've gotten past the original question? But if there's anything that we can help with then feel free to ask.

Also I'm totally planning on pulling over your Spotify integration; I didn't have a Spotify account and when I created one to test with I found out that the Bose account registration doesn't work anymore, so I was kind of dead in the water for that.

Anyway, nice to meet you and I'm looking forward to collaborating with you, now that, er, I know you exist. :)

[julius-d]

Hi, nice to meet you!

Yes, ueberboese-api now has support for TuneIn/Local internet radio.
When starting my project, I hoped that envswitch boseurls would be enough, because it is very user friendly, but from your project I learned that BMX is needed as well. So, depending on what Bose shouts down, logging into the speaker's root shell is needed.

The approach of the ueberboese-api is to forward requests that are not yet implemented and log the request and response,
so that implementing it is easy.
Unfortunately, that did not work with BMX. When looking in the "code", I even found hints that suggest that the API key header is not sent when the domain is reconfigured.
That prevented me from looking at the responses. Thanks to Soundcork, I could learn how they have to look.
How did you set up the Man-In-The-Middle?

[gmuth]

Check this issue for how to patch the library used by the device: #62

[akpdw]

@julius-d doing the sed approach is probably easiest, but if you would rather inject a header into your proxy directly:
eC1ibXgtYXBpLWtleTpzckkzMm9GbGtjQVh2TjYzMHM2MUpFWVo5SkpBemswVwo= (base64 encoded just because it feels weird)