Note: some travel time sensors such as Waze do not come with the destination address with it so you’ll need to specify it manually via the zone setting for an entity. You can also set a custom zone for any entity to override the destination address.
Options
Name
Type
Requirement
Default Description
entities
list
Required
List of entities to show (see entity config below)
title
string
Optional
Github Change card title
show_header
boolean
Optional
true Show or hide header
columns
list
Optional
['name', 'duration', 'distance', 'route'] Customize what columns are shown
map
string
Optional
google Open to google or waze maps when a route is clicked (google or waze only)
distance_units
string
Optional
`` Force conversion of distance units to metric or imperial if needed
Name
Type
Requirement
Default Description
entity
string
Required
The travel time entity id
zone
string
Optional
Override the destination route with a zone or add one if none is given from entitiy
One thing I have noticed is that I am not seeing this card show up in the tracker card even though I have included the link in LL config that should add it to card updater
Hello, thanks for the component. there is an error with the distance in metric units. the distance attribute is already in km in my case and does not need to be converted anymore. Also I don’t understand why I have to specify the zone. Thanks in advance