ha-remocon

Unofficial Home Assistant integration for Elco heat pumps via the Remocon-Net cloud service.

HACS Custom Open your Home Assistant instance and open a repository inside the Home Assistant Community Store.

Control and monitor your Elco heat pump (e.g. Aerotop SPK) through the Remocon-Net cloud API — directly in Home Assistant, no MQTT or AppDaemon needed.

Disclaimer: This is an unofficial community project. It is not endorsed by or affiliated with Elco or the Ariston Thermo Group.

• Climate entity — Set target temperature, switch operation mode (Auto / Heat / Off), presets (Comfort / Reduced)
• Sensors — Outside temperature, flow temperature, target temperature, system pressure
• Binary sensors — Heating active, cooling active, heat pump running
• Config flow — Easy setup directly in the Home Assistant UI
• CLI tool — Standalone remocon.py for testing and debugging from the terminal

• Elco heat pump with a Remocon-Net gateway (connected to the internet)
• Remocon-Net account (remocon-net.remotethermo.com)
• Home Assistant >= 202410
• HACS installed

1. Open HACS in Home Assistant
2. ≡ Menu → Custom Repositories
3. Add:
   • URL: https://github.com/macschlingel/ha-remocon
   • Category: Integration
4. Search for "Remocon-Net" in HACS and install
5. Restart Home Assistant

cd /path/to/homeassistant/config/custom_components/
git clone https://github.com/macschlingel/ha-remocon.git elco_remocon_temp
cp -r elco_remocon_temp/custom_components/elco_remocon ./
rm -rf elco_remocon_temp

Restart Home Assistant.

1. Go to Settings → Devices & Services → Add Integration
2. Search for "Remocon-Net"
3. Enter your credentials:
   • Email: Your Remocon-Net login email
   • Password: Your Remocon-Net login password
   • Gateway ID: Your system's gateway ID (see below)
   • Zone: Heating zone (default: 1)

1. Log in at remocon-net.remotethermo.com
2. The gateway ID is shown in the URL, e.g. A1B2C3D4E5F6 in:

   https://www.remocon-net.remotethermo.com/R2/Plant/Index/A1B2C3D4E5F6
   

After setup, the following entities are created:

The climate entity supports:

• HVAC modes: Heat (Comfort), Auto (time program), Off (frost protection)
• Presets: Comfort, Reduced
• Temperature: Adjustable within the range configured on the heat pump

A standalone CLI tool is included for testing and debugging:

pip install -r requirements.txt
# Create config
cp config.example.json config.json
# Edit config.json with your email, password and gateway ID
# Check status
python3 remocon.py --config-file config.json status
# Set temperature
python3 remocon.py --config-file config.json set-temp --comfort 22.0
# Change mode
python3 remocon.py --config-file config.json set-mode comfort
# Raw API response (debug)
python3 remocon.py --config-file config.json raw-get
# JSON output (for scripting)
python3 remocon.py --config-file config.json status --json

• Cloud-dependent: Control goes through the Remocon-Net cloud. No control possible during internet outages.
• Polling: Data is fetched every 2 minutes (no real-time streaming).
• No room sensor: If no room thermostat is connected, current_temperature shows the target value.
• DHW read-only: Domestic hot water entities are displayed, but DHW control is not yet available through the HA entity (works via CLI).

The integration uses the same API as the Elco Remocon-Net web app:

• Login: Cookie-based authentication via /R2/Account/Login
• Data: R2 Web API (/R2/PlantHomeBsb/GetData/) + v2 REST API (/api/v2/remote/dataItems/)
• Control: v2 REST API (/api/v2/remote/bsbZones/, /api/v2/remote/bsbPlantData/)
• Platform: remotethermo.com (Ariston Thermo Group)

Contributions are welcome! Please open an issue or submit a pull request.

MIT