Zwave JS sets Trane XR524 thermostat value equal parameter number

Configuration Z-Wave
1

Wondering if other having similar issue.

I have (2) Trane XR524 thermostat using V1.14 and V1.38 software for that unit
I find that when looking at conguration parameters in both zwaveJS and HA the values shown is same as the parameter number

EXAMPLE
In Device Info >> Configure Device >> Parameter 18 Cooling Delta Stage 1 ON value is 18
maximum value for the parameter is 8

In Device Info >> Configure Device >> Parameter 19 Cooling Delta Stage 1 OFF value is 19
maximum value for the parameter is 8

I set these on device so this appear to be display problem and not magically setting value incorrectly
just cant determine if this is zwave js or HA integration issue. Zwave js does not show these values or show “custom” so seems HA just showing as placeholder

2

It’s possible the device doesn’t send a state update when you change the parameter on the device, therefore the state of the device and the driver would be out of sync. To correct it, you would need to refresh the configuration parameters. You can do this from zwavejs2mqtt’s control panel, but not HA.

Are you using zwavejs2mqtt? It’s not clear what you are referring to when you say “both zwaveJS and HA”.

3

zwavejs in docker 8.1.1 , websocket
HA in docker 2012.8.8, not supervised

When values are updated for these devices in zwavejs they are not retained.
I change them to default but they will be returned to the previous value after “value updated” appears.
“Refresh” did not change this.

device values were greatly changed. I change back and zwavejs reflects a change but to wrong values.
Wonder if underlying definitions are wrong for device? I will check in spec. They work well with openzwave so I not expect them to have problem

4

Found that zwave js mappings are wrong.

For example:

device>>configuration>>58-112-0-1
Options in zwavejs are

  • 0 Gas/Electric (default)
  • 1 HeatPump

option in Trane 524 menu are

  • none
  • AC
  • HP

if i select AC on Trane, [1]HeatPump is selected in zwaveJS
if i select [1]HeatPump in zwaveJS, AC is slected on Trane

5

The definitions of the configuration parameters are identical to open-zwave. It’s likely that Z-Wave JS even imported their configuration from OZW. So that shouldn’t explain the differences between OZW and ZJS.

OZW parameter 1:

    <Value genre="config" index="1" label="System Type" max="1" min="0" size="1" type="list" units="" value="0">
      <Help></Help>
      <Item label="Gas/Electric" value="0"/>
      <Item label="HeatPump" value="1"/>
    </Value>

Z-Wave JS parameter 1:

		"1": {
			"label": "System Type",
			"valueSize": 1,
			"minValue": 0,
			"maxValue": 1,
			"defaultValue": 0,
			"allowManualEntry": false,
			"options": [
				{
					"label": "Gas/Electric",
					"value": 0
				},
				{
					"label": "HeatPump",
					"value": 1
				}
			]
		},

If you are using zwavejs2mqtt you can set the config parameter values manually. Maybe you can try that and see if they are programmed as you would expect.

6

I just checked this and notice both openzwave and zwavejs is the same. In fact I consider that even if that value is true, it not explain why the numeric values displayed in zwavejs (after refresh) revert to values that exceed “maxValue” and coincidentally match the parameter number

EXAMPLE
112-0-18] Cooling Delta Stage 1 ON equal 18
I change value to 3 and receive message in log

2021-09-02 00:06:03.929 INFO ZWAVE: Writing 3 to 58-112-0-18
2021-09-02 00:06:03.971 INFO ZWAVE: Success zwave api call writeValue undefined
2021-09-02 00:06:05.016 INFO ZWAVE: Node 58: value updated: 112-0-18 3 => 18

I also receive toast message “Value change” but immediately it is change in display to “18”
When I check unit the value is normally changed to “0” but I’d need to verify again. I assume this “0” is input since max value is “8”

As a note, all actions and everything I check is in the zwavejs UI. with openzwave integration these config parameters could not be changed so maybe this was not noticeable issue for me then. Now that parameters are changeable it seems to create issue where device settings are change to undesired values.

7

I would agree that something is wrong if the device is returning values that seem to be illegal, and also not what was programmed.

At this point I think your best option is to submit a bug report to the node-zwave-js project. If the config parameters are incorrect, they would be fixed there.

You will want to enable the z-wave driver debug logs and capture some logs. I would capture a) a Re-interview of the device, then b) Setting some of the troublesome config parameters. The log file can be downloaded from the zwavejs2mqtt UI and you can attach it to the issue (follow the instruction in the bug report).

8

I also have two XR524 Thermostats running the 1.38 firmware. Although I haven’t gotten very far in looking into the interactions of HomeAssistant and the thermonstat, I have noticed the current temperature doesn’t get updated.
For example, my upstairs thermostat currently shows the temperature is 24, even though it is more like 75. But the air temperature reads as 75.2…but has read as that since installing. (all of these readings are what HomeAssistant shows, but not what shows on the physical thermostat)
Have any of you noticed similar issues with your thermostats?
In relation to the above issues, my values are showing the same. It almost seems like parameters above 15 show the parameter number as their value rather than an actual value.

9

Did you ever find a fix? I have a xr524 and its reading low on the thermostat and the air temperature is also 2-3 degrees than it reads on the actual unit.

10

In zwavejsui you can set the default to Fahrenheit

Try changing temperature offset in zwavejs, HA or on the device. This adjust measured temp by small amount to adjust for difference in sensor and room