Yes, its mentioned in Hacs. There you still have to look for Waze-Card.
I added the new github page https://github.com/ljmerza/travel-time-card to HACS and installed it that way
1 Like
thanks, it works
@klogg I tried to recreate your issue and got a route with 444 characters. Could you share your config which creates your truncated route here?
After a succesfull install with HACS I get the following error:
Platform not found: sensor.here_travel_time
What can I do?
Thanks.
Can you copy in the full error, and the relevant configuration.yaml section for your sensor?
This will help identify where the issue might be.
1 Like
Sorry, Iāve been away a bit and a also involved with real life over the last few days.
I looked again today at this and yes, it looks like it must have just been the Lovelace more info box that was truncating the route.
Iām really sorry to have brought this up without properly checking first.
No worries I am glad you could solve it 
1 Like
So how would someone make an automation to only have this run when you are away from home? I saw the example on how to make it run more often, but nothing about less often. Seems like a waste to make calls while Iām zero mins from home all night.
Iām also getting the same issue. Not sure what is wrong, as I copied the example and changed the values to suite my setup.
There is no error in the log. It just wonāt work.
Here is my code.
- platform: here_travel_time
name: "here: Home to UOW"
app_id: !secret here_app_id
app_code: !secret here_app_code
origin: zone.home
destination: zone.uow
I do it like this for two sensors:
(One is time to home which you asked about, the other is from home to somewhere else based on whether I am home and the contents of a calendar event. I have removed identifying details so I hope it all still makes sense)
EDIT: I forgot to add that the actual sensors have a long scan_interval (of course).
#================
#=== Automations
#================
automation:
#================================
#=== Person1 Here Routes sensors
#================================
- alias: Here Routes when Person1 leaves or arrives Home
trigger:
- platform: homeassistant
event: start
- platform: state
entity_id: device_tracker.person1_composite
to: 'home'
- platform: state
entity_id: device_tracker.person1_composite
from: 'home'
action:
#== stop the looping scripts for Person1 to Home
- service: homeassistant.turn_off
entity_id:
- script.set_person1_to_home_update_interval
- script.loop_set_person1_to_home_update_interval
#== stop the looping scripts for Home to Somewhere Else
- service: homeassistant.turn_off
entity_id:
- script.set_home_to_somewhere_else_update_interval
- script.loop_set_home_to_somewhere_else_update_interval
- delay: "00:00:02"
#=== Start the loops
- service: script.set_person1_to_home_update_interval
- service: script.set_home_to_somewhere_else_update_interval
#============
#=== Scripts
#============
script:
#====================
#=== PERSON1 TO HOME
#===================================================
#=== Set update interval for Person1 to Home sensor
#===================================================
set_person1_to_home_update_interval:
sequence:
#== stop the looping script
- service: homeassistant.turn_off
entity_id: script.loop_set_person1_to_home_update_interval
#=== Call the looping script to set the interval for Person1 to Home
- service: script.loop_set_person1_to_home_update_interval
data_template:
interval: >
{% if states('device_tracker.person1_composite') == 'home' %}
12:00:00
{% elif states('device_tracker.person1_composite') != 'home' and
states('sensor.person1_local_time_offset') != '0.0' %}
12:00:00
{% else %}
00:00:30
{% endif %}
#=================================================================
#=== Looping script that sets the Person1 to Home sensor interval
#=================================================================
loop_set_person1_to_home_update_interval:
sequence:
#=== update the sensor
- service: homeassistant.update_entity
entity_id: sensor.person1_to_home
- delay: "{{ interval }}"
- service: script.set_person1_to_home_update_interval
#===========================
#=== HOME TO SOMEWHERE ELSE
#==========================================================
#=== Set update interval for Home to Somewhere Else sensor
#==========================================================
set_home_to_somewhere_else_update_interval:
sequence:
#== stop the looping script
- service: homeassistant.turn_off
entity_id: script.loop_set_home_to_somewhere_else_update_interval
#=== Call the looping script to set the correct interval
- service: script.loop_set_home_to_somewhere_else_update_interval
data_template:
interval: >
{% if states('device_tracker.person1_composite') == 'home' and
is_state('binary_sensor.reminder', 'on') and
'(H)' in state_attr('calendar.somecalendar', 'message') %}
00:05:00
{% else %}
12:00:00
{% endif %}
#========================================================================
#=== Looping script that sets the Home to Somewhere Else sensor interval
#========================================================================
loop_set_home_to_somewhere_else_update_interval:
sequence:
#=== update the sensor
- service: homeassistant.update_entity
entity_id: sensor.home_to_somewhere_else
- delay: "{{ interval }}"
- service: script.set_home_to_somewhere_else_update_interval
Iām using a long scan_interval for the sensor and a custom:button-card that shows the sensor and updates on long press.
- type: custom:button-card
layout: icon_name_state2nd
entity: sensor.home_to_work
name: Home -> Work
icon: mdi:car-back
show_state: true
show_label: true
label_template: >
return (states['sensor.home_to_work'].attributes.route.includes("St1234") ? 'Route 1' : 'Route 2')
color: var(--my-green)
tap_action:
action: more-info
hold_action:
action: call-service
service: homeassistant.update_entity
service_data:
entity_id: sensor.home_to_work
styles:
name:
- justify-self: end
- padding-right: 20px
state:
- justify-self: end
- padding-right: 20px
- color: var(--primary-color)
label:
- justify-self: end
- padding-right: 20px
- font-size: 14px
state:
- value: 30
operator: '>'
color: var(--my-red)
- value: 20
operator: '>'
color: var(--my-yellow)
I have exactly the same message, when I check my config against 0.96.3.
Iām still on 0.95.4 and everything is working fine.
My number of api-calls have decreased rapidly since the last changes last week.
@cjsimmons @brugk000 Could you please open an issue under https://github.com/eifinger/here_travel_time/issues and include your HA version? Thanks!
New Relase v1.3.0
Breaking Changes
Changes
Features
- Route is now populated for Public Transport and Pedestrian
Bugfixes
New Relase v1.3.1
Breaking Changes
Changes
Features
Bugfixes
- Hotfix Public Transport Route Generation
already done
Itās [quote=āeifinger, post:94, topic:125908ā]
Could you please open an issue under
[/quote]
Sorry I havenāt opened an issue yet, but saw itās now at 1.3.1, so thought Iād try that first and itās now working.
What installation method of homeassistant are you using? hass.io?
In v1.3.1 nothing is changed which would fix the errorā¦ strange
Iām using Hassio. Not sure why it started working then. Both installed manually and via HACS were failing for me.
Now itās working, and works great. Itās interesting to compare travel times with Waze, and soon Iāll look at the other options here offers.