What's new
By:

bug I found on energy usage

V

vishnumrao

Member

Joined
Sep 29, 2026
Messages
15
Reaction score
4
Cars
Gravity
I have had this happen twice . See pic of the energy usage screen. The battery percentage glitches and gets back to real value.

Anyone else have this?
 

Attachments

  • 101643.webp
    101643.webp
    2.3 MB · Views: 48
vishnumrao said:
I have had this happen twice . See pic of the energy usage screen. The battery percentage glitches and gets back to real value.

Anyone else have this?
Click to expand...
I think I've seen it in the car's reporting through its cloud API.
Unfortunately just another software glitch.
 
Ok glad its not just me. I hope its not some battery voltage / SoC reading sensor issue that reports a high value intermittently.
 
vishnumrao said:
Ok glad its not just me. I hope its not some battery voltage / SoC reading sensor issue that reports a high value intermittently.
Click to expand...
I see it in other data from the car. Hard to say if it's:

a: bad data read in the car and getting sent to Lucid
b: Lucid's cloud/API filling in missing data with invalid values
c: The HA app misinterpreting data from the Lucid API.
 
doubletwist said:
I see it in other data from the car. Hard to say if it's:

a: bad data read in the car and getting sent to Lucid
b: Lucid's cloud/API filling in missing data with invalid values
c: The HA app misinterpreting data from the Lucid API.
Click to expand...
The OP 's post was a screenshot from the car, so it would appear to be a software bug in the BMS.
 
DeaneG said:
The OP 's post was a screenshot from the car, so it would appear to be a software bug in the BMS.
Click to expand...
Thats right. It was a pic taken of the screen on the Gravity.

My thought /is that
1. There is a bug in the BMS leading to overly optimistic or overly conservative range projections leading to poor road trip experiences.
2. There is a faulty sensor giving erroneous readings.
3. Maybe I worry for nothing and its purely a benign SW bug and I should not worry about it!
 
vishnumrao said:
Thats right. It was a pic taken of the screen on the Gravity.

My thought /is that
1. There is a bug in the BMS leading to overly optimistic or overly conservative range projections leading to poor road trip experiences.
2. There is a faulty sensor giving erroneous readings.
3. Maybe I worry for nothing and its purely a benign SW bug and I should not worry about it!
Click to expand...
Interesting glitch. Curious if it is still there. Brings back memories(nightmares) of programming 8 bit microprocessor's as the glitches look like 256.
 
bicycleguy said:
Interesting glitch. Curious if it is still there. Brings back memories(nightmares) of programming 8 bit microprocessor's as the glitches look like 256.
Click to expand...
In think they are 255 and a simple benign bug.
 
doubletwist said:
I see it in other data from the car. Hard to say if it's:

a: bad data read in the car and getting sent to Lucid
b: Lucid's cloud/API filling in missing data with invalid values
c: The HA app misinterpreting data from the Lucid API.
Click to expand...
this is likely what the problem is (probably a. where bad data gets obtained and the delta is weird. Happens all the time in data networking throughput graphs for various reasons
 
Interesting that Lucid doesn't have logic to discard these anomalies. One of the wonderful community members recently submitted a PR for the Home Assistant integration that does exactly this.
 
Please do me a favor and send that to swfeedback

That’s definitely a fixable bug
 
You must log in or register to reply here.
Back
Top