Sensor Weirdness

[christophermichaelshaw]

I have two sensors to detect popular times at my local gyms -- one works and the other does not display the statistics despite similar data in the attributes.

I've tried removing history from db, and also created a new sensor with no improvement.

Any ideas?

[freakshock88]

When the sensor does not report live data, that is usually because Google maps does not provide it either. You can look up the places in google maps itself and see that there is no live data reported for those locations. The last few days none of my sensors have been working for that reason.. let's hope Google fixes that.

[christophermichaelshaw]

Google *is* reporting live data for the location -- https://www.google.com/search?q=la+fitness+ballard&oq=la+fitness+ballard [image: image.png]

…

On Tue, Dec 20, 2022 at 11:37 AM freakshock88 ***@***.***> wrote: Closed #9 <#9> as completed. — Reply to this email directly, view it on GitHub <#9 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APSZUKDV2HTMRUXK7KMQPRDWOIDHTANCNFSM6AAAAAAS4NMC4E> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- -- Christopher Shaw ***@***.*** 425.435.8440

[freakshock88]

I don't think that is live data, that is historical data.
If you check in Google maps, when there is live location the hour column in the graph has a pink color rather than blue.
It does not have that right now:
https://www.google.com/maps/place/LA+Fitness/@47.6626546,-122.3774023,17z/data=!3m1!4b1!4m5!3m4!1s0x549015b76456f2a5:0x344d169bfb22c9c7!8m2!3d47.662651!4d-122.3752136

[christophermichaelshaw]

Ah, thank you for the clarification! I appreciate your follow ups! Ok to close as it is an issue with Google.

On Tue, Dec 20, 2022 at 12:18 freakshock88 ***@***.***> wrote: I don't think that is live data, that is historical data. If you check in Google maps, when there is live location the hour column in the graph has a pink color rather than blue. It does not have that right now: ***@***.***,-122.3774023,17z/data=!3m1!4b1!4m5!3m4!1s0x549015b76456f2a5:0x344d169bfb22c9c7!8m2!3d47.662651!4d-122.3752136 — Reply to this email directly, view it on GitHub <#9 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APSZUKECYY6BDIMDJWOCSXLWOIIC3ANCNFSM6AAAAAAS4NMC4E> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- -- Christopher Shaw ***@***.*** 425.435.8440

[Posiek]

When the sensor does not report live data, that is usually because Google maps does not provide it either. You can look up the places in google maps itself and see that there is no live data reported for those locations. The last few days none of my sensors have been working for that reason.. let's hope Google fixes that.

Hi,
It is possible to display "not live data" when on some places live popularity is currently unavailable? I see popular times is correctly store in attributes:

[freakshock88]

@Posiek
I have now updated the component with these changes:

• Added fallback to historical Maps data, for when live popularity is not reported for a place.
• Added a new attribute to indicate whether current state is from historical or live data.

If you update (via HACS) to version 0.25 you should see historical data reflect in the sensor's value :)

[Posiek]

WOW! You are AWESOME! Thank you for that, everything works perfect now and without pain :)