vdbg/hubitile repository overview

⁠HubiTile: Hubitat & Tile Tracker integration

This program allows for associating Tile⁠ trackers with Hubitat⁠ virtual presence devices corresponding to geofences⁠.

⁠Highlights

• Can track any number n of tiles from a given Tile account.
• Can have any number g of geofences. This translates to n*g virtual presence sensors in Hubitat.
• Geofences can be entered as circles or complex polygons.
• Can have exclusion geofences, meaning areas from where the app will ignore reported positions.

⁠Lowlights

• Freshness of the signal depends both on a device (typically a phone with the Tile app installed) to see the Tile device and on how often this app calls the Tile cloud APIs.
• Accuracy is not always great. The position reported by the Tile APIs is the position of the phone when reported to the Tile backend it was within Bluetooth range of the Tile device, and not of the position of the Tile device itself. For example, any person with the Tile app installed on their phone driving past your house could detect the Tile sensor which would "move" the last Tile device location detected to somewhere on the road. If the Tile app is slow to report the position, then the Tile device will be reported as even further away down the road. Exclusion geofences can help mitigate this case.

⁠Pre-requisites

• A Hubitat⁠ hub.
• A device capable of running Docker containers that is on the same LAN as the hub.
• Maker API⁠ app installed and configured in Hubitat.
• A Virtual Presence device created in Hubitat for each pair of (geofence, tile_sensor) that the app should update.
• All of these virtual presence sensors are exported in Maker API.

⁠Installing

1. touch config.yaml
2. This will fail due to malformed config.yaml. That's intentional :)
   sudo docker run --name my_hubitile -v "`pwd`/config.yaml:/app/config.yaml" vdbg/hubitile
3. sudo docker cp my_hubitile:/app/template.config.yaml config.yaml
4. Edit config.yaml by following the instructions in the file
5. sudo docker start my_hubitile -i
   This will display logging on the command window allowing for rapid troubleshooting. Ctrl-C to stop the container if config.yaml is changed
6. When done testing the config:

• sudo docker container rm my_hubitile
• sudo docker run -d --name my_hubitile -v "`pwd`/config.yaml:/app/config.yaml" --restart=always --memory=100m vdbg/hubitile
• To see logs: sudo docker container logs -f my_hubitile

⁠Troubleshooting

• Set main:logverbosity to DEBUG in config.yaml to get more details. Note: Hubitat's token is printed in plain text when main:logverbosity is DEBUG
• Ensure the device running the Python script can access the Hubitat's Maker API by trying to access the <hubitat:url>/apps/api/<hubitat:appid>/devices?access_token=<hubitat:token> url from that device (replace placeholders with values from config.yaml)