zwave-js / node-zwave-js

Z-Wave driver written entirely in JavaScript/TypeScript
https://zwave-js.github.io/node-zwave-js/
MIT License
755 stars 613 forks source link

CT101 thermostat not updating values until 'Refresh' or re-interview is clicked in the UI manually #6938

Open automaton82 opened 5 months ago

automaton82 commented 5 months ago

Checklist

Deploy method

Snap

Z-Wave JS UI version

9.12.0

ZwaveJS version

12.9.1

Describe the bug

For some reason with the latest version of z-wave JS UI, when my thermostat updates the operating state (such as when the AC or furnace come on), there is no update given to z-wave JS UI until either 'Refresh' is clicked, or a re-interview is done manually in the UI. The moment this is done, all values are updated properly.

To Reproduce

Use the CT101 thermostat, join it in a network and then after it's running, change the temperature until it kicks on the furnace or AC. The value for 'Operating State v2' will not update even if you wait indefinitely, nor will the temperature.

Expected behavior

This should update like before.

Additional context

This has happened to me before with earlier versions but it always sorted itself out after re-interviewing. With the latest version nothing I do seems to fix it.

Here's an example log from today:

6/14/2024, 1:57:09 PM - VALUE UPDATED
Arg 0:
└─commandClassName: Thermostat Operating State
└─commandClass: 66
└─property: state
└─endpoint: 0
└─newValue: 2
└─prevValue: 0
└─propertyName: state
6/14/2024, 1:37:39 PM - INTERVIEW COMPLETED
6/14/2024, 1:37:39 PM - READY
6/14/2024, 1:37:39 PM - INTERVIEW STAGE COMPLETED
Arg 0:
Complete
6/14/2024, 1:37:39 PM - INTERVIEW STAGE COMPLETED
Arg 0:
OverwriteConfig

Notice I did a manual re-interview at 1:37pm. At this point, Operating State was Idle. I then kicked on the AC and let it run for about 10 minutes, but z-wave JS UI did not register the change.

I then manually clicked Refresh in the UI which caused the update at 1:57pm and showed the correct value, Cooling.

robertsLando commented 5 months ago

@automaton82 This looks to me like a device issue, does it used to work with previous versions so?

Please make a driver log, loglevel debug and attach it here as a file (drag & drop into the text field).

The log should contain both a re-interview and you doing something that should result in a report.

automaton82 commented 5 months ago

I think you're right, I think it's a CT101 device issue. I think it doesn't push out value updates and must be polled.

Indianb0y016 commented 5 months ago

I can chime in as I have a Ct100 and used to use a CT101. I can confirm that I recently began having issues where the device would send out its temperature values on every change. The fan state would send pretty regularly, with a few times being missed here and there. However, as of late, none of the parameters are receiving updates at all, even with various troubleshooting steps applied. In fact, I am actually running into some other issues with other nodes not having full node data points, like my zooz q sensors. I am investigating a little further and am gonna create a separate issue if needed, but I can assure that the CT100 SHOULD send out temperature updates regularly, including fan state (usually); assuming the associations are configured correctly.

Edit: Turns out the job of identifying the breakers in my house yesterday messed up the nodes, because the network infrastructure and all respective machines were powered down. I troubleshooted the issues I have been dealing with by hard resetting problematic nodes. The Q sensors are working fine now, and the CT100 is reporting temperature changes correctly now, after pressing the reset button.

apella12 commented 5 months ago

fwiw - I have the Ct101 and can verify the issue. It does always report when the room temperature changes, but other items like Op state, fan, etc are hit and miss. I have a poll rule setup based on the room temperature and the hysteresis. For instance if with 1 degree swing and heat if the temp drops 1 degree below the setpoint and the Op state is not Heat after 4 seconds, I poll it. Also basically poll when I change the setpoint, if it doesn't turn on. I keep track of the polls to make sure I'm not flooding the network. It varies by season, but somewhere between 10 and 40 a day are required.

PeteRager commented 5 months ago

Maybe unrelated but I am seeing problems with polling in the latest release, in that after a period of time, polls just get dropped. I'm debugging to see which version the problem starts occurring in.

zwave-js-assistant[bot] commented 4 months ago

This issue has not seen any recent activity and was marked as "stale 💤". Closing for housekeeping purposes... 🧹

Feel free to reopen if the issue persists.

Hilo4321 commented 4 weeks ago

Thought I'd toss a log in here since I was fixing something else, and I see this behavior also.

I'd call out that this does update sometimes, but generally I don't rely on it because it is so sporadic.

I changed the setpoint, waited for the heat to kick on, saw the status didn't update, then refreshed.

Log also contains an interview post update. Ignore log prior to 18:30 (log time) or so. I updated from v13.0 around then.

zwavejs_current.log

Hilo4321 commented 3 weeks ago

@robertsLando sorry for the ping, but I'm not sure how to reopen this. Seems like I don't have permission.

robertsLando commented 3 weeks ago

cc @AlCalzone