Well it looks like it’s not recognising the entity name “binary_sensor.2_amu_833_tire_warning”
Is it definitely correct? Does it expose the attributes you expect in Developer Tools?
Incidentally, since the time that mobiledude did his templates that I copied, Rene added many attributes as sensors. So it’s not strictly necessary to create templates for all of the attributes you want
please make sure that you run version 0.5.14 and restart HA after the update. Then please authenticate or delete the integration (plus restart of HA) and add it again.
@weemaba999 If you’re interested. I actually took my dashboard one step further and made a custom button card that when pressed opens a popup that summarizes all of my data. Very handy in a mobile view.
I think you’ll have to do that from Lovelace (and quite possibly only with something like lovelace_gen), I don’t think it’s possible to set icon color from sensor definitions.
Hi all! I have an A 250 e with pre-entry climate control functions, but I can’t find the pre-entry switches in my HA entities at all. Does this function have some country/vehicle-specific restrictions I’m not aware of?
first of all happy new year and thank you to the active and inactive users of this component. The latest stats showing that every day a new user is joining the club (btw: thanks for sharing the HA analytics/usage data).
Around 4 years ago, I got my first MB car and I tried to integrate the car data into Home Assistant. Over the time, I learned some basic python, MB changed their app landscape a lot (to the better of course) and I tried to keep the speed of all the HA changes.
As some of you know, this component does not use the official MB API’s. Main reasons are that the inofficial APIs deliver much more data and the updates come in near to realtime.
Nevertheless, it should be clear that the MB-Dev team can close the door whenever they want. And as I know, that some MB-devs reading this thread: Thanks to the MB-Dev team, for the great development in the last years and thanks for not shutting down the possibility to use my own data in the application that I like.
Let me give you some insights what is planned for the next months (as long as MB is on the friendly side):
Adding some new services to control the interior esp. interior lighting. This needs some refactoring of the component load process, the MB-API is not the fastest here and a reauth is needed and I try to find out a way to do this without big interruptions.
I want to learn more about Lovelace and therefore I plan to deliver the component with some preconfigured UI components. (Thanks to all the contributors in the thread here - I learned a lot)
Fix the HA-units vs. MB-units problem - my plan is to add an option where you can swith between HA-unit sytem and MB-App-unit sytem.
What else do you want to see?
Thanks again - you’re active involvement here gives me the motivation to move on.
BR
Rene
PS: If you like the integration give it a star on the Github-repo…
Hi Rene,
In the meantime I pretty much tried everything even completely re-installed HA and got the to same issue. Do you have any other options to try ? Thanks!
This error originated from a custom integration.
Logger: custom_components.mbapi2020.oauth
Source: custom_components/mbapi2020/oauth.py:246
Integration: MercedesME 2020 (documentation, issues)
First occurred: 1:21:00 PM (1 occurrences)
Last logged: 1:21:00 PM
Are you based in Europe or Noram? Does the feature work in the IOS/Android app? MY22 means model year 22?
can you enable “DEBUG ONLY: Enable save server messages to the messages folder” in the options of the integration. Restart your HA, wait 3minutes and send me the files out of the custom_integrations/mbapi2020/messages folder?