Integrations

MQTT publishing

Rerinku View can send events to your own MQTT broker (the Mosquitto that comes with Home Assistant, Node-RED, your automation system and so on). Topics follow Frigate’s conventions. Rerinku View connects to your broker as a client; its built-in MQTT service for devices isn’t open to third parties.

Turn it on under Settings → Notifications → MQTT publishing. It’s off by default:

Setting	Description
Broker URL	Supports tcp://, mqtt://, ssl://, tls://, mqtts://, ws:// and wss://, such as tcp://192.168.1.10:1883
Username / Password	Optional. The password is stored encrypted and isn’t shown again after you save
Topic prefix	Defaults to rerinku; can’t contain + or #

Topics

The examples below use the default prefix rerinku:

Topic	Content	Retained
rerinku/available	online or offline; set to offline by the last will message when Rerinku View disconnects	Yes
rerinku/events	One JSON message per event change (see below)	No
rerinku/<camera>/<kind>	ON while an event of this kind is in progress, OFF when it ends	Yes
rerinku/<camera>/<class>	The current number of objects of this class in the picture, such as rerinku/front-door/person → 2; back to 0 when the event ends	Yes

• <camera> is the camera name converted to lowercase, with spaces replaced by hyphens. Chinese and other non-Latin text is kept. If the result is empty, device-<id> is used.
• <kind> is object (AI recognition), motion (motion detection), tampering (covering or tampering), image-quality, digital-input, digital-output, audio-alarm or unknown. Besides AI recognition, alarms the camera reports itself are published too.
• Messages are sent with QoS 1. The latest state of retained topics is kept even while disconnected, and the whole set is published again on every connect. events is a live stream: events from while it was disconnected aren’t sent later.

A message on rerinku/events:

{
  "type": "new",
  "id": 1842,
  "camera": "front-door",
  "device_id": 3,
  "device_name": "Front Door",
  "kind": "object",
  "labels": ["person"],
  "faces": ["Alex"],
  "score": 0.91,
  "zones": [],
  "has_snapshot": true,
  "start_time": 1793000000,
  "end_time": null
}

type goes new, update, then end. Times are Unix seconds, and end_time is null while the event hasn’t ended.

Things to note: two cameras with the same name end up on the same topic. After you rename a camera, the retained messages under the old name stay on the broker; clear them yourself if needed. Compared with Frigate, there’s currently no snapshot topic and no Home Assistant MQTT discovery.

Home Assistant

The Rerinku View Home Assistant integration brings each camera into Home Assistant. It needs Home Assistant 2026.9.0 or later.

Installation

1. Download it from the integration repository, and copy its whole custom_components/rerinku directory into custom_components/ in your Home Assistant configuration directory.
2. Restart Home Assistant.
3. Under Settings → Devices & services → Add integration, search for Rerinku and enter Rerinku View’s address to finish binding.

Entities

Each camera gets:

Entity	Description
camera	Snapshots use Rerinku View’s thumbnail. Live video plays through Home Assistant’s native WebRTC, connecting directly to Rerinku View
binary_sensor × 5	Motion, Object detected, Person, Vehicle and Pet. Person has a recognized attribute that lists the people recognized

State is pushed in real time over WebSocket, and also reconciled every 60 seconds.

Limitations

• The integration can’t connect yet when Rerinku View has an access password set.
• H.265 cameras aren’t transcoded. If the browser you use Home Assistant in can’t decode H.265 over WebRTC, you won’t see video.
• The integration has no recording switch and no playback.
• If your Rerinku View was connected before October 2026: after you upgrade, the device serial-number format is unified, so Home Assistant creates a batch of new entities. Delete the old entities manually.