u/CantaloupeHeavy996

Hi all,

A while ago I shared here (https://www.reddit.com/r/homeassistant/comments/1u2bpvr/tired\_of\_digging\_through\_scattered\_vendor\_pdfs/) my open CC0 database of IP cameras with ready-to-copy configs.

https://preview.redd.it/p11hrf6ablkh1.png?width=1228&format=png&auto=webp&s=5e64b62789b29b6b839305f4e8021cc2ec64db67

The feedback was genuinely useful. Biggest gap people pointed out: knowing a camera "supports RTSP" doesn't tell you the actual path to type into Frigate.

Now I've fixed that, with help from some folks in the open source community.

Every camera now has:

• Actual RTSP URL structure (brand-level default + per-camera override where the manufacturer documents a different path)
• ONVIF port and profile info where documented
• Ready-to-copy Frigate config block per camera

All still sourced only from official datasheets and the data is always open source.

It would be great if you're up for a small contribution: pull up your camera, copy the config, and mark whether it worked. Happy to take feature requests / roasting in the comments too.

Direct link to the Frigate configs: cctv-database.com/frigate-configs

3,400+ cameras, 70+ brands now.

Browse: https://cctv-database.com
Repo: https://github.com/ch-bas/cctv-camera-database

Thanks!

Hi all,

A while ago I shared here (https://www.reddit.com/r/frigate_nvr/comments/1u2ezeb/built_an_open_database_of_1000_camera_specs_to/) my open CC0 database of IP cameras with ready-to-copy Frigate configs.

https://preview.redd.it/bg69v9jp4lkh1.png?width=2044&format=png&auto=webp&s=a71811d44082ad8975516f0ac431cb0d5e57ede3

The feedback was genuinely useful. Biggest gap people pointed out: knowing a camera "supports RTSP" doesn't tell you the actual path to type into Frigate.

Now I've fixed that, with help from some folks in the open source community.

Every camera now has:

• Actual RTSP URL structure (brand-level default + per-camera override where the manufacturer documents a different path)
• ONVIF port and profile info where documented
• Ready-to-copy Frigate config block per camera

All still sourced only from official datasheets and the data is always open source.

It would be great if you're up for a small contribution: pull up your camera, copy the config, and mark whether it worked. Happy to take feature requests / roasting in the comments too.

Direct link to the Frigate configs: cctv-database.com/frigate-configs

3,400+ cameras, 70+ brands now.

Browse: https://cctv-database.com
Repo: https://github.com/ch-bas/cctv-camera-database

Thanks!

https://preview.redd.it/h6tygllq7i6h1.png?width=2894&format=png&auto=webp&s=3816bf630e8d54f5225575a13950df45337d535b

Hey everyone,

Every time I needed to expand my Home Assistant setup or configure an NVR like Frigate, I hit the same wall. Checking for true ONVIF support, sub-stream resolutions, PoE vs. WiFi, or physical IP ratings meant opening 15 different tabs of scattered retailer specs and vendor PDFs.

To fix this, I compiled a fully queryable database (JSON + CSV) covering 50+ major brands (Hikvision, Dahua, Reolink, Axis, Amcrest, Tapo, UniFi, Ubiquiti, etc.).

What's inside for smart home builders:

• Local Control Check: True ONVIF / RTSP protocol support flag.
• Power & Connection: PoE / WiFi / Battery / 4G filters.
• Hardware Specs: Resolution, sensor size, lens, night vision range.
• Enclosure: IP (weather) and IK (vandal) ratings.
• Audio: Two-way audio support.
• Availability: Regional market tags (handy for filtering what you can actually buy in the US vs. EU/UK).

It's 100% Free, CC0 (Public Domain), no accounts, and no subscriptions. Just clean data to help you pick the right local hardware.

• Browse the web UI: https://ch-bas.github.io/cctv-camera-database/
• GitHub Repo: https://github.com/ch-bas/cctv-camera-database

If you notice a camera model missing from your own setup, there's a simple GitHub issue form to submit it—no git cloning or coding required. Hopefully, this saves you some tab-clutter on your next hardware upgrade!

I released an open dataset of IP/CCTV camera specifications under CC0 (public domain).

The problem it solves: camera specs are scattered across vendor PDFs, inconsistent retailer listings, and paywalled databases. There was no single structured open source to query from.

What's in it:

- 1,000 cameras across 49 brands (Hikvision, Dahua, Reolink, Axis, Hanwha, Tapo, Ubiquiti, and more)

- One JSON file per camera under cameras/<brand>/<model>.json, aggregated into data/cameras.json + CSV

- Fields: resolution, sensor, lens, connectivity (PoE/WiFi/battery/4G), night vision type and range, IP rating, ONVIF/RTSP support, audio, storage, price, market tags

- Schema validated on every PR via GitHub Actions

- CC0 — no attribution required, do whatever you want with it

Contributing:

Non-devs can submit cameras via a GitHub issue form (no cloning needed). Developers can use an interactive CLI wizard (npm run add) that writes the JSON file without needing to know the schema.

Browse it: https://ch-bas.github.io/cctv-camera-database/

Repo: https://github.com/ch-bas/cctv-camera-database

Built with Claude Code — specs sourced from manufacturer datasheets, each entry cites its source URL.

Hey everyone,

I wanted to share a project I've been working on to level up my 3D web development skills. It's a fully client-side, grid-based house builder (think The Sims build mode) with 0 external 3D models—everything is procedurally generated geometry.

Some of the architecture under the hood:

• State Management: Powered by a pure useReducer with ~30 action types and an assertNever exhaustiveness guard for complete type safety.
• Performance: Three.js is dynamically imported so it doesn't bloat the initial page load.
• Component Structure: React Context handles global state to avoid drilling props through 33 different UI panels.
• Testing: Because the reducer is 100% pure (zero React imports), testing the core game logic is incredibly straightforward.
• Data Persistence: Old single-floor layouts saved in localStorage automatically migrate to the new multi-floor format on load.

It's entirely open-source (MIT licensed) and statically hosted on GitHub Pages. I’d love to hear your thoughts on the state management architecture or the procedural generation approach!