I have a two console system (e.g. an EosTi master and a Puck backup) to control my stage lights and house lights. My architectural system (e.g. Paradigm) only controls my house lights.
When the master is in control, I have control of my house lights from either the master or the architectural system with normal Highest Takes Precedence (HTP) behavior. However, when I turn the master off, and the backup takes over, I lose control of my house lights from the architectural system.
If I unpatch my house lights from my console system, the architectural system retains control when the backup takes over.
This situation is likely due to an sACN priority mismatch within your networked system, and more specifically, a setting on the master console.
sACN operates on a priority system of 0 - 200, with 200 being the highest priority, and 100 being the default. In the system setup described above, the most common scenario would be the master console and architectural system both set to the default sACN priority of 100, which means the lights will respond to whichever control source is sending a higher value.
Eos consoles have an option in Settings > Network labeled "Backup takes over at higher priority." This setting, if checked on the master (Ti), means that when the backup (Puck) takes over, its sACN priority will automatically jump to 101, which would override any sources of control still at sACN priority 100 or lower (Paradigm).
- Exit to the Eos shell on your master console, and go into Settings.
- Go to the Network page, and scroll down to the section labeled "Output Protocols."
- Uncheck the box labeled "Backup takes over at higher priority."
- Hit Accept at the bottom, and log back in as Primary as normal.
When the backup takes over, its sACN priority will now remain at 100, and the HTP behavior between the console and the architectural system will persist.