Mercedes Me Component

It looks like some backend system is down right now – I cannot register a new meID at the moment.

ok, I created a user 10min before in MB Europe… What is your region?

Europe (Germany). Message says that due to internal maintenance activities the page cannot be loaded. But I just clicked around, and it looks like only the big button on the main page doesn’t work – but going via the login in the upper right corner does :smiley:

2 Likes

Using the app worked. New email registered, the only downside is that I can’t use the remote lock without id verification.

Do you mean the ID Verification on the profile page? I do not need to do this, only the email needs to be verified. I just tested this in Germany. What is your region/country?

Ah, you are right. I got a message about some digital extras not being available without verification but the remote locking and window closing works without doing anything more. I’m in the UK. I’m guessing the message relates only to the main user, not co-users.

I’ve experienced the same thing yesterday. I think it had to do something because I was still logged in to my primary account in my browser, while trying to confirm my HA account.

I retried by copying the link of the button in the mail to confirm the invitation and pasted it into an incognito window, but it still wouldn’t work.

Today, when retrying copy/pasting the link in incognito window, the link still wouldn’t want to work.
I then proceeded with removing the HA co-user from my primary account, invited it again and once I got the new invitation mail, I did the copy/paste into incognito window again and it worked like a charm.

So, not entirely sure if it was a temporary issue on the site yesterday or a browser cache issue…

I almost started a convo with Femke, as she was really pushing to help me on the MB site :rofl:

Just made a new account for my phone and left my admin account on my HA with MercedesME 2020.

And then then I updated from 0.19.1 to 0.20.1 and every entity lost connection. Nothing is showing up anymore. I tried to roll back and that didn’t help. Then i reinstalled 0.20.1 and then there where no devices or entity under MercedesMe 2020.

But after some testing i suddently got my device back and 2 entities, that didnt work… and af few moments later there where 6 enitities that still doesn’t work. When i click on the entity i get the following message:

“This entity is no longer being provided by the mbapi2020 integration. If the entity is no longer in use, delete it in settings.”

What is wrong? Am I blocked from Mercedes Me?

@jimscheel : Without the log output, its hard to answer. If this problem still exists after midnight (GMT), please open a issue and share all the requested details.

For now the logs sends this output:

This error originated from a custom integration.

Logger: custom_components.mbapi2020.client
Source: custom_components/mbapi2020/client.py:292
integration: MercedesME 2020 (documentation, issues)
First occurred: 12:31:08 AM (110 occurrences)
Last logged: 2:44:31 PM

Error with the websocket connection (retry counter: 12): 429 - Invalid response status
Error with the websocket connection (retry counter: 13): 429 - Invalid response status
Error with the websocket connection (retry counter: 0): 429 - Invalid response status
Error with the websocket connection (retry counter: 1): 429 - Invalid response status
Error with the websocket connection (retry counter: 2): 429 - Invalid response status

I have now disabled the integration and Will try again after midnight

The component should reload at next midnight (GMT). Enable the debug log as described in the release notes and share the complete the debug log for example via email. [email protected] (but after midnight (GMT))…

1 Like

One question for the secondary account.
the geofancy sensor is not visible, what about the tracker sensor? is this visible for the secondary account?

thanks

Yes, device tracker data is available.

Hi,
till a few days everything worked. With the latest updates I saw the blocking stuff and created another user. With this (and I also my primary user) I can see the data on the MB page. But it does not work in HA anymore.
The debug log states homeassistant.exceptions.HomeAssistantError: No car information registered for this account. Check the MB website with the same account.
I see in the debug log the correct FIN:

2024-11-28 09:52:40.790 INFO (MainThread) [custom_components.mbapi2020.oauth] PIN preflight request 1
2024-11-28 09:52:40.948 INFO (MainThread) [custom_components.mbapi2020.oauth] PIN request
2024-11-28 09:52:56.268 DEBUG (MainThread) [custom_components.mbapi2020] Token received
2024-11-28 09:52:56.270 DEBUG (MainThread) [custom_components.mbapi2020] Start async_setup_entry.
2024-11-28 09:52:56.271 DEBUG (MainThread) [custom_components.mbapi2020.client] WSL not detected - running in rlock mode
2024-11-28 09:52:56.271 DEBUG (MainThread) [custom_components.mbapi2020.oauth] Start async_get_cached_token()
2024-11-28 09:52:56.271 DEBUG (MainThread) [custom_components.mbapi2020.oauth] Start async_get_cached_token()
2024-11-28 09:52:56.490 DEBUG (MainThread) [custom_components.mbapi2020.oauth] Start async_get_cached_token()
2024-11-28 09:52:56.637 DEBUG (MainThread) [custom_components.mbapi2020.oauth] Start async_get_cached_token()
2024-11-28 09:52:56.815 DEBUG (MainThread) [custom_components.mbapi2020.oauth] Start async_get_cached_token()
2024-11-28 09:52:57.180 DEBUG (MainThread) [custom_components.mbapi2020] RCP supported for car W1KEGXXXXXXXX5580: True
2024-11-28 09:52:57.181 DEBUG (MainThread) [custom_components.mbapi2020] Init - car added - W1KEGXXXXXXXX5580
2024-11-28 09:52:57.181 DEBUG (MainThread) [custom_components.mbapi2020.client] start update_poll_states: W1KEGXXXXXXXX5580
2024-11-28 09:52:57.182 DEBUG (MainThread) [custom_components.mbapi2020.oauth] Start async_get_cached_token()
2024-11-28 09:52:58.930 DEBUG (MainThread) [custom_components.mbapi2020.coordinator] Finished fetching mbapi2020 data in 1.748 seconds (success: True)
2024-11-28 09:52:58.937 DEBUG (MainThread) [custom_components.mbapi2020.websocket] _start_websocket_handler: 01JDRZJBTCSTHV0EE7ZMCNK27E
2024-11-28 09:52:58.937 DEBUG (MainThread) [custom_components.mbapi2020.oauth] Start async_get_cached_token()
2024-11-28 09:52:58.937 INFO (MainThread) [custom_components.mbapi2020.websocket] Connecting to wss://websocket.emea-prod.mobilesdk.mercedes-benz.com/v2/ws
2024-11-28 09:52:59.048 INFO (MainThread) [custom_components.mbapi2020.websocket] Connected to mercedes websocket at wss://websocket.emea-prod.mobilesdk.mercedes-benz.com/v2/ws
2024-11-28 09:52:59.048 DEBUG (MainThread) [custom_components.mbapi2020] Connection Watchdog trigger
2024-11-28 09:52:59.049 DEBUG (MainThread) [custom_components.mbapi2020.websocket] Got notification: apptwin_pending_command_request
2024-11-28 09:52:59.049 DEBUG (MainThread) [custom_components.mbapi2020.client] Start _process_assigned_vehicles
2024-11-28 09:52:59.049 DEBUG (MainThread) [custom_components.mbapi2020.client] _process_assigned_vehicles - W1KEGXXXXXXXX5580 - False - Counter({'f': 0, 'p': 0}) - 1869
2024-11-28 09:52:59.057 DEBUG (MainThread) [custom_components.mbapi2020.websocket] Got notification: debugMessage
2024-11-28 09:52:59.057 DEBUG (MainThread) [custom_components.mbapi2020.client] debugMessage - Data: Registering User with ciamID: (*deleted*) and App-UUID: (*deleted*)
2024-11-28 09:52:59.057 DEBUG (MainThread) [custom_components.mbapi2020.websocket] Got notification: debugMessage
2024-11-28 09:52:59.058 DEBUG (MainThread) [custom_components.mbapi2020.client] debugMessage - Data: app twin actor was initialized
2024-11-28 09:52:59.194 DEBUG (MainThread) [custom_components.mbapi2020.websocket] Got notification: vepUpdates
2024-11-28 09:52:59.195 DEBUG (MainThread) [custom_components.mbapi2020.client] Start _process_vep_updates
2024-11-28 09:52:59.217 DEBUG (MainThread) [custom_components.mbapi2020.client] Full Update. W1KEGXXXXXXXX5580
2024-11-28 09:52:59.219 DEBUG (MainThread) [custom_components.mbapi2020.client] _process_vep_updates - W1KEGXXXXXXXX5580 - complete: True - Counter({'f': 1, 'p': 0})
2024-11-28 09:52:59.219 DEBUG (MainThread) [custom_components.mbapi2020.client] vepUpdates Sequence: 0
2024-11-28 09:53:32.857 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry *(*my mail adress*)* (Region: Europe) for mbapi2020

Am I doing something wrong? Or what might happen here?

Thanks and Kind Regards,
Marco

Hi Marco,

The log shows:

  1. Login was successful.
  2. Masterdata for your car was received → Acccount + Car linking is OK.
  3. Connection to the websocket backend, OK and Initial debug message received. → Ok- account is not blocked.
    4. In the first 30 seconds no Full-Data message was received from the websocket. → Fail

Question:
When do you have linked the new account and the car? Sometimes it takes a while until the websocket delivers the data.

Update:
Looks like the MB-Team deployed a change at 8:02 am and the websocket is acting differently. I need to analyze this. Link to the github issue

Since 8am a load of the component is failing with the error No car information registered for this account. Check the MB website with the same account..

I have published a beta release v0.20.2-beta.1. Would be great if some of you can test this. It should handle 95% of the use-cases - Only Smart-Cars, and a few edge cases are open.

Is there a Smart Car user still reading this? If so, I’m looking for access to such a car. Anyone who would like to can send me an access QR code to [email protected]. Thank you

v0.20.2-beta.1 solves the problem.
many thanks for that quick reaction!

I have released: “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 )
4 Likes

oh dear! thanks so much for the time spent and your reactivity tracking down MB backend changes ! Some important workflows of mine depend on your integration - I want to thank you warmly for your great work !