Just some additional info. The remote start gives the same error.
I reverted back to v3.4 and I’m back in business.
I suspect there’s an issue here… I’ll keep checking.
Hi @rmertz3282,
the new version 0.4.1 has an option to disable the capability check. See Integrations and then options of the MB component.
BR
Rene
Hi,
does anyone of the MBAPI2020 users has a car with TheftProtection? If yes and you would like to share some internals, let me know via private message.
BR
Rene
Thanks Rene,
All of the original functionality is present following the update to 0.4.1, including the new oil level sensor. However, I do have to disable the compatibility check.
Out of curiosity, which json file delivers the features list? I can’t seem to locate this designation. If I enable debug, I see json files with the prefix md and ve, but I don’t think they have what we need. Is it possible the US doesn’t deliver this info?
My vep*.json files do have the following info (among others).
"doorlockstatusvehicle": {
"timestamp": "1612570219",
"int_value": "2",
"timestamp_in_ms": "1612570219000",
"service_ids": [
669
]}
"doorLockStatusOverall": {
"timestamp": "1612570219",
"int_value": "0",
"timestamp_in_ms": "1612570219000"
}
One other comment.
I like the inclusion of icons in the component. Is it possible to include a device class?
For example, I customized these entities to show “ok” versus “on”. It also delivers a state change.
binary_sensor.la221804_low_wash_water_warning:
device_class: problem
icon: mdi:wiper-wash
binary_sensor.la221804_low_brake_fluid_warning:
device_class: problem
binary_sensor.la221804_low_coolant_level_warning:
device_class: problem
icon: mdi:car-coolant-level
This looks great. Mind sharing the picture and the code?
Sure thing. It’s wrapped inside a custom button card
type: 'custom:vertical-stack-in-card'
cards:
- type: 'custom:auto-entities'
card:
type: glance
show_name: false
state_color: true
filter:
include:
- entity_id: '[[filter]]'
exclude:
- entity_id: '*pressure*'
- entity_id: '*device*'
- entity_id: '*closed*'
- entity_id: '*lock'
- entity_id: '*starter*'
sort:
method: name
- type: map
entities:
- entity: '[[entity]]'
aspect_ratio: '16:9'
default_zoom: 12.5
hours_to_show: 24
Hi @rmertz3282,
do you not get a file starting with c*?
If I remember correct we had this “unsolved” vin issue on your side. The rest apis delivered vins that we had not seen on the websocket connection. right? I assume thats the issue, here.
BR
Rene
Hi @rmertz3282 ,
I have added the device_class on the master branch. I’m not sure if this is a breaking change. Could you take a look, before I submit an new release?
BR
Rene
Now it’s clear that you are out of the US. :-)) Three Bays and three MB Cars. This is seldom in Europe 
Just joking
BR
René
I figured I might catch some heat for that. In reality one is a 6yr old BMW and my house is built on stilts. Not as grand as it may seem. 
Negative on the “c” file.
I’ll test the device class and if it works I’ll prepare a PR for all the binary sensors.
Let us see if some other people in the US have the same problem. If the use rate keeps low then I prefer to stick to the current solution.
No problem with the lock. My template lock serves my need.
Rene,
I see you expanded the device class. I copied over your changes to my const.py and it worked perfectly.
Thank you.
How to interpret the values of the oil level sensor? Typically the oil level should be between min and max. My sensor shows 88%. What values should I expect for
Thanks in advance
Hi,
I have not found any information. My car is reporting 88 too.
BR
Rene
Mine’s at 100%.
I have found that recently some status are not changing for example gas level percentage. They show an outdated time stamp. I have even remove the integration and re added.
Retrievalstatus
VALID
Timestamp
2021-01-31T17:38:41
