Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reduce Update Delay in When Sensor Location Changes #316

Open
hsbaath opened this issue Jan 14, 2025 · 8 comments
Open

Reduce Update Delay in When Sensor Location Changes #316

hsbaath opened this issue Jan 14, 2025 · 8 comments

Comments

@hsbaath
Copy link

hsbaath commented Jan 14, 2025

Thank you for developing the Places component

Is it possible to configure the Places component to update immediately when the latitude or longitude of the tracked sensor changes?

I’m using the Places API to monitor my car's live location. However, I’ve noticed that updates are delayed by about 10 minutes. For example, when the car leaves home or arrives back, the Places entity continues to show the previous location and only updates after a delay.

Is there a way to configure the Places to trigger an update as soon as the original sensor's attributes (latitude or longitude) change?

Screenshot 2025-01-13 at 9 18 35 PM
@Snuffy2
Copy link
Collaborator

Snuffy2 commented Jan 15, 2025

It should be updating as soon as the lat/long changes. From your screenshot, Jeep is the tracked entity and Jeep Live Location is the Places sensor, correct? What kind of entity is Jeep? device_tracker, person, sensor, etc?

@michelscholte
Copy link

michelscholte commented Jan 15, 2025

I have the same problem. I am using pnbrckner's life360 integration to track a person. When the person moves, the latitude/longitude is updated about every 15 seconds, but the Places sensor updates about once every 2 minutes, and sometimes longer.

@Snuffy2
Copy link
Collaborator

Snuffy2 commented Jan 16, 2025

Mine updates pretty quickly. Top row is places sensor, bottom is device_tracker.
2025-01-15_19-35-03

@michelscholte, same question to you. What kind of entity is connected to the places sensor? device_tracker, person, sensor, etc?

@hsbaath
Copy link
Author

hsbaath commented Jan 16, 2025

It should be updating as soon as the lat/long changes. From your screenshot, Jeep is the tracked entity and Jeep Live Location is the Places sensor, correct? What kind of entity is Jeep? device_tracker, person, sensor, etc?

yes Jeep live location( below) is places sensor, and Jeep (top row) is sensor with these attributes

Latitude
Longitude
Source type = gps
GPS accuracy = 2

@michelscholte
Copy link

Hi,

First. Thanks for your quick comment.

It is a device_tracker.

As you can see below the last_update time is changed, but the las_updated not. At that moment the person is driving on a highway and the coordinates of device_tracker changed every 15 seconds.

image

@Snuffy2
Copy link
Collaborator

Snuffy2 commented Jan 17, 2025

Sorry, I'm still not able to determine if there is an issue. Last Changed at 08:31 and Last Updated at 08:37 says to me that places rechecked the device_tracker at 08:37 and determined the coordinates on the device_tracker were unchanged from 08:31.

places listens for the tracked entity to change and will trigger each time it changes (unless the change is <10 seconds from the prior check). Additionally, places runs every 10 minutes even if not triggered by a change in the entity.

Can you please enable debug logging and grab the logs while someone is driving (or something similar). You can post them here or email them to me at my7idwq0@mail.snuffy2.com if you prefer.

@michelscholte
Copy link

Unfortunately, I haven't had time to get more information together yet. Hopefully I'll manage it this week. I'll let you know.

@michelscholte
Copy link

Due to security reasons (locations of my family), I send you part of the logging through email. Hopefully you can find something. Thanks in forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants