node-zwave-js: Trane XR524 setting incorrect paremeters

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?

  • Configuration Parameters use illegal values
  • Configuration Parameters do not match device settings
  • When Configuration Parameters are changed, they revert back to illegal value

What do you observe? device>>configuration>>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

ALSO 112-0-18 Cooling Delta Stage 1 ON equal 18 I change value to 3 and receive message in log that show value is change From 3 to 18 value is change back from 3 to 18 in zwavejs UI as well 8 is maxValue for this setting

Refresh does not change these result and appears to cause device setting on device to become 0 for value that exceed maxValue

What did you expect to happen? I expect zwavejs value to change to similar option on device Gas/Electric to AC or Heatpump to HP I expect value change in zwaveJS not to revert OR not to allow change to illegal value

Steps to reproduce the behavior:

  1. Go to ‘node’
  2. Click on 'node >> Configuration’s
  3. Scroll down to ‘parameter 18’
  4. change data for parameter and watch it revert to 18, this will occur for many parameter

Device information

Manufacturer: Trane Model name: XR524 Version: 1.38 and 1.14 Node ID in your network: 93 and 58

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: 8.2.1 zwavejs2mqtt branch: 5.5.2 docker image zwavejs/zwavejs2mqtt:5.5.2

Did you change anything?

no

If yes, what did you change?

No response

Did this work before?

No, it never worked anywhere

If yes, where did it work?

No response

Attach Driver Logfile

zwavejs_2021-09-02.log

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 57 (24 by maintainers)

Most upvoted comments

You can’t set preferred scales in Home Assistant. If you need this functionality, you’ll have to switch to Z-Wave JS UI. You can try forcing ZJS to request the temperature in F. Here’s a service call you can copy and paste into Dev Tools Services (switch to YAML mode):

service: zwave_js.invoke_cc_api
data:
  command_class: "49"
  method_name: get
  parameters:
    - 1  # sensorType: Air temperature
    - 1  # scale: F
target:
  entity_id: climate.z_wave_thermostat

Replace target with your device. After sending this command, ZJS should default to F for future requests, as long as the device responds with the value in F and doesn’t report values in C later on.

The service call worked, it updated the current temperature in F. Now i’m waiting for the thermostat to update the temperature to see if it shows up correctly in HA.

I can confirm that a day later it’s still working after sending the service call that one time.

+1
LenirSantiago on Sep 14, 2023
Read more comments on GitHub
← node-zwave-js: Touchscreen Deadbolt Z-Wave Plus no longer reports Keypad unlock notifcations
node-zwave-js: Unable to set setpoint temperature without decimal for Everspring AC301 →