node-zwave-js: Air temperature doesn't refresh on Eurotronics Spirit radiator valves

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?

NO, my problem is NOT within Home Assistant or the ZWave JS integration

Is your problem within ZWaveJS2MQTT?

NO, my problem is NOT within ZWaveJS2MQTT

Checklist

Describe the bug

What causes the bug? I use those devices since about 2 years and hadn’t much troubles yet. About 6 month ago I did migrate from Open Z-Wave to Z-Wave JS (V0.1.45 currently) in combination with Z-Wave JS to MQTT. I’m not quite sure if the problem exists since the migration, or if it is caused by an update.

What do you observe? When I started to use my heating again I noticed that the air temperature wasn’t accurate anymore. In fact my HA Z-Wave setup does not refresh those values anymore. When I go to to the Z-Wave JS to MQTT Dashboard I can manually refresh the values and they get accurate then. What did you expect to happen? The sensor data should get updated regularly. Steps to reproduce the behavior:

  1. Go to ‘MQTT Z-Wave Dashboard’
  2. Click on ‘a Eurotronic Valve’
  3. Scroll down to ‘Multilevel Sensor’ and refresh the Air Temperture
  4. See that the value gets updated now.

Device information

Manufacturer: Eurotronics (Manufacturer ID: 0x0148) Model name: Spirit Node ID in your network: 7 (example dump)

How are you using node-zwave-js?

  • zwavejs2mqtt Docker image (latest)
  • zwavejs2mqtt Docker image (dev)
  • zwavejs2mqtt Docker manually built (please specify branches)
  • ioBroker.zwave2 adapter (please specify version)
  • HomeAssistant zwave_js integration (please specify version)
  • pkg
  • node-red-contrib-zwave-js (please specify version, double click node to find out)
  • Manually built from GitHub (please specify branch)
  • Other (please describe)

Which branches or versions?

version: node-zwave-js branch: HA version: 0.1.45, version 8.4.1 zwavejs2mqtt branch: : HA 0.27.0 version 8.4.1

Did you change anything?

no

If yes, what did you change?

No response

Did this work before?

Yes (please describe)

If yes, where did it work?

It did work with Open Z-Wave beta, but I’m not sure if it did with Z-Wave JS in a previous version.

Attach Driver Logfile

{
  "id": 7,
  "name": "Tstat Salon Entree",
  "loc": "Salon",
  "values": [
    {
      "id": "7-49-0-Air temperature",
      "nodeId": 7,
      "commandClass": 49,
      "commandClassName": "Multilevel Sensor",
      "endpoint": 0,
      "property": "Air temperature",
      "propertyName": "Air temperature",
      "type": "number",
      "readable": true,
      "writeable": false,
      "label": "Air temperature",
      "ccSpecific": {
        "sensorType": 1,
        "scale": 0
      },
      "stateless": false,
      "unit": "°C",
      "list": false,
      "value": 21.58,
      "lastUpdate": 1634825645858,
      "newValue": 21.58
    },
  
  "productLabel": "Spirit",
  "productDescription": "Thermostatic Valve",
  "manufacturer": "Eurotronics",
  "firmwareVersion": "0.15",
  "protocolVersion": 3,
  "zwavePlusVersion": 1,
  "zwavePlusNodeType": 0,
  "zwavePlusRoleType": 7,
  "nodeType": 1,
  "endpointsCount": 0,
  "endpointIndizes": [],
  "isSecure": "unknown",
  "supportsSecurity": false,
  "supportsBeaming": true,
  "isControllerNode": false,
  "isListening": false,
  "isFrequentListening": "1000ms",
  "isRouting": true,
  "keepAwake": false,
  "maxDataRate": 100000,
  "deviceClass": {
    "basic": 4,
    "generic": 8,
    "specific": 6
  },
  "deviceId": "328-1-3",
  "status": "Alive",
  "interviewStage": "NodeInfo",
  "statistics": {
    "commandsTX": 95,
    "commandsRX": 75,
    "commandsDroppedRX": 0,
    "commandsDroppedTX": 0,
    "timeoutResponse": 0
  },
  "lastActive": 1634900408260,
  "batteryLevel": 95,
  "_name": "Tstat Salon Entree (Salon)"
}

Here the log file plus some debug logs about node 7. It shows that the regular polling includes Air temp but does not update the value. But after a manual refresh it does it. log_MQTT_21-07.txt zwavejs_2021-10-25.log

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 27 (9 by maintainers)

Most upvoted comments

That parameter setting according to the manual should be a multiple of 0.1, 5 (default) being 0.5 degree and 1 being 0.1 degree change. Mine automatically reports the temp when it is set to 1 (0.1) but not when it is set to the default 5 (0.5) and temperature report only changes if I manually poll it.

image