Repository navigation
[upstream-doc] easee_cloud: Easee charger observations changed (390758b0) #117
Description
The upstream document easee_cloud is watched against has changed.
- Driver:
easee_cloud—drivers/lua/easee_cloud.lua,manifests/easee_cloud.yaml - Document: Easee charger observations
- URL: https://developer.easee.com/docs/charger-observation-ids
- Kind: api_docs
- URL stability: stable
- Previous SHA-256:
115f7a52c2490e30456010881ab8668a27795044f048ee79500bbbe4d63cd822 - New SHA-256:
390758b059370beff8f6f0a8e014333c4f40c26e7ef5551db61a057798875a7d - Detected: 2026-09-14T06:49:17+00:00
Review
- Read the new document and note what changed (registers renumbered,
parameters added, scaling corrected). - Cross-check against the registers/parameters
easee_cloudreads. - If the driver is affected, open a fix and bump its version;
otherwise close this issue.
Detection is a raw-byte hash: the file's bytes moved. That can be a
genuine content change or just rebuild churn in the PDF metadata —
this issue is a prompt to look, not proof the registers changed.
Activity
frahlg commentedon Sep 14, 2026
Reviewed the live content of https://developer.easee.com/docs/charger-observation-ids against what
drivers/lua/easee_cloud.luaactually reads.The driver polls a fixed set of observation IDs (
OBS_IDS = "48,96,103,109,120,121,124,183,194,223", defined at lines ~272-283). Checking each against the current page:All 10 IDs the driver reads are still present, with the same names, types and units the driver assumes (notably the kW→W and kWh→Wh scaling at
driver_poll, and the boolean coercion for 103). The enum value tables for 96 (REASON_LABELS) and 109 (OP_MODE_LABELS) live on separate linked enumeration pages, not on this specific page — this hash change is on the observation-ID listing itself, which reads as unchanged content (very likely formatting/metadata churn, consistent with the note that this is a raw byte-hash diff).For context: this driver's session/observation handling was actively reworked and merged just hours before this hash change was detected — PR #116 (merged 2026-09-14T03:51 UTC, this issue opened 2026-09-14T06:49 UTC) reworked observation freshness and session-proof logic against the live API. So this area is current, not stale.
No discrepancy found between what the driver expects and what the document currently states. Closing as not-planned.
Generated by Claude Code