Non CVE units support
The Itho Wifi add-on module of Arjen exists in two versions:
- CVE (originally supported cases)
- Non-CVE (HRU-350 / DemandFlow / QualityFlow / HRU Eco Fan)
This wiki entry covers the Non-CVE version as the control of these units is different. A key difference is the lack of 'speed' as a way to control the device.
Make sure you have the right add-on before continuing.
- QualityFlow / DemandFlow: it is not possible to control per room speeds (e.g. high for bathroom and low for a bedroom).
- Setting 'Auto' is not yet supported
The Itho Daalderop HRU-350 is a WTW (heat recovery unit) device and typically deployed to provide balance ventilation where one or more RFT-CO2 sensors are deployed throughout the house. In addition the unit can use humidity sensor input to automatically adjust air flow.
Unlike the CVE unit, the add-on can be connected via a straight UTP cable and the device does not need to be opened. This means however that the add-on is exposed and not shielded against dust or accidental damage. The recommendation is to put it in an enclosure, e.g. a 3D printed case.
To install the add-on, perform the following steps:
-
Locate the COM port on the left of the HRU unit labeled with 'COM'.
-
Put a UTP (CAT 5E will do) cable of sufficient length into the HRU unit
-
Connect the other side of the cable to the add-on's RJ45 port
-
Verify that the add-on turned on by confirming the lights on the RJ45 socket should flash.
Warning
The connector looks like a network connector but it is not. Do NOT connect the cable to a network port, power over Ethernet(PoE) port etc. only to the service/COM port of your Itho device.
The configuration of this add-on is similar to the CVE one with the notable exception that 'speed' parameter is not used. See here for configuration.
Itho devices other than the HRU-200 and CVEs seem not to support the PWM command via the I2C bus. These are basically all itho devices that need the non-cve add-on. This also means the slider on the frontpage and certain API commands won't work.
To control the speeds of these units you can use the 'vremote' (Virtual remote). A Virtual Remote is a physical remote emulated in software and works just like a physical remote. All normal remote commands are available like low, medium or high and timer. This is supported via the Web API, MQTT or via the web interface or via Home automation software. As of firmware version 2.4.0-alpha4 there is an explanation of the different API options related to this on the API page of the add-on.
| Label | Value | Description |
|---|---|---|
| temp | 0 | temperature from connected temp sensor |
| hum | 0 | humidity percentage from connected sensor |
| ppmw | 0 | absolute humidity in mg/kg |
| ReqFanspeed | 0.5 | Requested fan speed based on mode |
| Balance | 0 | |
| supply_fan_requested | 1142 | |
| supply_fan_actual | 1147 | Speed in RPM for air intake |
| exhaust_fan_requested | 762 | |
| exhaust_fan_actual | 760 | Speed in RPM for exhaust fan. This is around 1100 in low, 2000 in medium and 3200 in high |
| supplyTemp | 16.79 | |
| exhaustTemp | 13.45 | Outdoor temperature |
| status | 0 | |
| RoomTemp | 16.79 | Room temperature |
| OutdoorTemp | 13.45 | Outdoor temperature |
| Valve_position | 0 | |
| Bypass_position | 0 | Bypass indicator |
| Summercounter | 0 | |
| Summerday | 0 | Summer day |
| FrostTimer | 0 | Frost Timer |
| BoilTimer | 177 | |
| StartCounter | 120 | |
| CurPosition | 0 | |
| VKKswitch | 0 | |
| GroundHeatExchangerSwitch | 0 | |
| AirCounter | 2550 | |
| Global_fault_code | 0 | |
| Actual_Mode | 24 | 1 = Low, 2 = Medium, 3 = high, 24 = Automatic |
| pir_fan_speed_level | 65535 | |
| Highest_received_CO2_value | 645 | Highest CO2 received via RTF CO2 sensors |
| Highest_received_RH_value | 239 | |
| Air_Quality | 100 | Static value of 100? |
| Remaining_override_timer | 0 | Duration in seconds .... |
| Fallback_speed_timer | 0 | |
| Exhaust_Constant_Ca0 | 2 |