MQTT integration

Camera alerts on your MQTT broker

MQTT is what your automation already listens to. A few cameras can publish to it; most can't, and none of them publish a hosted snapshot or what was in the frame. NVR Bridge does that part. Every event is published to a topic on your own broker — the language Home Assistant, Node-RED and openHAB already speak — so whatever you've already automated can act on it.

You need
An MQTT broker — Mosquitto, EMQX, HiveMQ, or the one inside Home Assistant
Setup
Host, port, topic — plus SSH details if the broker is LAN-only
What arrives
A JSON message on the topic you chose, carrying links to the snapshots
Start freeRead the docsNo card. No NVR.
mosquitto · 192.168.1.10:8883qos 1 · retain

topic

nvrbridge/back-gate-cam/event

{
  "camera": "Back gate",
  "eventTime": "21:04:11Z",
  "objects": [
    { "label": "person", "score": 0.94 }
  ],
  "image": "https://…/optical.jpg"
}

How it works

Four steps · about five minutes

  1. 01

    Add your camera

    Each camera gets its own private inbound address. Point the camera's existing email or FTP alert settings at it — no firmware changes and nothing to install.

  2. 02

    Point us at your broker

    Add an MQTT notification with the broker's host, port and credentials, then choose the topic, the QoS and whether to retain. If the broker only exists on your LAN, give us SSH details instead and we'll publish through a tunnel — nothing is exposed to the internet.

  3. 03

    Say what should reach you

    A trigger describes what matters — motion on the back gate, a person on the driveway, one particular number plate. Attach the MQTT notification to it and only those events go out. One trigger can feed several destinations at once.

  4. 04

    Send a test

    Hit Test to push a sample event with sample detections, so you can see exactly how it lands in MQTT before a real one arrives. Every delivery after that is logged with its result.

What you get

One trigger, as many destinations as you like

  • Topics templated per camera, so one notification covers every camera you own
  • QoS and the retain flag are yours to set
  • TLS to a public broker, or an SSH tunnel to one that never leaves your LAN
  • No inbound ports, no VPN and no dynamic DNS at your end
  • Works with any camera brand that can email or upload by FTP
  • Filter to a person, a vehicle, an animal or one number plate before anything is published

Questions

The ones people actually ask

My broker isn't reachable from the internet. Does that rule this out?

No. Give us an SSH host and key and we'll open a tunnel for the moment it takes to publish, then close it. The broker keeps listening on your LAN only, exactly as it does now.

What does the message look like?

JSON by default — camera, time, event type, snapshot links and any detections. If the receiver wants a particular shape, write the body yourself with placeholders.

Do I need an NVR or something running at home?

No. The camera connects outward to us using the email or FTP settings it already has. There's no recorder, no mini-PC, no VPN and no inbound port to open.

Can I stop it alerting on every passing cat?

Yes. Turn on detection and filter the trigger to what you care about — a person, a vehicle, a particular animal, any number plate or one specific plate. Everything else still lands on your timeline; it just doesn't interrupt you.

Try it with your own camera

Add a camera, point its email at the address we give you, and watch the first event land. About five minutes, all of it in a browser.

Create a free accountFree tier · no card required