Add dashboard upload for local OTA firmware files - #939
Open
lboue wants to merge 3 commits into
Open
Conversation
Lets a user drop a .ota file on a node's detail page to store it in the server's OTA image store, the same store populated by --otaProviderDir directory scanning. New upload_ota_file WS command (schema 13) parses and validates the image, then the existing check/update-node flow picks it up for any node whose vendor/product ID matches. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The Python client's integration tests asserted schema_version == 12 directly, missed when SCHEMA_VERSION was bumped to 13 for upload_ota_file. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
lboue
marked this pull request as ready for review
July 26, 2026 21:11
Collaborator
|
Hm ... I am really unsure if i want to push some Megabyte of data through Websocket ... need to think about this |
Collaborator
Author
|
No problem. Come to think of it, the idea is to make it easier for users to upload update files. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Type of change
Description
Adds a way to upload a local
.otaMatter firmware image from the dashboard, without needing CLI/filesystem access to the server.upload_ota_fileWebSocket command (schema 13): decodes a base64-encoded.otafile and stores it into the server's local OTA image store — the same store populated by--otaProviderDirdirectory scanning. Returns the parsed vendor ID / product ID / software version..otaimage isn't node-scoped — it's identified by vendor/product ID in its header and becomes discoverable by any matching node via the existingcheck_node_update.OtaUploadError(101) for corrupt images, disabled OTA support, or store failures.Backing evidence
N/A — this is a feature addition, not a fix for an observed defect.
Checklist
npm testpasses (only pre-existing documented mDNS/commissioning integration flakes remain — seeCLAUDE.md)npm run format-verifyandnpm run lintpass🤖 Generated with Claude Code