core: Missing Manufacturer Specific mode and valve control for Aeotec TRV

The problem

Currently, climate entity exposes only Heat and Off modes and three presets for Aeotec Thermostat Radiator Valve (ZWA021).

However, Aeotec TRV supports a third mode, namely Manufacturer Specific, which allows direct valve control. Enabling this should expose a new entity (dimmer or cover type) allowing 0-100 / 0-255 valve control of the TRV.

When using Zwavejs2mqtt via mosquitto broker and mqtt integration, this third mode can be enabled by adding the following code in the ZWJS2M control panel - with fan_only: 31 being used to set the TRV to Manufacturer Specific

  "mode_map": {
    "off": 0,
    "auto": 1,
    "fan_only": 31

.......

  "discovery_payload": {
    "min_temp": 8,
    "max_temp": 28,
    "modes": [
      **"off",
      "auto",
      "fan_only"

........

    "mode_state_template": "{{ {0: \"off\",1: \"auto\",31: \"fan_only\"}[value_json.value] | default('off') }}",

This lets the user set the thermostat in Manufacturer Specific mode and control the valve position via a separate light dimmer entity. This allows to move the valve logic from the controller level up to HA level and allows the user to create more useful and precise automations for the TRV.

I know that the Zwave-js integration is at its beginning, but it would be useful if we could replicate this functionality via the Z-wave JS integration, without having to depend on a mqtt broker.

Environment

HA core-2021.2.0b1 supervisor-2021.01.8 Z-Wave JS addon 0.1.1

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 2
  • Comments: 22 (5 by maintainers)

Most upvoted comments

@MartinHjelmare this is not about config parameters.

Just further clarify, in open zwave beta these thermostats in my case the eurotronic spiritz enumerated with a valve position attribute that could be read in any mode. The configuration of the device includes a parameter for setting the report period based on the %change of the valve.

And then in manufacturer specific mode that attribute becomes the only mechanism to set the valve %.

I use the valve % to calculate heat demand in my house, which in turn activates the boiler to provide the heat.

So it’s going to be a little colder this week, and looking at the weather forecast it is going to be quite a bit cooler, with snow ❄️ on the weekend!

Attached. Rename to .jsonl zwave_js_dump.txt