The fox does not get to turn the porch light on.
Motion sensors fire at wind, shadows, and next door's cat. Put a model in the loop and your automations trigger on what is actually there.
The answer lands wherever you already are.
The EOT-1 speaks MCP and REST, so your agent can put what it sees into anything with an API. That is the difference between a camera you check and a camera that tells you.
Other things to ask it.
- ❯Start the coffee when someone actually sits at the kitchen table.
- ❯Only run the sprinklers if the lawn looks dry.
- ❯Nudge me if the bins are still out on Thursday morning.
Common questions
Do I need a hub or a cloud account?
Neither. The EOT-1 serves its own HTTP endpoint at eyeofthetiger.local, so anything on your network that can make a request can capture a frame and act on it. No bridge, no relay, no account.
Does it work with Home Assistant?
Yes, though not as a native integration at launch. Call the REST API from a Home Assistant shell command, a Node-RED flow, or any HTTP-capable node, and you have a trigger. The docs have working examples for Home Assistant, n8n, and plain curl.
Where does the trigger logic actually live?
In your code, which is the entire design intent. The camera provides the image and you decide the condition, the schedule, and what happens next. Nothing is baked into firmware, so you can change the rule by rewording a sentence rather than waiting for a vendor update.
Batch 001 is in stock and shipping now.
100 Founder Edition units. Ships worldwide. One-time payment, no subscription required, 30-day returns.