Are these errors normal in Frigate? And how is camera battery getting depleted?

[quantumentangledandy]

Are these errors normal in Frigate? And how is camera battery getting depleted?

[QuantumEntangledAndy]

Ok lots of questions but I'll try and answer:

| Are these errors from Frigate expected?

Depends, if that is at the start before the buffers are prepared then yes. There is a period after startup of neolink before we connect and get enough frames to work out the stream format that will cause issues in frigate.

| I got the idea that you implemented fake frames to be presented by neolink, so that when the camera stream was paused, clients connected to it would not have issues and the stream would show the last captured frame

This is a difficult one. I tried a couple of different approaches and it's not possible to just make up new fake frames without doing a decode and encode of the video. Instead what we do is keep the last few seconds of video. When a new client appears we send them this video so that the client can workout the format/size to display then we just stop sending frames. Some clients will drop the stream if there are no new frames while others will wait. If you want to wait for frames you will have to configure your client

| Also, given the configuration for my battery camera, if no detection is triggered, the camera stream is paused. But the camera battery gotten to very low values

Pausing is not a true pause. We stop pulling video frames which reduces the battery load BUT we don't fully disconnect, as we need to stay connected to listen to motion requests.

There is on-going work to listen to the push notifications instead then logout but its not done yet.

| What should be the optimal configuration for both camera and neolink?

Given config is fine, not much else that can be done to imporve battery until the push notification feature is in

Anything else you want to discuss?