Closed Sprk-nl closed 7 months ago
Same issue: Using a Frigate server (http://192.168.1.15:5001/) with version 0.12.1-367d724 <= 0.12.1 which is not compatible -- you must upgrade: https://github.com/blakeblackshear/frigate/releases 1:30:47 PM – (ERROR) Frigate (custom integration) - message first occurred at 11:20:41 AM and shows up 8 times
You need to pull a new image in a docker and then recreate a docker docker pull ghcr.io/blakeblackshear/frigate:stable docker compose up -d frigate
And then reload the integration. Now it works
you need to upgrade your frigate like the logs say
@NickM-27 "<=" means less than or equal to. 0.12.1-xx == 0.12.1.
@kwatkins yes, meaning your frigate version is less than or equal to 0.12.1 which is not compatible
wow, ok long day. you are right.
Release notes should be read before updating. HACS even includes the release notes when there is an update available and the fact that frigate 0.13 is needed is the first thing in the release notes.
there is no mechanism other than logs for a custom integration to communicate the problem to the user. The logs are enabled by default and explain that an upgrade is needed. Closing this as I don't see a way this could be improved.
Is your feature request related to a problem? Please describe. After working in Home Assistant, upgrading plugins, mostly it's noticed days later something is broken. In this case The Frigate Home Assistant plugin was upgraded, and Frigate was not, for just a few days. The integration and reconnecting of an already configured instance broke without a clear reason.
Describe the solution you'd like Feedback from Home Assistant integration plugin what the cause is of not able to connect to an already configured Frigate server. As the Frigate server could explain clearly an upgrade was required, the Home Assistant plugin could not. From my perspective there could be a two part API set-up. One for the current integration, one for supervising/feedback in-case a mismatch happens between the integration.
Describe alternatives you've considered Enable debugging of Frigate logs, and checking the logging on the Frigate server to find out the following: Using a Frigate server (http://192.168.1.37:5000) with version 0.12.1-367d724 <= 0.12.1 which is not compatible -- you must upgrade
Additional context None