home-assistant.io/source/_components/google_maps.markdown

title, description, logo, ha_release, ha_category, ha_iot_class, redirect_from

title	description	logo	ha_release	ha_category	ha_iot_class	redirect_from
Google Maps Location Sharing	Instructions how to use Google Maps Location Sharing to track devices in Home Assistant.	google_maps.png	0.67	Presence Detection	Cloud Polling	/components/device_tracker.google_maps/

The google_maps platform allows you to detect presence using the unofficial API of Google Maps Location Sharing.

Configuration

You first need to create an additional Google account and share your location with that account. This platform will use that account to fetch the location of your device(s).

1. You have to setup sharing through the Google Maps app on your mobile phone. You can find more information here.
2. You need to use the cookies from that account after you have properly authenticated which you can retrieve with either Export cookies for firefox (make sure that "Prefix HttpOnly cookies" is unchecked) or cookies.txt for chrome.
3. Save the cookie file to your Home Assistant configuration directory with the following name: .google_maps_location_sharing.cookies. followed by the slugified username of the NEW Google account.
   • For example: if your email was location.tracker@gmail.com, the filename would be: .google_maps_location_sharing.cookies.location_tracker_gmail_com.

To integrate Google Maps Location Sharing in Home Assistant, add the following section to your configuration.yaml file:

# Example configuration.yaml entry
device_tracker:
  - platform: google_maps
    username: YOUR_USERNAME

{% configuration %} username: description: The email address for the Google account that has access to your shared location. required: true type: string max_gps_accuracy: description: Sometimes Google Maps can report GPS locations with a very low accuracy (few kilometers). That can trigger false zoning. Using this parameter, you can filter these false GPS reports. The number has to be in meters. For example, if you put 200 only GPS reports with an accuracy under 200 will be taken into account - Defaults to 100km if not specified. required: false type: float scan_interval: description: The frequency (in seconds) to check for location updates. required: false default: 60 type: integer {% endconfiguration %}