Add quality scale to Tesla Fleet integration

[Bre77]

Proposed change

Adds Bronze tier quality scale tracking to the Tesla Fleet integration.

• Add quality_scale: bronze to manifest.json
• Create quality_scale.yaml with comprehensive rule tracking
• Document status of 18 Bronze rules (16 done, 2 exempt)
• Include Silver/Gold/Platinum tier tracking for future improvements

The integration meets all Bronze tier requirements with strong foundations for advancing to higher tiers.

Needs #160510
Needs #161201

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[joostlek]

Let's put the things we agree on fixing in the comments inside of the YAML file and get it merged, and we can fix the things in follow up PRs!

[joostlek]

We don't need CONFIG_SCHEMA = cv.config_entry_only_config_schema(DOMAIN) right?

[joostlek]

I'd remove the last part as I now got confused that you do use custom entity actions, which you don't

[joostlek]

It would be nice if we can patch the objects where we use them

    with patch(
        f"tesla_fleet_api.tesla.VehicleFleet.{func}",
        return_value=COMMAND_OK,
    ) as command:

[joostlek]

nit: test_climate_offline can use a hard assert instead of snapshot test

[joostlek]

        with patch(
            "homeassistant.helpers.translation.async_get_translations", return_value={}
        ):

I don't think we need this one right

[joostlek]

Why do we create our own OAuth2FlowHandler?

[joostlek]

    result = await old_entry.start_reauth_flow(hass)

    flows = hass.config_entries.flow.async_progress()
    assert len(flows) == 1

    result = await hass.config_entries.flow.async_configure(flows[0]["flow_id"], {})

nit: you can just use the first result to get the flow id :)

[joostlek]

Can we avoid touching entry.runtime_data in test_load_unload?

[joostlek]

Can we detect a tesla on a network? Would it make sense to autodetect the integration then

[Bre77]

No, only on Bluetooth, but I want to save that for the Tesla Bluetooth integration.

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[Copilot]

Pull request overview

This PR adds Bronze tier quality scale tracking to the Tesla Fleet integration by creating a comprehensive quality_scale.yaml file documenting compliance with 18 Bronze tier rules (16 done, 2 exempt) plus tracking for higher tiers. The change removes the integration from the INTEGRATIONS_WITHOUT_QUALITY_SCALE_FILE list in the hassfest validation script.

Changes:

• Create new quality_scale.yaml with comprehensive rule tracking across Bronze, Silver, Gold, and Platinum tiers
• Remove tesla_fleet from INTEGRATIONS_WITHOUT_QUALITY_SCALE_FILE list
• Document status of 49 quality rules (38 done, 6 exempt, 5 todo)

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
homeassistant/components/tesla_fleet/quality_scale.yaml	New file documenting quality scale compliance with 49 rules across all tiers
script/hassfest/quality_scale.py	Removes tesla_fleet from INTEGRATIONS_WITHOUT_QUALITY_SCALE_FILE list

Comments suppressed due to low confidence (1)

homeassistant/components/tesla_fleet/quality_scale.yaml:102

• The comment for exception-translations status is vague and doesn't provide context about which PR is addressing this or what needs to be fixed. Provide more specific information about the status or reference the PR that addresses this issue.

[Copilot]

The PR description states it should "Add quality_scale: bronze to manifest.json" and includes tracking for higher tiers. However, the manifest.json file is not modified in this diff. Additionally, the validation logic at lines 2242-2249 of this file requires that if a quality_scale field is added to the manifest, tesla_fleet must be removed from INTEGRATIONS_WITHOUT_SCALE in this file. The diff shows tesla_fleet still in INTEGRATIONS_WITHOUT_SCALE at line 1939. These changes appear to be missing from the PR.

[Copilot]

Consider using the shorthand format (e.g., rule-name: done) for rules with status "done" and no comment, to match the style used in other integrations like acaia. The expanded format with status: should be reserved for entries that have comments or non-"done" statuses. This would improve consistency across the codebase.