Closed clehmann closed 1 month ago
Thanks. I am looking at the file now.
I created a new build to debug the camera issue. I'm releasing it just to you. When I ran your config, it works as expected on my system and in Viewu. So, I'm hoping the new logging feature will give better insight as to what is happening. Toggle on DeveloperMode and return back to the TimeLine. From there, click on the Log menu button. Ideally, this should show an error log for ContentView. Please copy and paste the errors to here or take a screenshot.
I'm fairly certain I found the issue. Frigate config has a different value type in 0.14 than it does in 0.13 for min_initialized which in 0.14 is an Optional(Int). But in 0.13, this is returned as a Double/Float. To make this work with both version, I am removing this from the viewu app - as it's a read only field in viewu. I expect there could be more values like this to look out for in the future.
Build 29 resolves this issue by remove min_initialized from the app to accommodate people using both frigate 0.13 and 0.14.
I had the same problem, it was due to me having audio filters my config. If I comment the filters block the error disappears and cameras show normally. Having audio, whether on or off, throws the error and no cameras show...
audio:
enabled: True
max_not_heard: 30
# - 200 - high sensitivity - 500 - medium sensitivity - 1000 - low sensitivity
min_volume: 500
listen:
- bark
- fire_alarm
- scream
- speech
- yell
# Optional: Filters to configure detection.
filters:
# Label that matches label in listen config.
speech:
# Minimum score that triggers an audio event (default: shown below)
threshold: 0.8
Running the viewu server as a docker image vai compose on the same host as frigate.
Docker daemon is forwarding port 5099 to frigate
The timeline works, but nothing shows up when I go to the 'cameras' tab
Compose definition as follows:
Frigate config as follows: