-
-
Notifications
You must be signed in to change notification settings - Fork 259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After upgrade from 3.3.1 to 3.3.2 trips, position or charges don't get registered anymore. #744
Comments
I tried http://192.168.0.91:3000/get_vehicleinfo/VF3M4DGZUPSxxxxxx from a browserwindow and it gives an Internal Server Error.
|
Hi, I have observed the same issue, the database info.db isn't updated anymore with version 3.3.2. As soon as I downgrade to version 3.3.1 is see that database is updated again. |
The issue might be related to this error message TypeError: 2024-02-05T13:08:40.454181+01:00 mdha02-n psa-car-controller[1666030]: 2024-02-05 13:08:40,452 :: DEBUG :: vin:VINxxxxxxxxxxxxxx longitude:x.xxxxx latitude:yy.yyyyy date:2024-02-05 11:36:51+00:00 mileage:20672.5 level:27.0 charge_date:2024-02-05 11:37:47+00:00 level_fuel:None moving:False |
It seems fixed to me, in the sense that the error again no longer "crashes" the program. I again have a similar error as with v3.3.1
happy to close this bug and have this error as a new one if that's the preference. |
ok, I just realized the error is due to me not have set up the "paid" plan for openweathermap. not the cleanest error message, but that's irrelevant. |
Describe the bug
After upgrade from 3.3.1 to 3.3.2 trips, position or chargings don't get registered anymore.
To Reproduce
Steps to reproduce the behavior:
Upgrade from 3.3.1 to 3.3.2 via docker
what command did you use
docker-compose stop psa, docker-compose pull psa; docker-compose up -d psa
when the bug append ?
After the update
Does it persist after restarting the program?
Yes
Does it persist after recreate config by going to http://server_address:port/config?
not tried, but downgrading to 3.3.1 again solves the issue. It ran fine for days again, I gave the 3.3.2 another go, same issue again.
Config file
Environment (please complete the following information):
this is what I get in 3.3.1
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: