Repository navigation
v0.42.0
What's Changed
π New: your car's weekly departure profiles
Electric and plug-in hybrid cars keep a list of departure times β the ones you set in the Mercedes me app. The integration never showed them. Now it does, and it can change them.
A new diagnostic sensor: Active weekly profile
Every car that reports a weekly profile gets an Active weekly profile diagnostic sensor. Its state is the entry your car is currently following, written the way you would say it:
| State | Meaning |
|---|---|
Mo-Fr 06:30 |
The car leaves at 06:30 on weekdays |
Mo, Sa 08:15 |
Two days only β consecutive days are joined with a dash from three days on |
07:00 |
An entry with no weekdays, so it applies once |
unknown |
The car has no active entry, even if entries are stored |
The sensor is a diagnostic entity, so you will find it on the device page under Diagnostic rather than in the main card. Its attributes carry the whole picture:
weeklyProfileTimeProfilesβ every entry with its number, time, weekdays, whether it is active, what the car does when it is due, and whether it repeatsweeklyProfileLimitsβ how many entries your car can holdoriginal_valueβ the number of the active entry, which is what the new action below needs
Important
The sensor will show the first active entriy as a state only. All the non-active states are visible in the details aka attributes of the sensor.
A new action: Week Profile Configure - HIGHLY EXPERIMENTAL!!!
mbapi2020.week_profile_configure adds, changes or deletes a single entry:
action: mbapi2020.week_profile_configure
data:
vin: Wxxxxxxxxxxxxxxxx
operation: add # add, update or delete
time: "06:30:00"
days: [monday, tuesday, wednesday, thursday, friday]
active: true- Add takes no entry number β your car assigns one. It needs a time.
- Change and Delete need the number, which the sensor lists for every entry.
Important
An entry you add is not active unless you say so. Without active: true the car stores the entry but does not follow it, and the sensor stays unknown. That is how the car behaves, not a quirk of the integration.
Note
What a car accepts differs by model. Only newer cars accept the charging es per entry, or a repetition other than No selection. The options like "Charging", "Preconditioning", and "Batt preconditioning" are currently not visible in the MB-App and are just a guess from my side based on the API definition and not tested in detail...
Note
Entry numbers are not permanent. Your car hands out the next free number, you delete an entry and the next new entry can take it. For an automation, read the number from the sensor rather than hard-coding it.
Full Changelog: v0.41.0...v0.42.0