Companion Pi Redundant Setup

Hi All!

We have been using Companion running on a Raspberry Pi for about 2 years now and it has been great. We work in a live entertainment environment and Companion was originally brought in to supplement our hardware MIDI controllers connected to media servers for show control, but as we have grown more comfortable with it, Companion now controls that plus our LED wall processors, relays, and other show components. The MIDI controllers are basically a backup option at this point.

We are in the process of re-evaluating our control booth setup and would like to remove the MIDI controllers entirely, which brings me to my question: what is the best way to run dual redundant Companion Pi’s? Are there any pitfalls or other issues that anyone can think of off the top of their head? Is there an easy way to have changes automatically copy to both systems? Is there a way to deal with multiple connection issues to one device at the same time? Is this dumb and a waste of time and a Raspberry Pi?

Upstream we will have redundant power sources and redundant network. Downstream we would connect a Streamdeck to each Pi for a control surface. Most of the commands we send are HTTP and UDP and don’t send or require any feedback to Companion.

Has anyone out there done something similar to this? Thanks for any feedback.

Hi Kyle, I would suggest you take a look at Buttons from Companion, it is a commercial ready product with all of the same interface/connections to hardware, plus with new interface designed specifically for professional use. Among other features, it natively supports redundant hardware configurations.