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

Z-Wave JS not updating meter values for Heat-it Z-TRM3 #46175

Closed
depthchargex opened this issue Feb 7, 2021 · 8 comments
Closed

Z-Wave JS not updating meter values for Heat-it Z-TRM3 #46175

depthchargex opened this issue Feb 7, 2021 · 8 comments

Comments

@depthchargex
Copy link

depthchargex commented Feb 7, 2021

The problem

Thermofloor Heatit Z-TRM3 not updating energy meter values unless forcing node refresh values or reinterview using ZwaveJS2mqtt UI.

Have 4 units and all show the same behavior. None of my other devices with meter capability are displaying these issues and update their values fine.

What is version of Home Assistant Core has the issue?

core-2021.2.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Zwave JS

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zwave_js

No response

Example YAML snippet

# Put your YAML below this line

Anything in the logs that might be useful for us?

# Put your logs below this line
@probot-home-assistant
Copy link

zwave_js documentation
zwave_js source
(message by IssueLinks)

@raman325
Copy link
Contributor

@depthchargex are you still having issues with this? If you are not seeing updates, but you expect to, that may be something to report upstream to node-zwave-js. Also, we now have a refresh_value service which can be used to poll the values if you are still not seeing updates. Although it's not recommended because it could flood your network, you are free to create automations to call the service automatically for you

@depthchargex
Copy link
Author

depthchargex commented Mar 17, 2021

Hey @raman325 thanks for answering. Yes, I'm still having problems with the energy meter not updating unless manually refreshed. I'll try your workaround for creating the service call, refreshing it every 5 or 10 minutes is enough for me.

Would I need to create a new issue to report it upstream or can I or a admin convert this ticket or send it to the correct place? This is the first time I have done the process so not sure about the procedures.

@quack3d
Copy link

quack3d commented May 9, 2021

Like mentioned in #45932 I also have this issue but with HeatIt Z-TRM2fx.

@raman325
Copy link
Contributor

raman325 commented May 9, 2021

Hey @raman325 thanks for answering. Yes, I'm still having problems with the energy meter not updating unless manually refreshed. I'll try your workaround for creating the service call, refreshing it every 5 or 10 minutes is enough for me.

Would I need to create a new issue to report it upstream or can I or a admin convert this ticket or send it to the correct place? This is the first time I have done the process so not sure about the procedures.

You would need to create a new issue because it's in a different project (zwave-js).

Before you do, just to confirm, you get entities for these meters right? Do you see any value updates in your logs for the meter information? If not, it's definitely an upstream issue. If you are seeing value updates in the logs but you don't see the update in HA, that is likely an HA issue.

@Molodax
Copy link

Molodax commented Jun 8, 2021

To get the updates, you need to adjust parameter "Temperature report hysteresis" to e.g. 1 instead of default "10".

@quack3d
Copy link

quack3d commented Jun 9, 2021

@depthchargex Did you by any chance include this device in OZW prior to ZwaveJS? I had corrupt associations on my Z-TRM2fx that prevented meter from updating. I deleted one with target endpoint 1 and everything started working.

@depthchargex
Copy link
Author

hey @sepodele, I did add before but I also did remove and add them again after the JS switch. I'll close this ticket though as the workaround suggested by Raman325 works really well.

At some point in the future I may change the parameters as suggested @Molodax, but probably not until after the summer.

@github-actions github-actions bot locked and limited conversation to collaborators Jul 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants