Monitor Frigate NVR with DumbMonit
BetaCameras that stopped delivering frames, detector speed and hangs, frame rates, recording storage, updates.
DocumentationOfficial website: Frigate
Product descriptions are in English, as in the product. The page labels follow your language.
What DumbMonit watches
Whether Frigate still sees: cameras that stopped delivering frames, detector inference speed and hangs (Coral, GPU, CPU), frame rates, the disk holding the recordings and updates.
Typical use. NVR: cameras without frames, detector hangs, frame rates, recording storage
Examples
- Frigate 0.14 and later
How it connects
What you need
- Bearer tokenSent as "Authorization: Bearer …" on every request.
No account needed.
Network ports to open
5000/TCPAPI (HTTP, default, no login)8971/TCPOnly with the authenticated port behind a bearer-token proxy
Setup steps: Let DumbMonit read Frigate's statistics
Nothing to install: check from the DumbMonit host that Frigate's API answers on port 5000.
curl http://frigate.lan:5000/api/versionIf a proxy in front of Frigate expects a token (port 8971 requires a login), choose Bearer token below; otherwise choose No authentication.
In DumbMonit, enter Frigate's address, for example "frigate.lan".
Heads-up. Port 5000 has no login and gives full control of Frigate: expose it only to DumbMonit, never to the internet. A camera you turned off in Frigate's settings also reads as offline.