current now and average incorrect values

[toolsX]

the currentNow shows the correct value for some devices but it shows a large incorrect value for some other devices, also the CurrentAverage works for some devices and for others it shows -2147483648

[umerasrar176]

Hey toolsX !!

Did you find solution for this package or any other suitable package for getting current values. I am still facing same issue with this package.

[toolsX]

Hi, the current average issue is not from the package itself, but with the OEMs, some devices support it and some don’t that’s why it shows the large negative number for sum, but for the current now, for sum users it looks normal and some a large number, it isn’t a an issue with the package too, the reason why this happens is because some devices show the current in milli amperes and some in micro amperes, so for the devices that show it in micro amperes you have to device the number and convert it to milli amperes, there isn’t an app to check which unit the device uses but you can create an if statement and check if the current for example is larger than a big threshold it means it’s using micro then convert it to milli, simple as that.

…

On Thu, 15 Feb 2024 at 7:33 AM Umer Hayat ***@***.***> wrote: Hey toolsX !! Did you find solution for this package or any other suitable package for getting current values. I am still facing same issue with this package. — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AS4OFEN2FO42ZEPQMC4K2S3YTWM23AVCNFSM5IQ5GUN2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJUGU2DAMBVGA3A> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[umerasrar176]

Hey,

Thanks for your quick response and for shedding light on the current issue with the values from package. Your explanation helped me understand why we're seeing varying results across different devices.

I managed to work around the problem by implementing the solution you suggested. It's working like a charm!

I agree that updating the package documentation to explain this would be helpful for other developers. I'll create a PR against this issue soon updating the documentation about values for better understanding.

Thanks again for your help!