haithowifi
haithowifi copied to clipboard
Home Assistant custom component for Itho Wifi add-on integration
Table of Contents
- Home Assistant sensor component/integration for Itho Wifi
- What can be configured via this Integration
- Fan entity
- Differences with the add-on's Home Assistant MQTT Discovery
- Use-case
- Advanced configuration
- Available entities
- Why don't I see all entities?
- What can be configured via this Integration
- Installation
- Prerequisites
- Install via HACS (recommended)
- Manual install
- Screenshots
- Help us improve!
Home Assistant sensor component/integration for Itho Wifi
This integration for Home Assistant provides a configuration screen for the MQTT based "Itho Wifi add-on" from https://github.com/arjenhiemstra/ithowifi This simplifies the integration by creating the sensors for the various Itho Daalderop devices: Heatpump WPU 5G, HRU units, CVE boxes, Autotemp units for floor heating.
This custom component has no affiliation with the Itho Daalderop company or with Arjen Hiemstra's Itho WiFi add-on.
What can be configured via this Integration
- Autotemp sensors with up to 10 autotemp rooms using custom room names instead of Room 1, Room 2
- Heatpump WPU sensors
- CVE sensors
- NON-CVE / HRU sensors
- Up to 5 remotes for monitoring CO2 levels for CVE/NON-CVE (HRU) with custom names.
Fan entity
The integration creates a Fan entity for several devices which can be used to control the speed and/or mode. Currently the following devices and actions are provided:
CVE / HRU ECO 200
| HA action | Device action |
|---|---|
| Set % | Sets % |
| Turn on | Sets preset mode to High |
| Turf off | Sets % to 0 |
| Preset mode* | Sets to corresponding preset mode |
* Supported preset modes are Low, Medium, High, Timer 10, Timer 20, Timer 30
[!NOTE] Setting Fan preset mode works as fire-and-forget
The CVE / HRU ECO 200 don't provide information on their current preset. Setting a preset from a physical (RF)remote is currently impossible to know for the integration.
HRU ECO 250/300
| HA action | Device action |
|---|---|
| Turn on | Sets preset mode to High |
| Turf off | Sets preset mode to Auto |
| Preset mode* | Sets to corresponding preset mode |
* Supported preset modes are Low, Medium, High, Auto, Auto (night), Timer 10, Timer 20, Timer 30
[!NOTE] Setting Fan preset mode works as fire-and-forget
The HRU ECO 250/300 don't provide information on their current preset. Setting a preset from a physical (RF)remote is currently impossible to know for the integration.
HRU ECO 350
[!IMPORTANT] Requires a successfully paired virtual remote
Mediumpreset requires a virtual remote that provides this mode, for exampleRFT CO2
| HA action | Device action |
|---|---|
| Turn on | Sets preset mode to High |
| Turf off | Sets preset mode to Auto |
| Preset mode* | Sets to corresponding preset mode |
* Supported preset modes are Low, Medium, High, Auto, Auto (night), Timer 10, Timer 20, Timer 30
Differences with the Itho WiFi add-on Home Assistant MQTT Discovery
Custom autotemp roomnames and CO2 remote names are also unique to this integration.
Additional differences include the translations in Dutch, support for other Itho devices besides a fan, value translations for e.g. status.
Use-case
This integration should eliminate the manual creation via YAML of sensors for:
- Non-CVE (HRU) like Actual mode, Supply Temp, Supply / Exhaust RPM, Bypass
- CVE like Humidity, Temperature, Speed
- Autotemp like Power kW, Power %, Set Point Temp, Actual Temp per Room
- CO2 concencration for supported remotes
- WPU like Pump Percentage, Boiler Temp, From / To Source Temps, Operating Mode etc
Advanced configuration
The integration has an option for advanced configuration. This can be enable during setup which allows for the customization of one or more of the following settings:
- MQTT base topic
- Prefix used for the created entities
- Device name
This can be used to created multiple Home Assistant integration entries for the same device-type (for example, for users with multiple CVE's). Or just if you want to customize the entry to your own liking.
Available entities
The integration creates a device and sensors and uses a predefined MQTT state topic to distinct the devices. At first only a (by the authors) selected group of entities will be created. If you want to create all available entities for your device, you need to re-configure the integation entry:
Navigate to integrations and find the Itho WiFi Add-on. Click the three dots of the entry you want edit:
Click Reconfigure and reconfigure the created entities
Why don't I see all entities?
Some sensor are disabled by default. Follow these instructions to enable an entity.
Click xx entities not shown within the device or just navigate to the entity directly
Click the cogwheel icon
Click enable
Installation
Prerequisites
- Working WiFi add-on connected to the Itho device(s) (buy)
- Official HA MQTT Integration configured and connected to the MQTT broker.
- In the Itho WiFi add-on under 'MQTT' the
MQTT base topicshould be configured like the table below (or use the advanced configuration to customize): - Home Assistant MQTT Discovery under 'MQTT' configuration in the add-on should be set to Off (default) if your fan is supported via this integration.
| Device | MQTT base topic |
|---|---|
| Autotemp | ithotemp |
| CVE | ithocve |
| HRU | ithohru |
| WPU | ithowpu |
Install via HACS (recommended)
- Install HACS by following these steps
- Search for "Itho wifi" and download the integration.
Manual install
- Using a HA file editor like
Studio Code ServerorFile Editor, create a folder /usr/share/hassio/homeassistant/custom_components/ithodaalderop - Git clone this repository or download the content to custom_components in the /usr/share/hassio/homeassistant/custom_components/ithodaalderop directory
- Restart Home Assistant
- Go to Integrations
- Search for Itho Add-on integration
- Add an entry for each device
Screenshots
Add integration
Define remotes for CO2 monitoring
Define rooms for autotemp
Created devices
Created HRU sensors and two remotes
CVE sensors
Autotemp Control Unit + Connected Sensors
Advanced configuration
Help us improve!
As we don't own all Itho devices ourselves, we don't always know the exact meaning and usage of an available sensor. You can help us improve the integration by providing feedback about:
- Translations
- Binary sensors. When a sensor provides only binary data (on/off, open/close, ...)
- Should a sensor be within the 'selected' group of sensors
- Should a sensor be enabled by default
- ...
Feel free to create an issue!