My sprinkler system has an app I can't stand, so I connected a bot! It goes in through the API, not the screens.
The bad UI
I have a sprinkler system I like and an app I don't.
Everything takes too many taps. Just testing one zone means working through screen after screen. Every zone is managed on its own, which is what I want, but it means adjusting for the season is zone by zone, screen by screen, and takes far too long.
That would matter less if I could set it once and forget it. I can't. Some of the yard bakes, some of it stays shady, and June, August and September each need a different amount of water. So every few weeks I was back in the app, tapping.
The question I didn't ask
Then I was looking for things to try with Grok Bot, the AI agent I'd connected to my bank in a previous post. On a whim, I asked whether it had a connector or API access to my sprinkler company.
It did. Grok Bot reaches the controller through the company's API. No setup project, no new hardware. That was it.
I could have done this a year ago by creating a simple UI. I just never thought to ask whether there was an API.
The AI is the interface now
Nothing in the yard changed. The same controller runs the same valves on the same schedule. What changed is how I talk to it: I say what I want, in plain English, and skip the screens.
- Seasonal shifts: more water for the sunny areas in August, less across the board in September, without stepping through every zone in the app.
- Testing a zone: run one to check the heads, without digging through menus.
The part I like most: what I know about my own yard finally has somewhere to go. I always knew which areas bake and how much more August needs. The app made acting on that a chore, so mostly I didn't.
Use AI, but not to click the bad app
There are two ways to "use AI" on a bad app, and only one of them is a good idea.
The tempting one is desktop control: let the agent see the screen and tap through the same bad app for you. That keeps every problem with the screens and adds an agent who can misread them. When the vendor moves a button, it breaks.
The better one is the API. The app is one door into the system: the vendor's idea of how you should use it, and often the only door they advertise. The API is a door built for software, usually into the same system without the screens. The controller never cared how it got its instructions. Only the app made it hard.
| AI clicking the app | AI using the API |
|---|---|
| Works through the same screens you hate | Skips the screens |
| Breaks when the app changes | Usually keeps working when the app changes |
| Signs in as you | Gets its own access |
It doesn't ask first
Grok Bot makes changes without asking me first. I'm fine with that here. If it gets something wrong, some grass gets too much or too little water for a day.
That's the other half of my previous post. My bank connection is read-only because a mistake there is expensive. My sprinklers aren't. Set the guardrails by what a mistake would cost, not by how scary "AI" sounds.
Ask the same question around the house
I haven't done these. They're just the next places I'd ask.
| System | The question | If it gets it wrong |
|---|---|---|
| Thermostat | Can an agent change the schedule through an API? | Uncomfortable, maybe a higher bill. Low. |
| Outdoor lights | Can it turn them on and off, or set a schedule? | A light left on. Low. |
| Garage door | Can it open it, or only report whether it's open? | Your garage, open. High: read-only, or confirm first. |
| Door lock | Can it lock it? Can it unlock it? | Your front door, open. High: confirm first, or don't allow it. |
The easiest way to check is the way I did: ask your agent whether it has a connector or API access to the system. If it doesn't, search for the product name plus "API" or "developer."
Same question for your business
Every business has software with a bad UI: the scheduling tool, the field-service app, the inventory screens nobody can find anything in.
Before you replace it or train people around it, ask:
- Does it have an API?
- Can an agent do the tedious part in plain English, while the system you already paid for keeps running everything?
- What would a mistake cost, and does that call for read-only access, a confirmation step, or neither?
Replacing software is expensive. Putting AI in front of its API often isn't.
What I took away
Bad UI? Use AI. Just go in through the API, not the screens.
First question I ask now: is there an API?