Pair a Matter camera with Home Assistant today and you get a device with no camera entity, no live view and no recordings. That is not a setup mistake. The Matter integration doesn’t have a camera platform yet, while an RTSP camera fed through Frigate has given you live view, recording and person detection for years.
We confirmed both sides on October 20, 2026 with Home Assistant 2026.10.2, Frigate 0.18.2 and the matter.js server 1.5.0 in a Proxmox lab, using a test RTSP stream in place of camera hardware. Camera specs come from the makers and from owners’ reports, and prices are Amazon US on the same day. If you’re choosing a camera this month, buy for the RTSP path and treat Matter as a bonus that arrives with later firmware and Home Assistant releases.
| Matter camera in Home Assistant | RTSP camera with Frigate | |
|---|---|---|
| Live view | Draft pull request only; browser view capped at 1280×720 | Yes, restreamed from Frigate |
| Recording and clips | Not implemented | Yes, continuous or on events |
| Object detection and zones | Not implemented | Yes, with motion and object events in Home Assistant |
| Two-way audio, PTZ | Not in Home Assistant | Depends on the camera; PTZ over ONVIF |
| Cameras you can buy | One we found in US stock: the Aqara G350 | Most PoE cameras that output H.264 |
| Needs on the server | Matter Server app | Frigate, an MQTT broker and the Frigate integration |
Follow each camera path into Home Assistant
A Matter camera and an RTSP camera would give you the same kind of camera entity, but they get there over different wires. Matter 1.5, which the Connectivity Standards Alliance released in November 2025, carries live video over WebRTC, the same peer-to-peer media stack a browser video call uses. An RTSP camera serves a plain video stream that Frigate pulls, decodes, runs object detection on and records, then hands to Home Assistant.
The piece that ties the Frigate path together is MQTT. Frigate publishes every detection to a broker, and the Frigate integration turns those messages into sensors, binary sensors and event clips. Live video comes back to Home Assistant from Frigate’s RTSP restream on port 8554, so the camera itself only ever talks to Frigate. On the Matter side, the Matter Server would only broker the WebRTC handshake, while the video flows straight from the camera to the browser, and that is the link still unfinished.
Check what Matter gives Home Assistant today
Start on the Matter side, because that is where the gap is. Home Assistant’s Matter integration has no camera platform in any released version, so a Matter camera that commissions fine still produces no camera entity. We checked the integration’s own files inside the Home Assistant container:
docker exec homeassistant python -c "from homeassistant.components.matter.discovery import SUPPORTED_PLATFORMS as P; print(sorted(p.value for p in P)); print('camera' in [p.value for p in P])"Its output lists every entity platform the Matter integration can create, then whether camera is among them:
['binary_sensor', 'button', 'climate', 'cover', 'event', 'fan', 'light', 'lock', 'number', 'select', 'sensor', 'siren', 'switch', 'update', 'vacuum', 'valve', 'water_heater']
FalseSeventeen platforms, and camera is not one of them. The component folder has no camera.py, and a grep of it for camera or WebRTC returns nothing. The Python client underneath already carries a WebRTC command for cameras, but no code in the integration calls it. We also pointed the integration at a standalone matter.js server with no device paired. It connected and loaded with 0 entities, which proves the plumbing, not camera support.
The live view exists as a draft. Pull request 176080, opened in July 2026, adds a Matter camera entity that streams over Home Assistant’s native WebRTC, with the media flowing “directly between browser and camera”. Its own notes list the limits: the still image is a static placeholder, the stream is picked automatically, and the offer flow that battery cameras use is not implemented. A tester on the draft reports that a G350 on firmware 4.5.70 plays in the Companion app. On a follow-up pull request, now closed, another tester saw it play in Edge and go black in Firefox, which that pull request’s author put down to Firefox blocking it on unencrypted HTTP pages.
On the server side, things moved the day we checked. The matter.js server 1.5.0 release, out on October 20, adds a camera API with stream start, snapshots and talkback, but the Matter Server app that Home Assistant OS installs was still on 9.2.0 without it. Our probe of a standalone matter.js 1.5.0 server got “Node 99 does not exist” back for camera_snapshot, not “Unknown command”, so the API is there and waits for a camera to pair. Even when it lands, the matter.js camera notes cap a browser live view at 1280×720, because every browser offers H.264 level 3.1 in its WebRTC offer, and that level tops out at 720p. A 4K Matter camera shows 720p in a browser through that path, and nothing in the draft records, stores clips or raises motion and person events.
Set up an RTSP camera with Frigate and Home Assistant
Our Frigate path ran cleanly once the test stream was right. We put Frigate, Mosquitto and Home Assistant Container under Docker on one Ubuntu VM with 4 vCPU, 8 GB of RAM and no GPU. An RTSP server fed Frigate a looped street clip in place of a camera. Run the current Frigate release, because the October 15 maintenance release fixes two critical remote code execution bugs that run as root: one reachable by viewer accounts through websocket paths, and one for admins through the go2rtc exec filter. Our Frigate install guide for Docker covers the container itself, so this section sticks to what links it to Home Assistant. Keep port 5000 off your LAN: it serves the same API with no login, so Frigate’s docs reserve it for a private Docker network, such as the Home Assistant OS app at http://ccab4aaf-frigate:5000:
- Add an MQTT broker first. Frigate publishes every event to it, and the Frigate integration won’t set up until Home Assistant’s MQTT integration exists.
- Give the camera’s RTSP URL to Frigate’s go2rtc, then point detect and record at the restream on 127.0.0.1:8554, so the camera serves one connection.
- Install the Frigate integration (HACS is the documented route), then add it with https://10.0.1.50:8971, your Frigate username and password, and Validate SSL turned off while Frigate uses its self-signed certificate.
Below is the exact Frigate config.yml we ran. On a real camera, the go2rtc line becomes the camera’s own RTSP URL, such as the Dahua main-stream path in the picks below. Matter cameras can’t go into that slot: go2rtc has an open issue for Matter sources, where its maintainer says the documentation is in hand but wants live devices to test with.
mqtt:
enabled: true
host: mosquitto
port: 1883
detectors:
cpu1:
type: cpu
num_threads: 3
go2rtc:
streams:
street:
- rtsp://mediamtx:8554/street
cameras:
street:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/street
input_args: preset-rtsp-restream
roles:
- detect
- record
detect:
enabled: true
width: 768
height: 432
fps: 5
record:
enabled: true
snapshots:
enabled: true
objects:
track:
- person
- car
- bicycleOur lab broker allowed anonymous clients, so the mqtt block has no credentials. A stock Mosquitto 2 broker and the Home Assistant Mosquitto app both refuse anonymous clients, so add user: and password: keys under mqtt: on yours, or Frigate will get “not authorized” back.
You’ll wait a few seconds for the first picture. Frigate’s API answered 8.9 seconds after a cold start, and the first real frame arrived at 11.3 seconds. After a restart, the first frame took 16.9 seconds. Until then the UI shows a “No frames” placeholder, which is normal and does not mean the stream is broken. Once it settled, Frigate’s stats API had the camera at its target rate with nothing skipped. We queried it on the lab host itself, where port 5000 was published for these captures:
curl -s http://127.0.0.1:5000/api/stats | jqWe trimmed the output to the camera and the detector:
"street": {
"camera_fps": 5.0,
"process_fps": 5.1,
"skipped_fps": 0.0,
"detection_fps": 22.9,
"detection_enabled": true,
"connection_quality": "excellent",
"expected_fps": 5,
"reconnects_last_hour": 0,
"stalls_last_hour": 0,
...
"detectors": {
"cpu1": {
"inference_speed": 19.61,The CPU detector, Frigate’s default, needed about 19.6 ms per inference. CPU use followed the scene: about 6% with an empty car park and past 300%, so three of the four cores busy and a peak of 308%, with people and cars in view. Over 40 docker stats samples it averaged 168%, with 893 MiB of RAM. A trial with the OpenVINO detector on the same CPU cut inference to 15.1 ms and lifted top scores from about 0.76 to 0.97. It used a different model, though, so treat it as a reason for you to set up a real detector, not as a benchmark. Our Hailo vs Coral comparison covers the accelerators.
In about 16 minutes Frigate logged 35 person and 17 car events, each with a clip and a snapshot, but no bicycle events, because the 320×320 CPU model never labelled the bike. OpenVINO caught one bicycle in its short trial run. The frames come from the Intel IoT DevKit sample videos, shared under CC BY 4.0, which carry real people, cars and a cyclist across a car park.
On the Home Assistant side, adding the Frigate integration took 1.91 seconds and registered 45 entities, 20 of them disabled by default. The camera entity, camera.street, returned a 768×432 JPEG through Home Assistant’s camera proxy, and the frontend offered both HLS and WebRTC for live view. Create a long-lived access token under the Security tab of your Home Assistant profile and export it as HA_TOKEN, then fetch a still:
curl -s -o camera_proxy_street.jpg -w "%{http_code} %{content_type} %{size_download} %{time_total}s\n" -H "Authorization: Bearer ${HA_TOKEN}" http://10.0.1.50:8123/api/camera_proxy/camera.streetHome Assistant answered in 25 ms:
200 image/jpeg 13626 0.024776sYou get person, car and bicycle occupancy sensors that switch on and off with the MQTT events, and they’re what your automations hang off. That is the part the draft Matter entity doesn’t touch, since it streams video and raises no events at all.
Frigate and Home Assistant together used about 1.3 GB of RAM here, so a small box handles both. Our mini PC picks for Home Assistant size that host, and the PoE switch guide covers powering the wired cameras below.
Pick a camera for each path
Our PoE camera guide for Frigate already covers outdoor turrets, bullets and doorbells, so these four don’t repeat it. Two answer the Matter question, and two are the cameras Frigate’s own docs point to. Prices are Amazon US on October 20.
Aqara Camera Hub G350: the only Matter camera in US stock
Aqara calls the G350, about $140, “The World’s First Matter-Certified Camera”, and it is the only Matter camera with shipping firmware and US stock we found. It has a 4K wide lens and a 2560×1440 telephoto lens at 20 fps in H.264, plus a Zigbee hub, a Matter controller and a Thread radio in the same body. It runs on Wi-Fi and USB-C power, with no Ethernet port.
Its value today is that it speaks both languages. Derek Seaman reports that it joins Home Assistant over Matter as a bridge with no entities, while Aqara itself says Home Assistant gets “only streaming” over RTSP. Turn on RTSP LAN Preview in the Aqara app, and Seaman lists 360p, 1080p and 2160p streams to give Frigate. Frigate’s docs warn against Wi-Fi cameras for recording, so treat it as an indoor camera you can move to Matter later, not your main NVR feed.
Tapo C260: an RTSP camera now, maybe Matter later
At about $60 from Amazon.com, the C260 gives you 4K at up to 25 fps in H.264, pan and tilt, and both RTSP and ONVIF on TP-Link’s spec page. That’s enough for Frigate today, with one caveat: it is Wi-Fi only, like the G350, so keep it indoors and close to the router. Stock was marked limited when we checked.
The Matter part is a maybe. Matter Alpha reports that the C260 and two other 4K Tapo models passed Matter 1.5.1 certification in June, but TP-Link’s spec page makes no Matter claim and we found no Matter firmware. The C260 also ships in V1, V2 and V2.60 hardware revisions, and Matter Alpha advises waiting to see which one gets Matter. Buy it as a cheap 4K RTSP camera, and if a Matter update reaches your revision, count it as a bonus.
EmpireTech IPC-T549M-ALED-S3: the camera Frigate’s docs name first
Frigate’s recommended hardware page ranks Dahua, Hikvision and Amcrest in that order, and the first camera it lists is this Dahua-platform 4MP turret. The Amazon link in Frigate’s docs was out of stock on October 20. The same model code is about $200 from EmpireTech’s newer Amazon shop, which sells under the GemaVision name. It has a 1/1.8-inch sensor, warm LEDs for color at night up to 30 m, PoE and an IP67 rating.
Dahua cameras use the RTSP path Frigate documents, /cam/realmonitor?channel=1&subtype=0 for the main stream, and subtype=1 for the substream, which Frigate’s notes say typically supports low resolutions only, the right size for detection. It is a close sibling of the IPC-T54PRO-AS in our PoE guide. Pick this one if you want the exact model Frigate’s maintainers name.
Reolink RLC-510A: the budget PoE bullet
The RLC-510A is about $70 from ReolinkDirect: a 5MP bullet that streams H.264 at 2560×1920 and 30 fps, with a 4 to 15 fps substream and 802.3af PoE. That keeps it inside Frigate’s advice to stick with Reolink models of 5MP and lower, since owners report problems with Reolink’s 4K cameras.
Two settings matter before Frigate sees it. Frigate’s docs ask you to enable HTTP in the camera’s advanced network settings, because the recommended stream and the setup wizard both use it. Reolink’s FAQ says RTSP may be off by default too, and you only need it for a secondary two-way audio stream. Frigate’s camera notes then recommend http-flv rather than RTSP for 5MP Reolink models, with the camera set to On, fluency first and Interframe Space 1x for a steady key-frame rate.
Choose the path for each camera
Choose by what you need from the camera, not by the protocol logo on the box you’re holding. The matrix below is where we would land with Home Assistant as it ships today:
| What you want | Path | Camera |
|---|---|---|
| Recording, person detection, review clips | RTSP into Frigate | EmpireTech IPC-T549M-ALED-S3 or Reolink RLC-510A |
| One indoor camera for Apple, Google and Home Assistant users | Both: RTSP to Frigate now, Matter later | Aqara G350 |
| Cheap 4K indoor camera with pan and tilt | RTSP into Frigate, over Wi-Fi | Tapo C260 |
| Live view in SmartThings today | Matter | Aqara G350 |
| Battery or doorbell camera over Matter | Wait | The draft can’t handle battery cameras yet |
The camera that does both is the safe buy, because its RTSP stream works with Frigate now and its Matter side improves with firmware and Home Assistant releases. Watch pull request 176080 and the Matter Server app changelog. When the camera API reaches the app and the pull request merges, the Matter column above changes, while the RTSP path through Frigate keeps working as it does today.
