If you're buying a smart lighting controller or an LED driver, stop looking at features first. Look at compatibility. Most of the problems I've seen—and caused—stem from not checking compatibility early enough.
I manage procurement for a 150-person company, handling around $250,000 annually across our facility and office needs. That includes a fair bit of specialized lighting—think controlled environment rooms and storage areas where we use LED grow lights. When I took over purchasing in 2020, I had a few very expensive lessons about lighting controls. This is what I wish someone had told me.
Why compatibility is the first and often the last problem
When we decided to upgrade our facility's lighting in 2022, we wanted “smart control.” The idea was to automate dimming schedules for our LED grow lights—like the Mars Hydro TS1000 we had in a test room—to mimic dawn/dusk cycles. A vendor sold me a great controller, but it was a different protocol (not Zigbee). Our lights were Zigbee-compatible. (Mars Hydro's smart controllers are Zigbee-based, which is good—it's an open standard).
I assumed 'smart' meant 'works with everything.' It doesn't. The controller couldn't talk to the lights. We ended up with a $400 paperweight and had to buy the right one. That's $400 I had to explain to my VP.
My rule now is: Always check the communication protocol (Wi-Fi, Zigbee, Bluetooth) of the light and the controller before you buy anything else. If they don't match, you're buying two things that won't work together.
What I check now before buying a controller
- Protocol match. Is it Zigbee? (That's what most modern LED grow lights like the Mars Hydro FC-E4800 use). But double-check. Some systems are proprietary.
- Phone app or dedicated hub? Some controllers need a dedicated hub; others connect directly to your phone. For a B2B setup, a hub is often better for reliability. (I learned this the hard way when a Bluetooth-dependent system dropped connection during a critical light cycle—surprise, surprise).
- Does it need a constant internet connection? For a facility, this is a big deal. If the internet goes down, do your lights stay on schedule? Ours need to, even if the network is down.
What about the LED driver? (The part everyone forgets)
When I talk about lighting controls, I'm also talking about the LED driver. It's the power supply that drives the light. If you're replacing a driver (like a Mars Hydro TS600 driver), or buying a complete kit, compatibility is vital again.
(I should mention: I do not have a background in electrical engineering. I learned this by reading spec sheets and, once, by causing a small electrical issue.)
The one thing to get right: voltage and wattage
I assumed 'same specifications' meant identical results across different brands of LED drivers. It doesn't. The voltage and wattage rating must be a perfect match. I once ordered a 'compatible' driver without checking the fine print. It was rated for 120V, but our facility's wiring was 240V for that circuit. The driver failed within a week. It cost us $150 in replacement shipping and a day of lost light in our test room.
The 12-point checklist I created after my third mistake has saved us an estimated $4,000 in potential rework. Here's the key check for a driver:
- Input voltage: Must match your building's power. Check the spec sheet (often on the manufacturer's site, like mars-hydro.com for their drivers).
- Output voltage/current: Must match the light's requirements. It isn't always printed on the light itself. Look for the product manual.
- Is it a constant current or constant voltage driver? Most LED grow lights use constant current drivers. A constant voltage driver will burn them out. (I didn't know this until I read it on a forum. Now I check).
I've only worked with domestic vendors. I can't speak to how these principles apply to international sourcing or voltage differences in other countries.
My favorite thing about smart controllers: the PPFD map and data logging
One thing that made our switch to smart controls worthwhile was the data. The controller for our Mars Hydro TSW 2000, for example, logs temperature and humidity. More importantly, it lets us automate based on PPFD maps (Photosynthetic Photon Flux Density).
If you search for “Mars Hydro TSW 2000 PPFD map,” you'll find one on their site. This tells you how much light your plants get at different distances and power levels. With a smart controller, you can set the light to run at, say, 80% power during one phase and 100% during another, based on the map's recommendations. This isn't magic—it's just applying the data the manufacturer already provides.
(Should mention: We use this for our test room, not a full greenhouse. My experience is based on about 20 smaller-scale projects. If you're running a large commercial operation, your requirements might be different.)
A quick note on where to put under cabinet lighting (and it's not where you think)
I see a lot of advice online about placing under-cabinet lights. The standard tip is to mount them near the front edge of the cabinet to avoid shadows. That's fine for kitchens.
For our facility's workbenches, where we sometimes use LED strips for task lighting, we found a different rule: Mount them 4” back from the front edge. This prevents the light from shining into your eyes when you're seated at the bench, but still covers the work surface. It felt wrong, but it works better. You don't always have to follow the 'rule of thumb' if your use case is different. Test it yourself.
The takeaways I'd give my 2020 self
- Check compatibility before price. A cheap controller that doesn't work with your lights is $400 wasted.
- A smart controller without a backup plan is risky. If your internet goes down, your lights should still run on their local schedule.
- PPFD maps are not marketing fluff. They are the most useful data sheet you can use with a smart controller. Bookmark the one for your light.
- Don't assume a replacement driver is universal. Check voltage, current, and type (constant current vs. constant voltage). If in doubt, buy the exact replacement from the original manufacturer (e.g., Mars Hydro).
I don't have hard data on industry-wide failure rates for mismatched controllers and drivers. What I can say anecdotally is that about 40% of the issues I've seen on forums like this are caused by a simple compatibility error—not a product defect. Verifying this before your order saves a lot of time. (Oh, and always save your invoices. Our accounting team requires them for any expense over $100. It's not a bad habit to get into).