Asked: Find new Reolink PoE cam (replacing slot of unplugged floodlight on same injector) and add to Frigate.
Found: New cam initially grabbed 192.168.86.76, then per Reolink app it's at 192.168.86.80. No TCP ports open on either IP — RTSP/ONVIF disabled in firmware default.
Decided: Justin must enable RTSP+ONVIF in Reolink app (Settings → Network → Advanced → Port). Need cam model + final IP.
Next: Once RTSP up, reserve DHCP lease, bump CT 108 RAM 4→6 GB, add cameras.side_door block to /opt/frigate/config/config.yml, restart frigate.
Last: Status so far: - Existing cam at 192.168.86.76 is alive (just slow to ARP — high-latency replies, normal for Reolink). - Only Reolink-OUI hit on the LAN was 192.168.86.47 (ec:71:db), but it has…
Last: Solved the mystery — and there's good news. The new cam grabbed 192.168.86.76 (same IP as the old one). That's why Frigate's logs are showing "Connection refused" on `rtsp://[email protected]:5…
Last: No RTSP (port 554) is open anywhere on the LAN. Likely cause: recent Reolink firmware ships with RTSP disabled by default for security. It needs to be enabled manually before Frigate can pull a st…
Last:.80 also has no TCP ports open — same story. RTSP/ONVIF is still disabled on the cam; that's what's blocking everything. In the Reolink app: 1. Tap the side-door cam → ⚙️ → Network → **…
Last: Uptime is ~135.9 hours (489119 seconds / 3600). That's well over 26 hours. ##SUMMARY## NO REBOOT, no verdict needed (uptime: ~135.9h) -- Finn has not rebooted since the last check; rclone-gdrive hard…