Skip to content

Conversation

@ptarjan
Copy link
Contributor

@ptarjan ptarjan commented Dec 10, 2025

When a Tesla software update is scheduled for later (e.g., tonight), the update entity was incorrectly showing as "Installing" because the SCHEDULED status was being treated the same as INSTALLING.

This change:

  1. Makes in_progress only true when the status is INSTALLING
  2. Adds an update_status attribute to show the actual API status (available, scheduled, installing, downloading, etc.)
  3. Shows "Update scheduled" in the release_summary when scheduled, making it visible in the update card UI

Users can now clearly see when an update is scheduled vs installing.

In my current HA I see this when I have scheduled the update:

image

Breaking change

Proposed change

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:

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:

When a Tesla software update is scheduled for later (e.g., tonight),
the update entity was incorrectly showing as "Installing" because
the SCHEDULED status was being treated the same as INSTALLING.

This change:
1. Makes in_progress only true when the status is INSTALLING
2. Adds an update_status attribute to show the actual API status
   (available, scheduled, installing, downloading, etc.)
3. Shows "Update scheduled" in the release_summary when scheduled,
   making it visible in the update card UI

Users can now clearly see when an update is scheduled vs installing.
@home-assistant
Copy link

Hey there @Bre77, mind taking a look at this pull request as it has been labeled with an integration (tesla_fleet) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tesla_fleet can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign tesla_fleet Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

@Bre77
Copy link
Contributor

Bre77 commented Dec 10, 2025

Yeah I know exactly what's wrong here. PR incoming.

@Bre77
Copy link
Contributor

Bre77 commented Dec 10, 2025

Actually the problem is if scheduled isn't in progress then when you click install nothing will happen because it always goes scheduled for a minute before starting.

Would it be okay to be in progress but with 0%?

@ptarjan
Copy link
Contributor Author

ptarjan commented Dec 10, 2025

Sorry if I wasn't clear. My issue is on my car I pressed the Schedule Update button and scheduled it for 3am tomorrow morning. Now all day my Home Assistant is telling me the update is Installing... and at 10% as per the screenshot. I'd like it to not show that and just list it as scheduled all day.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants