The issue of IPC-E541F-E2-AS working together with Frigate NVR

EMPIRETECANDY

IPCT Vendor
Nov 8, 2016
9,782
28,861
HONGKONG
Hey guys

We met a request for how to make the camera working with the Frigate NVR, any idea/suggestion would be appreciated!

Camera model: IPC-E541F-E2-AS (dual-lens, 2x4MP)

Firmware: V2.840.0000000.30 (released Feb 27, 2025) — confirmed up to date as of this report
NVR software: Frigate NVR (Docker, Unraid host)
Network: Both lenses on the same LAN as 11 other IP cameras (various single-lens models), all confirmed stable independently
ISSUE SUMMARY: When both lenses (channel=1 and channel=2) of this camera are actively streaming to our NVR at the same time, EVERY OTHER CAMERA on the network — not just this one — stops writing new recording segments simultaneously and has to be restarted. This happens whether the two lenses connect via a restreaming proxy (go2rtc) or via direct independent RTSP connections straight to the camera. The moment both lenses are disabled, all other cameras remain stable indefinitely (8+ hours tested with zero issues).

TROUBLESHOOTING ALREADY COMPLETED:
  • Confirmed both streams are set to H.264 (not H.265)
  • Confirmed camera's "max users" setting is 10, well above the 2 concurrent sessions being used
  • Ruled out storage/disk space (recording storage confirmed to have ample free space during failures)
  • Ruled out shared memory / cache exhaustion (tmpfs cache confirmed near-empty during failures)
  • Ruled out CPU/GPU resource exhaustion (both under 15% utilization during failures)
  • Ruled out network-level causes on our end (no relevant errors in host system/kernel logs at time of failures)
  • Tested with recording routed through a restreaming proxy (go2rtc) — failures occurred
  • Tested with recording connected DIRECTLY to the camera via independent RTSP sessions per channel (bypassing any proxy) — failures still occurred
  • Updated to latest available firmware (V2.840.0000000.30) — issue persists
  • Confirmed this is reproducible: disabling both lenses immediately and reliably stops the issue; re-enabling both reliably reproduces it within minutes

TECHNICAL DETAIL: Our NVR logs show a "wrong response on DESCRIBE" / "start from CONN state" error specifically tied to this camera's RTSP endpoints when both channels are queried concurrently. This appears to be a known issue — we found another user reporting the same symptom with this exact camera model in a public Frigate NVR support forum (GitHub discussion #21506), also involving DESCRIBE failures when both channels are active concurrently.
REQUEST: Please advise whether this is a known firmware issue with concurrent dual-channel RTSP sessions, and whether a fix or updated firmware is planned. We are currently unable to use both lenses of this camera simultaneously without disrupting our entire camera network, which leaves us with three of these unusable cameras that we just purchased last week. Happy to provide full logs, camera configuration screenshots, or further diagnostic detail on request.