CTRLbot
CTRLbot IoT // android
control simplified. intelligence amplified.
CTRLbot IoT turns an Android phone or tablet into a standalone professional AV control system. Connect to compatible equipment, test commands in real time, and hand the room over ready to use. No separate CTRLbot control processor or server.
THE CONTROL SYSTEM IS THE APP
nothing in the rackTraditional pro AV control splits programming, processing and operation across several components. A programmer needs a laptop and specialist software to configure a dedicated processor, which then serves an interface to a touch panel or tablet. CTRLbot IoT combines those jobs on the Android device in your hand, for installers, integrators, technicians and system developers.
The traditional path puts a processor in the rack before the room can say a word.
CTRLbot IoT configures and runs the room from a phone or tablet, installed from Google Play.
TEST IT BEFORE YOU BUILD ON IT
terminal workbenchFire commands. Watch it answer.
Point a driver at a real device, then send commands straight at it. ASCII or HEX, with the carriage return and line ending the device expects. Add and remove test rows on the fly.
This is how you confirm the gear is reachable and the driver is right, before you build anything on top of it.
WHAT IT DRIVES
73 manufacturers / 124 drivers / 7,561 commandsThe driver catalog ships inside the app, so it can be searched without downloading anything. Counts are from the snapshot generated 21 July 2026 and change as the catalog is revised. A driver may cover several related models, so confirm the real equipment during live testing.
TWO MODES. ONE APP.
one button flips itSearch the bundled catalog by manufacturer or model, filter by equipment type, switch between IP_RS232 and IR, and review supported models and control defaults before adding the equipment.
Enter address, port, transport and credentials. Choose ASCII or hexadecimal encoding and the line ending the device expects, then send live commands and read the responses.
CTRLbot builds system Power On and Power Off presets as connections are added. Set up Many-to-One or Many-to-Many switching, relabel inputs, and map the volume and mute commands the gear exposes.
A full-screen room-control view with the setup navigation removed. Power On and Power Off run as sequences assembled from the configured equipment.
Many-to-One source selection and Many-to-Many matrix routing, using the room-friendly labels and icons set during configuration instead of technical port names.
Volume up and down, direct adjustment where a Volume Set range exists, and speaker or microphone mute when mapped. Press and hold the CTRLbot mark for two seconds to return to setup.
GENERATED, NOT DRAWN
setup and interface creation, one workflowA driver is a translation layer. It carries the commands, transport defaults and capability information for its supported models, so nobody hand-crafts command strings.
See what it drives ↓
drivers/index.json
connection.create/
Nobody designs a screen. Controls are generated from each driver's capabilities, so the interface grows as equipment is added rather than being drawn page by page.
Saved connections can be searched, copied, edited or deleted at any time.
As connections are added, CTRLbot assembles the system Power On and Power Off presets, the switching arrangement and the audio mappings from the equipment and the commands it exposes.
You still verify routes, commands, labels, timing and network behaviour against the real room before handoff.
HOW IT CONNECTS
straight to the addresses you configureDevice-control traffic goes directly from the Android device to your equipment over the reachable network. CTRLbot does not relay it through its own servers. RS-232 and IR installations need a compatible Global Cache endpoint on that network.
Commands go straight to the device's address and port.
For compatible legacy devices. Unencrypted, so the app warns first.
Host keys are verified on connection and stored locally.
Through a compatible Global Cache network endpoint.
Through a compatible Global Cache IR endpoint.
Android Keystore-backed storage, never plain text in the room database.
Room config stays on the device. Android backup is disabled for it.
No analytics, no user tracking, no advertising in the app.
THE TRADE
what it deliberately is notClear boundaries make the promise credible. There is no graphics builder: the interface is generated from the system configuration instead of being designed screen by screen. Customization covers equipment, mappings, labels, icons, sequences and settings, not unrestricted interface design. CTRLbot drives equipment it has a compatible driver and control path for, the Android device has to be able to reach that equipment, and this release is Android only.
The payoff: configure, test and operate a compatible room from the device in your pocket, with no separate control processor to program.
BUILT DIFFERENT. BY DESIGN.
SIMPLICITY OVER FEATURE CREEP
PRIVACY OVER DATA HARVESTING
SOLUTIONS OVER ENGAGEMENT METRICS
we build software that translates human intent into system action.