⚠️ Test Release Notice
This is a test release. Install it only if you enjoy debugging, want to try out new features early, or are interested in helping to keep this integration stable and evolving.
Please report any issues via GitHub, and include as much detail as possible — debug logging should be enabled before installation.
Please avoid duplicate reports and “me too” comments — thank you!
🆕 What’s New
🔄 Backup Mode: Pull Fallback
- When the connection to the Mercedes-Benz data pipeline (WebSocket) is blocked — even after a re-login — the component will now switch to a backup mode, falling back from push to pull operation.
- This scenario was observed in test environments between 10–11 PM, with the connection remaining blocked until around 2 AM. (timezone CEST)
- During backup mode, data is pulled every 3 minutes to maintain updates.
- This fallback mechanism is also applied during restarts of HA or the integration. If the WebSocket is still blocked, the component starts in pull mode.
- Note: In this case, startup may take approximately 30 seconds.
🔁 Automatic Recovery to Push Mode
- Once the blocking by MB ends and the WebSocket connection becomes available again, the component will automatically switch back to push mode — no user interaction required.
🛰️ New Sensor: Data Mode
- A new diagnostic sensor named
data modehas been introduced. It indicates the current data transfer method:push→ Standard mode using the WebSocket connection.pull→ Fallback mode when WebSocket is blocked.
⚠️ Limitations in Pull Mode
Important: When the component is in pull mode, it is not possible to execute actions (e.g., locking/unlocking or sending commands), as these require an active WebSocket connection.
Special thanks to all the new or old sponsors (a, b), everyone who starred the repository, and all contributors in the beta phase - you helped a lot!