Heatit TF016 / TF021 - Basic report

[kjetilsn]

Checklist

• I have read and followed the above instructions

• I have checked the troubleshooting section and my problem is not described there.

• I have read the changelog and my problem was not mentioned there or the fix did not work.

Describe the issue

This relates to older Heatit thermostats TF016 / TF021 which does not report power usage or relay state. In order to calculate power usage we have used the On/Off control group association back to the gateway to get the state. I will admit that I don't know if the "bug" (i guess it is not really a bug) is in Z-wave JS, or in home assistant.
In the past a number entity has been available in home assistant for basic report from the zwave device for knowing the state of the relay. This worked when the on/off association were established between the node and gateway. A while ago this was replaced by a light entity, I suspect this was not intentional, but it worked. However, now there are no entities available for this information, nor is it available as i.e zwave_js.value_updated in the events listener I home assistant. Z-wave JS logs the information, so the node does send it:

2024-06-14T07:22:23.727Z CNTRLR [Node 005] [~] [Basic] currentValue: 99 => 99 [Endpoint 0] 2024-06-14T07:22:23.733Z DRIVER « [Node 005] [REQ] [ApplicationCommand] └─[BasicCCReport] current value: 99 2024-06-14T07:22:23.734Z CNTRLR [Node 005] [~] [Basic] currentValue: 99 => 99

Software versions

Driver (node-zwave-js): 12.10.0

Z-Wave JS UI: 9.13.4.e803879

Device information

Manufacturer: Heatit
Model name: TF016 / TF021
Node ID: 006

Checklist

• I made sure to provide a driver log on level debug.

• The log includes a re-interview of the problematic device (if applicable).

• The log includes the problematic interaction with the device (if applicable).

• I provided the node ID of the problematic device (if applicable).

Upload Logfile

zwave_js.log
zwave_js-a52298b972a36aa7260d504c814976b8-Bad-b2e9f709f4337079d6f4bd0988ee018c.json

[AlCalzone]

Have you tried re-interviewing the device?

[kjetilsn]

I have, no change.
I think it is related to this:
#6485

[AlCalzone]

Please share a log of the re-interview, so I can try to reproduce this.

[kjetilsn]

Thank you for looking into this!

I had a look at the device json file and perhaps found the cause, the value mapBasicReport": false?
Attached is json file and debug log during re-interview.

"state": { "nodeId": 6, "index": 0, "installerIcon": 4608, "userIcon": 4608, "status": 4, "ready": true, "isListening": true, "isRouting": true, "isSecure": false, "manufacturerId": 411, "productId": 1, "productType": 1, "firmwareVersion": "1.8", "zwavePlusVersion": 1, "name": "Bad", "location": "**REDACTED**", "deviceConfig": { "filename": "/usr/src/app/store/.config-db/devices/0x019b/tf016_tf021.json", "isEmbedded": true, "manufacturer": "Heatit", "manufacturerId": 411, "label": "TF016 / TF021", "description": "Z-Wave Thermostat", "devices": [ { "productType": 1, "productId": 1 }, { "productType": 3, "productId": 513 } ], "firmwareVersion": { "min": "0.0", "max": "255.255" }, "preferred": false, "associations": {}, "paramInformation": { "_map": {} }, "compat": { "mapBasicReport": false

re_interview.txt
zwave_js-a52298b972a36aa7260d504c814976b8-Bad-b2e9f709f4337079d6f4bd0988ee018c (2).json

[AlCalzone]

Can you try using Z-Wave JS UI for the logging?
I see only half the log contents - no outgoing commands, no incoming commands. Only the responses from the stick itself.
Something is filtering or dropping information from the log.

[kjetilsn]

Please see z-wave js us log file below:

zwavejs_2024-06-24.log

[AlCalzone]

Same thing (also there's no interview in that log). Please check what you have here in the settings. It should be empty.

[kjetilsn]

That is strange, I have the same setting, no spesific node selected:

[AlCalzone]

You're looking at the wrong section (General instead of Z-Wave)

[kjetilsn]

Changed from "debug" to "silly":
zwavejs_2024-06-24_b.log

[kjetilsn]

This is strange, after repeatadly re-interview and turning on and off logging I now have the basic light entity!
I tried to replicate on another device, first re-interview in HA, then in Zwave-js UI, restarted HA each time to no success, however when turning on logging in Zwave JS UI (which seem to restart Zwave-JS), then re-interview seems to solve it. Sorry for wasting your time, I guess there are no errors here

[kjetilsn]

Aha,
I'm doing most things wrong today it seems. Yes there were a filter for a single node..
I now slowly get one by one working by repeatably restarting zwave-js and doing re-interview just after restart, weirdly this works.
zwavejs_2024-06-24_d.log

[AlCalzone]

Thanks - I'll try to reproduce anyways, since there's still something that bothers me.

[kjetilsn]

Ok, thank you very much!

[AlCalzone]

escalated to an issue: #6963

[kjetilsn]

Hello again,
I updated to latest docker containing v12.12.1 and updated latest HA docker as well, hoping that would be the solution.
Still the problem remains. Actually the few nodes where I got the basic light entity back are now gone again, and don't come back when doing interview and restart. attached a fresh log of interview.

re_interview_e.txt

[AlCalzone]

Can you double check what you see in Z-Wave JS UI? There's also a new option to export a node dump from the driver, this would also be helpful.

[kjetilsn]

Thank you.
What specifically should I check in Z-Wave JS UI? The Basic v0 values does update.
Attached is the dump of the node I previously shared the interview log for.
node_9_dump.json

[AlCalzone]

Ok then I think you'll just have to wait a bit and update HA. These values will be exposed as sensors, not light entities in 2024.7.0b0:
home-assistant/core#105134

[kjetilsn]

Thank you,
I will wait for next release and test then.

[kjetilsn]

Hello again,

Just wanted to report that my issue is now solved with the new basic sensor entities with the latest version of home assistant, thank you very much for fixing this!