Enode connection missing from Connections, cannot disconnect/reconnect (Jeep Avenger)

Hi,

I use ABRP on iPhone with a Jeep Avenger Summit FWD 18" (2023, electric). My vehicle was connected to ABRP via Enode (Stellantis cloud) plus an OBD adapter.

What happened:

Since 22 October 2026 the odometer coming from Enode has been stuck at 67,418 km, while the SoC kept updating. ABRP uses the Enode odometer even when the OBD adapter is connected, so all my trip logs since then show a wrong odometer. (The stuck data is a Stellantis telematics issue; I have an open case with Jeep.)
On 31 October, following Jeep support's instructions, I changed my Jeep account password. A few days later my Jeep account was locked for "too many failed login attempts". I suspect an integration (possibly Enode) kept trying to log in with the old credentials. I have now set the password back to the original one.
Now, in ABRP:
- "Live data" shows Enode: not connected and OBD: not connected (OBD is expected, the car is parked while I'm abroad).
- In the Connections screen, Enode is not listed, neither under added connections nor under available connections. Only the OBD adapter, Car Scanner and Custom connection are shown.
- So I cannot disconnect and reconnect Enode.

Requests:

Please check why Enode no longer appears for my vehicle and let me re-link it (or reset the existing Enode link on your side).
Could you confirm whether the Enode integration could have caused the repeated failed logins on my Jeep account after the password change?
Feature request: let users choose which source has priority for each data field (for example, odometer from OBD instead of the cloud), so a cloud failure does not corrupt the logs when OBD data is available.

Thanks,
Luca Scarponi