Skip to content

v0.1.44 — per-asset sub-devices + diagnostic timestamps + portal link

Choose a tag to compare

View all tags
@mrebbert mrebbert released this 27 Jun 05:23
v0.1.44
d222659

Per-asset sub-devices, two new diagnostic timestamps, portal link

What changed

The single 1k5 device now splits into one parent device plus a sub-device per hardware asset (inverter, heat pump, smart meter, wallbox) — so the Settings → Devices & Services UI shows the real manufacturer, model and firmware of each component:

1k5° System (parent)
├── Inverter      (Sungrow / SH6.0RT-V112 / SAPPHIRE-…)
├── Heat pump     (Stiebel Eltron / WPMsystem / …)
├── Smart meter   (Chint / DTSU666 / …)
├── Wallbox       (go-e / HOMEfix 11kW / 60.5)
└── EV vehicle    (existing sub-device, unchanged)

You can now assign an area per sub-device, disable a single asset's entities at once, and read the firmware version straight from the device card.

Each sub-device exposes only PII-safe fields from the cloud (manufacturer, model, firmware). Serial numbers, network addresses, asset IDs and gateway secrets stay redacted. Devices the platform doesn't classify (UNKNOWN type, e.g. a Shelly Pro 3EM behind the smart meter) stay attached to the parent — no empty placeholder devices.

Two new diagnostic timestamps cover the previously un-tracked weather and connectivity coordinators (Letztes Wetter-Update / Letztes Konnektivitäts-Update) — useful when troubleshooting "when did the weather/connectivity layer last refresh?".

The system device now exposes a configuration_url, so the "Visit device" button in the device card opens the 1KOMMA5° customer portal directly.

What you need to do

Nothing. entity_ids and unique_ids are unchanged on existing installs, so:

  • Long-term statistics keep their continuous timeline.
  • Automations referencing sensor.<system>_* keep working.
  • Dashboards and Energy-Dashboard configuration stay intact.

After the upgrade, the next coordinator refresh creates the sub-devices automatically (≤15 min). Friendly names will then carry the sub-device label (e.g. "Wechselrichter PV-Leistung" instead of "1k5 PV-Leistung"). User-set name overrides in the entity registry are preserved.

Fresh installs (new HA setups after this version) will see sub-device names in entity_id slugs as well — that's normal HA behaviour for entities under named devices.

Full changelog

See CHANGELOG.md.

Assets 3
Loading