Call for testers: ecoSTER

[jontofront]

Hi everyone with an ecoSTER room panel! 👋

This discussion is the place to try new ecoSTER features before they go into a stable release. Each new test version is posted as a comment below, with what changed and what to check. Use Subscribe in the right sidebar to get notified.

Latest test version: none right now. Everything tested so far is in the stable v1.3.4 release.

@AdamK80 (ecoMAX920P1-O), @osdi-thiellet (ecoMAX 920i), @churos78 (ecoMAX 960D), @aintnogeek (ecoMAX920P1-T, #202), @michauMiau (#90): you mentioned an ecoSTER panel before, so your feedback would help a lot. Anyone else with an ecoSTER is welcome too. Thanks to @fsaidl for testing on ecoMAX860D3-HB.

How to install a test version

1. In HACS, enable the Pre-release switch for ecoNET300 Home Assistant integration. It is disabled by default; find it under Settings → Devices & services → Entities.
2. Update to the latest pre-release, or open HACS → ecoNET300 → ⋮ → Redownload and pick the version.
3. Restart Home Assistant.

To go back, use Redownload and pick the latest stable release, then turn the Pre-release switch off.

Please reply with

• The test version, your controller model and the number of ecoSTER panels.
• What worked and what didn't.
• A diagnostics file: Settings → Devices & services → ecoNET300 → ⋮ → Download diagnostics. Passwords are redacted.

Thanks for helping! 🙏

[jontofront]

🧪 v1.3.4-alpha.3

Release: v1.3.4-alpha.3

What's new

• Setpoints you can change from HA ([FEATURE] Change target temperature on connected ecoSTER thermostats - e.g. Configure number.ecoster_X_temperature_2 #236): each connected panel gets Room thermostat N day setpoint and Room thermostat N night setpoint numbers on its ecoSTER N device. Party, holiday and antifreeze setpoints are also created, but disabled by default. Values come from the controller's editParams.
• No more extra ecoSTER devices (Empty ecoSTER slots create an extra ecoSTER N device #256): the controller reports every slot it supports, so empty slots used to get their own ecoSTER N device. Now only connected panels get entities. A leftover device can be deleted from its device page (⋮ → Delete).

What to check

1. Each connected panel has its own ecoSTER N device with room temperature, active setpoint, mode, and the day and night setpoints.
2. Change the day or night setpoint in HA. The panel (or econet24.com) shows the new value, and HA keeps it. The controller needs up to about 20 seconds to apply a write.
3. Devices of empty slots: if you see an ecoSTER N without a panel, it can be deleted with ⋮ → Delete. Devices of connected panels cannot be deleted.
4. If the setpoints don't appear: not every ecoNET module answers editParams. The integration retries a few times in the first 40 minutes after start, so please wait a bit before reporting.

[fsaidl]

diagnostics-alpha3-20261004-po-testech.json

Tested v1.3.4-alpha.3 on an ecoMAX860D3-HB with two ecoSTER panels (ecoSTER module soft ver 1.20.21). Diagnostics attached.

Everything on your list checked out:

• Both panels kept their entities. The entity IDs are the same as before the update and the history is continuous — no unavailable states across the restart.
• I deleted the ecoSTER 3 device and its three leftover entities went with it. Only ecoSTER 1 and 2 are left.
• Deleting ecoSTER 1 or 2 is refused with "Failed to remove device entry, rejected by integration", as you described.
• Night setpoints work on both panels. I set 18.9 and 18.4 in HA, both values held, and the controller had them in editParams (STER_TEMP_NIGHT_1 / _2) within about 5–10 seconds. I put the original 18.1 / 18.2 back afterwards; the day setpoints were not touched.

ecoSterNumber still reports 3 and ecoSterTemp3 is null, but only the two connected panels get entities now, so that looks exactly as intended.

About a panel losing its connection: I have not seen it here. I went through 10 days of the ecoSTER temperature history in HA and there is not a single unavailable or unknown state, so I have no regParams sample from such a moment. I am not going to unplug anything.

Two things I ran into that might be worth knowing:

1. Home Assistant logs a deprecation warning for the integration: device_registry.async_get_or_create is called with the deprecated via_device parameter (calendar.py:269, number.py:1399, select.py:860, switch.py:561, sensor.py:1728). It says that will stop working in HA 2027.8.0.
2. While polling the controller during the test, /econet/editParams twice came back without the STER_TEMP_NIGHT_* keys. Same intermittent behaviour as the regParams issue in [Bug]: Intermittent "regParams endpoint returned no usable data" ERROR (transient, ~88×/day, also on stable releases) #255 — the data is there again a moment later.

[jontofront]

Thanks a lot, @fsaidl — that was fast and very thorough! 🙏

Everything you checked matches the expected behaviour, so the fix is merged and released in the stable v1.3.4. You can turn the HACS pre-release switch off again and update to it. Your diagnostics file is now also the test data for the ecoMAX860D3-HB.

About the two things you noticed:

• via_device warning: Home Assistant 2026.8 changed how sub-devices are linked to the main device. The warning is harmless for now and will be fixed in the next version, well before 2027.8.
• editParams without the STER_TEMP_NIGHT_* keys: thanks for spotting it. If Home Assistant gets such a partial reply, the setpoints could show as unavailable until the next read. I'll handle it together with [Bug]: Intermittent "regParams endpoint returned no usable data" ERROR (transient, ~88×/day, also on stable releases) #255 by keeping the last known values.

[michauMiau]

Sorry, I can't participate as I already sold my ecoNET module and switched to the Plum ecoMAX integration, that being said thank you for maintaining this integration, if not for the wifi issues with the module, i wouldn't have switched.