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 |
|---|---|---|
 |
 |
 |
The ecoNET300 Home Assistant Integration allows local control and monitoring of ecoNET300 devices directly from Home Assistant. It communicates over your local network via the ecoNET-300'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
- Dynamic Entity Creation: 165+ entities auto-discovered from your boiler's menu (v1.2.0+)
- Boiler Control: Turn your boiler ON/OFF directly from Home Assistant
- Real-time Monitoring: Monitor temperatures, fuel levels, and system status
- Comprehensive API Access: Access to 80+ API endpoints
- Multiple Entity Types: Sensors, Binary Sensors, Calendars, Events, Switches, Select, and Number entities
- Parameter Locking: Device-side locks reflected in Home Assistant UI
- Repair Issues: Automatic connection failure detection with one-click fix
- Diagnostics Support: Download diagnostics with core API data plus optional RM/
editParamssnapshots (v1.2.5+)
The integration supports 6 languages with comprehensive translations:
| Language | Code | Status | Coverage |
|---|---|---|---|
| 🇬🇧 English | en |
✅ Complete | Base language |
| 🇵🇱 Polish | pl |
✅ Complete | Full translation |
| 🇨🇿 Czech | cs |
✅ Complete | 348 parameters |
| 🇫🇷 French | fr |
✅ Complete | 876 parameters |
| 🇺🇦 Ukrainian | uk |
✅ Complete | 855 parameters |
- ecoMAX810P-L TOUCH controller from Plum Sp. z o.o.
- ecoMAX850R2-X pellet boiler controller
- ecoMAX360 boiler controller
- ecoMAX860P2-N boiler controller
- ecoMAX860P3-V boiler controller
- ecoSOL 500 solar collector system controller
- ecoSOL 301 solar controller (flat
regParams/T1,P1, …) - ecoSOL solar thermal controller
- SControl MK1 control module
- Other ecoNET300 compatible devices
- Installation
- Upgrading
- Configuration
- Entities
- Diagnostics
- Documentation
- Versions
- Contributing
- Support
- 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/. - Restart Home Assistant.
v1.2.0+ introduces significant new features including 165+ dynamic entities, parameter locking, and the repair issues system. No manual migration is required — your existing configuration keeps working.
After upgrading:
- Restart Home Assistant
- Check Settings → Devices & Services → ecoNET300 for new entities
- New CONFIG category entities are disabled by default — enable as needed
Integrate ecoNET300 via the user interface:
Enter your local device Host (IP/domain) and local credentials — not your econet24.com cloud login.
After setup, open Settings → Devices & Services → ecoNET300 → Configure to adjust connection settings, polling intervals, device grouping, custom entities, and to generate diagnostics reports.
Tip: For better graph granularity, lower the regParams polling interval in Polling settings (default 15s, minimum 5s).
📖 Complete Configuration Guide — manual setup steps, polling, device grouping, and custom entities.
The integration provides multiple entity types:
| Type | Count | Description |
|---|---|---|
| Sensors | 50+ | Temperature, status, alarms |
| Binary Sensors | 25+ | Pumps, fans, connections, alarms |
| Calendars | 1-20 | Weekly heating schedules per component |
| Events | 1 | Boiler alarm triggered / cleared |
| Switches | 1 | Boiler ON/OFF control |
| Select | 1+ | Heater mode, dynamic parameters |
| Number | 15+ | Temperature setpoints |
Starting with v1.2.0, the integration automatically discovers 165+ additional entities from your boiler's remote menu via the mergedData API endpoint, with automatic type detection, category grouping, parameter locking, and mixer/ecoSTER support.
📖 Complete Entity Reference — full list of all entities with descriptions.
Related usage guides:
- Heating Schedules — display weekly schedules as calendar entities
- Alarms & Events — alarm monitoring and push notifications
- Fuel Consumption — track total fuel usage with the Riemann Sum helper
The integration includes comprehensive diagnostics support to help troubleshoot issues. Downloads include coordinator data, core endpoint snapshots, and extended snapshots (v1.2.5+): RM endpoints plus optional editParams, with automatic sensitive-data redaction.
To download: Settings → Devices & Services → ecoNET300 → Download diagnostics. For a one-click triage report (useful for GitHub issues, heat pumps, and controller variants), use Configure → Generate diagnostics report.
📖 Complete Diagnostics Documentation
All documentation lives in the docs/ folder. Start here:
| Guide | Description |
|---|---|
| Configuration | Configure menu, polling, device grouping, custom entities |
| Migration | Upgrading between versions |
| Entities | Complete entity reference |
| Heating Schedules | Display schedules as calendar entities |
| Alarms & Events | Alarm monitoring and automations |
| Fuel Consumption | Track total fuel usage |
| Boiler Control | Boiler ON/OFF switch behavior |
| Diagnostics | Diagnostics and troubleshooting |
| Guide | Description |
|---|---|
| API v1 Documentation | Complete API documentation (80+ endpoints) |
| API Construction Guide | How API requests are built |
| Dynamic Entity Validation | Dynamic entity system (v1.2.0+) |
| New API Endpoints | Newly discovered endpoints |
| Device | Description |
|---|---|
| ecoMAX810P-L | Most feature-rich pellet controller |
| ecoMAX360 | Boiler / heat pump controller |
| ecoSOL 500 | Solar collector controller |
| ecoMAX850R2-X | Pellet boiler controller |
| ecoSOL Discovery | ecoSOL line discovery summary |
| Guide | Description |
|---|---|
| Architecture | High-level integration architecture |
| Developer Tools | Scripts and tooling |
| Cloud Translations | Translation references and workflow |
- Schedule Calendar entities: heating, mixer, and hot-water schedules are now native Home Assistant Calendar entities instead of text-based sensors.
- Configurable polling and device grouping: tune polling intervals per endpoint, and choose split (default) or single device grouping — via the options flow.
- Health diagnostics:
Data age,Consecutive failures,Last successful update, and aLive pollingconnectivity sensor. - More heat-pump / Phoenix sensors and an
editParamscatalog of editable parameters. - Cleaner entity list: duplicate boiler-output sensors removed (running-state binary sensors kept), and registration/config values moved to Diagnostics.
Upgrading? Old
*_scheduletext sensors and a few removed duplicate sensors may show as Unavailable — delete them manually. See the Migration guide.
📖 Full Changelog — complete version history and release notes.
We welcome contributions! Please feel free to submit a Pull Request. For major changes, please open an issue first to discuss what you would like to change.
- Fork the repository
- Create a feature branch
- Make your changes and test thoroughly
- Submit a pull request
See the Architecture and Developer Tools guides to get started.
- @jontofront - Current maintainer and developer
- @pblxpt - Original developer and maintainer up to v0.3.3
- @KirilKurkianec - Contributor and supporter
- ecoNET300 Community - For testing, feedback, and support
- Plum Sp. z o.o. - For creating the ecoNET300 system
This integration is not officially affiliated with or endorsed by Plum Sp. z o.o. Use at your own risk. The developers are not responsible for any damage to your equipment or system.
If you encounter any issues or have questions:
- Check the Documentation
- Search existing Issues
- Create a new issue with detailed information about your problem (attach a diagnostics report when possible)
This README was last updated on 2026-07-01 for v1.3.0.