myVAILLANT

For each ambisense devices, this PR adds: - one binary_sensor for battery_low (`false` = OK, `true` = battery low) - one binary_sensor for unreach (`false` = unreachable, `true` = OK). Tested with my steup (with ambisense). It could be nice if it could be tested without ambisense

Excerpt saved from GitHub on 2026-10-23.

Problem On VRC700 controllers (e.g. sensoCOMFORT) `climate.set_fan_mode` fails for the ventilation entity for every mode except `auto`. Each call returns a 500 in Home Assistant because the myVAILLANT API rejects the request: [code] ### Root cause `async_set_fan_mode` resolves the operation mode with `[k for k, v in self.fan_mode_map.items() if v == fan_mode][0]`. The VRC700 `fan_mode_map` maps both `NORMAL → FAN_ON` and `DAY → FAN_ON` (and `REDUCED → FAN_LOW`, `SET_BACK → FAN_LOW`). `[0]` therefore picks `NORMAL` / `REDUCED`, which the VRC700 ventilation endpoint does not accept. I verified …

Excerpt saved from GitHub on 2026-10-23.

Summary This PR fixes three separate issues that prevented temperature control from working on VRC700 systems (e.g. Vaillant aroTHERM heat pump with VRC700 controller). It was developed with the assistance of Claude AI (Anthropic), which helped diagnose the issues, write the fixes, and reverse engineer the missing cooling API endpoint. ### Fix 1, VRC700 heating DAY mode not recognised as manual setpoint `ZoneOperatingModeVRC700.DAY` is the VRC700 equivalent of a fixed/manual heating setpoint, but `async_set_temperature` only checked for `ZoneOperatingMode.MANUAL` (non-VRC700). This caused …

Excerpt saved from GitHub on 2026-10-23.

Apple's homekit integration is local. And it can control our Vaillant heat pump. Not possible to control the water heater part.

Excerpt saved from GitHub on 2026-10-23.

Hello, after a mandatory migration to myvaillant (I used Multimatic before), I installed this component to continue using my heater in HA. After installation, I notice that no sensor is present, here are the messages I see in the log: This is the error detail of the VRC700 line: Cette erreur provient d'une intégration personnalisée Logger: custom_components.mypyllant Source: helpers/update_coordinator.py:313 Integration: myVAILLANT (documentation, issues) First occurred: 20:47:44 (2 occurrences) Last logged: 20:47:45 Unexpected error fetching myVAILLANT data: 'DAY' is not a valid …

Excerpt saved from GitHub on 2026-10-23.

Integration version: v0.9.19 (latest available via HACS, no pending update) Home Assistant Core: 2026.9.1 Device: aroTHERM plus heat pump ## Problem Since 2026-09-05, both `consumed_electrical_energy_heating` and `consumed_electrical_energy_domestic_hot_water` (and the corresponding `heat_generated_*` sensors) only ever report values that are exact multiples of 1000 Wh (i.e. whole kWh, 0, 1000, 2000, 3000 Wh), never any value with the granularity I'd expect from a real energy meter (e.g. 1247, 1832 Wh). The daily reset itself works correctly (resets to 0.0 around 22:00 UTC / midnight …

Excerpt saved from GitHub on 2026-10-23.

Adds support for iQconnect-generation Vaillant devices (control identifier `scf`, product type `VR_NEEXT`, e.g. geoCOMPACT VWS 5.2/8.1 iQ). Today these aren't visible: `/homes` returns them but the aggregate `System` endpoint 404s, so 0 entities. Rebased onto current `main` (`myPyllant==0.9.18`, no manifest change needed). `scf` is native in the base library since signalkraft/myPyllant#160, so no runtime enum patching is needed here. With signalkraft/myPyllant#161 (merged) `get_systems()` also skips `scf` homes itself, so the split in the coordinator is belt-and-braces rather than …

Excerpt saved from GitHub on 2026-10-23.