Now works perfectly!! Thank you so much 
This is great thank you. I can finally retire my janky node red flow.
Working in Ireland. I did have an issue where it would pull in my 2 cars as devices but not create any entities. One of my cars is not enabled for mercedes me (but registered to my account) so I excluded this and updated my country in the option and my entities were then created.
Is not in add-ons
Try in HACS, Integrations, Custom repositories (tree dots in uper right corner)
1 Like
As a smart fortwo EQ owner, I am following this thread because my car is visible in
my mercedes.me account! I installed your component without issues and everything looks fine, although I do not get any entities. If you have a spare moment, could you look if it is possible to support the Smart Cars? Ofcourse if I can help or test, please let me know! Thank you!
@ReneNulschDE fyi so far looking really good! a small error fyi:
Logger: custom_components.mbapi2020.client
Source: custom_components/mbapi2020/client.py:175
Integration: MercedesME 2020 (documentation, issues)
First occurred: 0:22:45 (1 occurrences)
Last logged: 0:22:45
Error with the websocket connection: Received message 257:None is not bytes
I even managed to get a small card up already ;-). Keep up the good work!
5 Likes
any chance you could share your card setup? it looks nice
1 Like
Hi,
I will, give me a bit of time to clean it up a bit and make it better ;-). I will post it in this forum.
5 Likes
your work is very great!
Great work! Works good with an E300de and I can throw away the Node-RED implementation.
The new version is working great with my C300de as well.
The only question I have is how to interpret the state values of the attribute chargingstatus in the range_electric sensor. Maybe I’ve overlooked it, but I could not find any description.
At the moment the state is 3 = charging finished(?). The mercedes me app describes the status as “charging cable disconnected”.
Edit:
I discovered the values on my car by comparing with the app:
chargingstatus = 0 means charging
chargingstatus = 1 means charging finished
chargingstatus = 2 ?? unknown
chargingstatus = 3 means charging cable disconnected
2 Likes
@ReneNulschDE - It will work for US region and for 2017 vehicles ? What are the minimum requirements ?!
Thank you.
1 Like
I guess the minimum requirement would be that you can use the Mercedes Me app to access your car’s data.
@robertklep -
Mercedes US Region has two different apps/platforms for different years models (excluding 2013-2015 witch is using first version of mbrace):
- 2016 to 1018 is using Mercedes ME - mbrace for 2016-2018 Models | Mercedes-Benz USA (mbusa.com)
- 2019 to present is using Mercedes me connect - Mercedes me connect | Mercedes-Benz USA (mbusa.com)
So my question was if mbrace for 2016-2018 vehicules will work with this component.
Also - to answer to your statement - Yes - I can access my vehicle’s data with my Mercedes ME app for mbrace but my goal is to integrate my 2017 GLS450’s data into my HA - if possible.
Thanks.
I have a 2016/17 c350e and it works fine for me…
2 Likes
Hi @DerekO -
Perfect - great news - are you in US region ?
After I have installed the custom repo under HACS - and installed the integration under Configuration > Integrations - this is what I see:
It is there something that needs to be done prior ? I have followed all the integration install/config instructions line by line…
That doesn’t look right, it looks like this for me (NL/EU region):
Were you able to log in successfully?
Yes - the log in step was successfully and I was surprised to have zero devices/entities under the integration. And under logs I have this error:
Logger: custom_components.mbapi2020.client
Source: custom_components/mbapi2020/client.py:175
Integration: MercedesME 2020 (documentation, issues)
First occurred: 10:37:27 AM (1 occurrences)
Last logged: 10:37:27 AM
Error with the websocket connection: Received message 257:None is not bytes
1 Like
Looks like something you should report to the developer
Never mind, I’m seeing the same issue at the moment. Probably a backend issue at Mercedes 
1 Like
