3.7.5 - OTP reports success but activation_finalize returns NOK:FORBIDDEN (remote control unavailable)

[guydl012]

Environment

• PSA Car Controller: 3.7.5
• Installation: Home Assistant Add-on
• Home Assistant: 2026.7.1
• Supervisor: 2026.06.2
• Brand: Opel
• Vehicle: Opel Corsa-e (2023)

Description

After upgrading to PSACC 3.7.5, vehicle data is still retrieved correctly, but Remote Control no longer works.

The Control page remains empty (no charge/preconditioning controls).

Steps performed

1. Updated PSACC to 3.7.5.
2. OTP initially failed with NOK:MAXNBTOOLS.
3. Uninstalled and reinstalled the myOpel application.
4. Reset the Opel account trusted devices (all device associations were removed).
5. Logged back into myOpel.
6. Re-ran the OTP configuration from PSACC.

The UI displayed a success message.

However, remote control is still unavailable.

Relevant logs

log.txt

remote_refresh_token isn't defined

Error during activation finalize:
{'err': 'NOK:FORBIDDEN'}

Please redo otp config

start_remote_control failed redo otp config:
Error during activation finalize: {'err': 'NOK:FORBIDDEN'}

Charge control not setup check your PSACC configuration and logs

Later:

Can't refresh remote token please wait...
Rate limit exceeded for get_otp_code

Can't configure MQTT Client

Vehicle authentication still works correctly:

Your vehicles:
corsa-e

App version 3.7.5

GET /get_vehicleinfo/... 200

### Observed behaviour

- OAuth authentication succeeds.
- Vehicle discovery succeeds.
- Vehicle data is updated correctly.
- `activation_finalize()` fails with `NOK:FORBIDDEN`.
- `remote_refresh_token` is never created.
- MQTT cannot be configured.
- The Control page remains empty.

### Expected behaviour

The OTP wizard should complete the remote activation successfully, create the `remote_refresh_token`, configure MQTT and display the Remote Control page.

If `activation_finalize()` fails, the UI should probably not report the OTP configuration as successful.

### Question

Is this a known regression in 3.7.5, or is it related to a recent change in the Stellantis/Opel remote activation API?