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

Incorrect values ​​in battery #594

Open
DickenSerm opened this issue Mar 22, 2024 · 3 comments
Open

Incorrect values ​​in battery #594

DickenSerm opened this issue Mar 22, 2024 · 3 comments
Labels

Comments

@DickenSerm
Copy link

DickenSerm commented Mar 22, 2024

Describe the bug
The data point battery from mine Hue Smart Button fluctuates extremely with its values.

Screenshots & Logfiles
To check, I had a Telegram message sent to me when there was a change:

Schalter Bett.battery => 33
Schalter Bett.battery => 44
Schalter Bett.battery => 41
Schalter Bett.battery => 39
Schalter Bett.battery => 38
Schalter Bett.battery => 39
Schalter Bett.battery => 38
Schalter Bett.battery => 39
Schalter Bett.battery => 38
Schalter Bett.battery => 37
Schalter Bett.battery => 36
Schalter Bett.battery => 35
Schalter Bett.battery => 34
Schalter Bett.battery => 42
Schalter Bett.battery => 39
Schalter Bett.battery => 38
Schalter Bett.battery => 37
Schalter Bett.battery => 38
Schalter Bett.battery => 37
Schalter Bett.battery => 36
Schalter Bett.battery => 38
Schalter Bett.battery => 37
Schalter Bett.battery => 36
Schalter Bett.battery => 35
Schalter Bett.battery => 34
Schalter Bett.battery => 33
Schalter Bett.battery => 34

Before logging, it would occasionally drop to 1% for a short time

Versions:

  • Adapter version: 3.10.2
  • JS-Controller version: 5.0.19
  • Node version: v18.19.1
@mcm1957
Copy link
Member

mcm1957 commented Jul 14, 2024

Please track with curretn version (3.12.0) and add a debug log at time of occurence.
While thre could be a problem with the adapter the device could send faulty data too. So aslong as there is no record of data received it's hard to search for the problem.

@DickenSerm
Copy link
Author

At the time the issue was created, 3.10.2 was current.
I now have 3.11 (stable) and will keep an eye on it.

@mcm1957
Copy link
Member

mcm1957 commented Jul 15, 2024

Thanks and sorry for long time withoput any response.

I know that this issue is ruther old. And there have been several changes in between. But I do not like to close a issue only
because it is old.

Let wait some time and your feedback.

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

No branches or pull requests

2 participants