Reviving this, I just did some design to try to do something similar to what @aiotea was talking about with a lighting installation involving 4 pixelblazes which should be acting as simple pixel receivers. I have no knowledge of other protocols, I’m still pretty new in the lighting world, but my requirements are that I want the system to be able to set itself up and be able to be tolerant in the face of possible rain / weather related issues like a Pixelblaze losing power gracefully, and to be able to catch a new pixelblaze if it starts back up without me having to take out my computer.
I decided to try to take the pixelblaze discover code out from Firestorm and to write an orchestrator to spin up / tear down sACN proxies, like this:
Note the part at the bottom that says “Pixelblaze Fleet Orchestrator”. The idea was that then my friend’s DMX source will be sending Multicast sACN and we can predetermine which poles are using which universes. We haven’t figured out if the sACN stream should be over Ethernet or WiFi and figured we’d experiment but any guidance here would be welcome.
@zranger1 does this seem like the right idea? I could try to flash the Pixelblaze like you said but that’s a scary proposition with only a month and a half, including holiday season, to put this together, and sACN is nice in that it’s widely supported and the pixel data will be coming from TouchDesigner, which natively supports sACN.