Skip to content

HA Bridge Plugin Guide

seenzus Bridge is the plugin that runs inside Home Assistant and connects your space to seenzus, both ways:

  • No tunneling required: the bridge dials out over public MQTT; your HA exposes no ports;
  • Per-bridge credentials: every bridge gets its own connection credentials and can only send/receive on its own lane;
  • Three-channel protocol: commands, results and state flow separately, with device state reported as an event stream — what you see in the app is what’s happening at home.

Download the plugin package, unzip it into Home Assistant’s config/custom_components/ directory, and restart HA. You’ll then find it under Settings → Devices & Services → Add Integration.

  1. When adding the integration, choose Quick pair and enter the seenzus service address;
  2. Your browser opens the authorization page — log in and confirm;
  3. Back in HA, the integration completes automatically: the bridge receives its own credentials and starts reporting the device catalog.

You never type a single MQTT parameter.

Pairing mode 2: Manual MQTT (bring your own broker)

Section titled “Pairing mode 2: Manual MQTT (bring your own broker)”

Prefer your own MQTT broker? Choose manual mode: fill in broker host, port, username, password and bridgeId, then pick “Manual” on the app’s Sources page with the same parameters. It’s the escape hatch for power users — most people should quick-pair.

  • A card for the bridge appears on the Sources page, with live status and coverage (N devices · M spaces);
  • Devices get sorted into Spaces — rename and rearrange them in the app; seenzus follows your naming;
  • Renaming, broker changes and disabling all live on the source card: disabling cuts the connection but keeps your data.
SymptomCheck this first
Authorization page won’t openVerify the service address is complete (including scheme); try another browser
”Pairing session expired”Sessions are one-shot — start a fresh quick-pair from HA
Paired but no devicesGive it a moment (catalog sync takes a beat); confirm the source card shows “online”
Source shows offlineIs the plugin running in HA? The bridge reconnects automatically after outages/restarts
Device state frozenBridge online but stale? Hit “Test connection” on the source card

Still stuck? See the FAQ or come find us.