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

Battery icon is showing level "unknown" but level is 100% #2845

Closed
3 tasks done
kpine opened this issue Dec 14, 2022 · 7 comments · Fixed by #2860
Closed
3 tasks done

Battery icon is showing level "unknown" but level is 100% #2845

kpine opened this issue Dec 14, 2022 · 7 comments · Fixed by #2860
Labels
bug Something isn't working

Comments

@kpine
Copy link
Contributor

kpine commented Dec 14, 2022

Checklist

  • I am not using Home Assistant. Or: a developer has told me to come here.
  • I have checked the troubleshooting section and my problem is not described there.
  • I have read the changelog and my problem is not mentioned there.

Deploy method

Docker

Z-Wave JS UI version

8.6.0.01c659b

ZwaveJS version

10.3.1

Describe the bug

The battery icon for a node is showing "unknown", but the battery level exists at 100%. Screenshot:

image

To Reproduce

Not sure, it might be specific to this device and how the interview went.

Expected behavior

Battery icon should be correct.

Additional context

The only interesting thing I can think of is that the initial interview failed to Get the battery level, as there was a command timeout. However, after interview a Battery Report was sent, which triggered a 'value added' event (visible in debug info). You can see this in the attached inclusion logs.

zwavejs_current.log

Node Debug info:

debug.json.txt

@kpine kpine added the bug Something isn't working label Dec 14, 2022
@robertsLando
Copy link
Member

I think that restarting application fixes the issue, right?

@kpine
Copy link
Contributor Author

kpine commented Dec 14, 2022

Let me try to reproduce tomorrow and I'll report back. This is one of my test systems, so I already tore it down to report some other issues. 😅

@robertsLando
Copy link
Member

Let me know :)

@robertsLando
Copy link
Member

News on this ?

@kpine
Copy link
Contributor Author

kpine commented Dec 24, 2022

Nope, not sure how to reproduce. So there's no clue as to what may have caused it?

@robertsLando
Copy link
Member

I have a feel the problem is:

Not sure, it might be specific to this device and how the interview went.

ATM I don't really like how this is handled internally, I'm going to rewrite the logic soon

@kpine
Copy link
Contributor Author

kpine commented Dec 27, 2022

OK. Feel free to close the issue for now, if you'd like.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants