Hi, the latest update provides UI configuration.
We should delete the config out of the yaml configuration - so far so good.
But shall we delete the sensors as well? Where should I configure a new one?
There is no UI for that.
There is no current documentation about it available.
Now I’m a little confused
You only have to delete the yaml config. The sensors are still there.
1 Like
The new integration is still not working for me. It gives unknown error.
Hi @eifinger,
two more questions:
I received this error more then 20 times last night:
Logger: homeassistant.components.here_travel_time
Source: components/here_travel_time/__init__.py:154
Integration: HERE Travel Time (documentation, issues)
First occurred: 25. Juni 2022, 17:19:10 (25 occurrences)
Last logged: 06:59:10
Unexpected error fetching here_travel_time data: Error occured on __get
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 191, in _async_refresh
self.data = await self._async_update_data()
File "/usr/src/homeassistant/homeassistant/components/here_travel_time/__init__.py", line 134, in _async_update_data
return await self.hass.async_add_executor_job(self._update)
File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/here_travel_time/__init__.py", line 154, in _update
response: RoutingResponse = self._api.public_transport_timetable(
File "/usr/local/lib/python3.9/site-packages/herepy/routing_api.py", line 241, in public_transport_timetable
return self._route(waypoint_a, waypoint_b, modes, departure, arrival)
File "/usr/local/lib/python3.9/site-packages/herepy/routing_api.py", line 67, in _route
response = self.__get(self.URL_CALCULATE_ROUTE, data, RoutingResponse)
File "/usr/local/lib/python3.9/site-packages/herepy/routing_api.py", line 40, in __get
raise error_from_routing_service_error(json_data)
herepy.error.HEREError: Error occured on __get
Nothing urgent. I’m wondering if I should raise the log level or if it is something, you have to react on?
Second question:
I have a new road to my work which is relatively long:
I’m only interestet in the Highways I have to use which would tell me enough. Is there any chance to filter that by road class or something else? I cannot find the documentation of sensor declaration anymore.
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 