Skip to content

Renault: HTTP-Session im SoC-Abruf wiederverwenden, Kilometerstand optional behandeln - #3849

Merged
benderl merged 1 commit into
openWB:masterfrom
seaspotter:fix-renault-soc-session
Aug 25, 2026
Merged

benderl merged 1 commit into
openWB:masterfrom
seaspotter:fix-renault-soc-session

Conversation

@seaspotter

@seaspotter seaspotter commented Aug 24, 2026 •

Copy link
Copy Markdown
Collaborator

Bisher wurde für jeden der 7 Requests im Login-/Abrufablauf (Gigya-Login, Kamereon-Daten) eine neue Session erzeugt, wodurch Cookies nicht über den Ablauf hinweg erhalten blieben und der SoC-Abruf bei manchen Accounts komplett fehlschlug. Jetzt wird eine einzige Session für den gesamten Ablauf verwendet.

Zusätzlich wird der Kilometerstand (Cockpit-Daten) jetzt mit try/except abgefangen, da nicht jedes Fahrzeug diesen Wert liefert – ein Fehlschlag dort verhindert nicht mehr den Abruf von SoC und Reichweite.

Fixt: #3409 (comment)

…ckpit odometer

req.get_http_session() created a fresh session (and cookie jar) for every one
of the 7 requests in fetch_soc(), breaking Renault's Gigya/Kamereon login
chain for some accounts and causing SoC reads to fail entirely. Reuse a
single session for the whole flow instead.

Also guard the cockpit odometer lookup: some vehicles don't report mileage,
and odometer is already optional on CarState, so a missing/failing cockpit
response should no longer take down the SoC/range read with it.
@benderl
benderl merged commit 9ea0d3c into openWB:master Aug 25, 2026
1 check passed
@seaspotter
seaspotter deleted the fix-renault-soc-session branch August 25, 2026 06:15
Brett-S-OWB pushed a commit that referenced this pull request Sep 2, 2026
…ckpit odometer (#3849)

req.get_http_session() created a fresh session (and cookie jar) for every one
of the 7 requests in fetch_soc(), breaking Renault's Gigya/Kamereon login
chain for some accounts and causing SoC reads to fail entirely. Reuse a
single session for the whole flow instead.

Also guard the cockpit odometer lookup: some vehicles don't report mileage,
and odometer is already optional on CarState, so a missing/failing cockpit
response should no longer take down the SoC/range read with it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants