What was announced
Lightware introduced a physical General Purpose Input/Output (GPIO) button control for its MTRoW integration. It lets users switch between the native Microsoft Teams system and BYOD operation. The button is designed to connect directly to Lightware's existing Taurus UCX and TPX platforms.
The practical point is what the button replaces. GPIO Button control lets users pick their operating mode without the Companion App or Microsoft Teams call-status monitoring. Lightware's release describes this as a method that stays independent of network connectivity and background service states. That is the company's claim. The coverage I reviewed includes no independent reliability testing and no measured reduction in support tickets.
How it works in the room
- MTR mode: The room operates through its dedicated Microsoft Teams PC.
- BYOD mode: Per Lightware's release, the connected laptop can take control of the room's displays and USB peripherals. That lets the room's camera, microphone and speakers work with other conferencing or presentation apps.
- Routing: Lightware Advanced Room Automation (LARA) is the switching and routing system behind the button. The release says it assigns the right video and USB resources automatically when the mode changes.
- Feedback: Optional LED feedback shows which mode is active.
Not a standalone replacement for automation
Lightware does not pitch the button as the only option. The optional Companion App can still add convenience, such as automatic switching based on Teams call status, subject to the software installation terms. The button is best read as a deterministic, local alternative or fallback. It is not a ban on automation.
Is this actually new?
Not entirely. Lightware's Taurus UCX-4x3-HCM40 product page already lists a physical GPIO button for one-touch MTR/BYOD switching with LED status. That makes the October and November coverage better described as an announcement or promotion of the capability within the MTRoW offering than as a first-time technical debut. I couldn't retrieve Lightware's installation manual to confirm version history, so treat any claim about when the feature first shipped as unverified.
The button hardware
Lightware separately launched a dedicated GPIO-Button-10S accessory. Up to two of these buttons can be connected to a six-GPIO Lightware device, such as Taurus or MMX2 units. The LEDs can show red, green or blue, with continuous, slow-blink or fast-blink patterns. Each button uses one GPIO channel for the press and two channels to drive the LED. It ships with a pre-terminated 2.5 m pigtail.
Those details come from Lightware's general GPIO-Button-10S launch material. They are not specific to the MTRoW integration, so check that the pairing is supported for your configuration.
What IT and AV teams should check
- Model and package compatibility. The announcement names Taurus UCX and TPX. Confirm your exact unit and the matching integration package from Lightware before you buy or plan.
- GPIO allocation. Button input and LED outputs consume GPIO channels. Plan which ports the room's other automation already uses.
- Installation. Lightware's own materials point to LARA configuration for button behavior. Have a qualified installer do the wiring.
- User expectations. A physical button is simple. It still needs clear labeling so visitors know which mode they are in, which is where the LED feedback helps.
- Verify claims locally. Test both modes with your camera, audio and USB devices. "Always-available" is marketing language until you have tested it.
Bottom line
For Teams Rooms on Windows admins, the value is a local, call-state-independent way to flip a room between MTR and BYOD. The caveats are that this is vendor-reported, the capability appears to predate the announcement, and compatibility depends on specific Lightware hardware. It's a modest feature, but a sensible one. A mode switch you can press beats a service you have to troubleshoot.