User Interface
Map:
This page gives us a overall view of the health of the system. Any error will trigger that house's status LED to turn red and the perimeter border of the UI to go red. In the upper right the statistics from the show are presented - including current playlist, timecode, schedule overview, car count, and status of ShowTime script.
Sequences:
On this screen, users are able to select between the Primary / Secondary FPP player. Enabling automatic failover will switch from the primary to the secondary player automatically if the primary player encounters an error during ShowHours or AfterHours playback times. Once a placer is selected, users are able to view available sequences on the player and start/stop the sequence.
Controllers:
On this screen, users are able to interact with the individual FPP players. All status / control is currently done via HTTP calls (for 2025 we will be transitioning to MQTT for communications). Users are able to change the player mode, enable/disable sending MultiSync, enable/disable test mode, and even remotely update the software on the player.
RF:
On this screen we are presenting the signal strength and maximum upload/download speed acheivable on the wireless backhaul connection between each house. This information is pulled via API from Ubiquiti UISP software running on-prem. The radio input provides feedback from our two-way radio control integration.
Network:
On this screen, users are able to view the status and control POE power for all remote network switches in the show over SNMP. The device column is a user-editable text label that can easily be updated when out in the field as devices are connected to the switch. The link LED and Uptime displays link status information from the switch. The POE toggle button displays the status of POE for the port and users can manually press it to enable/disable POE power. If the auto button is enabled, automatic POE reboot will be enabled for the connected device wired to that port of the plugin. If that device's status (shown in Device Status column) reports as an error or missing and when auto mode is enabled, the system will automatically wait 30s for it to recover before automatically rebooting the device.
Audio:
As part of the re-designed Headend system, we relocated our FM transmit and main player from a remote location to the MDF system. This now allows us to run the show audio through the ShowMon system processor. From this screen, users are able to monitor the audio feed on both the primary and secondary FPP players which are connected via USB to the Q-SYS Core processor. They are also able to monitor the status of the ShowMon core as well as audio being sent to the FM transmitter. The system monitors the FM audio transmission and ensures that show audio is being played on the FM freqnency. In the event that no show audio is detected, the system will automatically fail-over to the secondary FM transmitter. Users are also able to bypass the programmed hours for the FM transmitter if they wish to transmit show audio outside of show hours.
Power:
This is the newest section of the UI and much of it is still under development. As part of our network IDF v3 design and our desire to be able to power cycle non-POE powered controllers, we have started installing Shelly 1PM and Shelly Plug US. We are communicating with these via MQTT. For 2024, we are simply gathering the overall health, current, wattage, and voltage from each unit. In addition, the ShowMon system is calculating the total power draw and looking up electrical cost via the National Renewable Energy Labs API. This seciton will grow a lot for 2025 as we roll out more power monitors and start integrating more control / automation around them.