Temp. setpoint VS Heltun HEL_THERM_FL2

Configuration Z-Wave
1

No way to set temperature setpoint
Try:

service: climate.set_temperature
data:
  temperature: 11
target:
  entity_id: climate.wall_heating_thermostat

Result:

Stopped because an error was encountered at * ***** 2021 г., 12:53:32 (runtime: 0.01 seconds)
**Value requested is not available**

Traceback:

Traceback (most recent call last):
  File "/snap/home-assistant-snap/420/lib/python3.8/site-packages/homeassistant/components/websocket_api/commands.py", line 185, in handle_call_service
    await hass.services.async_call(
  File "/snap/home-assistant-snap/420/lib/python3.8/site-packages/homeassistant/core.py", line 1491, in async_call
    task.result()
  File "/snap/home-assistant-snap/420/lib/python3.8/site-packages/homeassistant/core.py", line 1526, in _execute_service
    await handler.job.target(service_call)
  File "/snap/home-assistant-snap/420/lib/python3.8/site-packages/homeassistant/helpers/entity_component.py", line 213, in handle_service
    await self.hass.helpers.service.entity_service_call(
  File "/snap/home-assistant-snap/420/lib/python3.8/site-packages/homeassistant/helpers/service.py", line 658, in entity_service_call
    future.result()  # pop exception if have
  File "/snap/home-assistant-snap/420/lib/python3.8/site-packages/homeassistant/helpers/entity.py", line 830, in async_request_call
    await coro
  File "/snap/home-assistant-snap/420/lib/python3.8/site-packages/homeassistant/helpers/service.py", line 695, in _handle_entity_call
    await result
  File "/snap/home-assistant-snap/420/lib/python3.8/site-packages/homeassistant/components/climate/__init__.py", line 586, in async_service_temperature_set
    await entity.async_set_temperature(**kwargs)
  File "/snap/home-assistant-snap/420/lib/python3.8/site-packages/homeassistant/components/zwave_js/climate.py", line 451, in async_set_temperature
    setpoint: ZwaveValue = self._setpoint_value(
  File "/snap/home-assistant-snap/420/lib/python3.8/site-packages/homeassistant/components/zwave_js/climate.py", line 214, in _setpoint_value
    raise ValueError("Value requested is not available")
ValueError: Value requested is not available

Same result, when activated from lovelace, or from NodeRED.
Similiar devices work well throw MIOS Vera integration.

Environment

snap info home-assistant-snap
installed:           2021.10.6             (420) 421MB -

snap info snap info zwavejs2mqtt
installed:          v5.10.0            (237) 157MB -
2

Quite from zwavejs2mqtt debug output:

 {
      "id": "41-67-0-setpoint-1",
      "nodeId": 41,
      "commandClass": 67,
      "commandClassName": "Thermostat Setpoint",
      "endpoint": 0,
      "property": "setpoint",
      "propertyName": "setpoint",
      "propertyKey": 1,
      "propertyKeyName": "Heating",
      "type": "number",
      "readable": true,
      "writeable": true,
      "label": "setpoint (property)",
      "ccSpecific": {
        "setpointType": 1
      },
      "stateless": false,
      "min": 0.5,
      "max": 40,
      "unit": "°C",
      "list": false,
      "value": 14.5,
      "lastUpdate": 1635766517605,
      "newValue": 14.5
    },
3

Who know, what is “undefined”, when setpoint called from ZwavwJS CP?

{
nodeId: XX,
commandClass: 67,
endpoint: 0,
property: 'setpoint',
propertyKey: 1
},
12.5,
{},
[length]: 3
]
2021-11-08 11:44:05.504 INFO ZWAVE: Writing 12.5 to 46-67-0-setpoint-1
2021-11-08 11:44:05.622 INFO ZWAVE: Success zwave api call writeValue undefined
4

@Tmorfus did you find a solution for this issue? I’m having same kind of error with my Qubino thermostat. I cannot set temperature for it. Previously I haven’t got any issue with it. When trying to set temp it gives me an error “Value requested is not available”.

Also it’s controls doesn’t look that good. I think it only has one setpoint and no hi/low setpoints at all.

image
image413×506 16.8 KB

Found a bit similar issue from HA Github Aeotec Radiator Thermostat ZWA021-C presets not registering properly · Issue #46127 · home-assistant/core · GitHub
From that I realized to look at developer tool and saw that my thermostat has “target_temp_high: null”. Other temperature values has numbers.

developertool
developertool991×188 14 KB

I think we need to raise this as an issue at HA Github if no other solutions are available.

5

issue #59479 opened 22 days ago.
It’s not looks like Aeotek case. Aeotec can’t lookup for preset mode, Heltun (and possiblr - Qubino) - for SetpointType.

I don’t have a solution for now, only workaround - use direct API calls throw MQTT.

6

Yes. It fixed.
It merged into master today.
Only for MQTT integration.

I haven’t fixed the WS integration, I don’t use it, and I don’t have much time.
But I will now describe the essence of the problem in an opened issue.