silabs-flasher: Bump firmwares to Gecko SDK 4.4.3

[puddly]

The firmwares are now tracking https://github.com/NabuCasa/silabs-firmware-builder/releases/tag/v2024.8.6, including the filename format.

I've bumped universal-silabs-flasher as well, to allow people to downgrade from EZSPv14 if they flashed to it by accident.

Summary by CodeRabbit

• New Features

  • Updated firmware to EmberZNet 7.4.3, improving performance and compatibility.
  • Upgraded universal-silabs-flasher to version 0.0.22, enhancing functionality.
  • Incremented version number of the Silicon Labs Flasher add-on to 0.3.0, signifying significant updates.

• Bug Fixes

  • Revised firmware filenames for Yellow and SkyConnect devices to reflect updated versions, ensuring proper flashing of firmware.

[coderabbitai]

Walkthrough

Walkthrough

The updates in version 0.3.0 of the silabs_flasher project include significant enhancements such as upgrading the firmware to EmberZNet 7.4.3 and updating the universal-silabs-flasher to version 0.0.22. Additionally, the flashing script has been modified to use the new firmware filenames for the Yellow and SkyConnect devices. These changes are designed to enhance performance, compatibility, and overall user experience.

Changes

File Path	Change Summary
silabs_flasher/CHANGELOG.md	Updated changelog for version 0.3.0, detailing firmware and flasher updates.
silabs_flasher/build.yaml	Incremented UNIVERSAL_SILABS_FLASHER version from 0.0.19 to 0.0.22.
silabs_flasher/config.yaml	Updated version from 0.2.3 to 0.3.0 in configuration file.
silabs_flasher/rootfs/etc/s6-overlay/scripts/universal-silabs-flasher-up	Updated firmware filenames for Yellow and SkyConnect devices to reflect new versions.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Flasher
    participant Device
    User->>Flasher: Request firmware flash
    Flasher->>Device: Identify device type
    Device-->>Flasher: Device type identified
    Flasher->>Flasher: Select firmware based on device type
    Flasher->>Device: Flash updated firmware
    Device-->>Flasher: Flashing complete
    Flasher-->>User: Notify completion

Loading

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7f2bbc5 and dedc20d.

Files selected for processing (2)

• silabs_flasher/CHANGELOG.md (1 hunks)
• silabs_flasher/config.yaml (1 hunks)

Files skipped from review due to trivial changes (1)

• silabs_flasher/config.yaml

Files skipped from review as they are similar to previous changes (1)

• silabs_flasher/CHANGELOG.md

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[agners]

This needs a version bump in config.yaml.

Also should we maybe go to 0.3.0? 🤔

[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.