#CT101 Thermostat - Can control mode, but not setpoint

1 messages · Page 1 of 1 (latest)

stray sierra
#

Hi folks,

I've got 3 CT101's in my house, one for each floor. I control the 1st and 2nd floor via temp control, so I don't have any critical failures (ie, set temp to 70 when I want heat, 62 when I don't).

When I change the setpoint in HA or NR, the tstat doesn't register the change, and it spits the current setpoint back to me (interface in HA changes back to the original.

However, I am able to turn the heat on and off via Mode.

I have tried re-interviewing, excluding/re-including, excluding/resetting device/including. There is no change in the behavior.

I can change the setpoint at the tstat and it will hold, but the setpoint does not display in ZJS or HA.

I have also tried toggling the "Lock Setpoint Changes" option, which doesn't seem to affect anything.

This snippet is the debug level for ZJS when setting the setpoint. Quickly sends back the 70f report, which is not accurate (currently 66 at the device).

2024-10-28 17:13:21.219 INFO Z-WAVE: Writing 66 to 101-67-0-setpoint-1
2024-10-28 17:13:21.271 INFO Z-WAVE: [Node 101] Value updated: 67-0-setpoint-1 70 => 66
2024-10-28 17:13:21.276 INFO Z-WAVE: Success zwave api call writeValue { status: 254 }
2024-10-28 17:13:26.379 INFO Z-WAVE: [Node 101] Value updated: 67-0-setpoint-1 66 => 70

Please let me know if I can provide more info here, and thanks for reading.

thorny cloak
stray sierra
#

ugh, i didn't save when i updated verbosity

thorny cloak
#

I mean you pasted the wrong logs anyways

#

Those are not driver logs

stray sierra
# 
2024-10-28 17:44:05.727 INFO Z-WAVE: Calling api writeValue with args: [
  {
    nodeId: 101,
    commandClass: 67,
    endpoint: 0,
    property: 'setpoint',
    propertyKey: 1
  },
  66,
  null,
  [length]: 3
]
2024-10-28 17:44:05.730 INFO Z-WAVE: Writing 66 to 101-67-0-setpoint-1
2024-10-28 17:44:05.799 INFO Z-WAVE: [Node 101] Value updated: 67-0-setpoint-1 70 => 66
2024-10-28 17:44:05.803 INFO Z-WAVE: Success zwave api call writeValue { status: 254 }
2024-10-28 17:44:10.905 INFO Z-WAVE: [Node 101] Value updated: 67-0-setpoint-1 66 => 70
2024-10-28 17:44:18.368 INFO APP: GET /assets/Store-DS7bGYpj.css 200 6.422 ms - 787
2024-10-28 17:44:18.372 INFO APP: GET /assets/Store-DmKOivQl.js 200 9.140 ms - 10946
2024-10-28 17:44:18.505 INFO APP: GET /api/store 200 51.458 ms - 30766
thorny cloak
#

Still not driver logs

stray sierra
#

Doesn't seem that anything is registering in the driver logs when i make that change

#

for some reason, everything rebooted when i changed verbosity, not sure if that's normal

#

tstats are 007, 043, 101

#

this log is focused on specific changes

also notable is that my operating state seemed to update right away (as opposed to what that github issue called out)

18:00 (approx. log time) - reinterview
18:02 - change setpoint 1, change setpoint 2
18:04 - change setpoint at tstat to trigger operating state (successful, and showed in interface)

https://paste.debian.net/1333721/

thorny cloak
#

Changing Z-wave settings usually restarts ZUI

#

✅ Driver logs, ❌ Debug

stray sierra
#

are these not the correct logs still?

thorny cloak
#

They are not Debug

stray sierra
#

wtf

thorny cloak
#

You're also using a fairly old version of Z-Wave JS

#

I would upgrade before debugging further

#

For example, I believe errors like this have been fixed since 13.0.0:

2024-10-28T00:06:44.069Z DRIVER   dropping CC with invalid values (Reason: Unsupported scale Percentage value or
                                   corrupted data)
#

You must be using an old version of HA too.

stray sierra
#

yes, been a minute. i will update and re-log

#

update did it. fixed sometime in the last few months of releases. i thought i did it more recently. sorry about that.

thorny cloak
#

Yep, based on the rate of activity in node-zwave-js you were certainly on an "ancient" version.

#

Doesn't help it also happened to be the first major version

stray sierra
#

yeah i saw that. not ideal

#

i was going to go look back at the notes to see how it got broken/fixed... nah

thorny cloak