Repository navigation
feat(onboard): register devices with their firmware's type; fix the ESP-IDF component install - #18
Merged
reubenmiller merged 2 commits intoNov 12, 2026
Conversation
tedge-onboard registered every device with go-c8y-cli's default type, "thin-edge.io", so firmware offered for a device's own type (for example thin-edge.io-esp-idf-agent) never showed in its Firmware tab. - The provisioning library's info command (0xE0) now ends with the device type, from the new tedge_get_device_type(). A tool that reads only the first five fields still understands the reply. - tedge-onboard passes that type to `deviceregistration register-ca --type`. A device with older firmware reports none and keeps the default. - The DTM definitions tag thin-edge.io-esp-idf-agent too. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The component manager fetches only ports/freertos/esp-idf/tiny_edge, but the component builds the core, the provisioning library and the shared port code from beside it, so the documented git + path dependency failed to configure. Outside a tiny-edge checkout, the component now fetches the rest of tiny-edge into the build directory at configure time: the commit the component manager resolved (the component's version), from the URL in the project's dependencies.lock. TINY_EDGE_DIR uses a checkout instead. ESP-IDF's early requirements pass no longer needs the sources. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
reubenmiller
deleted the
feat/onboard-device-type-and-standalone-component
branch
November 12, 2026 14:17
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
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.
What
1.
tedge-onboardregisters devices with the type their firmware reports. Until now it registered every device as go-c8y-cli's default,thin-edge.io, so firmware offered for a device's own type (for examplethin-edge.io-esp-idf-agent) never showed in the device's Firmware tab.0xE0) now ends with the device type, from the newtedge_get_device_type(). A tool that reads only the first five fields still understands the reply.tedge-onboardpasses that type todeviceregistration register-ca --type. A device with older firmware reports no type and keeps the default.thin-edge.io-esp-idf-agent.2. The ESP-IDF component builds when the component manager installs it. The README's
git+pathdependency failed to configure. The component manager fetches onlyports/freertos/esp-idf/tiny_edge, but the component buildscore/,provisioning/, andports/common/from beside it.dependencies.lock, so a fork is fetched from the fork.TINY_EDGE_DIRuses a checkout instead.Tests
git: file://…+path:with a tag, starting from an empty component cache. The component fetched tiny-edge at the resolved commit, and the image built (tedge-minimal.bin, 37% of the slot free).ctestpasses, 3 of 3, and the provisioning test now checks the type field. host-compile passes.go vetis clean andgo test ./...passes, including new tests for parsing the info reply with and without the type, and for--typein the registration.🤖 Generated with Claude Code