You are reading a single comment by @Cyyyy and its replies.
Click here to read the full conversation.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@Cyyyy
Thank you for your helpful response!
I've been closely monitoring my battery levels, especially considering my specific usage pattern. To provide more context, my usage primarily involves requesting an accelerometer reading once a second (with Puck.accel()) and utilizing the LED lights as status indicators.
The LED lights are used solely as status indicators to reflect the activation or deactivation of certain functions in my code. This is achieved through specific button presses of varying lengths, which then trigger LED patterns and colors to signify the enabled functions.
Overall, my usage scenario involves relatively light activity, with the accelerometer readings and LED indicators (on button presses, which don't happen often) active for about 1-2 hours a day at most.
Despite this usage pattern, I've noticed a significant discrepancy in the battery readings provided by E.getBattery(). According to it, my battery seems to be depleting quite rapidly, dropping from 100% to 40% in just around 6-7 days.
While I understand that E.getBattery() is an estimation, I find it a bit extreme for the battery to deplete from 100% to 40% in such a short span of time - even if its just a rough estimation. I'm currently using LiCB CR2032 batteries purchased from Amazon. Could you kindly confirm if E.getBattery() is accurate to indicate how much % is left in the battery in scenarios like mine or if there might be other factors influencing the readings? Your insights would be immensely helpful!
EDIT: My Battery Charge just drained from 40-45% yesterday over night down to 15%.. without actively executing any code. Something is really weird.
Greetings,
Cyyy