Someone earlier in the thread posted to add the following … but just wondered what this does?
http://127.0.0.1:5000/get_vehicleinfo/YOURVIN?from_cache=1
Also … I do have the re-authenticate every few days … when my status become unknown/unavailable … is there any resolution to fixing that?
Hello,
I am trying to add a Peugeot to this integration, but I am struggling with finding the OAUTH2 code described like this:
, it only describes a redirect at my side. I have tried FireFox and Chrome browser developer mode. Is it still possible to set up this integration, or has anything changed on the Stellantis side?
It also a possibility to run the python script ( GitHub - benbox69/stellantis-oauth-helper: This tool simplifies the OAuth2 flow for Stellantis services by dynamically loading configurations and providing a user-friendly interface. ), but guidance to do this, is much appreciated.
As you can see, the redirect try to open a native mobile app and get error (because you dont have it on your desktop), from this redirect copy the auth code and paste it on integration config flow 
Did someone already check this integration with EVCC?
You need to press OK and then fetch the code.
Thank you very much, now i finally got it!
I only found it by persevering (after giving up several times). I think you need to be pretty quick on the consol after pressing OK otherwise the API seems to get rejected as invalid when you try to use it.
The positive is that it doesn’t seem to need to be updated - giving the hassle in getting it in the first place it would make the integration pretty useless.
It’s a real shame that Stellantis don’t provide an easy way to get the data from the car in a proper API like other car makers do - I can understand possible security concerns about remote opening doors through an API (although this could be tied down with a little effort), but to just provide real-time non-writable data, which is all most people are interested in anyway, should be pretty easy to do.
Having said that, given the quality of the Stellantis stable apps, it’s probably a big ask.
They are going to need to watch out as more things become integrated and more people want to automate tasks - the likes of BYD are going to be snapping at their heels as their software is streets ahead.
I have got the 2 wake-up automations in place and they seem to be working OK.
The issue I’m still having is the sensors are still not being updated with any sort of regularity. Seems OK during the day (even if the car is being driven), but at night, when charging, updates on the Battery Residual and SOC seems erratic.
Just tested an automation to charge and 7.4 kW going through the charger didn’t move the SOC% or residual for about 15 minutes, I went to the app and refreshed data (as that hadn’t updated dynamically either) then a couple minutes later the SOC jumped to 84%. The wake-up button command was triggered every 5 minutes during this period and the ‘time to 100%’ sensor was updating dynamically too - seems very odd, anyone got any idea’s or similar experience?
I have somewhat similar experiences that the car (citroen e-c4) is just not always properly communicating changes back to the app/ha integration. For what I’ve seen on the GitHub issues this depends probably on the brand/type of car, where this connection appears to be more stable than for other brands/types…
To summarize you have done what you can afaik and this is as “good” as it gets…
After a month or so, Home Assistant issued a notification saying the authorisation needed to be refreshed - could have cried because it took a couple of months of trying and giving up to find it from the console (If I’m missing something obvious, please someone, educate me!!).
Came across @Marius_Stensrod post mentioning the python script on GitHub. I have tried doing various things in the past with Python - some worked, some didn’t and don’t really understand what I am doing but was determined to persevere this time.
Finally got it working using a venv in Windows 11 - in the end pretty simple with help from the AI.
Steps were to install Python using PowerShell, create a Virtual Enviroment using ‘python -m venv .venv’. change to the .venv directory (had to hunt around for it) then run ‘.venv\Scripts\Activate.ps1’. There was a security error message - to allow the script to run, I had to enter: ‘Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser’ then run the Activate.ps1 script again.
You’ll know it works as .venv with preface the terminal prompt.
Followed the instructions from https://github.com/benbox69/stellantis-oauth-helper, it took a few seconds, screen to select brand and county appeared, then the signing screen. Once signed in, click on ‘OK’ then a dialogue box with the code appears.
Hey! I have a few questions:
So I have a Corsa-e with a 50 kWh battery and the API shows it’s 41. Will all these false kWh claims be fixed in the near future? Also what is “Service Battery” ? It’s obviously not the traction battery, might be my 12v which probably needs changing (it shows 70% 
)
Thanks!
I have had to re-autenticate with the oauth code every other day for the past 3 weeks … is anyone else getting the same difficulty?
Not oauth requests but the integration is no longer providing battery information (since 16:47 30 June). Tried reloading and restarting but no success. Integration is still connected to the car as the horn will beep is the button is pressed. Wonder if the api fields have changed?
Anyone else experienced this? Car is a Vauxhall Combo electric.
Thanks, saw that this morning. I’ve now installed the new beta and looks to be working great with the charging limit number and switch working too (always greyed out previously). Can test charging sensors as the car is being driven ATM but first impression look great.
Thanks for your hard work and time on this.
Hellp
the intégration ask for a pin code, but i have no pin code entered on apps. it’s for Citroen eC3 car.
Thanck
Can anyone tell me how the charging limit works - apart from the obvious, lol!
What’s confused me is that I can’t see any options for charging limit on the (pretty dire) Vauxhall app so am really surprised (and pleased) it’s on the integration.
Does it relate to a setting on the car that for some reason best known to themselves, Vauxhall have decided to keep from users and if so, is it reliable? Or, is it a setting within the integration that turns the charging off automatically by telling the car to stop charging when reached - ie: akin to an automation as it relies on the integration to trigger a change.
Currently I use automations to prevent charging above 80% normally but they are a bit clunky and have timeout’s in place as historically, I have frequent periods where SOC, residual etc are not updated consistantly but if this charging limit is a setting on the car’s OS then that would provide a more fool proof way to limit charging - and remove some complexity from my massive HA automation files!
Any thoughts anyone?
Can’t speak for Citroen specifically but for the Vauxhall app, you need to enter a (4 digit?) PIN periodically and when setting up the app. It’s probably a sensible security feature as you don’t really want unauthorised people unlocking your car etc!
As the integration leverages the app for it’s API, I assume this needs to be passed to the Stellantis server before any meaningful data is passed in either direction.
You mean battery capacity? That’s the capacity left from the original 50, this means your battery’s health is ~90% or so which is also availalble as the SoH sensor.
The other battery is the 12V service battery which goes up and down as systems are used (e.g. remote control, …) but is regularly charged via the traction battery (e.g. when driving or charging the traction battery)
