1
0
Fork
You've already forked esphome-components
0

refactor(ezo_types): remove dead/legacy callback plumbing #4

Merged
stackdrift merged 1 commit from refactor/ezo-dead-code into main 2026年05月31日 13:52:43 +02:00

Summary

Legacy / dead-code refactor for ezo_types. Stacked on #3 — based on feat/migrate-ezo-types and targets that branch, so this diff is only the cleanup (retarget to main once #3 merges).

  • Removes five CallbackManagers + their add_*_callback methods — cell_constant, temp_scale, datalogger, temperature_change, extended_scale — that were declared and mostly fired but never subscribed by anything. They're relics of an earlier callback-based design, superseded by direct entity pointers (cell_constant_select_, tds_conversion_factor_number_), direct command methods (set_datalogger / set_extended_scale / ...), and the RT,<temp> compensated read.
  • Keeps the load-bearing path: RTDSensor::check_temperature_change_ still maintains last_known_temperature_ (read by send_compensated_read_ for RT temp comp), and all parse_*_response_ logging is unchanged.

Test plan

  • ./docker/esphome compile configs/test-ezo-types.yaml — green.
  • No behaviour change (the .call()s fired into empty managers). OTA'd to the Atlas hydro monitor and verified: pH/EC/RTD/ORP, EC/TDS, and temperature compensation all read normally.
## Summary Legacy / dead-code refactor for `ezo_types`. **Stacked on #3** — based on `feat/migrate-ezo-types` and targets that branch, so this diff is only the cleanup (retarget to `main` once #3 merges). - Removes five `CallbackManager`s + their `add_*_callback` methods — `cell_constant`, `temp_scale`, `datalogger`, `temperature_change`, `extended_scale` — that were declared and mostly fired but **never subscribed** by anything. They're relics of an earlier callback-based design, superseded by direct entity pointers (`cell_constant_select_`, `tds_conversion_factor_number_`), direct command methods (`set_datalogger` / `set_extended_scale` / ...), and the `RT,<temp>` compensated read. - Keeps the load-bearing path: `RTDSensor::check_temperature_change_` still maintains `last_known_temperature_` (read by `send_compensated_read_` for RT temp comp), and all `parse_*_response_` logging is unchanged. ## Test plan - `./docker/esphome compile configs/test-ezo-types.yaml` — green. - No behaviour change (the `.call()`s fired into empty managers). OTA'd to the Atlas hydro monitor and verified: pH/EC/RTD/ORP, EC/TDS, and temperature compensation all read normally.
stackdrift changed target branch from feat/migrate-ezo-types to main 2026年05月31日 13:42:46 +02:00
stackdrift force-pushed refactor/ezo-dead-code from 646c977496 to ff74d90db5 2026年05月31日 13:44:06 +02:00 Compare
stackdrift deleted branch refactor/ezo-dead-code 2026年05月31日 13:52:44 +02:00
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/esphome-components!4
Reference in a new issue
stackdrift/esphome-components
No description provided.
Delete branch "refactor/ezo-dead-code"

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?