bennyb0i

Hey @georgejung, this sounds really cool and intuitive. I, too, have been considering to use Frigate to manage my Arlo object detections since it works so well with my IP...

Interesting. Thanks for that info. I'm using Arlo Pro & Pro2 as well which sound like they work great with this solution, though it was a shame to find that...

> Can I ask what kind of cameras you have? 0.7.1.7 -> 0.7.1.8 contained a polling change. > > edit: you have pro1 and pro2. Nothing in 0.7.1.8 should have...

@georgejung, do you get errors in the Frigate log regarding `ffmpeg` unexpectedly crashing? I assume this is due to having no more video to process so `ffmpeg` terminates after the...

Thanks for the detailed reply! Unfortunately I still think my log errors are a direct result of the mp4 stream ending and ffmpeg terminating. I removed the stream and camera...

I actually did try looping a test clip before without much success though I didn't check if the crash error was eliminated as another issue popped up. Both in the...

Yep, I actually discovered earlier that 'camera.record' does indeed work, thanks! Though, sadly it doesn't look like it's going to be a viable solution since it takes at least several...

Agreed, it's a bit awkward only being able to show the current temperature and not being able to instead display the temperature setpoint. Would be great to see the temperature...

Hey there, I'm also curious about getting DOODS2 to work with MQTT. I've configured my mqtt broker in the config.yaml and copied it to the DOODS2 docker container, confirming that...

Thanks, I started a new docker container using docker run and the mqtt flag you mentioned, but now I'm getting an error in the log that says: `[tcp @ ox7f6e540039c0]...