Is the Google Travel Time Sensor Broke

Configuration
18

I have four sensors set up, and a CC in the account. Checking the usage I’m well under the free limits and I’m not seeing any issues in the sensors updating.

19

Cool, what version of HA are you running. I’ve been noticing issues since 74, and have not made any changes to the sensors. The only other things I’ve messed with is the Alexa TTS stuff, maybe something realted, but I could not see how.

I did install this

pip install lxml

Other than that, I’ve made no configuration changes other than updating HA to the lastest versions 74, 74.1, 75, 75.1, etc

20

I’m on 0.74.0 (yeah, behind the times).

21

That’s good info. Is there anyone on .74.1 or higher with multiple sensors, CC loaded, etc that is not having problems?

22

I guess I’ll come back to this later. For now, I just swapped out the compoent for the waze travel time.

It’s working just fine.

23

I’m on 0.75.2 with 5 sensors, no issues.

Keep in mind after adding your billing info, you need to link it to your project.

image
image949×619 96.8 KB

image
image467×630 31.5 KB

1 Like
24

Well… I was not aware of this. After linking the billing to my project and a Hassio restart, it started working :man_shrugging:

25

yes. you need to add creditcard information, also for your free account. But you can check in your dashboard if your google travel api active or not

26

Thanks, I was not aware of that either. Had the info entered, but never linked. I did link it, but have not gone back to enable yet. The waze sensor is working good. I’ll probably go ahead and put it back to google at some time in the near future though.

Brings up a side question. Anyone have any pros/cons of the waze vs google sensors

Only thing I can think of for waze is - No API key, or billing account required

27

Google allows for public transport times, that’s a pro for anyone not driving…

1 Like
28

I rebuilt the waze app based on the google app’s functionality. So it should be identical in that regards.

EDIT: Waze does not do public transport though as @johnflorin said.

1 Like
29

@petro The Waze Travel Time doesn’t seem to like zip codes, can you confirm?

image

My Config:

### Waze Travel Time Test
  - platform: waze_travel_time
    name: Travel Time To NYC Waze
    origin: zone.home
    destination: 10001
    region: 'US'

Error Log:
2018-08-08 19:45:26 ERROR (Thread-16) [homeassistant.components.sensor.waze_travel_time] Error on retrieving data: Internal Error

FYI, for those wondering how Google Travel Time may compare to Waze Travel Time.

image

FYI, Waze can take upto two minutes to update, where as Google seems to be instant.

My Config:

### Waze Travel Time Test
  - platform: waze_travel_time
    name: Bruce Time To Home Waze
    origin: device_tracker.bruce
    destination: zone.home
    region: 'US'
30

It does not, the waze api doesn’t accept it. All we do is hand the origin and desitnation string to waze http api and it returns a 3 duration, route pairs. The api appears to only accept addresses, towns, cities, states, and lat/long.

31

to get back to topic, is the google travel time sensor broke…?
in my settings, credit card is added, and both static and traveltime are enabled in the dashboard, and were working until 2 days ago.
Not sure if updating to 0.75 helped, but since then all of my google_travel_time sensors fail to initialize.

any suggestions please?

32

After linking to my account as recommended here, it has been working for me. Definitely not intutive, but made sense once I did it.

33

thx, will try again.

Believed to have followed Google previous announcements and form filling…
am I correct this is the google distance matrix api? that google site is so confusing…

34

Yeah, I set it up, loaded my CC and thought I was good. Once you do that, then you need to link your API to the paid account. makes sense, You get to pick what count towards your credits, CC. Not automatic. It is confusing.

35

Thanks…

Adding a CC and linking it to the HomeAssistant project solved this riddle for me… now my travel time sensors work again!

does anybody know how much a single traffic sensor will cost after the free trial is over?

36

I I understand it correctly, you should not have to pay for a single sensor at all. I believe the cost of a pull is low enough that you could have 4-5 sensors running and stay under the limit. Don’t quote me on that, but that was what I had read somewhere.

37

I’m running with four sensors, and I’m comfortably inside the free limits.