Does Slimserver support the Bluetooth speaker (bluetooth audio profile)? I think Slimserver may be a sidetrack to adding the speakers. You may need to look at some of the other audio options in Linux.
Slimserver is good but its really designed to support Squeezeboxes and their clones on a network. But you really need an independent audio stream to be sent to the BT driver under DCERouter control (hence the value of Slimserver if you can configure it that way).
There is another Linux network audio solution (at least) called Pulse Audio that hooks into Alsa and sends the audio stream out the network.
LMCE currently doesn't know how to handle more than one audio device per MD but the BT may look like a local audio device to the system and Alsa would the audio stream to the BT driver.
Thanks for the advice. I was advised earlier in this topic that SlimServer would do what I want. I don't think SlimServer directly supports the BT speakers, but I think sharing the archtecture already built into LMCE, SlimServer, with either its SqueezeBox HW clients or a new client that behaves essentially the same by wrapping the BT speakers in a SW client that triggers SlimServer and pulls audio from it like the SqueezeBox does, then sends audio to the BT speakers, is the most consistent with how LMCE does it.
However, the SlimServer might not be the best streaming server. Probably the best is Icecast, for fidelity, performance, scalability, programmability, and with a larger and more open developer community. But Asterisk also already has a streaming RTP server. So adding Icecast would mean a third streaming server. Pulse Audio and others would mean a third one, too, with limited application compared to the others. Probably using the Asterisk RTP server would be best overall, but it's so integrated into Asterisk (it's not even a separate "stack" or module, but RTP is processed all through the Asterisk audio signal path) that such is probably the least feasible.
Probably the fastest way to get something going that isn't a dead end is to wrap madplay in something triggered by the existing BT detection script, that triggers whatever is monitoring DHCP for SqueezeBox MACs, hitting SlimServer for audio. The existing integration of SlimServer/SqueezeBox probably means the minimum work to integrate the new SW/BT client into the Floorplan. Maybe all of their streaming servers should be factored into a single multiprotocol server (or bundle), which use the DB and DCE rather than their native, incompatible data and IPC. Maybe all the audio should be run under a GStreamer pipeline. I'll be in a better position to figure that out once I've got something up and running. In no small part because I'll be able to listen to music while thinking about it.