Skip to content

feat: take tiny-edge 0.5.0 - #27

Merged
reubenmiller merged 2 commits into
mainfrom
feat/tiny-edge-0.5.0
Nov 15, 2026
Merged

reubenmiller merged 2 commits into
mainfrom
feat/tiny-edge-0.5.0

Conversation

@reubenmiller

Copy link
Copy Markdown
Contributor

What

The Zephyr applications move from tiny-edge 0.3.0 to 0.5.0 (west.yml).

What an updated device reports to Cumulocity:

  • Parameter sets: the client's sets are tiny_edge and tiny_edge_remote_access. They were zephyr_tedge and zephyr_tedge_remote_access. The applications' own sets (zephyr_modbus_* and the others) keep their names.
  • New fragments: c8y_Agent, tedge_OS, and c8y_Hardware. tedge_Agent now holds only the transport.
  • Interrupted operations: an operation cut short by a reset is reported as failed after the reboot.
  • Firmware versions: versions up to 31 characters now reach Cumulocity in full.

A tenant needs the tiny-edge DTM definitions and the tiny-edge-* Smart Functions. cumulocity/README.md explains this and links tiny-edge's migration steps. The docs, the DTM tags of the applications' sets, and two code comments now use the new names.

Sizes

scripts/release/baseline.sh re-recorded all 36 Zephyr builds in release/size-baseline.json:

  • Flash: at most +1,058 B per tedge image, on the classic ESP32 tedge-ota images.
  • RAM: at most +216 B per tedge image.
  • Standalone images: unchanged.

Every build stays within its flash budget.

Tests

  • Builds: all 36 release builds compile against tiny-edge v0.5.0 in the Zephyr 4.4.2 container.
  • Not run on boards: the client changes themselves were tested on tiny-edge's own boards and samples.

🤖 Generated with Claude Code

reubenmiller and others added 2 commits November 12, 2026 23:59
The Zephyr applications move from tiny-edge 0.3.0 to 0.5.0. What a device
reports to Cumulocity changes with it:

- The client's parameter sets are tiny_edge and tiny_edge_remote_access
  (were zephyr_tedge and zephyr_tedge_remote_access); the tenant needs the
  tiny-edge DTM definitions and the tiny-edge-* Smart Functions.
- The device sends c8y_Agent, tedge_OS and c8y_Hardware, and tedge_Agent
  keeps only the transport.
- An operation interrupted by a reset is reported as failed after the
  reboot, and firmware versions up to 31 characters reach Cumulocity whole.

cumulocity/README.md says what a tenant set up for earlier images needs. The
applications' own parameter sets keep their names.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
At most +1,058 B of flash (classic ESP32 tedge-ota images) and +216 B of RAM
per tedge image; every build stays within its flash budget.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@reubenmiller
reubenmiller merged commit 37e1de7 into main Nov 15, 2026
21 checks passed
@reubenmiller
reubenmiller deleted the feat/tiny-edge-0.5.0 branch November 15, 2026 23:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant