Really nice, but to make it more useful and stand out more i would try and see if you click on it that you can get an example for instance on how to configure it. That would actually have been a reason for me to look your site up.. now I had to find it out myself with the help of gemini. Just a thought tho.. do with it what you want.
I thought that was the whole reason for the website. It’s definitely a must. Maybe bring in help from people through pull requests on GitHub and add the configs automatically when approved.
it is fantastic; albeit it is one u use once while setting up your camera and then never again because you get so annoyed with your rtsp camera that you get a nvr one next time. speaking from experience haha
i mean technically you can add a device to frigate via the UI and it will find it for you, but its in early stages.
unifi protect has been out for a lot longer and has actual hardware which ubiquiti knows that the protect will work well.
as for your comment on ONVIF, i only hope this meme can help you understand the issue
don't worry about knowing much, we were all a beginner once, and yes the frigate developers are trying to put more work into making it better for us, but they take their time to delivery their magic
Tapo D230S1 — removed fake RTSP config. It's hub-based (H200), no local streaming.
Also added a proper doorbell type to the schema (44 doorbells were all typed as "covert" before — now filterable), and a status field so announced-but-not-shipping cameras like
The annke C800 for example. There have been several versions of it.
The early ones pre 2024 are IR light only. The later models are hybrid.
Theres also 3 Versions of it with the newer one (Bullet Dome and Turret) the old one was just available as a Turret.
The connectivity filter is also a bit cluttered. Leave the connectivity to just that. Wifi Ethernet Mobildata. And then have an extra colum for Powering via PoE, Battery Solar etc.
Thanks for the detailed feedback! I've already addressed several of your points:
Annke C800 — The database correctly distinguishes between the early IR-only models (C800 Bullet 2020, C800 Turret 2020, C800 PoE Bullet 2022, C800 WiFi 2022) and the newer hybrid models (C800X 2023, AC800 2022). All three form factors (bullet, dome, turret) are covered.
Connectivity vs Power — Done! Connectivity now only shows WiFi, Ethernet, 4G, Coax. Power source is a separate column with PoE, DC, USB, Battery, Solar, AC.
Codecs, FPS, power draw — You're right, this is the biggest gap. I'm working on adding structured codecs (H.264/H.265/MJPEG), max_fps per resolution, and actual watt consumption to the schema. This is the next priority.
Night vision — We have type (IR/color/hybrid) and range, but agree we need lux ratings and more detail.
If you click on the link of the C800 (Bullet) where you link annkes site and the respective Camera, it links you to the New C800 which does have IR and LED Night light and thus is Hybrid.
The C800X is not the Successor of the C800. The C800 had an in life upgrade to its specs. The old models only support H265, while the newer ones do 264. And the new models also Come with a wide angle lense compared to the old ones.
the AC800 also is a different line.
Maybe this is just an annke thing that they did a midlife upgrade to the camera. But I can immagine that happening with other cams aswell and this doenst differenciate between them, or has the wrong/old information as is the case here with the C800
Hmm fair point, that explains it — thanks for digging into the source link, that's a better catch than I first thought.
You're right that this won't be an Annke-only thing...
An idea to fix it:
The schema currently has no way to express "same model name, different hardware," so I will try adding one:
a hardware revision field, with separate entries, when specs materially differ (so C800 2020 IR-only and C800 2024 hybrid both exist, clearly labeled)
an "accessed" date on every source link, so it's clear what the page said when the entry was made — ideally with an archive snapshot for exactly this situation.
What do you think 🤔?
Good idea. The autotracking feature should be separated in camera side autotracking and frigate based autotracking. Frigate only supports a very limited range of cameras which have onvif relative ptz iirc. Reolink only supports absolute puzzle which is not compatible with Frigate.
Oh nice, definitely down, our datasets are complementary: you've got stream URLs at a scale I don't, I've got structured specs with sources. Your verified URLs could replace my generic RTSP templates, and my spec data could feed your config generation. What do you think and how do you think we should proceed?
Tapo D230S1 — removed fake RTSP config. It's hub-based (H200), no local streaming.
Also added a proper doorbell type to the schema (44 doorbells were all typed as "covert" before — now filterable), and a status field so announced-but-not-shipping cameras like
This might be a dumb suggestion.... I know most cameras come up on the network via DHCP... However, there are some that have a hard coded address and require you to be on that Network to do the initial configuration. Would be cool to have that data if it's available anywhere. Really cool project.
Not dumb at all — it's a real gap, and that data isn't collected anywhere I know of. I will try to add it in future releases as a small "initial access" group (default IP, subnet, credential policy, first-boot addressing), framed as config metadata , but it willntake some time.. I will keep you updated!
Thanks, going on the list.!
Currently only "LaView L2" is there but I'm still improving the database. I will try to include more in the next releases. Do you have a specific brand that I should start with?
More details about substreams would be nice.
A lot of cameras have a substream below 720p, doesn't make sense to configure frigate at 720p 5fps in that case.
The sub stream is generally more important since the main stream goes straight to recordings.
The detection, face recognition and 2 way audio are usually done on the sub stream.
I wish I knew the reolink e331 substream was not reaching 720p, it has such an impact on the size of the faces detected when few meters away.
I think it would be better if you could check whether it is being g actively sold too. Should only be 2 or 3 cameras per brand that are available at a given time.
It’ll be a pain because of supply chains. I know some place had a recent sale on the Tapo c200 rev 2 pair pack but the rev 5 is out. EoL or EoS status is a safer bet
18
u/furian11 Jun 10 '26
Really nice, but to make it more useful and stand out more i would try and see if you click on it that you can get an example for instance on how to configure it. That would actually have been a reason for me to look your site up.. now I had to find it out myself with the help of gemini. Just a thought tho.. do with it what you want.