Iphone device tracker home assistant

Device Tracker

The device tracker allows you to track devices in Home Assistant. This can happen by querying your wireless router or by having applications push location info.

Configuring a device_tracker platform

To get started add the following lines to your configuration.yaml (example for Netgear):

The following optional parameters can be used with any platform:

Parameter	Default	Description
interval_seconds	12	Seconds between each scan for new devices. This only applies to local device trackers, not applications that push updates.
consider_home	180	Seconds to wait till marking someone as not home after not being seen. This parameter is most useful for households with Apple iOS devices that go into sleep mode while still at home to conserve battery life. iPhones will occasionally drop off the network and then re-appear. consider_home helps prevent false alarms in presence detection when using IP scanners such as Nmap. consider_home accepts various time representations, (e.g., the following all represents 3 minutes: 180 , 0:03 , 0:03:00 )

Note that setting track_new_devices: false will still result in new devices being recorded in known_devices.yaml , but they won’t be tracked ( track: false ).

The extended example from above would look like the following sample:

Multiple device trackers can be used in parallel, such as Owntracks and Nmap. The state of the device will be determined by the source that reported last.

known_devices.yaml

As of 0.94 known_devices.yaml is being phased out and no longer used by all trackers. Depending on the integration you use this section may no longer apply. This includes OwnTracks, GeoFency, GPSLogger, Locative and Huawei LTE.

Once device_tracker is enabled, a file will be created in your configuration dir named known_devices.yaml . Edit this file to adjust which devices to be tracked.

Here’s an example configuration for a single device:

In the example above, devicename refers to the detected name of the device. For example, with nmap , this will be the MAC address (with byte separators omitted).

Parameter	Default	Description
name	Host name or “Unnamed Device”	The friendly name of the device.
mac	None	The MAC address of the device. Add this if you are using a network device tracker like Nmap or SNMP.
picture	None	A picture that you can use to easily identify the person or device. You can also save the image file in a folder “www” in the same location (can be obtained from developer tools) where you have your configuration.yaml file and just use picture: /local/favicon-192×192.png . The path ‘local’ is mapped to the ‘www’ folder you create.
icon	mdi:account	An icon for this device (use as an alternative to picture ).
gravatar	None	An email address for the device’s owner. If provided, it will override picture .
track	[uses platform setting]	If yes / on / true then the device will be tracked. Otherwise its location and state will not update.
consider_home	[uses platform setting]	Seconds to wait till marking someone as not home after not being seen. Allows you to override the global consider_home setting from the platform configuration on a per device level.

Device states

The state of your tracked device will be ‘home’ if it is in the home zone, detected by your network or Bluetooth based presence detection. If you’re using a presence detection method that includes coordinates then when it’s in a zone the state will be the name of the zone (case sensitive). When a device isn’t at home and isn’t in any zone, the state will be ‘not_home’ .

Источник

OwnTracks

OwnTracks (and its Android fork NextTracks) is a free and open source application for iOS and Android that allow you to track your location and send it directly to Home Assistant. It can be set up via the integrations panel in the configuration screen.

By default the integration will listen for incoming messages from OwnTracks via HTTP. It will also listen for MQTT messages if Home Assistant is configured to use MQTT. When a location is submitted via HTTP, Home Assistant will return all Persons’ last known locations and they will be displayed within the OwnTracks app.

Configuration

To configure OwnTracks, you must set it up via the integrations panel in the configuration screen. This will give you the webhook URL to use during mobile device configuration (below).

Configuring the app — Android

Install OwnTracks or NextTracks (Available from F-Droid) application for Android.

In the app, open the sidebar and click on preferences, then on the connection. Change the following settings:

• Mode: Private HTTP
• Host:
• Identification:
  • Username:
  • Password: Can be left blank.
  • Device ID:
  • Tracker ID: Two character tracker ID. (can be left blank)

Your tracker device will be known in Home Assistant as _ . If you entered a Tracker ID the tid attribute will be set to that ID.

Configuring the app — iOS

In the OwnTracks app, tap the (i) in the top left and click on settings. Change the following settings:

• Mode: HTTP
• URL:
• Turn on authentication
• User ID:

Advanced configuration

OwnTracks allows the user to set advanced configuration by adding a section to your configuration.yaml .

Configuration Variables

Sometimes Owntracks can report GPS location with a very low accuracy (few kilometers). That can trigger false zoning in your Home Assistant installation. With the parameter, you can filter these GPS reports. The number has to be in meter. For example, if you put 200 only GPS report with an accuracy under 200 will be take in account.

Owntracks users can define waypoints (a.k.a regions) which are similar in spirit to Home Assistant zones. If this configuration variable is true , the Owntracks users who are in waypoint_whitelist can export waypoints from the device and Home Assistant will import them as zone definitions.

A list of user names (as defined for Owntracks) who can export their waypoints from Owntracks to Home Assistant. This would be the username portion of the Base Topic Name, (e.g., owntracks/username/iPhone)

All users who are connected to Home Assistant via Owntracks.

Payload encryption key. This is usable when communicating with a third-party untrusted server or a public server (where anybody can subscribe to any topic). By default the payload is assumed to be unencrypted (although the communication between Home Assistant and the server might still be encrypted). This feature requires the libsodium library to be present.

The topic to subscribe for Owntracks updates on your MQTT instance.

Home Assistant will ignore all location updates and rely solely on geofence enter/leave events.

Dictionary to remap names of regions as configured in the Owntracks app to Home Assistant zones. Use this if you have multiple homes or Home Assistant instances and want to map a different label to ‘home’. key: value maps Owntracks region key to Home Assistant zone value .

A full sample configuration for the owntracks platform is shown below:

Using Owntracks regions

Owntracks can track regions, and send region entry and exit information to Home Assistant. You set up a region in the Owntracks app which you should name the same as your Home Assistant Zone, and then make sure to turn on the share option for the region in the owntracks app. Please see the owntracks documentation.

Home Assistant will use the enter and leave messages to set your zone location. Your location will be set to the center of zone when you enter. Location updates from OwnTracks will be ignored while you are inside a zone.

When you exit a zone, Home Assistant will start using location updates to track you again. To make sure that Home Assistant correctly exits a zone (which it calculates based on your GPS coordinates), you may want to set your Zone radius in HA to be slightly smaller that the Owntracks region radius.

Using Owntracks regions — forcing Owntracks to update using iBeacons

When run in the usual significant changes mode (which is kind to your phone battery), Owntracks sometimes doesn’t update your location as quickly as you’d like when you arrive at a zone. This can be annoying if you want to trigger an automation when you get home. You can improve the situation using iBeacons.

iBeacons are simple Bluetooth devices that send out an “I’m here” message. They are supported by iOS and some Android devices. Owntracks explain more here.

When you enter an iBeacon region, Owntracks will send a region enter message to HA as described above. So if you want to have an event triggered when you arrive home, you can put an iBeacon outside your front door. If you set up an OwnTracks iBeacon region called home then getting close to the beacon will trigger an update to HA that will set your zone to be home .

When you exit an iBeacon region HA will switch back to using GPS to determine your location. Depending on the size of your zone, and the accuracy of your GPS location this may change your HA zone.

Sometimes Owntracks will lose connection with an iBeacon for a few seconds. If you name your beacon starting with — Owntracks will wait longer before deciding it has exited the beacon zone. HA will ignore the — when it matches the Owntracks region with Zones. So if you call your Owntracks region -home then HA will recognize it as home , but you will have a more stable iBeacon connection.

Using Owntracks iBeacons to track devices

iBeacons don’t need to be stationary. You could put one on your key ring, or in your car.

When your phone sees a mobile iBeacon that it knows about, it will tell HA the location of that iBeacon. If your phone moves while you are connected to the iBeacon, HA will update the location of the iBeacon. But when your phone loses the connection, HA will stop updating the iBeacon location.

To use mobile iBeacons with HA, you just set up a region that doesn’t match your Zone names. If HA sees an entry event for an iBeacon region that doesn’t match a Zone name (say keys ) — it will start tracking it, calling the device device_tracker.beacon_keys ).

This allows you to write zone automations for devices that can’t track themselves (for example alert me if I leave the house and my keys are still at home). Another example would be open the gates if my car arrives home.

Using mobile and fixed iBeacons together

You can use iBeacons of both types together, so if you have a Zone drive with an iBeacon region called -drive and you arrive home with a mobile iBeacon called -car , then device_tracker.beacon_car will be set to a state of drive .

Importing Owntracks waypoints as zones

By default, any Owntracks user connected to Home Assistant can export their waypoint definitions (from the Export — Export to Endpoint menu item) which will then be translated to zone definitions in Home Assistant. The zones will be named — — . This functionality can be controlled in 2 ways:

1. The configuration variable waypoints can be set to false which will disable importing waypoints for all users.
2. The configuration variable waypoint_whitelist can contain a list of users who are allowed to import waypoints.

Источник

Apple iCloud

The icloud integration allows you to detect presence using the iCloud service. iCloud allows users to track their location on iOS devices.

There is currently support for the following platforms within Home Assistant:

It does require that your devices are registered with the Find My service.

Configuration

Adding Apple iCloud to your Home Assistant instance can be done via the user interface, by using this My button:

If the above My button doesn’t work, you can also perform the following steps manually:

• Browse to your Home Assistant instance.
• In the sidebar click on Configuration.
• From the configuration menu select: Integrations.
• In the bottom right, click on the Add Integration button.
• From the list, search and select “Apple iCloud”.
• Follow the instruction on screen to complete the set up.

For the notification, press “Allow”, then “OK”.

To prevent excessive battery drainage, a dynamic interval is used for each individual device instead of a fixed interval for all devices linked to one account. The dynamic interval is based on the current zone of a device, the distance towards home and the battery level of the device.

Two Factor Authentication

If two-step authentication is enabled for your iCloud account, some time after Home Assistant startup the integration will ask to enter the verification code you receive on your device via a notification in the Home Assistant UI. The duration of this authentication is determined by Apple, so you will need to verify your account every now and then.

In case of troubleshooting

Go into your Home Assistant configuration .storage folder and delete the “icloud” folder, then retry.

Platforms

Device Tracker

The iCloud integration will track available devices on your iCloud account.

Sensor

The iCloud integration will add a battery sensor for each iCloud devices available on your iCloud account.

Services

4 services are available:

Service icloud.update

This service can be used to ask an update of a certain iDevice or all devices linked to an iCloud account. Request will result in new Home Assistant state_changed event describing current iPhone location. It can be used in automations when a manual location update is needed, e.g., to check if anyone is home when a door has been opened.

Service icloud.play_sound

This service will play the Lost iPhone sound on your iDevice. It will still ring if you are on “Mute” or “Do not disturb” mode.

Service data attribute	Optional	Description
account	no	E-mail address of the iCloud account
device_name	no	Human Friendly device name like Bob’s iPhone

Service icloud.display_message

This service will display a message on your iDevice. It can also ring your device.

Service icloud.lost_device

This service will put your iDevice on “lost” mode (compatible devices only). You have to provide a phone number with a suffixed country code and a message.

Источник