Frigate / Wyze / go2rtc / Thingino
and the adventures in stream stability...

My current project (as of Dec 24 ->) in creating the platform for local camera storage without the use of the internet. We currently use Wyze cams and they have been generally fine but constantly uploading to the internet and with privacy being a higher priority I have decided to move them all locally to Frigate. I've used the Wyze v2 and v3's as test cameras to get my NVR system stable with the plan of upgrading to higher quality dome cameras in the future.
At the time of writing im using versions:
Frigate: 0.14.1
go2rtc: 1.9.8 (Frigate 0.14.1 uses version 1.9.7)
Thingino: 2025-01-16 (Wyze v3's)
Wyze v3 substream video stopping
The bane of my existance has been diagnosing issues with the video streams stopping at random times. Whjat I found out in the end was if I stop the substream completely and just use the main stream then everything continues to work. I've also set the RTSP streaming audio protocol to AAC 16k.
Note:
The substream on the v2 worked fine but I just decided not to use that either.
Also, if Thingino is running and go2rtc is not accessing it then it's stable and does not crash.
Update 16/Jan/25:
- Upgrading to later versions makes it slightly more stable.
- Will test changing the power adapaters around on the Wyze Cams
Kernel updates causing Google Coral to Fail
After a reboot today Frigate was not working. I found that the Apex (Google Coral) device was failing and as I needed to reinstall its drivers and reboot the node.
dpkg -i gasket-dkms_1.0-18_all.deb
When orignally installed I somewhat followed the instructions here: https://forum.proxmox.com/threads/pcie-google-coral-install-instructions.143187/
The real way to avoid is to pin the Kernel so this doesn't happen without manual kernel change.