@NickM-27 commented on GitHub (Nov 20, 2023):
It's not clear to me what you're asking, but I'd suggest reading the FAQ https://deploy-preview-6262--frigate-docs.netlify.app/plus/#frequently-asked-…
@ivlis commented on GitHub (Nov 20, 2023):
Hmm, but what means the breaking change is not breaking change if I configure the db location, correct?
@NickM-27 commented on GitHub (Nov 20, 2023):
I would suggest defining a detect resolution for the stream
@kiloptero commented on GitHub (Nov 20, 2023):
yes , i read that. the question if this frigate + include new objects ?
@NickM-27 commented on GitHub (Nov 20, 2023):
the change is only for the default location, if you manually configure a db location then frigate will use that instead
@NickM-27 commented on GitHub (Nov 20, 2023):
Frigate has supported configuring the DB path for many versions
@Dibblah1 commented on GitHub (Nov 22, 2023):
I don't have logs prior to the change, but I have seen this symptom (with 0.13 beta) prior to changing the cameras from h.265 to h.264.
No other…
@NickM-27 commented on GitHub (Nov 22, 2023):
The problem here is something when frigate tries to get the time in the local timezone causing the video and recordings threads to crash.
@NickM-27 commented on GitHub (Nov 22, 2023):
We will need to catch this and potentially put a warning.
@doug62 commented on GitHub (Nov 22, 2023):
For the TimeZone - that section should be wrapped in a non fatal exception that produces a log entry.
I followed the directions on: https://docs.frig…
@NickM-27 commented on GitHub (Nov 22, 2023):
It might need to be surrounded by quotes or something, not sure why it wouldn't work.
@pos-ei-don commented on GitHub (Nov 22, 2023):
See #8636
@doug62 commented on GitHub (Nov 22, 2023):
OH DEAR LORD! I have: America/Chicaco Should have been America/Chicago
@NickM-27 commented on GitHub (Nov 22, 2023):
Regardless we will need to catch that exception, we can use #8636 to cover that