EUROTRONIC TRV Valve position helper
Small helper AppDaemon application for EUROTRONIC Z-Wave TRVs.
Maybe other TRVs from EUROTRONIC will work as well.
- allows access to
valve position (%)value from Z-Wave TRVs in Home Assistant
- normally Home Assistant doesn't expose this value (at least in version 0.103)
- periodically reads OpenZWave log file and parses values from there
- this value is useful:
- when you want to monitor what's going on and how well the internal regulation of the TRV performs
- for detection of some conditions that require attention, like when the valve is stuck and not able to move or when the TRV is not able to detect "closed" position of the valve
For successful operation you have to configure your TRV to report valve opening percentage values. Go to your Home Assistant Z-Wave control panel, select TRV Z-Wave node and then in Node Config Options change parameter
Valve Opening Percentage Report to some reasonable value (say 2-5).
This application is suitable for operating the TRV in ordinary "Heat" mode, when the regulation is performed by the TRV itself and Home Assistant only manages the setpoint temperature. The TRV also allows "Manufacturer specific" mode or preset when the internal regulation algorithm is switched off and external system is able to control the valve opening percentage directly. Unfortunately Home Assistant doesn't support this mode (at least in version 0.103) and it's not possible to modify the value even through low-level services (like zwave.set_node_value even with known value_id).
AppDaemon app configuration
eurotronic-trv-valvepos: module: eurotronic-trv-valvepos class: EurotronicTRVValvePos ozw_log_path: "/config/OZW_Log.txt" look_for_productname: "EUR_SPIRITZ Wall Radiator Thermostat" refresh_seconds: 300
||True||string||Module name, should be
||True||string||App class name, should be
||Path to OZW log file, default works in Hass.io|
||Z-Wave product name to look for when searching for TRV Z-Wave device entities, default works for SPIRIT Z-Wave Plus TRV|
||False||integer||300||Seconds between log scans|
Look for errors in AppDaemon log, this application logs all relevant information. You can even turn DEBUG logging on to see a little bit more.
Below is a screenshot from Grafana showing data from one TRV performing its duties.