Closed skywurz closed 1 year ago
From what I can see if your log you are just connecting before it is ready. Originally I planned to not let the stream be visible before it was ready and it would return a 404 however an early tester found that BI would not retry a stream if a 404 was returned. So instead an invalid stream is now created. This means that at the beginning before the stream is ready you will get these errors.
What happens after you get the "Avaliable at" message?
I'll add back in the splash screen instead then you will get the "Stream Not Ready" static instead of an invalid
Ok splash screen is back let me know if that keeps your errors quite by trying out 0.6.2
Sorry for the late reply. I saw your first comment and tried delaying connection etc but could never get the all streams to connect.
0.6.2 solved my issue
I installed 0.6.2 and all cameras load into my nvr within seconds .
Thank you so much for your work on this project and fixing this issue!!!
Describe the bug After upgrading to 0.6.x connecting via go2rtc does not work so well
To Reproduce Steps to reproduce the behavior. Example:
Expected behavior Camera streams to load
Versions NVR software: Frigate Neolink software: 0.6.1 Reolink camera model and firmware: Reolink Lumus Firmware Version v2.0.0.705_21052800
Neolink Logs