How can I get the gps location (latitude and longitude) of a device tracker in order to send it to Waze Travel Time Integration

Can someone here help me with the subject possibly? Also, I have read something about the waze integration only updating every 5 minutes- I believe what this meant is that home assistant only asks the waze integration for an update every 5 minutes but I didn’t fully understand the small amount of information I was reading. Is there a way to request a refresh if running an automation? Thank you all for helping me with this. Essentially, I am just wanting a way to use this for planning home arrivals.

Do you all know of any better methods/ other integrations for this.

the service call update entity might work.

But isn’t every five minutes accurate enough?

Check out Waze Travel Time - Configuration of Multiple Sensors
I have an input select and added how to update the location.

I appreciate your response. It really probably is, I was just curious if anyone knew how to overcome it within an automaton so it would be real time. The biggest thing I was after was how do I get the latitude and longitude into their own variables (I guess that’s what it would be called) in order to add it to the configuration of waze. Like device_tracker.person.longitude?

Thank you for this Bill, I’ll look at this a bit around my lunch hour. I appreciate your help!
I will shift my responses on your link to that thread in order to keep similar topics grouped within the same thread for others. That thread is similar but not really what I am asking so I’ll have to reword and try again over there. I’m essentially wanting the origin to be the device trackers latitude and longitude, not a hard coded address. For destinations, I would be ok with those being hardcode addresses unless I wanted to use a device tracker in the destination also— like in an instance where I wanted to see how far a family member was from my current location.

I believe this may be a better explanation. The way the integration is written, it makes me think it would only accept a latitude and longitude as inputs so I was trying to get them into variables so that I could satisfy the configuration on the waze integration since the device trackers would be moving targets.

Send me a message if you have questions. Over the years I have had issues (lack of understanding) with latitude and longitude as well as different integrations that use them. For me, I believe I have them working well. I use the Android app that feeds the location to HA . I also have gps logger that I have had for years ( prior to the Android App being released) that I now use for a backup.

homeassistant.update_entity

- service: homeassistant.update_entity
  target:
    entity_id: sensor.my_waze_travel_time_sensor

I appreciate this @petro. Very helpful for that portion of the questions.

This sounds like me. “Lack of understanding” is definitely my issue, I am new to home assistant and feel like I am reading more information than I can take in.

So, I am using the android app for device tracker location on 2 phones. So, the last question I have is, let’s say I wanted to know the travel time between 2 devices. Is it as simple as creating the integration and in the origin/ destination areas below just typing in the entity ids “device_tracker.deviceA” for origin and “device_tracker.deviceB” for destination? And as you said, I could use the input select idea to have a selectable situation (input select will act as a variable, I believe is what you are doing there)

Based on looking at your example, it looks you are using a destination with a hardcoded address (not a home assistant zone); The question below stems from this statement.

Can you use zone names in this integration (without typing discrete addresses)? I’m sorry for asking so many questions on this. I think this will be all of them though. When I try the below, it is not working even though the documents at the address below say it should. Maybe I should give it 5-10 minutes to see if it updates but every time I create the integration and go look at the travel time value it says 586 minutes.

yes

you don’t need to use an address, the travel time integrations work off lat/lon, zones and device trackers have lat/lon. All you need to do is provide the integration with an entity that has a lat and lon attribute.

Thank you for these responses, I guess I need help troubleshooting then. Maybe I’m an idiot- it wouldn’t be the first time.

The below is my setup of waze travel time integration. These areas area about an hour apart. (no erroring on submission of the form)

The below is after a HA restart (and before). It is showing a 588 min travel time for the travel time sensor for some reason.

Below is my sensor device tracker sensor. It seems to be reporting properly. It is showing me in my work zone. I used my home zone as the destination.

Could I have also used the person.weston for this? I would assume so-- but this is a question for another day as I should get it working before going on to additional questions.

Here is the waze dashboad area

After further inspection, the origin and destination shown on this screen are correct but the duration/ distance (don’t really know what distance is, miles?) and the route I’ve never heard of.

@petro @bschatzow Lord God, save me. It was capitalization on my destination. I had “home” in the destination instead of “Home” (which is how it is written in my config.yaml).

For future knowledge for myself, are most all things in Home Assistant picky with regards to capitalization. Thank you all for trying to help this monkey. Sorry for all of the beginner questions.

You also might look into proximity. This show how far from a given location and if you are traveling towards or away. Many people use these for automations.

You are lucky that you caught @petro 's attention on this. He is very helpful, and you can learn a lot from him.

Yeah, I saw that one also. I have it saved for later reading. Yeah, I noticed @petro helps alot of people. It was nice that he was willing to pitch in a bit here. Thank you both for your help. I thought about the capitilization situation a little bit ago but thought “sure not”, I guess I should’ve been thinking “yes surely”. It is home assistant to say the least. Fully capable for the fully capable. haha.