Custom Component: here_travel_time

Share your Projects! Custom Integrations
101

I installed it again and ignored the error.
Restarted manually through ssh and it works now
Thanks for the assistance.

1 Like
102

New Relase v1.4.0

Breaking Changes

Changes

  • Added additional attributes origin and destination to fully support travel-time-card by @ljmerza
  • Code is now using type annotations

Features

Bugfixes

103

I already checked my 0.95.4 vs 0.96.5 and got the known error again
- Platform not found: sensor.here_travel_time

IT was solved some days ago.

104

Iā€™m also getting this error:

Platform not found: sensor.here_travel_time

when I check configā€¦ Is the accepted solution simply to restart anyway and just power through?

105

Yep. If it still wonā€™t work feel free to report back :wink:

106

It workedā€¦ Hass.io refused to reboot so I had to restart it from the command line, but when it came back it was runningā€¦

The results shown for my commute to work donā€™t match what I get from the here app, thoughā€¦ The route also only shows part of the trams/busses I would need to work and the time is quite a bit differentā€¦ Is there a way to check itā€™s working properly? Itā€™s getting the locations right, I can see that.

107

So after some playing around with the API a bit, it looks like publicTransport doesnā€™t work well in my region, but publicTransportTimetable does (matches results I get from the app)ā€¦ Iā€™m guessing this has to do with missing realtime transport information for some lines hereā€¦ I tried just adding it to all your enums and using it as an option but that wasnā€™t enough to make it work ;-).

108

New Relase v1.4.2

Breaking Changes

Changes

Features

  • Added mode: bicycle

  • Added mode: publicTransportTimeTable - Please look here for differences between the two public modes.

  • Release notes are shown in HACS depending on your installed version

Bugfixes

@scstraus let me know if this works out for you =)

1 Like
109

Big upvote from me!! Will see if I can find the time to test it before I head to vacation, thanks!!

110

I gave it a try, but unfortunately am getting an error:

API returned error No timetable route found.

I will send you a PM with the URL I use to get the route from the API which gives me good resultsā€¦ Same as what I have programmed into the sensor.

111

Canā€™t add custom repository in settings of HACSā€¦ Canā€™t it be put in HACS store like all other components?

112

Make sure you use ā€œgithubā€ and not ā€œGitHubā€.
I have had this happen to meā€¦ it is case sensitive I guess and wonā€™t work with capital GitHub (very odd - probably need to submit an issue in the HACS repo if no one has already).

113

New Relase v1.4.3

Breaking Changes

Changes

Features

Bugfixes

  • Fix for mode: publicTransportTimeTable returning No timetable route found

@scstraus Thanks for helping with this one

114

Hi, I have the checker error again

General Errors: 
    - Platform not found: sensor.here_travel_time
    - Platform not found: sensor.here_travel_time

Iā€™m not familiar with starting HA from command line and so Iā€™m a little afraid of executing the update. Whatā€™s your advice?

115

Everything points to the fact that the Checker Script is currently broken at least for custom components.
The actual functionality is not impacted. You can install it

116

good to know,thanks.
The checker script seems to have even some more issues. It claims a long log file containing the customizings without pointing on an issue.

117

publicTransportTimeTable works perfectly for me now!! Thanks!

Now I can toss out Waze, Google Maps, and GTFS, all of which give me troubles, as this does a better job than all of them combined!!

1 Like
118

Thank you. Itā€™s really great to hear when your work makes someone happy :slight_smile:

1 Like
119

will test your wonderful component/integrtion because of the really enthusiastic reports weā€™re reading here, so cool, thanks for this.

Will you allow for travel time using city names? Had that option in Waze before, but it stopped working, requiring gps long/lat instead of

origin: Berlin 
destination: Brussels

would really make it a no brainer.

120

Unfortunately this is not supported by the API itself. It would be possible to combine two APIs to achieve that. Maybe sometime in the future :wink: