range false reading 2046.0

SAIC-iSmart-API / saic-python-mqtt-gateway

A service that queries the data from an MG iSMART account and publishes the data over MQTT and to other sources

MIT License

72 stars 23 forks source link

range false reading 2046.0 #71

Closed mrniemand closed 7 months ago

mrniemand commented 1 year ago

a few times over a day i get an value of 2046.0 for the /drivetrain/range reading. It happens in last and actual docker version.

nanomad commented 1 year ago

Yeah, those spurious values also appear under power and other fields. Maybe we should have a "sanity check" in place for known false positives.

Edit:

Power is derived as voltage*current/1000 and the spikes in power align with the spikes in voltage/current

So, it seems like:

A value of 4.096 for bmsPackVol is an indicator of a false reading from the BMS and it should be discarded
A value of 65.536 for bmsPackCrnt is an indicator of a false reading from the BMS and it should be discarded

cybersmart-eu commented 1 year ago

What car model do you have? I am since some days now collecting all data in influxDB and did not find any such peak for my MG5 SR Comfort

mrniemand commented 1 year ago

i have an MG4 Luxury, in other countries is think it's the trophy version. I log with FHEM .

octvcdrc commented 1 year ago

Same issue happening here Exact same model : MG4 Luxury/Trophy firefox_jiaM1n34Ay

dudelburg commented 1 year ago

I would like to add the filter for the interior temperature as well - it reports 87 °C some times. Car is MG4 Luxury MY2022.

enrico1036 commented 11 months ago

I'm sure that the temperature problem is visible also on the MG iSmart app. Sometimes it goes exactly to 87°C. BTW would be great if there is a way to recognize those unreal values and discard them instead of showing.

bjoernkowarsch commented 10 months ago

I have never seen strange readings for the range, but for climate I see the 87°C on a regular basis (MG5 LR):

nanomad commented 10 months ago

This is a known issue of the MG infotainment system. The same weird values are show in-car as well at times :(

garthy commented 9 months ago

So I also see this and it makes the graphs somewhat useless.

Can we filter and just throw away these extreme values?

nanomad commented 9 months ago

Definitely, PR are more than welcome

nanomad commented 7 months ago

Fixed in 0.6.1 :)

layanto commented 1 week ago

I still have this issue - range sometimes incorrectly read as 2046km. I use latest Docker Image. Maybe Docker Image has not been updated to include this fix?