@hawkeye217 commented on GitHub (Sep 22, 2023):
@gotschi, @NickM-27's PR should solve this issue. Thanks for the bug report.
@NickM-27 commented on GitHub (Sep 22, 2023):
@hawkeye217 just put up a PR for this
@github-actions[bot] commented on GitHub (Oct 23, 2023):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.…
@hawkeye217 commented on GitHub (Sep 22, 2023):
Are there any more errors in the logs?
@J-Smits commented on GitHub (Sep 22, 2023):
Problem solved already, default the container is using NAT, i added a second adapter to the container as brige using a free static IP adress, and when…
@leaskovski commented on GitHub (Sep 21, 2023):
I am wondering if it is something to do with the change in paths to the DB between versions...
you are manually setting the path to…
@divemasterjm commented on GitHub (Sep 21, 2023):
Then most likely it was two different objects that were detected. You can get the MQTT payloads from the automation trace in HA ui
if i…
@LeDuySon commented on GitHub (Sep 21, 2023):
Oh great, i will have a look at that. Thank you so much @NickM-27
@NickM-27 commented on GitHub (Sep 21, 2023):
I'd suggest reading https://github.com/blakeblackshear/frigate/discussions/7850
@github-actions[bot] commented on GitHub (Oct 22, 2023):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.…
@leaskovski commented on GitHub (Sep 21, 2023):
It does look like it is the CPU that has gone through the roof since the upgrade... :
Different things can happen each time, it's best to use the traces to understand what exactly happened and change the automation.
@github-actions[bot] commented on GitHub (Oct 22, 2023):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.…