The issue is already tracked here: Here_travel_time: Error occured on __get · Issue #72530 · home-assistant/core · GitHub
As for the roads, that is currently not possible
1 Like
Hey Kevin,
if https://github.com/home-assistant/core/pull/74348 wont make it after all, wouldn’t it be possible to keep that route attribute in another way? Was thinking of a rest command of sorts querying the same resource. I mean, I have some that pull in way more characters than those from the Route without the blink of an eye.
Or, if that wouldn’t be possible either, maybe a small CC only creating those routes…?
I am trying to keep the attribute in the frontend as it is currently, but struggle to get that in a browser-mod popup, because that doest support the config.entity templates apparently see discord and link to the community post in Browsermode channel
Next, I figured te reinstall the travel-time-card once more, but forgot that uses the single entity with attributes, which we now no longer have…
Fearing we will loose the Route anytime soon, I hope you will consider some alternative options with me…
thanks for the effort!
I came to the same conclusions as you did. What else is a component like here_travel_travel_time than a rest sensor which is better integrated into Hass. Why allow the one and not the other.
As you I have usecases for the route.
The only thing I can think of if routes aren’t allowed anymore is to publish a custom component/integration which does have routes.
As I wouldn’t want to maintain both I would have to decide what to do…
3 Likes
The route is essential for me as well as it gives me a hint about the direction I have to leave in the morning. I’d prefer a custom component then
agreed. added that, what use it the integration without Route…
As I posted in the PR’s we already have distance and time in HA core, at least by approximation.
Still hope the dev team see they’re on the wrong track with this, for more than 1 reason, If not, a CC would be the way to go really.
Also, we could use the Travel time card back again, which now is of no use either…or at least needs a rewrite to use the 3 separate sensors.https://github.com/ljmerza/travel-time-card
1 Like
It’s official now. New entities for the here integration. Good news - a route entity seem to be available but Will the travel-time-card now be useless and we have to build our own overview with button card?
Can you manage to use the integration ? I am always getting “Unexpected Error” during installation.
1 Like
The integration works here and is rock solid
It’s a known issue and I’m working on the fix https://github.com/home-assistant/core/issues/72530
1 Like
You wrote “it’s official” did I miss a decision?
Release notes 2022.8 - breaking changes
Well I hope the PR gets merged otherwise we have a bug in the release
Does anybody has new information or an alternate solution for the travel-time-card or do
I have to rebuild this with custom-button-card?
The travel-time-card will definitely have to be rebuilt
Ok thanks, then I start work… 
What a f… by the way 
Maybe it is easier to create a template sensor, which looks similar to the here sensor today 
ok: this works:
- unique_id: yvonnes_way_to_work
attributes:
route: "{{ state_attr('sensor.yvonnes_arbeitsweg','route') }}"
unit_of_measurement: min
destination_name: "Klaus-Bungert-Straße"
friendly_name: "Yvonnes Weg zur Arbeit"
duration_in_traffic: "{{ state_attr('sensor.yvonnes_arbeitsweg','duration_in_traffic') }}"
duration: "{{ state_attr('sensor.yvonnes_arbeitsweg','duration') }}"
state: "{{ states('sensor.yvonnes_arbeitsweg') }}"
````
After the update, replace the sources :-)Thanks for the idea, works great, I had to use states and not state_attr though as the HERE integration doesn’t use attributes any more, they are all separate sensors
Yes, I’m still on the former version 2022.7.x and simply preparing the update 
It’s something funny, we have to think about deeper:
A sensor has been splitted into different entities which we have to combine again in a template sensor in order to work with it as before. 
I think I read it was something to do with an issue of the route being over 255 chars sometimes so had to be split out. It’s only a hack for the travel-time-card until it is updated (if at all)