A comprehensive Home Assistant integration for Kronoterm heat pumps, supporting both Cloud API and local Modbus TCP connections.
- Cloud API: Internet-based connection using Kronoterm mobile app credentials
- Modbus TCP: Local network connection for faster polling and offline operation
- Seamless switching: Reconfigure between modes without losing entity history
- 4 Climate Controls: DHW, Heating Loop 1-2, Reservoir
- Smart Temperature Sensors: Automatically prefers thermostat temperature over loop temperature
- Direct Control: Set target temperatures with instant feedback
- Example: Loop 2 displays room temperature (23.2ยฐC) from thermostat instead of loop outlet temperature (27.8ยฐC)
- 100+ Sensors: Temperatures, pressures, energy consumption, operational hours
- Binary Sensors: Status indicators for pumps, compressor, heating/cooling modes
- Switches: Control system operation, reserve source, additional source
- Number Entities: Adjust temperature offsets and setpoints
- Select Entities: Change operation modes and working functions
- Fast Polling: Configurable update interval (5-600 seconds)
- Energy Dashboard: Full integration with Home Assistant energy tracking
Tested with:
- Hydro S + Adapt 0416-K3 HT / HK 3F
- Other Kronoterm heat pumps with Modbus TCP support
- Open HACS โ Integrations โ โฎ (Menu) โ Custom Repositories
- Add repository:
https://github.com/Favio25/Kronoterm-homeassistant - Category: Integration
- Search for "Kronoterm" and install
- Restart Home Assistant
- Go to Settings โ Devices & Services โ Add Integration โ Kronoterm
- Copy the
custom_components/kronotermfolder to your Home Assistant'scustom_componentsdirectory - Restart Home Assistant
- Go to Settings โ Devices & Services โ Add Integration โ Kronoterm
- Select Cloud API as connection type
- Enter your Kronoterm mobile app username and password
- Configure update interval (default: 60 seconds)
Kronoterm heat pumps use Modbus RTU (RS-485) by default and do not have built-in Modbus TCP support. You need a Modbus RTU to TCP adapter to use local Modbus mode.
Recommended adapters:
- USR-TCP232-410S (Ethernet)
- Elfin EW11 (WiFi option)
- Waveshare RS485-to-Ethernet
- Any RS485-to-TCP converter with configurable serial settings
Adapter configuration:
- Baud rate: 19200
- Data bits: 8
- Parity: None (N)
- Stop bits: 1
- Protocol: Modbus RTU
Once connected, configure the integration:
- Select Modbus TCP as connection type
- Enter your adapter's IP address
- Port:
502(default) - Unit ID:
20(default) - Update interval:
5-600seconds
Finding your adapter's IP address:
- Check adapter documentation (web interface or LED display)
- Or find it in your router's DHCP list
| Feature | Cloud API | Modbus TCP |
|---|---|---|
| Connection | Internet required | Local network only |
| Speed | ~60s refresh | 5-600s configurable |
| Reliability | Depends on cloud | Direct connection |
| Climate Entities | Limited | Full support (4 entities) |
| Sensors | ~80 entities | ~120 entities |
| Offline Operation | โ No | โ Yes |
Switch between Cloud API and Modbus modes without losing entity history:
- Settings โ Devices & Services โ Kronoterm
- Click Reconfigure
- Choose new connection type
- All entity IDs, history, and dashboard references preserved
Modbus climate entities intelligently select temperature sensors:
- Priority 1: Thermostat temperature (room temperature)
- Priority 2: Loop temperature (outlet temperature)
- Result: Shows the most relevant temperature for each loop
Example:
- Loop 1 (no thermostat): Shows loop outlet temperature (38.9ยฐC)
- Loop 2 (with thermostat): Shows room temperature (23.2ยฐC) โจ
Modbus mode supports direct register writes:
- Temperature setpoints via climate entities
- Temperature offsets via number entities
- System control via switch entities
- Verify files are in
custom_components/kronoterm/ - Restart Home Assistant
- Check logs: Settings โ System โ Logs
- Verify credentials match Kronoterm mobile app
- Check internet connection
- Some sensors may show as unavailable (normal)
- Verify IP address is correct
- Check port 502 is accessible (firewall)
- Ensure Unit ID is 20 (default)
- Try pinging the heat pump IP
- Cloud API: Some registers not available via cloud (expected)
- Modbus: Check network connection and unit ID
- Use reconfigure flow to refresh
- Settings โ Dashboards โ Energy
- Add electricity consumption:
sensor.electrical_energy_heating_dhw - Add heat production:
sensor.heating_energy_heating_dhw - View COP/SCOP in real-time
Contributions welcome! Please:
- Fork the repository
- Create a feature branch
- Submit a pull request
Bug reports: Open an issue with:
- Home Assistant version
- Integration version
- Connection mode (Cloud API / Modbus)
- Relevant log entries
- Original integration: Favio25
- Modbus TCP support and climate entities: Community contributions
- Based on Kronoterm official register documentation
This project is licensed under the MIT License - see the LICENSE file for details.
This integration is not officially endorsed by Kronoterm. Use at your own risk.
Supported Models: All Kronoterm heat pumps with Modbus TCP interface
Home Assistant Version: 2023.1.0 or newer
Python Version: 3.11+



