Preset

reCamera

Install object detection, text reading, face analysis, fall detection or people counting from the reCamera console, switch between them in the browser, and optionally send the results to Home Assistant over MQTT.

Devices: reCamera; steps 4 to 6 (Home Assistant) also need a computer or reComputer R1100.
Network: this computer needs internet access while installing apps.
Limit: one app runs at a time. Switching apps stops the previous one and its RTSP and MQTT output; nothing is uninstalled.

Update the reCamera Console

Install console 0.5.5. The step is skipped if the camera is already on that version.

Prerequisites

Connect the camera over USB (address 192.168.42.1), or put it on the same network as this computer (use the IP your router shows).
Username recamera, default password recamera (older units use recamera.2).
New devices need SSH enabled first: connect over USB, wait about two minutes, open http://192.168.42.1/#/security, sign in, and turn on the SSH toggle.

Troubleshooting

Symptom	Fix
Cannot connect	USB: use `192.168.42.1`; network: check your router for the IP
Password rejected	Default is `recamera`; units with older firmware use `recamera.2`
Install failed	Restart the camera and run the step again
Node-RED stopped working	The console has taken over the camera; switch back from the console's system settings
Want the original panel back	Hold the User button while plugging in power and release when the red LED stops blinking and stays on; this factory-resets the camera

Choose and Install an App

Pick an app from the dropdown and press Deploy. Download, install and activation run automatically.

Prerequisites

This computer has internet access; the camera does not need it.
Address and password carry over from the previous step.
An app with its models can be a few hundred megabytes; progress is shown during deployment.

Troubleshooting

Symptom	Fix
Dropdown is empty or short	This computer cannot reach `sensecraft-statics.seeed.cc`; fix the network and press refresh
Login rejected	Use the camera's credentials, default `recamera` / `recamera` (`recamera.2` on older units). Repeated failures lock login for 60s
Console not answering	The camera may still be restarting; wait a minute and deploy again
"busy" error	The console is running another app operation; retry when it finishes
Not enough storage	Uninstall an unused app from the console first
Installed but not running	Check its status on the console's Applications page; if files are missing, deploy this step again
Camera won't start after enabling privacy blur	Unplug the camera and plug it back in; a software reboot is not enough

After Deployment

The camera is running the app you picked. The apps answer ONVIF, so an NVR or video management system can discover the camera and pull its stream.

Steps 4 to 6 are optional and bring the results into Home Assistant.

Open the Console

Open the camera's console and check the app's detection results.

Prerequisites

Sign in with the camera credentials from step 1.
On Applications, press Debug on the active app for the live view and detection results.
Switch apps on Applications; Install from cloud lists the rest of the catalog.

Troubleshooting

Symptom	Fix
Page won't load	Wait a minute for the camera to finish restarting, then refresh
Login rejected	Use the camera's credentials, default `recamera` / `recamera`
Live view is black	No app is running; go back one step and deploy an app

After Deployment

The console is at http://<camera-ip>/: install or switch apps, check the live view, and change network, privacy and system settings.

Deploy Home Assistant

Start Home Assistant and an MQTT broker. Skip this if you already run both.

Deployment method

Prerequisites

Docker Desktop installed and running.
At least 2 GB free disk.
Ports 8123 and 1883 free.

Troubleshooting

Symptom	Fix
Port 8123 or 1883 busy	Stop the existing Home Assistant or Mosquitto, or skip this step and use it
Docker not starting	Open the Docker Desktop application
Container keeps restarting	Make sure at least 2 GB RAM is available

After Deployment

Open http://localhost:8123 and create your admin account in the onboarding wizard.
The MQTT broker listens on port 1883 of this machine. Step 5 asks for its address.

Connect the Camera to Home Assistant

Point Home Assistant and the camera at the same broker. The entities appear automatically.

Prerequisites

Home Assistant is running and you can sign in.
An MQTT broker reachable from the camera (from step 4, or your own).
An app is running on the camera.

Troubleshooting

Symptom	Fix
Test Connection fails on the camera	Enter the IP of the broker's machine, not `localhost`
Saved, but nothing appears in Home Assistant	Confirm the MQTT integration in Home Assistant uses the same broker and port, then restart the running app from the console
Entities appear but stay unavailable	No app is running on the camera; activate one from the console
Entities vanished after switching apps	Expected; each app publishes its own entity set

After Deployment

Detection results appear in Home Assistant through MQTT discovery, and the entity set changes when you switch apps. Discovery carries no video; add the picture in step 6.

See the Results in Home Assistant

Put the picture and the detections on one card.

Prerequisites

Find the entities. Settings → Devices & Services → MQTT → the camera's device. Note the entities you want on the dashboard.
Add the video. Settings → Devices & Services → Add integration → Generic Camera:
- Stream Source URL: rtsp://<camera-ip>:8554/live0 (copy it from the console's Integrations page)
- RTSP transport protocol: TCP
- Leave Verify SSL certificate unticked
Build the card. Settings → Dashboards → open your dashboard → pencil to edit → + Add card → Picture glance. Set Camera Entity to the Generic Camera, then add the detection entities to the Entities list.
Separate cards (optional). An Entities card lists the values as rows; a History card shows how they change.
Automation (optional). Settings → Automations & scenes → Create automation → trigger Entity → State on a detection entity.

Troubleshooting

Symptom	Fix
Generic Camera says it cannot connect	Test the URL in VLC first; if VLC plays and Home Assistant does not, set RTSP transport to TCP
Picture is black or stalls after a few seconds	Close the console's live view and any VLC window
Card shows the camera but no detection icons	Confirm the entities exist under Settings → Devices & Services → MQTT, then add them to the card
Entities show `unknown`	Values appear after something changes in front of the camera
Picture glance will not accept an entity	Add individual entities, not the device

After Deployment

The dashboard shows the camera picture and the detection entities. Switching apps changes the MQTT entities; the Generic Camera picture is unaffected.

Preset

reCamera Pro

Install apps from the reCamera Pro App Center and optionally send the results to Home Assistant over MQTT.

Devices: reCamera Pro; steps 3 to 5 (Home Assistant) also need a computer or reComputer R1100.
Network: camera and this computer on the same network; this computer needs internet access while installing apps.
Limit: the camera has no built-in MQTT broker, so results stay on the device until you enter a broker address in step 4, and that address is set per app. One inference app runs at a time.

Check and Update Firmware

Only needed once, and only if the camera's page has no App Center yet.

Device Management, the Embedded tab, and the reCamera Pro entry with its address and ADB port

Prerequisites

Open the camera's page; if the App Center is there, skip this step.
In this app: Device Management → Embedded → reCamera Pro, fill in the camera's address, then Check for device updates.
The update uses ADB on port 5555 over the network; USB alone is not enough.
The camera reboots during the update, which takes a few minutes. Do not power it off. Factory reset on the same page rolls it back.

Troubleshooting

Symptom	Fix
Test connection fails	Check the address, and that port 5555 is reachable from this computer
Nothing happens after Check for device updates	The camera may already be up to date; look for the App Center on its page
App Center still missing afterwards	Reload the page after the camera finishes rebooting

Choose and Install an App

Open the App Center, install an app and start it.

Prerequisites

Sign in with the camera dashboard's credentials (not SSH credentials).
Open App Center in the sidebar and press + to open the install dialog.
If an app needs a runtime component, the dialog asks before downloading it; declining cancels the install.
Press Start on the app's card. Starting one inference app stops the other.
Open Live Preview or Live View in the sidebar to see the picture and detections.

Troubleshooting

Symptom	Fix
The page does not open	Enter the address starting with `http://` and let the browser follow the redirect
Certificate warning	With HTTPS enabled the camera uses a self-signed certificate; continue past the warning
App Center is empty or asks you to sign in	Sign in to the dashboard first, then reopen the tab
Failed to load catalog	This computer cannot reach `sensecraft-statics.seeed.cc`; if you host your own catalog, change its URL in the install dialog
Checksum mismatch — refusing to install	Reload the catalog and retry
An app is listed but will not start	Its model is missing; reinstall the app
No detections in Live Preview	Confirm the app you installed is the one running

After Deployment

The camera is running the app you picked. Steps 3 to 5 are optional and bring the results into Home Assistant.

Deploy Home Assistant

Start Home Assistant and an MQTT broker. Skip this if you already run both.

Deployment method

Prerequisites

Docker Desktop installed and running.
At least 2 GB free disk.
Ports 8123 and 1883 free.

Troubleshooting

Symptom	Fix
Port 8123 or 1883 busy	Stop the existing Home Assistant or Mosquitto, or skip this step and use it
Docker not starting	Open the Docker Desktop application
Container keeps restarting	Make sure at least 2 GB RAM is available

After Deployment

Open http://localhost:8123 and create your admin account in the onboarding wizard.
The MQTT broker listens on port 1883 of this machine. Step 4 asks for its address.

Connect the Camera to Home Assistant

Enter the broker address in the app's configuration; the entities appear in Home Assistant automatically.

Prerequisites

Home Assistant is running and you can sign in.
An MQTT broker reachable from the camera (from step 3, or your own).
An app is running on the camera.

Troubleshooting

Symptom	Fix
No Result output group in Configure	The app has no MQTT output; its results stay on the device
Nothing arrives at the broker	Make sure the broker address is not empty and is reachable from the camera
Save is refused	Broker host must not be empty; base topic must not be empty or contain `+`, `#` or a space
Saved, but nothing appears in Home Assistant	Set Output mode to Home Assistant, and confirm the MQTT integration in Home Assistant uses the same broker and port
Entities appear but stay unavailable	No app is running on the camera; start one from the App Center
Entities vanished after starting a different app	Expected; each app publishes its own entity set, and an app without MQTT configured publishes none

After Deployment

Detection results appear in Home Assistant. This setting belongs to the current app only: apps you install later start with MQTT output off, so repeat this step in their Configure dialog.

See the Results in Home Assistant

Put the picture and the detections on one card.

Prerequisites

Find the entities. Settings → Devices & Services → MQTT → the camera's device. Note the entities you want on the dashboard.
Turn on RTSP. On the camera: Live View → Stream Settings, pick RTSP and enable it, then copy the stream URL shown. Set a username and password on the same page if you want authentication.
Add the video. In Home Assistant: Settings → Devices & Services → Add integration → Generic Camera, paste the URL, and set RTSP transport protocol to TCP. With authentication, use rtsp://user:password@….
Build the card. Settings → Dashboards → open your dashboard → pencil to edit → + Add card → Picture glance. Set Camera Entity to the Generic Camera, then add the detection entities to the Entities list.
Separate cards (optional). An Entities card lists the values as rows; a History card shows how they change.
Automation (optional). Settings → Automations & scenes → Create automation → trigger Entity → State on a detection entity.

Troubleshooting

Symptom	Fix
No stream URL under Stream Settings	RTSP is not enabled or another protocol is selected; picking RTSP turns RTMP and ONVIF off
Generic Camera says it cannot connect	Test the URL in VLC first; if VLC plays and Home Assistant does not, set RTSP transport to TCP. Credentials set on the camera go in the URL
Picture is black or stalls after a few seconds	Close the camera's Live Preview and any VLC window
Card shows the camera but no detection icons	Confirm the running app has MQTT configured (step 4) and the entities exist under Settings → Devices & Services → MQTT
Entities show `unknown`	Values appear after something changes in front of the camera

After Deployment

The dashboard shows the camera picture and the detection entities. Switching apps replaces the MQTT entities with the new app's set; the Generic Camera picture is unaffected.

Plug & Play AI Camera — Deployment Guide

reCamera

Update the reCamera Console

Choose and Install an App

Open the Console

Deploy Home Assistant

Connect the Camera to Home Assistant

See the Results in Home Assistant

reCamera Pro

Check and Update Firmware

Choose and Install an App

Deploy Home Assistant

Connect the Camera to Home Assistant

See the Results in Home Assistant