I've added your BZ4X's VIN to the Sidecar offline decoding matrix, so it should correctly decode again in the next Sidecar release (shipping early next week). You might need to remove the vehicle and re-add it for it to pick up the change.
at the moment i have problems with my ride registration. start and end point do not match anymore.
I don't fully understand what you mean by the start and end point matching; do you mean the trip logger is not starting and stopping trips when you expect it to?
at the moment i have problems with my ride registration. start and end point do not match anymore.
I don't fully understand what you mean by the start and end point matching; do you mean the trip logger is not starting and stopping trips when you expect it to?
Yes exactly!
Start point and end point is not the location where I actually started and stopped.
@Jefbos90 Sidecar v1.18 includes the bZ4X VIN decoding fix; can you confirm that your car is getting decoded as the right kind of vehicle now in the app? You might need to remove and re-add the offline vehicle using your VIN to test this flow (you won't lose any data associated with the VIN when you do this).
@Jefbos90 ah I also realized we haven't confirmed that the BZ4X_HVBAT_SOC parameter works in your car yet. Are you getting accurate state of charge values when connected with an OBD scanner in Sidecar?
@Jefbos90 Sidecar v1.18 includes the bZ4X VIN decoding fix; can you confirm that your car is getting decoded as the right kind of vehicle now in the app? You might need to remove and re-add the offline vehicle using your VIN to test this flow (you won't lose any data associated with the VIN when you do this).