Skip to content

Conversation

@puddly
Copy link
Contributor

@puddly puddly commented Nov 10, 2025

Proposed change

Bump universal-silabs-flasher from 0.0.37 to 0.1.0. This release improves communication with OpenThread RCP firmware and provides a new API to speed up probing during firmware flashing. Our approach is now:

  1. Identify firmware type when setting up the adapter (to avoid unnecessarily downgrading or reinstalling the current firmware). This is now optimized per-adapter by omitting unused firmware+baudrate configurations (e.g. CPC firmware for the ZBT-2)
  2. If we cannot detect the firmware type or the detected firmware is lower than the recommended, we perform a firmware upgrade. This directly uses the bootloader trigger (when available), removing unnecessary waiting.

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:

@home-assistant
Copy link

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (homeassistant_sky_connect) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of homeassistant_sky_connect 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 homeassistant_sky_connect 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.

@home-assistant
Copy link

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (homeassistant_yellow) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of homeassistant_yellow 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 homeassistant_yellow 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.

@home-assistant
Copy link

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (homeassistant_hardware) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of homeassistant_hardware 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 homeassistant_hardware 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.

@home-assistant
Copy link

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (homeassistant_connect_zbt2) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of homeassistant_connect_zbt2 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 homeassistant_connect_zbt2 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.

@puddly puddly marked this pull request as ready for review November 11, 2025 21:44
Copilot AI review requested due to automatic review settings November 11, 2025 21:44
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR bumps the universal-silabs-flasher dependency from version 0.0.37 to 0.1.0, which introduces a new API for more efficient firmware probing and flashing. The key changes include:

  • Updated API now requires both bootloader_reset_methods and application_probe_methods parameters
  • Changed from instance variables to class variables (BOOTLOADER_RESET_METHODS and APPLICATION_PROBE_METHODS)
  • Optimized firmware probing to use device-specific configurations

Reviewed Changes

Copilot reviewed 17 out of 17 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
requirements_all.txt Updated universal-silabs-flasher dependency to v0.1.0
requirements_test_all.txt Updated universal-silabs-flasher dependency to v0.1.0
homeassistant/components/homeassistant_hardware/manifest.json Updated universal-silabs-flasher requirement to v0.1.0
homeassistant/components/homeassistant_hardware/util.py Updated API calls to include new required parameters for bootloader reset and application probe methods; contains a type conversion bug on line 417
homeassistant/components/homeassistant_hardware/update.py Changed from instance variable to class variables for reset/probe methods
homeassistant/components/homeassistant_hardware/firmware_config_flow.py Added APPLICATION_PROBE_METHODS class variable and updated probe calls
homeassistant/components/homeassistant_sky_connect/config_flow.py Added device-specific bootloader reset and application probe method configurations
homeassistant/components/homeassistant_sky_connect/update.py Updated to reference mixin class variables instead of direct assignment
homeassistant/components/homeassistant_yellow/config_flow.py Added device-specific bootloader reset and application probe method configurations
homeassistant/components/homeassistant_yellow/update.py Updated to reference mixin class variables instead of direct assignment
homeassistant/components/homeassistant_connect_zbt2/config_flow.py Added device-specific bootloader reset and application probe methods including both RTS_DTR and BAUDRATE
homeassistant/components/homeassistant_connect_zbt2/update.py Updated to reference mixin class variables instead of direct assignment
homeassistant/components/zha/repairs/wrong_silabs_firmware.py Updated probe_silabs_firmware_type call with new required parameters
tests/components/homeassistant_hardware/test_util.py Updated test calls to include new parameters
tests/components/homeassistant_hardware/test_update.py Updated mock entity to use class variables and added application_probe_methods to mock function signatures
tests/components/homeassistant_hardware/test_config_flow.py Added application_probe_methods parameter to mock function signature
tests/components/homeassistant_connect_zbt2/test_config_flow.py Updated test assertion to expect both RTS_DTR and BAUDRATE reset methods

Copy link
Member

@edenhaus edenhaus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @puddly 👍

Copy link
Member

@TheJulianJES TheJulianJES left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me! Did a quick test run with ZBT-2 as well and had no issues.
One small question:

@edenhaus edenhaus merged commit 1fcaf95 into home-assistant:dev Nov 12, 2025
123 of 124 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Nov 13, 2025
@puddly puddly added this to the 2025.11.3 milestone Nov 20, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants