Asked: Debug Frigate not seeing Reolink floodlight camera (HA could see it). Then verify 3-layer camera setup (HA for live view, Reolink SD for local, Frigate for long-term).
Found: RTSP streams were fine, camera had been disabled in Frigate UI. Re-enabled fixed it. Verified all 3 layers working: HA sees all cameras, Frigate recording motion 14d + events 30d to 7.3TB NVMe.
Next: SD card recording should be confirmed in Reolink app. May add 2 more Reolink cameras to Frigate.
Asked: Add Proxmox CPU/RAM usage to Home Assistant dashboard
Found: No Proxmox integration in HA yet. API tokens recommended (bypasses 2FA). HA says "cannot connect", confirmed port 8006 is reachable from UDev (401 = working). Likely SSL verify issue in HA integration setup.
Next: Retry adding Proxmox VE integration in HA with "Verify SSL" unchecked. Then set up dashboard cards.
Asked: Fix unavailable Frigate sensors in HA + add Frigate card to dashboard
Done: Enabled MQTT in Frigate config (pointing to Mosquitto on HA at 192.168.86.70:1883), restarted Frigate. All sensors now live (car/person/dog/cat counts, occupancy, motion, detect switches). Added Advanced Camera Card for front_floodlight to Security Cameras section on Home dashboard.
Next: Frigate card should now show full timeline scrubbing, event clips, and detection snapshots. 2 more Reolink cameras still pending.
Asked: Reorder Frigate card to top, unhide Media Browser in sidebar, fix card expand/fullscreen, add more object types (truck/bus/motorcycle/bicycle/bird), remove Reolink driveway cam from home view.
Done: All changes applied. Frigate now tracks 9 object types. Security Cameras section has Frigate card + doorbell only. Media Browser visible in sidebar.
Next: Face recognition setup on Frigate 0.17.1 still available. 2 more Reolink cameras pending install.
Asked: How much power is Finn pulling? Is it bad? Can we do a low-power night mode?
Found: Finn idles at ~48-50W, currently ~91W with Frigate active (35% CPU for CPU-based detection). ~$5-7/mo estimated. Very efficient for an MS-01.
Decided: Let Frigate run a week to get real power data with it active. 3 cameras on CPU detection would push 90-110W: Coral TPU ($25-35) recommended before adding 2 more cameras.
Next: Review power data after a week. Consider Coral TPU for detection offload.
Asked: Can we get Finn down to 40W? Also realized SFP+ (vmbr1/nic3) is used for desktop editing, restored it. Concerned about CPU governor/turbo hurting performance.
Done: Restored turbo boost + performance governor + SFP link. Disabled WiFi + nic1 (unused). OpenVINO remains the big win (~15W saved). CPU tuning traded ~$1.50/mo for real performance loss, not worth it.
Decided: ~70W is the right number for Finn's workload. No further power tuning needed.
Asked: Add Proxmox CPU/RAM per-VM indicators to HA dashboard
Done: Created hamonitor@pam (no 2FA, PVEAuditor). Nginx reverse proxy on UDev:8006→Finn:8006 (bridge hairpin workaround). Connected HA Proxmox VE integration. Added Finn gauges + condensed per-VM glance cards (8 VMs/CTs) to Home dashboard.
Next: Justin reviewing layout, may want further styling tweaks.