Automations In pilot
What the camera sees, you decide.
A visual editor to build flows: what triggers them, which condition they meet and what they do. Drag blocks, connect them and save. Templates get you started in a minute, and every camera option is also a flow you can open.
Three pieces, any combination
More than sixty blocks in the editor. Each one says whether it runs on the camera or in the cloud.
Something happens
A camera event, a schedule, a place opening, a device without signal, a count, "Hola Tero", a webhook from another system or a button.
A condition is met
Conditions, time windows, "within opening hours", debounce, "repeated N times", wait, "still offline?" or "current count".
TeroVision acts
Moves the camera, takes a snapshot, records, asks the AI, plays a phrase on the speaker, alerts and sends the event to your systems.
In pilot
Simple mode and advanced mode
Tick an option on the camera (the patrol, scheduled snapshots, "Hola Tero", recording) and the camera does it, as always. That same option is already a flow: "View as automation" opens it, and you can hang alerts, snapshots or webhooks on the events it emits.
- Changing the flow changes the camera setting, with the same permissions, conflicts and audit as the page.
- The patrol, the watermark, "Hola Tero" and recording keep running on the camera, even without internet. What you hang on them runs in the cloud.
- Each feature can run always, during its place’s opening hours or on its own schedule.
- A managed flow is never deleted, only turned off. "Unlink" copies it to a regular one.
Everything an automation can do
Cameras, places, counting, AI and your systems, on the same canvas.
-
Events in seconds
What happens on the camera reaches the cloud over a signed channel and starts the flow. Everything in its log (rebooted, disconnected, SD card, uploads) works as a trigger.
In pilot -
The whole camera
Go to an x/y position, move it, go home, save positions, patrol, record, stream, say a phrase, watermark, scheduled snapshots, tracking and face blurring.
In pilot -
Schedules and places
"The shop opened", "the camera’s hours ended", "within opening hours": record, take snapshots or detect only when it makes sense.
In pilot -
No signal
"Offline for more than X minutes", once per outage or repeated, and "Signal is back". Your own alert chain.
In pilot -
Counting and occupancy
Full parking, crowding within hours, line crossings, long dwell times and hourly summaries.
In pilot -
AI in the middle
A snapshot and a question to a model, and the flow continues through "yes", "no" or whichever category it answers.
In pilot -
Outputs to your systems
Panel notice, email, call, signed webhook, Discord with the snapshot, SFTP, FTP/FTPS, external S3 and MQTT.
In pilot -
With a brake and a log
One button stops them all, every flow has caps and loop protection, runs with the permissions of whoever saved it, and everything is audited.
Works today
Ready-to-use templates
Fifteen flows so you never start from a blank canvas. They are created switched off: fill in the camera, the zone or who to notify, and turn it on.
-
Counting
Occupancy at a spot
- What it does
- Takes a snapshot every minute and counts people. If there are 5 or more for a while, it speaks through the speaker, saves the snapshot and calls a webhook.
- Why
- Keep the till or the fitting rooms from filling up unnoticed.
-
Counting
Full parking
- What it does
- When no space is left it posts a notice and calls a webhook. When a space frees up, it says so too.
- Why
- Turn on the "full" sign or close the barrier automatically.
-
Counting
Crowding during opening hours
- What it does
- When a crowd starts at a spot, within hours, it alerts and emails. When it breaks up, it reports the peak and how long it lasted.
- Why
- Add staff in time and measure how long people waited.
-
Counting
Entries per hour
- What it does
- At the end of each hour it sends how many people went in and out through a line to another system and by email.
- Why
- Compare footfall with sales, hour by hour.
-
Counting
Someone stayed more than X minutes
- What it does
- If live counting sees someone in a zone longer than you set, it alerts and emails. Once per person.
- Why
- Help whoever waits too long, or check a sensitive area.
-
Signal
Camera offline
- What it does
- When a camera disconnects it posts a notice and sends an email, debounced for flapping connections.
- Why
- Find out before you need the recording.
-
Signal
No signal for 10 minutes
- What it does
- If any device goes 10 minutes without signal, it posts a notice. Once per outage.
- Why
- A calm alert, without noise from micro-outages.
-
Signal
Alert chain per outage
- What it does
- After 10 minutes offline, a notice; if it is still down at 20, an email and ringing the phones from another online device.
- Why
- Escalate only while the problem persists.
-
Voice
Someone said "Hola Tero"
- What it does
- During opening hours it takes a snapshot, saves it and alerts. After hours it only alerts.
- Why
- A call for help that arrives with context.
-
Hours
Record only during opening hours
- What it does
- When the place’s hours start, its cameras start recording; when they end, they stop.
- Why
- Record what matters and don’t fill the card at night.
-
Hours
Snapshots only during hours
- What it does
- Takes a snapshot every 10 minutes while the place is open.
- Why
- See how the day is going without watching video.
-
Hours
Detect only during hours
- What it does
- On motion within hours it takes a snapshot, counts people and alerts if someone is there. After hours it does nothing.
- Why
- Fewer false alarms while the place is closed.
-
AI
Has someone fallen?
- What it does
- Every 5 minutes it takes a snapshot and asks the AI whether someone is on the floor. If yes, it calls and alerts with the reason.
- Why
- A second look at a common area, measured in a pilot.
-
AI
Classify what the camera sees
- What it does
- On motion, the AI says whether it sees a person, a vehicle, an animal or nothing, and each answer takes its own path.
- Why
- Alert on people, not on the cat.
-
AI
Daily summary
- What it does
- At 20:00 it reads what the counting recorded and asks the AI for a short summary, sent by email. No snapshots leave.
- Why
- A written daily report without opening the panel.
They live alongside your system
The API can list, enable, disable and run automations. If your system needs a camera to stay still for a few minutes, it takes control and the automations that would move it are skipped, with the reason in the history.
In pilot For developers
Floor plans and operations
Counting and occupancy
AI in your flows
For developersShall we try it with your cameras?
We show you the panel running and build the first automations for your place together. Whatever is in pilot gets tested with you before we promise it.