OpenIPC: Open IP Camera Firmware

Original Article ↗ Hacker News Discussion ↗

Motivation: Cloud-Tied, Locked-Down IP Cameras

  • Many complain that mainstream “smart” cams (TP-Link Tapo, generic cloud cams) require permanent internet and vendor cloud to function or even to record, despite having SD cards.
  • Others report Tapo can run offline as RTSP-only on an isolated subnet, but still needs internet for initial setup and is seen as overly cloud-centric.

Hardware Support and SoC vs Device Mapping

  • OpenIPC’s public list is SoC-focused, not product-focused, making it hard to know which retail cameras are compatible before buying.
  • Several users say it’s especially difficult in the US to map cheap Amazon cameras to supported SoCs without disassembling them.

OpenIPC vs Thingino and Degree of Openness

  • One side claims OpenIPC isn’t fully open because its main streamer/encoder (Majestic) is closed; many devs reportedly moved to Thingino, which is fully open in that part.
  • OpenIPC contributors counter that OpenIPC is “as open as possible” and can use open streamers like Divinus alongside vendor blobs where necessary.
  • Thingino focuses on Ingenic MIPS SoCs (Xburst), with per-device firmware, aiming for reliability and easier setup vs “generic” OpenIPC configs.

Cheap Supported Cameras and Installation Experience

  • Thingino provides explicit lists with product photos; supports many low-cost Amazon brands (e.g., Wansview, Imou, Cinnado, Wyze, some TP-Link/Wyze/Eufy models).
  • Users share specific sub-$20 models that work and report successful flashes, often via SD-card-based “easy installers” rather than soldering, though some devices still need UART/flash programmers.
  • There is discussion about a potential business of selling pre-flashed “open” cams; some see value, others doubt margins given easy DIY flashing and heavy vendor subsidies of closed cams.

Integration with NVRs and Local Networks

  • OpenIPC/Thingino expose RTSP/ONVIF and work with open NVRs like Frigate, Shinobi, ZoneMinder; some mention two-way audio and PTZ working via ONVIF backchannel.
  • Many run cameras on isolated VLANs with no internet, only allowing NVR access, to reduce compromise and data exfiltration risk.

PoE, High-End, and Brand Landscape

  • Strong interest in PoE outdoor and PTZ cams with open firmware; Thingino currently mostly supports cheaper Wi-Fi devices, with PoE still rare.
  • Several recommend closed but robust brands (Axis, Hanwha, Hikvision, Dahua, Reolink, Amcrest, Foscam) for reliability and ONVIF support, often paired with VLAN isolation.
  • Some highlight a gap: open firmware currently targets lower-end 2–4 MP devices, while mainstream vendors have long offered 4K@25fps+; Thingino notes 4K Ingenic-based support is “coming” but not here yet.

Security, Ethics, and Privacy Concerns

  • Beyond technical risk, some object morally to buying from certain Chinese OEMs linked to state surveillance and repression, even if VLANs mitigate personal spying risk.
  • Others emphasize that no third party (especially clouds) should be trusted with raw video data; local storage and processing are preferred.

Licensing and Low-Level Technical Issues

  • There is debate over OpenIPC’s licensing: code labeled MIT but website text “asks” commercial users to contact them; some see this as conflicting with MIT, others say it’s just a request.
  • A commenter notes cheap SoC vendors don’t implement standard V4L2, each ships proprietary kernel drivers and middleware, increasing porting complexity.
  • Discussion touches on small RAM sizes (32–128 MB), heavy reliance on hardware encode blocks, and why these devices still run Linux rather than an RTOS.

Related and DIY Alternatives

  • Mention of related open firmware projects (Thingino, Openmiko for Wyze v2, Wyrecam for HomeKit on Wyze v3).
  • Some users bypass IP cams entirely with Raspberry Pi + Motion + scripts, or use commercial but locally usable RTSP/CGI-based cams as a “good enough” compromise.