-
-
Notifications
You must be signed in to change notification settings - Fork 246
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
Vehicle Position Data Not Updating in Home Assistant Integration #956
Comments
Did you use eevee in the past to get it working? #975 I have the same behaviour |
Yes, I did use Eevee in the past, and it worked very well. However, since they switched to a subscription model, it hasn’t worked as smoothly as before. Now, I only receive updates in my Home Assistant map intermittently. |
Yes so that confirms my suspicion that after a while stellantis stops sending detailed data via the API. Don't know why 3rd party applications enable to stellantis to sent these responses back. @flobz is there any change we can have similar responses back, without paying for e.g Eevee? |
It’s likely they had to cover costs for accessing vehicle position data from Stellantis, which could have contributed to their shift to a subscription model. This aligns with their announcement, where they cite increased licensing fees and a growing user base as factors behind the change. Their full statement is here. |
Describe the bug
The integration with Home Assistant stopped updating the vehicle's position. Other features (e.g., preconditioning) are still working correctly. Accessing the endpoint
http://127.0.0.1/get_vehicleinfo/[VIN Number]
shows the last position date as 31/08/2024, even though the preconditioning date updates correctly to the current date.To Reproduce
updated_at
date does not reflect the current date.Expected behavior
The vehicle's position should update with the current date and time.
Vehicle Info
http://127.0.0.1/get_vehicleinfo/[VIN Number]
"updated_at": "2024-08-31 20:03:38+00:00"
"updated_at": "2024-09-14 10:26:39+00:00"
Additional context
The text was updated successfully, but these errors were encountered: