v0.29.0

Changed

• Rate-shaped gateway polling — live reads (r_dca/r_not/r_lse) every cycle, rarely-changing config reads every 6th cycle. Removes a ~9-concurrent-BAPI burst every 10 s that was a token-bucket 429 storm and a contributor to gateway task-watchdog reboots.

Added

• Gateway temperature diagnostic sensor (ESP32-S3 die temperature) — parity with the MQTT entity; unavailable on hardware without a real internal sensor.

Fixed

• schedule_paused binary sensor now reads the gateway's authoritative flag (r_lse.control_mode == 1) instead of a gen field that /api/status never carried (so it was always off). Requires gateway fw ≥ v3.2.0-rc.4.

Best paired with gateway firmware v3.2.0-rc.4.

v0.28.2 — code-review fixes

Post-review fixes (no new features):

• Release-default enforcer now defers to an add-on-owned charge — it only acts while the integration owns control (the add-on is a config layer over the integration).
• Auto-efficiency no longer silently switches existing users — an install with a fixed efficiency stays Fixed; Auto is the default only for new configs.
• House Current (L1) enabled by default + 1dp, consistent with the new L2/L3 phase sensors.
• Auto-efficiency no longer reads the odometer history twice per learn refresh.

Pairs with Add-on 0.51.0.

v0.28.1 — hassfest fixes (dependencies + issue text)

Patch over v0.28.0 — no functional change, fixes the Validate/hassfest CI:

• Declare http (dependencies) + recorder (after_dependencies) in the manifest — both were used (frontend static paths, commute history) but undeclared.
• Removed HTML (<gateway-ip>) from the "not_control_owner" repair-issue text so hassfest's no-HTML translation check passes.

All the 0.28.0 features (resume_eco handback default, EM340 per-phase parity + House-Current fix, reminder cooldown, self-learning commute efficiency) are unchanged — see v0.28.0 notes.

v0.28.0 — Charge Assistant: handback default, EM340 parity, reminder + efficiency

Rolls up 0.24.0 → 0.28.0.

Charge Assistant — return-to-default on control release

• New "return the charger to a default when the Assistant/Add-on stops controlling" option — for when a mode is turned off or a stray/leftover start leaves it charging with nothing watching it. Defaults to Resume Eco-Smart / Solar: hands the charger back to its own schedule + solar rather than leaving it paused/idle. Only ever acts on charges the integration/add-on owned — manual and native-schedule charges are never touched. Degrades gracefully on chargers without solar. Validated end-to-end on hardware.

Per-phase EM340 / Power-Boost meter

• Added Mains Voltage L2/L3 and House Current L2/L3 sensors, at parity with MQTT discovery (community contribution, thanks @hannesjanno).
• Fixed: House Current read ~10× too high — the meter's per-phase current is in deci-amps; it's now scaled correctly (16 A reads 16.0 A, not 160 A).

Plug-in reminders

• Fixed reminder spam: a flappy presence entity (phone GPS/Wi-Fi bouncing home→away→home) fired a fresh notification each time. A 30-minute cooldown now gates repeats (the escalation re-nudge is unaffected; it resets when the car plugs in).

Smart-charge commute efficiency

• Self-learning efficiency (kWh/100km): the odometer source can now learn your real consumption from SOC-drop × battery over the odometer distance (Auto, default when odometer + SOC + battery are set), read a Sensor, or use a Fixed value. No more hand-entered guess.

Full detail in CHANGELOG.md.

v0.23.3 — Max current setpoint fallback

Fixed

• "Max current" number (and the native Controls card's slider) no longer reads "unknown". It only read charger_status.cm / realtime.ic, which some chargers (Pulsar Plus/MAX firmware) don't report — so the setpoint was blank even though the sensor had a value. It now falls back to r_dat.cur (the active max current the dashboard + max_charging_current sensor use), so it's populated everywhere. Found while verifying the native Controls card on real hardware.

Update: HACS → redownload the integration → restart Home Assistant.

v0.23.2 — OTA install + energy-sensor fixes

Fixed

• Firmware "Install" (OTA from HA) no longer shows a bogus error. The gateway reboots into the new image right after accepting the upload, so its HTTP response is often empty / the connection drops — the client tried to parse that as JSON and raised "unexpected character: line 1 column 1 (char 0)" on a flash that had actually succeeded. A 2xx is now treated as success without parsing the body.
• Energy sensors no longer spam the log. "Green energy (session)" / "Grid energy (session)" were state_class: measurement, invalid for the energy device class — now total_increasing. "Last charge burst" is a per-burst snapshot, so it now carries no state_class.

Added

• Test guard validating every sensor's device_class / state_class combo against HA's rules, so this class of bug can't ship again.

Update: HACS → redownload the integration → restart Home Assistant.

v0.23.1 — Native Lovelace cards + Max-current re-enable (#75)

Added

• Native Lovelace cards, auto-registered by the integration (no manual resource setup — they appear in the card picker once you update):

  • Wallbox Energy Flow (custom:wallbox-energy-flow) — Solar/Grid → Vehicle live power-flow
  • Wallbox Controls (custom:wallbox-controls) — Start/Stop, max-current slider, solar toggle, resume schedule
  • Wallbox Status (custom:wallbox-status) — charger state + quick stats
  • Wallbox Session (custom:wallbox-sessions) — session energy + solar/grid split

  Each card auto-finds your Wallbox device (or takes device: for multi-charger setups) and resolves its entities — no wiring needed.

Fixed

• "Max charging current" now shows for users who already had the integration (#75). Enabling a sensor by default doesn't retroactively enable one that was already registered as disabled under an older version. The integration now re-enables it on update — only if it was disabled by the old default, never a deliberate manual disable.

Update: HACS → redownload the integration → restart Home Assistant.

v0.22.1 — Max charging current sensor fix (#75)

Fixed

• "Max charging current" sensor now shows up and populates on all chargers. It was disabled by default (so it never appeared unless you went hunting for it in the entity registry) and it read only r_sta.max_charging_current, which some chargers — e.g. the Pulsar Plus — don't report, leaving it blank even when enabled. It's now enabled by default (matching the dashboard and MQTT discovery) and falls back to r_dat.cur — the same active max-current value the dashboard shows — when r_sta omits the field. (andypnz, forum #75)

Update: HACS → redownload the integration → restart Home Assistant.

v0.22.0 — Solar switch + resume-mode

Added: a Solar-charging on/off switch (mirrors the app's Solar Charging toggle — on restores your last solar Eco-Smart mode, off disables it), and a "return the charger to …" preference (Leave as set / Full Green / Eco Smart / Disabled) so after a managed charge the assistant hands back to your chosen native mode. 185-case test suite.

v0.21.0 — Capability-aware solar

Added — use the charger's native Eco-Smart when it has it, emulate it when it doesn't

Solar and Smart + Solar now detect whether your charger has a built-in Eco-Smart feature:

• Has it → the assistant defers to it — sets the right native mode (Solar → Full Green; Smart+Solar → Eco Smart / solar+grid) and lets the charger follow the sun itself, with no Home-Assistant start/stop churn and without pausing your schedule. Writes are idempotent.
• Lacks it → Home Assistant emulates it, modulating the charge current to follow your surplus (smooth, not crude on/off).

New "Use the charger's built-in Eco-Smart when available" toggle (default on) on both Solar and Smart+Solar. 177-case test suite.