Closed vlycop closed 3 years ago
I get the same error since a few days and the values e.g. for Charge are no longer updating. Interestingly my the Peugeot iOS-App is also no longer updating.
Given the b2c bad development and production environment, I'll just put this as a "PSA server don't want to give you the info you requested, go away"
Did you try the solution number 2 in the FAQ?
i haven't actively encounter it since because i only do my daily commute right now, and don't check that the battery % still work I just encounter a 100% charge when it should have stop a 80%, but browsing the log that far is kind of to much with the number request i do (local, with cache and not to the psa api). So since i didn't do any sms activation in the last 6 month, i don't belive it could be error 2.
Well, I have had this for four days now:
2023-04-23 08:09:56,933 :: ERROR :: 420 : [rights.error.ves.sev.not.stopped.key]
and yes, I did read FAQ, and yes, I did delete the app from the iPhone and reinstalled it. But the app also does not get updates. The data the app shows is consistent with the last update I can see on the controller's log.
Vlycop is right, I believe. The Stellantis servers are notoriously unreliable. I've had these errors intermittently in the past, they went away after a day or so. I believe Stellantis fired their IT department this time...
They are not the only ones. On the news this week was the failure of the system used for repairs to car damage in Belgium. They have not been able to do anything for a week and the cars are piling up at the workshops.
Describe the bug hello, not really a bug but i was wondering if you knew what this error was about. it doesen't look like a "to mqny request" to me
status stuck for 1h and counting ;D To Reproduce Steps to reproduce the behavior:
Config file Give the anonymize content of the config file
Environment (please complete the following information):
Additional context Add any other context about the problem here. i am on the road, will fill later if needed. i don't think this is an issue with the app, but i am looking for what the error mean