Nice work. Very interesting, I look forward to seeing more! Well done!👍

Thx pl212 for your offer, I'll gladly accept.  I've been slow to release the software for GA because I wanted to make sure that I got the syntax mostly usable, and I'm also suffering a bit from feature creep.  More on that in a following post. This following solution is not really a good final solution, but I'll mention it anyways as a thought exercise: at a minimum what would work with little effort is if you had 2 sources that you connected via a Y-cable to BeoBabble, and connected the BB DL86 output to an ML/MCL converter, which then connected to the BC2300. On a start signal from either source, the BB can be easily modified using a macro to send a DL86 "System-on, switch to Aux" to the BC23000 through the ML/MCL when BB detects a "Playing" Status from one or the other source, and also send a "Pause" signal to the other source, much in the same way a BeoMaster does when you switch sources.  So that part would work already, but I think it would be a bit of a kludge, and likely introduce some unwanted noise interference.  There would also be some wiring needed to bridge the audio pins, which I currently have not spent much time on. So the BB Setup would look like this: 2 BB Macros: On DL80 Trigger "Beogram.Playing", Send DL80 "BeoTooth.Pause"; Send DL86 "BC23000.Src=>Aux";  On DL80 Trigger "BeoTooth.Playing", Send DL80 "Beogram.Pause"; Send DL86 "BC23000.Src=>Aux" (Which I assume would power the BC2300 on as most B&O conventions allow for)  In theory (THEORY!) that would kinda-sorta work out of the box with just a couple of Y cables, but AFAIK it's not really the best idea to have two sources sharing a common output channel without having a proper MUX that can isolate each source's audio signal from the other, and switch cleanly between them.  What we are doing in this example is sharing an audio L+R, and shutting one system off if the other starts playing - probably not recommended. Getting into the weeds here, so indulge me and feel free to ask questions or offer a clarification if I'm off-base: with respect to the BC2300, I think that it speaks ML, and not MCL2, which would mean for the moment that there would be a bit more hardware to acquire in the form of an ML/MCL converter just to get the communications working (I'll get to ML support at some point in the future, but probably it will be a while), and then also an additional piece of hardware in the form of an Audio MUX that has, say, 2-4 input channels and an output channel for the BC2300 Aux connection, and the channel selection would have to be settable via a logic signal that BeoBabble can send out. So, what am I saying? I think it <could> work out of the box, but I don't know that the result would be great without a proper audio MUX. It's clearly worth exploring what it would take to put a MUX like you would need on-board, but my experience is not in audio engineering, so my hope would be that someone resourceful could help design one, or offer another hardware audio MUX solution to with an API/Interface. Keep those product extension ideas coming!  

Over the past week, I started stress testing the design to see how malleable it was to feature expansion - and it fared pretty poorly.  So I decided to add a few features that I knew I would need in order to make the system work for me the way I wanted it to, and see what that did to my design.  I purchased a $30 Ethernet add-on to the Mega, and added a rudimentary telnet server to BB.  This forced me to retrofit a bunch of code, because I had never considered what it would mean to read and write I/O to and from several clients.   My current solution is incomplete and sloppy, but it did allow me to prototype something else: an iOS console that connects via TCP/IP to BB and can send and receive Datalink in parallel with the Serial port. From there, it was a very short hop to writing an iOS MCP-Style remote control.  In reality, this is a real stretch for me from a programming standpoint.  I know next to nothing about how Swift works, but thanks to Claude.ai, I just got it working sending commands tonight by pressing MCP buttons.  The tougher part is next- translating all the MCP update status commands into LED readouts on the status screen.  This has yet to be coded in Swift, but I'm elated to know that it's actually going to work as I imagined.  Prototyping screenshots attached.  When I get the LEDs programmed so that it behaves like a real honest-to-goodness MCP, I'll upload a video. Shout out to all you BM5000 users out there.  There's an MCP in there for you too!  

Oh an btw if it was from ML I would suspect that a Beolink Converter type 1611/1612 could be used just as well since that tranlates between ML and DL86