Note: This repository is a fork of the original pblxptr/ecoNET-300-Home-Assistant-Integration. Most of the work was done by @pblxpt, and we are very grateful for their efforts. Additionally, I maintained and supported this code up to version v0.3.3.
| Home Assistant | ecoNET300 | device |
|---|---|---|
 |
 |
 |
he ecoNET300 Home Assistant Integration allows local control and monitoring of ecoNET300 devices directly from Home Assistant. It communicates over your local network via the ecoNET300’s native REST API, avoiding any external cloud services.
- Local Operation: No dependency on econet24.com cloud services.
- Easy Configuration: Integrate directly via Home Assistant UI.
- Tested With: ecoMAX810P-L TOUCH controller from Plum Sp. z o.o.
- ecoNET300 Home Assistant Integration
- Overview
- Versions
- Example
- Installation
- Configuration
- Entities
- Contributing
- Acknowledgments
- Disclaimer
- v0.3.3 - version is stable. Most of the work was done by @pblxpt, for which we're very thankful as the community.
- v1.0.0 - A development version that retrieves more data from the API. It may be unstable, and upgrades from previous versions are not supported.
Important: This release resets versioning. To upgrade:
- Remove the existing integration.
- Install v1.0.0_beta fresh.
- Reconfigure as instructed below.
- Install and configure HACS.
- Add this repository as a custom repository using:
https://github.com/jontofront/ecoNET-300-Home-Assistant-Integration
- In HACS, search for "ecoNET300", install the integration.
- Restart Home Assistant.
- Download or clone this repository.
- Copy
custom_components/econet300into your<config_directory>/custom_components/.
<config directory>/
|-- custom_components/
| |-- econet300/
| |-- [...]
- Restart Home Assistant.
Integrate ecoNET300 via the user interface:
Manual Configuration Steps
Apart from using 'My button' (in case it doesn't work) you can also perform the following steps manually:
- Go to Settings > Devices & Services in Home Assistant.
- Click Add Integration.
- Search and select "ecoNET300".
- In the bottom right, click on the Add Integration button.
- From the list, search and select "ecoNET300".
- Enter your local device IP/domain and local credentials (not econet24.com credentials). "Submit".
Host: Local IP/domain of your device.
Username: Local username (NOT the username that you use to login to econet24.com!).
Password: Local password (NOT the password that you use to login to econet24.com!).
- Your device should now be available in your Home Assistant installation.
These sensors are retrieved from the ../econet/regParams and ../econet/sysParams endpoints. Below is the list of available entity keys, their descriptions, and the corresponding API endpoint keys:
**👉 Click here to expand the table**
| Entity Key | Description | Endpoint |
|---|---|---|
tempFeeder |
Temperature of the feeder mechanism | ../econet/regParams |
fuelLevel |
Current fuel level in the system | ../econet/regParams |
tempCO |
Current fireplace temperature | ../econet/regParams |
tempCOSet |
Desired fireplace set temperature | ../econet/regParams |
statusCWU |
Status of the hot water (CWU) system | ../econet/regParams |
tempCWU |
Current hot water (CWU) temperature | ../econet/regParams |
tempCWUSet |
Desired hot water (CWU) temperature | ../econet/regParams |
tempFlueGas |
Exhaust temperature reading | ../econet/regParams |
mode |
Current operational mode of the device | ../econet/regParams |
fanPower |
Current fan power usage | ../econet/regParams |
thermostat |
Thermostat status or set temperature | ../econet/regParams |
tempExternalSensor |
Outside (external) temperature | ../econet/regParams |
tempLowerBuffer |
Temperature of the lower thermal buffer | ../econet/regParams |
tempUpperBuffer |
Temperature of the upper thermal buffer | ../econet/regParams |
boilerPower |
Current power output of the boiler | ../econet/regParams |
quality |
Fuel quality or system quality indicator (if applicable) | ../econet/sysParams |
signal |
Signal strength or communication status | ../econet/sysParams |
softVer |
Software version of the controller | ../econet/sysParams |
controllerID |
Unique identifier for the controller | ../econet/sysParams |
moduleASoftVer |
Software version of Module A | ../econet/sysParams |
moduleBSoftVer |
Software version of Module B | ../econet/sysParams |
moduleCSoftVer |
Software version of Module C | ../econet/sysParams |
moduleLambdaSoftVer |
Software version of the lambda module | ../econet/sysParams |
modulePanelSoftVer |
Software version of the control panel | ../econet/sysParams |
These binary sensors are retrieved from the ../econet/regParams and ../econet/sysParams endpoints. Below is the list of available entity keys, their descriptions, and the corresponding API endpoint keys:
**👉 Click here to expand the table**
| Entity Key | Description | Endpoint |
|---|---|---|
lighter |
Indicates if the lighter is active | ../econet/regParams |
pumpCOWorks |
Indicates if the fireplace pump is working | ../econet/regParams |
fanWorks |
Indicates if the fan is currently active | ../econet/regParams |
pumpFireplaceWorks |
Indicates if the fireplace pump is working | ../econet/regParams |
pumpCWUWorks |
Indicates if the hot water (CWU) pump is active | ../econet/regParams |
mainSrv |
Indicates if the main server is operational | ../econet/sysParams |
wifi |
Indicates if the Wi-Fi connection is active | ../econet/sysParams |
lan |
Indicates if the LAN connection is active | ../econet/sysParams |
These number entities are retrieved from the ../econet/rmCurrentDataParamsEdits endpoint. Below is the list of available entity keys, their descriptions, and the corresponding API endpoint keys:
**👉 Click here to expand the table**
| Entity Key | Description | Endpoint |
|---|---|---|
tempCOSet |
Desired fireplace set temperature | ../econet/rmCurrentDataParamsEdits |
tempCWUSet |
Desired hot water (CWU) set temperature | ../econet/rmCurrentDataParamsEdits |
We welcome contributions to improve the ecoNET300 integration! Please follow these steps to ensure your contributions align with Home Assistant's development guidelines:
- Familiarize yourself with the Home Assistant Contribution Guidelines.
- Fork this repository and create a new branch for your changes.
- Write code that follows Home Assistant's Coding Standards.
- Update documentation to reflect any changes or new functionality.
- Open a pull request with a clear description of your changes and reference any related issues.
Thank you for contributing to the Home Assistant community!
Acknowledgments:
- @pblxpt for the original integration code.
- @denpamusic for guidance.
Use at your own risk.
This software is provided as-is, for educational purposes. The authors and contributors hold no responsibility for any harm, data loss, or damage caused by using this integration.