ReneNulschDE/mbapi2020 v0.20.0

v0.20.0 - Account blocking

on GitHub

Important Notice: Changes to the MB Backend

A few days ago, the MB team made some changes to their backend environment. As a result, accounts may be blocked in cases of intensive use. In the context of this integration, extensive use can happen after multiple restart/reloads per day. When blocked, access with this component and all official MB apps will no longer be possible. The account is unblocked at midnight (GMT).

How to Prevent Account Blocking

To reduce the risk of your account being blocked, please follow these recommendations:

1. Create a separate MB user account for use with this component.
2. Invite the new user to the vehicle:
   The primary user of the vehicle can invite the new HA-MB account to access the vehicle. Up to six additional users can be invited to each vehicle.
3. Use each account in a single environment only:
   Use one account exclusively in HA or in the official MB tools, but never in both simultaneously.

Important Notes

• Certain features, such as geofencing data, are available only to the primary user.
• If geofencing is required in your HA environment, use the primary user account in HA and the secondary accounts in the official MB apps.
• Make sure that you not run more at one account (with the same cars) in one instance.
• You can delete the authentication information in the "Configure"-Dialog of the integration and then relogin with the new account.

Key Improvements in This Release

• If an account is blocked (HTTP 429), the system will now automatically attempt to re-establish the connection after midnight (GMT) The retry delay is based on the following formula Retry delay = 15 seconds × (retry count)². When the reconnect was successful a reload of the component is initiated. (Fixes #279, #282)
• The value of chargingPowerKW is rounded now. (Thanks @tvcsantos, #283)

Technical details

Q: Why do you not act like the official app and reuse the application-id to prevent blocking?
A: Only with a new app-id, the component gets a full-data update from the MB-servers on start/reload. A full dataset is currently needed to create the sensors as I decide based on this full update which sensors are available for the car. I'll try to address this in one of the next releases.

Q: How can I see the details?
A: Enable the debug logging of this component to see all the details like wait time or other output.

You can support the development.