I just got a Squeezebox Radio, which is rather neat. It's smaller than a Boom, and has a colour display. The volume control is also a proper rotary knob, which is much easier than a pair of up/down buttons.
On the flip side, the setup was an absolute nightmare! The device pretty much demands that you set it up to use DHCP, and the DHCP
1 server on my router has "issues". It hasn't worked well with Squeezebox hardware in the past, so I've just configured them with static IPs. This time I had great difficulty getting it into a mode where I could input the values. It allowed me to do this once, but wouldn't let my input an IP address for the DNS where the first digit was 2 (I needed 212.x.x.x) which was very odd. End the end it took some of the values, but forgot others. This ended up with a configuration which wouldn't work, but which it wouldn't prompt me to input details (ie it assumed they were valid).
In the end I managed to connect to it with an Ethernet cable (for some odd reason the DHCP works better over Ethernet than WiFi), and SSH'ed into the box, so that I could edit the networking details by hand. I still can't get it to work with DHCP, but the static IP works fine.
Of course, then it turns out that the version of the server I'm running isn't compatible with the Squeezebox Radio either (predictable on reflection), so I need to update it, and after spending several hours struggling with the Radio, the NAS, and the router, I've had it for a while. I'm just listening to the Radio on the Squeezebox Network at the moment.
I like the Squeezeboxen, but occasionally they can make things "interesting".
Footnote 1: As an experiment, I turned off DHCP on the router, and enabled it on the NAS. This almost worked, although the Squeezebox Radio still wouldn't pick up the DNS over WiFi, but it worked more reliably with my laptops, so foolishly I left it like that. Sometime later I lost Internet connectivity. It looks like stopping the DHCP server also may have killed the DHCP client or some other oddity, since the router seemed to loose it's IP address (although that's an internal value, and shouldn't be effected...). Either way, it took me well over an hour to reconnect to the router, reload an earlier known working configuration, and then stop fiddling for a while!