v0.21.0 - New Strategy against account blocking

Main goal: Prevent the account blocking with a new connection handling

• The connection is closed after 30 seconds if no update messages are received from the MB server.
• If a message is received or a car ignition state is on, the 30 seconds window restarts.
• The connection is re-established after 60 seconds.
• Changes that have happened in the meantime are delivered by the MB systems. (the latest values, not all)
• If an action, button or switch is triggered, the connection remains active for 120 seconds in order to receive long-running responses from the MB system.
• It can take 24 hours until the new logic is effective. During this time, you might experience account blocks, particularly if you update the component in the afternoon. (See here for some test results)

Other fixes:

• New capability modes for auxHeat (fixes: #288, some cars reporting that the "command capabilities" for auxheat are not available, but at the same time the car reports the "capability" auxHeat. We check "auxHeat" also now.)
• Polish and Spanish translation improvements (#291, #293 - Thanks @piotrgt and gallegonovato)

New

• The Device overview and the diagnostic report contains more information about the hardware and software stack of the car. This could be helpful to diagnose different behaviors of the MB-API (see here fore more details)

Thanks to the supporters!

v0.21.0-beta.2: New connection handling

Additional fix:

• Access Token check (fixes: #292)

IMPORTANT:

• This is a test release and it contains a new logic for the connection handling. Please be aware of potential bugs and provide feedback.
• It can take 24 hours until the new logic is effective. During this time, you might experience account blocks, particularly if you update the component in the afternoon. (See here for some test results)
• Please check the homeassistant.log and/or enable the debug logging before you file an issue. (The help page is using MQTT as an example, please replace MQTT with MBAPI2020)

Main goal: Prevent the account blocking with a new connection handling

New connection handling:

• the connection is closed after 30 seconds if no update messages are received from the MB server. If a message is received or a car's ignition state is on, the 30 seconds window restarts.
• the connection is re-established after 60 seconds.
• changes that have happened in the meantime are delivered by the MB systems. (the latest values, not all)
• if an action, button or switch is triggered, the connection remains active for 120 seconds in order to receive long-running responses from the MB system.

Other fixes:

• New capability modes for auxHeat (fixes: #288, some cars reporting that the command capabilities for auxheat are not available, but at the same time the car reports the capability auxHeat. We check "auxHeat" also now.)

v0.21.0-beta.1: New connection handling

IMPORTANT:

• This is a test release and it contains a new logic for the connection handling. Please be aware of potential bugs and provide feedback.
• It can take 24 hours until the new logic is effective. During this time, you might experience account blocks, particularly if you update the component in the afternoon. (See here for some test results)
• Please check the homeassistant.log and/or enable the debug logging before you file an issue. (The help page is using MQTT as an example, please replace MQTT with MBAPI2020)

Main goal: Prevent the account blocking with a new connection handling

New connection handling:

• the connection is closed after 30 seconds if no update messages are received from the MB server. If a message is received or a car's ignition state is on, the 30 seconds window restarts.
• the connection is re-established after 60 seconds.
• changes that have happened in the meantime are delivered by the MB systems. (the latest values, not all)
• if an action, button or switch is triggered, the connection remains active for 120 seconds in order to receive long-running responses from the MB system.

Other fixes:

• New capability modes for auxHeat (fixes: #288, some cars reporting that the command capabilities for auxheat are not available, but at the same time the car reports the capability auxHeat. We check "auxHeat" also now.)

v0.20.3 - Bringing Smart cars back on stage

Fix:

• Smart cars are not available in v0.20.2 (as expected, #285 )

v0.20.2 - MB Backend Changes again...

Fixes:

• Error message Error: No car information registered for this account. Check the MB website with the same account. since this morning
  Changed internal message handling. (fixes: #284 )

v0.20.2-beta.1 - MB Backend Changes again...

Looks like the MB-team made some more changes, and as the result the integration does not load anymore since Nov-28 8am CET.
Error: No car information registered for this account. Check the MB website with the same account.

This test release is addressing the change.

Fixes:

• Changed internal message handling. (fixes: #284 )

v0.20.1 - Account blocking, Bugfix Configure Dialog

Bugfix v0.20.1

• "Configure"-Dialog does not work

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 extensive 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.

v0.20.0 - Account blocking

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.

BETA Release - Bugfix - HTTP429

This test release 3 - tackles the HTTP429 errors.

• Changed handling of websocket connection resets
• New retry logic for websocket connections

BETA Release - Bugfix - HTTP429

This test release tackles the HTTP429 errors.

• Changed handling of websocket connection resets
• Improved error handling (Phase 1)