HA cameras switch OFF motion + recordings constantly with 2024.5.0 upgrade

[richardfoley]

The problem

Using Frigate with HA to manage a couple of home security systems. They both have almost identical setups and work really well together. With the last update of HA to 2024.5.0 (from 2024.4.4) both systems cameras refuse to leave "motion" and "recordings" switched ON. If I switch them on via the frontend, while the camera remains on, the motion and recordings switches immediately flick back to OFF.
This is constant. I've tried removing the retained flag from the MQTT broker/explorer, as suggested in an older/similar thread. I've restarted Frigate, HA, the box itself. Nada.

Anecdotally, I noticed from the "Settings->Devices->Frigate->Device" window, that when manually switching the options in the Configuration panel, a new entry appeared, or not, in the Logbook panel. eg;

May 3, 2024 Camera-Name Recordings turned on triggered by service Switch: Turn on 9:03:29 AM - 2 seconds ago
In the working version 2024.4.4 the LogBook showed a new switch service item as above.
In the faulty version 2024.5.0 the LogBook did not show any new switch service item.

It seemed this might be a Frigate issue, until it dawned on me that the only thing I'd changed recently was the regular HA upgrade. I finally restored HA-only from a backup to the previous version on both systems, and all cameras are working exactly as expected, and as they used to. With HA-2024.4.4 I do see the switch entry in the LogBook and the switches control the cameras correctly again, on both systems.

Working version:
HA Core 2024.4.4
Supervisor 2024.04.4
Operating System 12.2
Frontend 20240404.2
Frigate 0.13.2
MQTT broker 6.4.0

Fault version:
HA Core 2024.5.0

Faulty version is upgrade to Core 2024.5.0 only, although I think this upgraded the Frontend to 20240501 too (am not sure of the Frontend version but it's tied to, and came with, Core 2024.5.0). As the bug seems to manifest itself via the frontend switches apparently not sending the command to the backend, perhaps it's the frontend?

I hope this information helps someone to fix this usually excellent piece of software.

What version of Home Assistant Core has the issue?

2024.5.0

What was the last working version of Home Assistant Core?

2024.4.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

HomeAssistant/MQTT/Frigate

[JohannCR]

Also seeing this. Any workaround to make the motion switches work ?

[richardfoley]

I think the Frigate github has (possibly) identified an issue with the integration, and are looking into it, in this topic here.

[bdraco]

This looks like a race in the frigate integration. 2024.5.x is a bit faster so its expected that any race bugs in integrations will be more obvious.

This isn't something we can solve in core. It needs to be solved in the custom component.

[sgurgul]

I experienced this problem as well. It seems to be solved in today released Frigate integration update (v5.2.0)