Skip to content

v0.3.1 - Eletta Explore sensor fix

Choose a tag to compare

@actabi actabi released this 03 Jun 07:52
0661d02

Fixed

  • Sensors stuck on unknown for Eletta Explore (oem_model=DL-striker-cb): counter property names now resolve from a per-model candidate list (e.g. d700_tot_bev_b on Soul vs d701_tot_bev_b on Eletta), same approach as the v0.3.0 command-property detection.
  • Last Connected now resolves device_connected / app_device_connected via the candidate list.

Changed

  • Counter/info sensors whose property is absent on the device are no longer created, instead of appearing permanently unknown (e.g. Total Milk Drinks / Total Water / Descale Status on Eletta).
  • Counter parsing is more robust (handles int and numeric strings); when a counter value is present but not a plain integer, the raw value and Ayla base_type are logged once so unknown encodings can be reported and supported.

No regression on PrimaDonna Soul

All 16 sensors still resolve on DL-millcore (total_beverages -> d700_tot_bev_b, last_connected -> device_connected).

How to update: HACS > De'Longhi Coffee Link > Redownload > v0.3.1, then restart Home Assistant.

Fixes the sensor-naming part of #2.

Full Changelog: v0.3.0...v0.3.1