RokuM500Automation
Note: You are viewing an old revision of this page. View the current version.
Overview
I am a long-time owner of a Roku Soundbridge M500 internet radio. You may have never heard of these devices - the Soundbridge was Roku's first foray in to streaming before they moved to video streaming. While the M500 was discontinued many years ago, it still works and in fact I use mine daily to listen to the radio. This post covers my attempts to understand how to control the M500 remotely, and provides some info about how to make one of these old devices work in the modern age.
One of the big reasons I like this thing is that it's complete'y self-contained once you set it up. It doesn't require you to control it via an app (although you can do that if you want). It just sits there and plays audio. That's it.
Network Control
The m500 is a small device that connects to your network via wifi and and can play internet radio streams (and your own media, theoretically - see below). It outputs stereo audio via RCA jacks or SPDIF optical, so you have to connect it to a receiver or amplifier of some sort. Here's a picture of mine. It runs a very simple web interface, so presumably it should be easy to automate. I spent an hour in the chrome dev console figuring out how to GET and POST data from and to it. The great thing is there is no authentication on the web interface, so you can just interact with it directly. This makes me miss the early 2000s. You don't even need to bother with https (well actually, the m500 just can't do https). More on that later in the section about setting up internet radio stations on this device.
Anyway, after futzing around with the dev console in chrome and with curl, I was able to figure out the following remote control commands. I leave them on this page in case someone else finds this useful.
Commands
For reference, here's what the m500 main screen looks like:
Control of the device can be done by faking a click on each of the buttons, or submitting a value in the case of the volume control. This can all be done via standard http POST commands.
First, the basic commands. The number after "x=" can vary, I think it's actually the x location on the button image where the mouse was clicked. That doesn't matter since each image only controls one function.
Play
curl --data Play.x=1 http://192.168.1.45/Forms/SoundBridgeNP_1
Pause
curl --data Pause.x=1 http://192.168.1.45/Forms/SoundBridgeNP_1
Others
Rinse and repeat for the remaining buttons on the page, if desired:
- Prev
- Stop
- Next
- RptOff
- Shutoff
Volume Control
For volume control, you POST a number between 0 and 100:
curl --data gPageVolume=80 http://192.168.1.45/Forms/SoundBridgeNP_2
Presets
Presets work the same basic way, although the format of the data you send is more complex. Here's what the presets page looks like:
And here's what a curl command to set the presets looks like:
curl -v --data "PresetName%3F1=KAPA+FM+Hilo&SR_WP_PS_PLAY=Play&PresetLocation %3F1=http%3A%2F%2Fplayerservices.streamtheworld.com%2Fapi%2Flivestream- redirect%2FKAPAFM.mp3&PresetNum%3F1=1 http://192.168.1.45/Forms/SoundBridgePresets_1
HOWEVER note that if you send that command to your Soundbridge, it will set the first preset and ERASE the rest. To really use this command, you need to send your entire set of presets in one command. Here's a full curl command that sets all 18 presets at once.
Setting the presets is important because it's the only realistic way to set up a Soundbridge to play internet radio streams these days. I'll provide more details on that later in this article and a list of radio stations I currently use.
Remote Control
Phone App
Prior to this investigation, I found an android app that allows you to remote control a Soundbridge on your network. So to be fair, I actually knew it was possible to do this, I just didn't know the details. That app is Remote for Soundbridge and it works great. I recommend you use it (and donate a few bucks to the developer!).
Wifi IR Blasters
Another remote control idea I'm planning on trying is a wifi IR blaster. These things sit in your living room and fire remote control commands to devices. I have one of these but I haven't tried it yet. One reason I'm interested in this is it would allow me to easily switch on/off my Soundbridge and my receiver in concert. More to follow on this in the future.
Finding Stations
A huge challenge with these old devices is finding music and streaming stations to play on them. The initial allure of the Soundbridge was that it could easily stream music from iTunes via Apple's proprietary DAAP protocol. That stopped working many years ago, as iTunes changed the protocol (and probably eventually abandoned it, for all I know). There are alternative open source DAAP servers such as Tangerine, but I haven't had much luck with them over the years.
For a number of years, you could use the free Radio Roku service to set your Favorite stations on your Soundbridge. This is separate from the 16 preset stations, and allows a very large number of stations to be stored on the Soundbridge.
Unfortunately, I haven't been able to get Radio Roku to work for the last few years, because it relies on a java applet to talk to your Soundbridge. I eventually just gave up and stuck with using presets. In practice, 16 stations is enough for me.
Finding Unencrypted Stations
Another big issue with internet radio streams is that they have been moving to https, particularly in the last few years. Typically you feed your Soundbridge a .m3u playlist file url for a station. The Soundbridge downloads that file and then attempts to connect to the streams listed in it. As I said, those streams have largely switched from https to http, so if you give a Soundbridge the m3u file, it won't play anything. Luckily, there's a workaround that generally works.
As an example, let's look at the KQED live stream. If you look on their audio help page, you can find that url: http://streams.kqed.org/kqedradio.m3u .
That url will not work with a Soundbridge. If you look in the file, you will see something like this:
https://streams2.kqed.org/kqedradio
and as I said previously, https will not work with Soundbridge.
Luckily, in all cases I've checked I've found that the servers still support http. Thus instead of using the m3u url in your Soundbridge presets, point at a http version of the stream instead, i.e. http://streams2.kqed.org/kqedradio.
One thing you can't fix is when internet radio stations decide to move behind proprietary player apps. I've seen this happen a few times over the years, but so far I've been able to find reasonable alternatives.
My Stations
As of May 2019, I have the following 16 stations programmed and working on my Soundbridge:
Conclusion
Well, that's about it folks - that's my brain dump on how to configure, use, and automate a Roku Soundbridge. I've never tried any of the other models such as the M1000 or M2000, but I assume they would probably work similarly. I just looked on ebay, and you can get a M1000 for around $40. I think that might be a good buy if you just want a simple and reliable internet radio. I've been running my M500 almost every day for more than ten years, and I've had zero problems with it (other than the tech becoming outdated of course). I plan on running this thing basically forever.
I genuinely hope someone else finds this info helpful. I have no idea if anyone still cares about these devices or not. Keep hacking!
