From b741ca5a70f5f50ba50d83e06c1c1c39df449db0 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Thu, 26 May 2016 06:57:00 -0700 Subject: [PATCH] Add Android comment --- ...-to-track-things-that-cant-track-themselves-part-ii.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_posts/2016-05-26-ibeacons-how-to-track-things-that-cant-track-themselves-part-ii.markdown b/source/_posts/2016-05-26-ibeacons-how-to-track-things-that-cant-track-themselves-part-ii.markdown index daf71b228ac..4c60d345549 100644 --- a/source/_posts/2016-05-26-ibeacons-how-to-track-things-that-cant-track-themselves-part-ii.markdown +++ b/source/_posts/2016-05-26-ibeacons-how-to-track-things-that-cant-track-themselves-part-ii.markdown @@ -36,6 +36,8 @@ So if you put an iBeacon on your keys or in your car - then you can track them. It’s easier to set up OwnTracks and HA to track a mobile beacon than the fixed beacon I discussed in Part 1, because you only need to tell OwnTracks about your iBeacon. You don’t need to configure HA at all. +

OwnTracks currently only supports mobile beacons on iOS.

+ You set up the beacon the same way as we discussed in part 1. The only difference is that instead of calling the region the name of a location (eg -drive) you call it the name of the device you want to track (eg -keys). Remember the leading ‘-’ that makes the connection more reliable.