Process completed with exit code 1.

test_llm_api_not_registered_with_version_017 AssertionError: assert 'llm_unregister' not in {'74565ad414754616000674c87bdc876c': {'client': <AsyncMock id='140034283464960'>, 'config': {'cameras': {'front_door':... 'model': '5.14.2/0.18.0', ...}, 'llm_unregister': <function async_register_api.<locals>.unregister at 0x7f5c4646ccc0>}

[CONFIG_SCHEMA] Integrations which implement 'async_setup' or 'setup' must define either 'CONFIG_SCHEMA', 'PLATFORM_SCHEMA' or 'PLATFORM_SCHEMA_BASE'. If the integration has no configuration parameters, can only be set up from platforms or can only be set up from config entries, one of the helpers cv.empty_config_schema, cv.platform_only_config_schema or cv.config_entry_only_config_schema can be used.

The repository does not contain brands assets at custom_components/frigate/brand/icon.png. Falling back to checking the brands repository.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.6.0, astral-sh/setup-uv@v6.4.3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/