[Bug]: "Unable to publish to model_state: client is not connected" briefly on startup

[leccelecce]

Checklist

• I have updated to the latest available Frigate version.
• I have cleared the cache of my browser.
• I have tried a different browser to see if it is related to my browser.
• I have tried reproducing the issue in incognito mode to rule out problems with any third party extensions or plugins I have installed.

Describe the problem you are having

See logs - these messages reliably appear on every startup in 0.15

Unable to publish to model_state: client is not connected

Seems like something is just trying to publish early on before MQTT connection has occurred, presumably harmless but creates a bit of noise.

Steps to reproduce

n/a

Version

0.15.0-4ff0c8a

In which browser(s) are you experiencing the issue with?

No response

Frigate config file

n/a

docker-compose file or Docker CLI command

n/a

Relevant Frigate log output

2024-10-25 10:55:13.425065274  [INFO] Preparing Frigate...
2024-10-25 10:55:13.434955328  [INFO] Starting Frigate...
2024-10-25 10:55:17.302236595  [2024-10-25 10:55:17] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-10-25 10:55:17.496188004  [2024-10-25 10:55:17] frigate.util.config            INFO    : frigate config does not need migration...
2024-10-25 10:55:17.666292310  [rtsp @ 0x5626680] method DESCRIBE failed: 404 Not Found
2024-10-25 10:55:26.016618034  [rtsp @ 0x5629480] method DESCRIBE failed: 404 Not Found
2024-10-25 10:55:26.019214903  [rtsp @ 0x55f0ac0] method DESCRIBE failed: 404 Not Found
2024-10-25 10:55:26.043894819  [2024-10-25 10:55:26] frigate.app                    INFO    : Starting Frigate (0.15.0-4ff0c8a)
2024-10-25 10:55:26.098024561  [2024-10-25 10:55:26] peewee_migrate.logs            INFO    : Starting migrations
2024-10-25 10:55:26.098474301  [2024-10-25 10:55:26] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-10-25 10:55:26.114881343  [2024-10-25 10:55:26] frigate.app                    INFO    : Recording process started: 437
2024-10-25 10:55:26.122057444  [2024-10-25 10:55:26] frigate.app                    INFO    : Review process started: 446
2024-10-25 10:55:26.125473344  [2024-10-25 10:55:26] frigate.app                    INFO    : go2rtc process pid: 98
2024-10-25 10:55:26.153946927  [2024-10-25 10:55:26] detector.coral                 INFO    : Starting detection process: 454
2024-10-25 10:55:28.808238976  [2024-10-25 10:55:26] frigate.app                    INFO    : Embedding process started: 456
2024-10-25 10:55:28.808362299  [2024-10-25 10:55:26] frigate.comms.mqtt             ERROR   : Unable to publish to model_state: client is not connected
2024-10-25 10:55:28.813988653  [2024-10-25 10:55:26] frigate.detectors.plugins.edgetpu_tfl INFO    : Attempting to load TPU as usb
2024-10-25 10:55:28.814623503  [2024-10-25 10:55:26] frigate.app                    INFO    : Output process started: 479
2024-10-25 10:55:28.814692926  [2024-10-25 10:55:28] frigate.detectors.plugins.edgetpu_tfl INFO    : TPU found
2024-10-25 10:55:28.815104459  [2024-10-25 10:55:26] frigate.comms.mqtt             ERROR   : Unable to publish to model_state: client is not connected
2024-10-25 10:55:28.815197299  [2024-10-25 10:55:26] frigate.comms.mqtt             ERROR   : Unable to publish to model_state: client is not connected
2024-10-25 10:55:28.815607382  [2024-10-25 10:55:26] frigate.comms.mqtt             ERROR   : Unable to publish to model_state: client is not connected
2024-10-25 10:55:28.815635556  [2024-10-25 10:55:26] frigate.comms.mqtt             ERROR   : Unable to publish to model_state: client is not connected
2024-10-25 10:55:28.815727640  [2024-10-25 10:55:26] frigate.app                    INFO    : Camera processor started for front_porch: 542
...

Relevant go2rtc log output

n/a

Operating system

Debian

Install method

Docker Compose

Network connection

Wired

Camera make and model

n/a

Screenshots of the Frigate UI's System metrics pages

n/a

Any other information that may be helpful

No response

[hawkeye217]

I can't reproduce this. Do you have the web UI open on startup?

[leccelecce]

I'm frequently restarting from the web UI yes, will try restarting from command line and see if it goes away.

[hawkeye217]

#14588 should fix this

[NickM-27]

Fixed in next PR

[leccelecce]

For what it's worth, the message is still logged, just at debug level not error.

[NickM-27]

yeah, that's expected. It's not really a problem. Fixing the disconnect and other logs will ensure users will know when mqtt is not connected

[leccelecce]

gotcha, thanks. Looks good now.