Audio detect and recording shows incorrect information after MQTT restart

[JuanDYB]

Version of the custom_component

5.4.0

Configuration

mqtt:
  enabled: true
  host: mosquitto_mqtt
  user: frigate_usr
  password: xxxxxxxxxx

review:
  alerts:
    labels:
      - cat
      - dog
      - person
      - speech
detect:
  enabled: true

audio:
  enabled: true
  listen:
    - bark
    - fire_alarm
    - scream
    - speech
    - yell

record:
  enabled: true
  retain:
    days: 3
    mode: motion
  events:
    retain:
      default: 30
      mode: motion

snapshots:
  enabled: true
  timestamp: true
  retain:
    default: 10
    objects:
      person: 15

go2rtc:
  streams:
    e1zoom:
      - ffmpeg:http://ip/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=usr&password=pass#video=copy#audio=copy#audio=aac
    e1zoom_sub:
      - ffmpeg:http://ip/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=usr&password=pass

cameras:
  e1zoom:
    enabled: true
    onvif:
      host: ip
      port: 8000
      user: usr
      password: pass
      autotracking:
        enabled: false
        return_preset: home
        timeout: 60
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/e1zoom
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/e1zoom_sub
          input_args: preset-rtsp-restream
          roles:
            - detect
            - audio
      output_args:
        record: preset-record-generic-audio-copy
version: 0.14

Describe the bug

After mosquitto MQTT server is restarted the Home Assistant integration shows incorrect state of audio detection and recording.

Could be related to this issue? #662

Debug log

N/A

[NickM-27]

actually, this is an issue where the frontend shows the wrong state and that bug was fixed in 0.14.1

[JuanDYB]

Thanks for your comment! I'll wait until 0.14.1 will be in the stable docker tag.

[NickM-27]

it already is https://github.com/blakeblackshear/frigate/pkgs/container/frigate/264807004?tag=0.14.1

[JuanDYB]

I have updated to tag 0.14.1 and it is still with same error. maybe it's not the same bug. Mine error is reproduced after restarting MQTT server, not after restarting frigate or HA.
With regards,

[NickM-27]

I see, well that would be a frigate issue not an integration issue since the integration can only go off of what is in the integration

[JuanDYB]

Ok, I'll open the isuue on frigate project. Thanks!