Frenck is not doing that at all, and it’s most certainly not personal to you.
It’s more of a generic attitude, (not very well) explained, and without empathy. Otoh, if the main team of dev’s decide, I always (have to) believe it’s for the sanity of the whole project in the long run.
Please dont give up your great integrations. Using these on a daily base, and need the detail we had from them!
The thing is, that maintaining a custom component is more work as I have to keep a watch on commits in the core repository where the code/funcationality of the inner workings change.
A native integration part of the core repository will be upgraded/changed by other developers when they add or change anything. They can see where the funcationality they change is used or see tests breaking.
For a custom component using functionality I have to keep an eye on that and apply the changes myself. This is a drawback which I try to avoid. I have less collaboration.
Good point. Understand your position which doesn’t make things/decisions easier 
I support Marius. Don’t give up your great work. I use your component since the first days and enjoing it as it adds real value to my home system.
Thanks a lot.
I still hope a good way is found to integrate the information. Until then I created the custom component here for the unsupported workaroung: GitHub - eifinger/here_travel_time_route_sensor: Homeassistant Custom Component which adds a Route Sensor to HERE Travel Time
Ugh. I would hate to go back to google or waze for this. Please keep up the good work!
Hi,
I already upgraded to 11.4. The component works excellent but I still receive errors regading this 255 characters boundary.
I simply would increase the loglevel for the here component but this error is reported by the homeassistant logger. Is there a smart solution beside this?
So I was poking around here travel travel because the latest core update had a breaking changing for Here Travel Time. The developer guide does not have Japan listed. However, I found this line that mention country Japan.
The sample api has the address written in Japanese. My first setup consist of alphabets. So I tried again with an address written in Japanese as a test. The request came back with data. Perhaps Japan is supported. Will give this a try again in HA.
I only find this now… sorry for not responding to that CC before and thanks!
the limit is not unexpected. In fact, we should go back even ome more step, to the point where route was an attribute of the main sensor.
Not sure if that can still be done, certainly hope so. Must check in the repo when this was still ok to find the correct version.
I don’t use the origin and destination sensors at all. What are your usecases with them?
I think I misexpressed myself. (Ill edit that) What I meant was that the Route was an attribute before, and not a stand alone sensor. Given the fact the route often is longer than 255 chars, this still errors as @Pirol62 said.
on my usecase: I use a dynamic route selector based on all available zones in my system.
select origin
select destinatie
click Update
show all available details, and before, the route details, and the O&D on the map. The Route was/is most important for me, since the other details can be had from other integrations, even core, which uses distance for example (aware this is less precise)
I have a template sensor which extracts the highways:
- unique_id: joergs_way_to_work
attributes:
route: >
{% set list = states('sensor.jorg_arbeitsweg_route')|regex_findall('A[0-9]{1,3}', ignorecase=false)%}
{{list|replace('[','')|replace(']','')|replace("'",'')}}
unit_of_measurement: min
destination_name: "netgo Borken"
friendly_name: "Jörgs Arbeitsweg"
duration_in_traffic: "{{ states('sensor.jorg_arbeitsweg_duration') }}"
duration: "{{ states('sensor.jorg_arbeitsweg_duration') }}"
state: "{{ states('sensor.jorg_arbeitsweg_distance') }}"
- unique_id: yvonnes_way_to_work
attributes:
route: >
{% set list = states('sensor.yvonnes_arbeitsweg_route')|regex_replace('L[0-9]{1,4}', ignorecase=false)%}
{{list|replace('-','')|replace(' ','')|replace("'",'')}}
unit_of_measurement: min
destination_name: "{{ states('sensor.yvonnes_arbeitsweg_destination')}}"
friendly_name: "Yvonnes Weg zu Intersnack"
duration_in_traffic: "{{ states('sensor.yvonnes_arbeitsweg_duration') }}"
duration: "{{ states('sensor.yvonnes_arbeitsweg_duration') }}"
state: "{{ states('sensor.yvonnes_arbeitsweg_distance') }}"
Looks like this:
As I have around 3 to 4 possibilities for my route to work, it gives me a hint about the traffic situation when I get up in the morning.
In addition to that: My wife gets an announcement via alexa when she gets up in the morning and travel time is > 18 Minutes and knows the way she has to use.
Hi @all, long time no see 
I use the custom component provided by eifinger in order to keep the route info.
I still receive errors about the 255 characters border which is ok when I raise the log level.
Unfortunately, the logger is homeassistant.
Setting the log level to ‘critical’, avoids all other error messages coming via this channel to be logged.
Is there a chance for a workaround?
Hi, I just installed here_travel_time integration and I have alredy some problem with it.
How you can see on graph there is a lot “unavailable” gaps. I know free HERE Travel Time Account has some request limits, but is this possible to run out with requests that fast? I just started using it 2 days ago (graph is showing full period).
I am getting error:
Logger: homeassistant.components.here_travel_time.coordinator
Source: helpers/update_coordinator.py:229
Integration: HERE Travel Time (documentation, issues)
First occurred: 5 July 2023 at 07:20:19 (328 occurrences)
Last logged: 14:36:45
Error fetching here_travel_time data:
Error fetching here_travel_time data: Rate limit has been reached
If I try to use homeassistant.update_enitiy I am getting unavailable state and this error.
Have you changed the default update interval? How many sensors have you configured?
It may also be that the API did restrict free API keys for a certain duration.
I did not changed the default update interval. Is default update interval 15 min? But next question is good. I was thinking about it yesterday and I did some changes. I have created 12 sensor but each sensor has 5 entities so in total is 60. I think with free account you have 1000 transactions per day for free. So if 1 transaction is equal to 1 request (I am not sure if that is true) and update every entity is equal to 1 request so that is far too much requests per day (if default update interval is 15 min).
I disabled entities what do I do not need, reducing it to 17 (that is still to much).
Conclusion is I have really reach daily limits because too many sensors. Today after midnight around 1 o’clock all sensor became available again and update_entity is working without error.
It is possible to create update interval schedule? For example: do not update between 1:00 and 7:00 (I do not need to update sensors in night time)
The daily limit on the API is news to me. I will have to investigate that.
Here is a starting point for your interval schedule: HERE Travel Time - Home Assistant
You can also disable automatic polling for each entry:
In the Devices&Services page click on the cogwheel for HERE Travel Time:
Click on the 3 dots:
Click on system options:
Disable “Enable polling for updates”:
I know updating sensors on-demand but I missed option “Enable polling for updates”.
I have disabled all sensors. Only updating on demand. Thanks
Hi.
As it is clearly stated on setup page that here maps has 250.000 transaction free. But today I saw that I was charged with 85 euros for 47.000 transactions.
Did I do something wrong during my setup or the information on Home Assistant information page is false ?
I just checked the documentation. The link points to a HERE knowledge base article which states that the Freemium Plan (this is where the values in the HA documentation are taken from) is “legacy”.
For the new platform I found these pricings: HERE Base Plan | Location Services | Pricing | HERE
Among others it states that only the first 5000 time aware routings are free. I have not found a definition of “time aware” yet.
tl;Dr If you create/have an account on the new HERE platform the HA docs are outdated.
So what I understand is there is no way of creating that old account. Plus, “here maps” page that HA refferred, has no mentions for free transactions limits.
As a result new accounts have very short limitations for route preferences and HA guide is misguided and should be deleted immediately. Because of the wrong info on HA site I was charged 85 euros.
