Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Basic CC currentValue is not exposed despite compat.mapBasicReport: false #6963

Closed
5 of 7 tasks
AlCalzone opened this issue Jun 25, 2024 Discussed in #6946 · 0 comments · Fixed by #6964
Closed
5 of 7 tasks

Basic CC currentValue is not exposed despite compat.mapBasicReport: false #6963

AlCalzone opened this issue Jun 25, 2024 Discussed in #6946 · 0 comments · Fixed by #6964

Comments

@AlCalzone
Copy link
Member

Discussed in #6946

Originally posted by @kjetilsn June 17, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant