Mercedes is deleting all datasets for the smart eq cars
Yes, also my test smart got unavailable 8 hours ago…
Have you found more consistent result if using the geocodejson attribute, as mentioned in the Manual?
It’s a little better in that it drops the “town” tag and uses “city” instead but for my location it’s exactly the same result as the XML version.
In that case, either the OSM data is wrong (which can be fixed), or the english tend to use “colloquial” names instead of the “correct” ones, or identify with a suburb more than the city.
Which is not wrong in itself, just that it does not square with official naming of areas. Just like a lot of foreigners use “England” as a synonym for the UK, or “Holland” for the whole country of The Netherlands. Which of course irks the “locals” to great extend (Which self-respecting Scot likes to be miscalled “English”?, or the fact the The Netherlands has more than two provinces).
Not wanting to drag this too much off topic it depends on the size of the city. In somewhere like London or Birmingham the suburb is meaningful. In a small city like Lancaster less so.
I’ve modified the card for the next release, combined to
city: suburb || city || town || '',
So the choice is always suburb over city or town. Is that more appropriate? In my case, the location doesn’t change anything. Here we always use the suburb in a bigger city.
Vielleicht habe ich etwas nicht mitbekommen: Warum werden mir für den Smart EQ keine Daten mehr angezeigt, auch bei EVCC funktioniert es nicht mehr. Jemand eine Idee?
MB has disabled the Smart data feed. See here
There is a component available for smart #1 and #3. I have never tested it.
Info: Some attributes are not up-to-date for some car types
Start: After 2pm CET 15-01-2025
End: After 9:36am CET 16-01-2025
Reason: Data is not delivered by the MB API (official app has the same problem)
Affected attributes: Odometer, Ignitionstate, Lock, …
Not affected attributes: Location
Affected cars in my test car park: GLA (2019)
Not affected cars: EQ*
1 Like
Is there a way to add a sensor to show if the rear trunk/boot is open? It’s visible from the mercedesme app, but I want to configure a notification if it’s left open.
Thanks
Yes, it’s the decklidstatus attribute under the lock sensor. I’ve created a binary sensor to trigger a Google Home message and phone notification if it’s left open:
- binary_sensor:
- name: "Luggage Compartment Open"
unique_id: *******_decklidstatus
icon: >-
{% if is_state_attr('sensor.*******_lock', 'decklidstatus', 'true') %}
mdi:lock-open-alert-outline
{% else %}
mdi:lock-outline
{% endif %}
state: "{{ state_attr('sensor.*******_lock', 'decklidstatus') }}"
alias: Car boot open message
description: ""
triggers:
- entity_id:
- binary_sensor.luggage_compartment_open
trigger: state
for:
hours: 0
minutes: 4
seconds: 0
from: "off"
to: "on"
conditions:
- condition: zone
entity_id: device_tracker.*******_device_tracker
zone: zone.home
actions:
- action: tts.speak
data:
cache: true
message: Hello there! Did you know the car boot is open?
media_player_entity_id: media_player.dining_room_speaker
target:
entity_id: tts.google_en_com
- action: notify.mobile_app_pixel
metadata: {}
data:
message: The luggage compartment is open
title: Luggage Compartment
mode: single
Slightly off-topic: Assuming you want to solve the same issue I fixed with a similar automation, I can recommend this key cover as a “real” solution: https://makerworld.com/en/models/861784#profileId-812199
After adding this to my key I’ve never had an unintended trunk/boot open anymore.
Hi Thomas , I removed the background from some A35 AMG stock images of my car I found online. I have a few more of this if you require ?
Cheers
Looks good. Unfortunately, I don’t have an AMG A class. 
Can you do one of my EQS?
