Replies: 1 comment 1 reply
-
I get the "Unable to read frames" problem as well but only from my wifi connected v3. If you're interested in reliable connection, the best option I took was to use "USB CDC_NCM" support from wz_mini_hacks and make the v3s all communicate via usb (wifi is no longer used). In my situation, I have a rpi4 connected to 1 or 2 of these v3. You have to be familar with setting up peer to peer networks since USB CDC_NCM makes the rpi4 see the v3's as tcp peer networking clients. rpi4 seems to run frigate fine but I've put one of them under heavy strain/load and it's overheating now and not running reliably. Another one I setup has been running fine so far (although less motion is triggered which lowers frigate cpu use). If you use a N100 mini pc I believe the setup will be fine. I have had to power cycle once or twice a year on my wifi connected one when it looses connectivity. On some occasions when the v3 doesn't respond, I have to re-flash wz_mini_hacks onto the v3. |
Beta Was this translation helpful? Give feedback.
-
I am wondering if most people find using wz_mini_hacks find it to be pretty reliable. Right now I have 4 wyze v2's using docker wyze bridge sending rtsp to Frigate. For the most part they work pretty good, I do occasionally get camera's loose connectivity and have to power cycle cams to get stream back up. Also I see a lot of "Unable to read frames from ffmpeg process" in the logs of Frigate. Wondering if I would be better to give wz_mini_hacks a go.
One other question for anyone, do most people self-host their wyze cams?
Thnanks
Beta Was this translation helpful? Give feedback.
All reactions