SoC is at 0% in ABRP

[Str1atum]

Since upgrade to 2.0 via docker my SoC on ABRP website and app is always at 0%.
Log output shows no obvious problem:

2023-12-13 12:55:05: [INFO] Data object successfully sent: {'utc': 1702472104, 'soc': 0, 'power': 0, 'speed': 0, 'lat': XXX, 'lon': XXX, 'elevation': 0, 'is_charging': False, 'is_dcfc': False, 'is_parked': True, 'est_battery_range': 130.55, 'ideal_battery_range': 136.73, 'ext_temp': 6.0, 'model': '', 'trim_badging': '', 'car_model': 'tesla:my:22:mylr_22:perf:heatpump', 'tlm_type': 'api', 'voltage': 0, 'current': 0, 'heading': 330}

[fetzu]

Hello @Str1atum,

First of, kinda unrelated to your issue, did you remove the "odometer" key of the object above?

Second of all, there's indeed something wrong, but that's not nearly enough information to help me debug this:

1. Could you please check that TeslaMate's MQTT is working properly and sending the "right" value for the SoC? (see an example of it here; teslamate/cars/1/usable_battery_level is the topic you are looking for; it should not be 0.)
2. Can you revert to the previous release (using "fetzu/teslamate-abrp:1.4.0" as a Docker image) and tell me if the SoC is being reported properly?

[Str1atum]

I just tried a reboot of my server and now it's working again - sorry for the bothering

[fetzu]

No worries, I’m glad it works ;).