Technology
What Can You Control With an LED Controller Mobile App?
A phone is the fastest way to change what a finished pixel LED installation is doing. No laptop, no software licence, no site visit. This article explains what an LED controller mobile app actually controls, which LSS devices appear in it, and where its limits are.
It is written for integrators, installers and owners of existing LSS controllers who want the end client to change scenes without calling anyone. The examples come from four zones in our own building, each running a different device.
What Is an LED Controller Mobile App?
An LED controller mobile app is a phone or tablet application that finds pixel LED controllers on the local network and switches between the effects already stored on each device. It is a recall interface, not a design tool.
That distinction matters more than it sounds. Content is created in LED Strip Studio pixel mapping software and written to the controller’s SD card. The app reads the card contents through the device and lets you pick from that list.
The practical consequence: whatever is not on the card cannot be selected on the phone. Programming stays a design job. Operation becomes a two-tap job.
Why Do the Effects Have to Live on the SD Card?
Because the controller plays them standalone. The animation is rendered on the device from local files, so the phone only sends a short control command telling it which file to run.
This is what makes app control usable in a house or a shop. The installation keeps running its scene whether or not a phone is nearby, and the app is only needed at the moment someone wants a change.
Which Controllers Does LSS Remote Support?
The LSS Remote app lists every supported device it finds on the local network. Reactivo was supported from the start. Two of our more advanced controllers were previously omitted from that list and are now included: the LED Ethernet Controller 3 and the SPI Matrix.
Each device appears with its type, its IP address and the name you gave it, which is why the naming convention on the card matters as much as the wiring.
Source: LED Strip Studio
What Can You Change on LEC3 and SPI Matrix?
Three things: which effect plays, the speed of the animation, and the brightness. That is deliberately narrow, and in daily use it covers most of what anyone asks for.
Effect selection sets the mood, speed sets the energy, brightness matches the room to the time of day. A client who can reach those three controls rarely needs anything else between one programming session and the next.
Why Does Reactivo Offer More Than Effect, Speed and Brightness?
Because Reactivo accepts physical triggers and external sensors, so its app screen exposes settings the other two controllers have no hardware for. A motion sensor, a button or a contact can start a specific effect instead of a person doing it.
Which Controller Gives You the Most Control From the App?
| Capability in the app | LEC3 | SPI Matrix | Reactivo |
|---|---|---|---|
| Appears in the network device list | Yes | Yes | Yes |
| Select effect from SD card | Yes | Yes | Yes |
| Animation speed | Yes | Yes | Yes |
| Brightness | Yes | Yes | Yes |
| Trigger and external sensor settings | No | No | Yes |
| Typical role in our own building | Video backgrounds, ceiling show | Stairs, mobile rigs | Desk zone with screen grabbing |
Case Study: Four Zones, Four Ways to Use the App
Our building has decorations in several rooms, and each zone is controlled by a single device with its own SD card. That one-device-per-zone rule is what makes the app list readable: the device name in the app is effectively the room name.
- Gaming table — Reactivo, effects on card plus real-time screen grabbing
- Digital horizon — one LEC3, mostly driven live from software
- Staircase — still an unfinished project
- Office ceiling — one LEC3, music-synchronised show
How Is the Gaming Table Zone Controlled?
The gaming table is a wannabe studio corner running on a Reactivo. Effects sit on its SD card for normal use. The same zone also runs Reactivo screen grabbing software when the light needs to follow what is on the monitor in real time.
Both modes live on one device. The app switches back to a stored effect the moment the real-time source is not wanted. How those effects reach the card is covered in our guide to SD card playback without a PC.
Why Is App Control Useful on a Video Background?
The digital horizon was repurposed from an earlier installation and is built from digital LED strips. It appears as a background in our videos and is normally fed live from software over a single LEC3.
The app earns its place in one specific moment: switching the whole wall to flat green for keying. That takes two taps on a phone instead of opening a project on a computer. How a stored neutral look fits into a whole shoot is covered in our guide to pixel LED for video production.
Source: LED Strip Studio
The staircase is the honest entry in that list. It is still unfinished, and the plan is to move it to a controller that accepts a sensor, so the steps light up in the direction of travel and dim down by time of day. How the same one-device-per-zone rule applies to a house is covered in our guide to residential pixel LED lighting.
Source: LED Strip Studio
What Runs the Office Ceiling Show?
The office ceiling runs a programmed show synchronised with music. One LEC3 drives the pixels, paired with a Shelly switch and a custom sound board.
The sound board triggers the show from the card and the music from a player at the same time. The app is the fallback for anyone who just wants a different effect without starting the whole show.
Source: LED Strip Studio
How Do You Set Up App Control Step by Step?
- Program the effects for the zone in LED Strip Studio software.
- Write them to the controller’s SD card and keep the file names meaningful — those names are what the client reads on the phone.
- Put the controller and the phone on the same local network. App discovery works over that network, not over the internet.
- Install LSS Remote from Google Play or the App Store.
- Open the app and let it list the devices. Each supported controller on the network appears with the effects found on its card.
- Select a device, then an effect, and set speed and brightness to taste.
- Hand over with one page of notes naming each device, its zone and its three or four most-used effects.
Which Mistakes Break App Control?
The “the app does not see my controller” cases we get are almost always one of the following, and none of them is a hardware fault.
- Phone on a guest or mobile network. If the phone is not on the same local network as the controller, the device list stays empty.
- Empty or badly named SD card. The app can only show what is on the card, so unnamed files make the list unusable for a non-technical client.
- Expecting the app to create effects. It recalls content; it does not design it. New scenes still need a programming session.
- One controller across zones that need independent control. Zones sharing a device share its effect, which removes the point of per-room control.
- Weak Wi-Fi at the far end of the building. Coverage decides whether the handover feels instant or unreliable.
Planning an installation the client should be able to operate alone? Book a free consultation and we will design the zones and the card contents around that.
Summary
An LED controller mobile app is a recall interface, not a design tool: it lists the controllers it finds on the local network and plays back the effects already written to each device's SD card. LSS Remote now includes LEC3 and SPI Matrix alongside Reactivo, exposing effect selection, animation speed and brightness on all three — Reactivo adds trigger and sensor settings because it has the hardware inputs for them. This article walks through four zones in our own building, the step-by-step setup, and the handful of mistakes that account for almost every case of a controller not appearing in the app.