jontofront/ecoNET-300-Home-Assistant-Integration v1.3.0-beta.3 on GitHub

ecoNET300 v1.3.0-beta.3 (pre-release)

⚠️ Beta release for testing. Please back up your Home Assistant configuration before upgrading. Feedback and bug reports are very welcome — especially from ecoMAX360i and mixer users.

This beta builds on the configurable device grouping from beta.2 and fixes mixer entity grouping, duplicate entities, and locked-parameter handling.

🔧 Fixed

Mixer entities for unconnected mixers no longer created — the controller all-sensors sweep created Mixer N target temperature sensors from phantom mixerSetTemp{N} values even when the mixer was not connected (mixerTemp{N} is null). Mixer temperature/setpoint sensors are now owned exclusively by the mixer creator (which validates mixer presence and groups them on the Mixer device), and phantom mixer keys for unconnected mixers are dropped.
Duplicate unique_id collisions for mixer/lambda sensors fixed — the sweep emitted the same keys as the dedicated mixer/lambda creators and, running first, shadowed the device-grouped sensors onto the main device (logged as ... does not generate unique IDs. ID ...-mixerTemp1 already exists). Mixer and lambda keys are now excluded from the sweep so the correctly-grouped Mixer/Lambda-device sensors win.
Mixer/HUW schedule sensors grouped on the correct device — schedule sensors (e.g. Mixer 1 schedule) ignored device grouping and always landed on the main controller device. They now route to their Mixer/HUW device in split mode, and schedules for unconnected mixers are skipped.
Locked mixer setpoints are now detected and surfaced — Mixer N target temperature number entities lacked a param_id, so device-side parameter locks (e.g. "Preset temp. mixer 1: the ability to edit this parameter has been locked") were invisible. They now resolve their mergedData counterpart by key (preset_mixer{N}_temperature), show the lock icon and lock reason, and raise a user-facing error when a write is attempted on a locked parameter.
Clear error on rejected number writes — when the device rejects a setpoint write, the entity now raises a UI error notification instead of silently logging a warning.

🧪 What to test

Mixers: verify each connected mixer appears once on its own Mixer device, with no duplicate-unique-id warnings in the log.
Confirm no phantom Mixer 2/3/4 target temperature entities appear for mixers you don't have.
Try changing a mixer target temperature that is locked on the device/cloud — you should see a lock icon, a lock_reason attribute, and an error popup when attempting to change it.
Mixer/HUW schedule sensors land on the correct device (split mode).

📦 Installation (HACS)

In HACS, open the ecoNET300 integration.
Enable Show beta versions (⋮ menu).
Select v1.3.0-beta.3 and download.
Restart Home Assistant.

Full changelog: see CHANGELOG.md.