1
0
Fork
You've already forked grow-fleet
0

chore(fleet): bump esphome components ref #4

Merged
stackdrift merged 1 commit from chore/bump-esphome-components-vpd into main 2026年06月14日 22:27:29 +02:00

Summary

  • Bumps the pinned stackdrift/esphome-components dependency from 1b6242a3afe71e96eec577155ae3d86d58d3ac3c to merged PR #18 commit 798fa7268b5940f1dcfef3ff05e601e5b004fe81.
  • Updates fleet.yaml and each device external_components block to the same ref.
  • Leaves per-device VPD precision config unchanged because the component default now provides the metadata.

Test Plan

  • git diff --check
  • python3 scripts/list_devices.py
  • docker run --rm --entrypoint /usr/bin/env --user "$(id -u):$(id -g)" -e HOME=/tmp -e PLATFORMIO_CORE_DIR=/config/.esphome/platformio -v "$PWD":/config -w /config ghcr.io/esphome/esphome:2026.5 python3 scripts/compile_devices.py --all
  • Verified generated AtomS3U source includes VPD state_class=measurement, accuracy_decimals=2, and uom:kPa.

Notes

  • The compile produced firmware binaries locally for all three release devices.
  • Existing warnings observed: ESPHome strapping-pin warnings and the pre-existing mlx90640 request->url() deprecation for ESPHome 202690.
## Summary - Bumps the pinned `stackdrift/esphome-components` dependency from `1b6242a3afe71e96eec577155ae3d86d58d3ac3c` to merged PR #18 commit `798fa7268b5940f1dcfef3ff05e601e5b004fe81`. - Updates `fleet.yaml` and each device `external_components` block to the same ref. - Leaves per-device VPD precision config unchanged because the component default now provides the metadata. ## Test Plan - `git diff --check` - `python3 scripts/list_devices.py` - `docker run --rm --entrypoint /usr/bin/env --user "$(id -u):$(id -g)" -e HOME=/tmp -e PLATFORMIO_CORE_DIR=/config/.esphome/platformio -v "$PWD":/config -w /config ghcr.io/esphome/esphome:2026.5 python3 scripts/compile_devices.py --all` - Verified generated AtomS3U source includes VPD `state_class=measurement`, `accuracy_decimals=2`, and `uom:kPa`. ## Notes - The compile produced firmware binaries locally for all three release devices. - Existing warnings observed: ESPHome strapping-pin warnings and the pre-existing `mlx90640` `request->url()` deprecation for ESPHome 202690.
chore(fleet): bump esphome components ref
All checks were successful
firmware / pr_prepare (pull_request) Successful in 3s
firmware / main (pull_request) Has been skipped
firmware / release (pull_request) Has been skipped
firmware / dispatch (pull_request) Has been skipped
firmware / pr_prepare (push) Has been skipped
firmware / main (push) Has been skipped
firmware / release (push) Has been skipped
firmware / dispatch (push) Has been skipped
firmware / pr_compile (atlas-hydro-kit) (pull_request) Successful in 2m6s
firmware / pr_compile (atoms3u-sensor-rig) (pull_request) Successful in 2m5s
firmware / pr_compile (m5stack-airq) (pull_request) Successful in 2m7s
44c4b9fa71
Sign in to join this conversation.
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
stackdrift/grow-fleet!4
Reference in a new issue
stackdrift/grow-fleet
No description provided.
Delete branch "chore/bump-esphome-components-vpd"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?