Releases: omc69/Truma-Aventa2-HomeAssistant-Integration
Release list
v0.9.8
Temperatures and supply rails now build long-term statistics.
They had a device class and a unit but no state class, which is what Home Assistant needs to keep statistics — so they were recorded as history and would have vanished with the recorder's retention without ever becoming a trend.
Parameters that are states rather than measurements keep no statistics: averaging a firmware revision or a mode number says nothing.
v0.9.7
Fixes sensor names on the air conditioning.
It answers on two bus addresses and carries its name on the second one. Deciding from the first alone put 0x0702 into the name of every one of its sensors, on a device that was named correctly.
Also corrects the manifest version, which had said 0.9.3 for three releases because the bump was a sed whose pattern had stopped matching. CI now compares the manifest against the tag.
v0.9.6
Cleans up the device list.
Every bus address that answered became its own Home Assistant device — nine entries where the system has two. Six were bookkeeping endpoints (registration slots, the BLE chip, the Bluetooth record) reporting nothing but their own state.
Only an address that names itself is a device now; the rest hang their parameters on the appliance with the address in the entity name. No sensor is lost. Leftover entries from earlier versions can be deleted by hand.
v0.9.5
Corrects the documentation's claim that an ESP32 Bluetooth proxy is mandatory.
Measured on a bonded appliance, the link held through the host's own adapter for over two hours continuously, across many address-rotation windows. The frequent drops that produced the original claim were this integration crashing inside its own connection callback — the measurement that condemned the adapter was measuring a bug.
A proxy remains recommended: it reconnects reliably after a drop, and it can sit metres from the appliance rather than wherever the server is.
v0.9.4
Fixes a silent loss of parameters.
A notification can carry several messages, and each builds its parameter map from the state stored so far. Collecting them and applying only the last discarded everything the earlier messages added — the frames decoded correctly, only the result went missing. Two devices finishing their discovery inside one notification likewise cost one of them all its sensors.
v0.9.3
The climate entity now reports an action — cooling, heating, drying, fan or idle — alongside the mode. The appliance reports separately whether each function is running, which is the only way to tell a compressor that has reached its target from one still working towards it.
v0.9.2
Adds tests for the entity layer.
The last two faults both lived in Home Assistant code and neither was reachable from a protocol test. Both raise the moment an entity writes its state, so the suite now imports the integration and builds real entities from captured parameters. Reintroducing either fault fails the tests.
v0.9.1
Fixes v0.9.0, where every non-temperature parameter sensor raised AttributeError on each state write and most sensors never appeared.
Also skips MobileIdentity: the bus reports our own pairing identity back to us, and it belongs in diagnostics (redacted) rather than in an entity state.
v0.9.0
Every parameter the bus reports is now a sensor.
Parameter discovery returns everything each device knows about itself — 88 values on the air conditioning alone: measured temperatures, mains presence, error codes, firmware and hardware revisions, timer configuration. Until now only a handful were reachable.
- one sensor per parameter, per device
- parameters are keyed by the device that reported them, so the interface's copy of a topic no longer overwrites the appliance's
- addresses belonging to the same physical device are folded into one Home Assistant device (the interface here answers on three)
- temperatures that carry real readings are converted from tenths; raw sensor values are left as they are
Writes stay with the climate and light entities: the same surface exposes System.FactoryReset and DeviceManagement.Delete.