1833c32a2c
* Sets front matter defaults * Removes default front matter from section templates/pages * Removes default front matter from addon pages * Removes default front matter from integration pages * Removes default front matter from posts * Removes default front matter from docs pages * Removes default front matter from other pages * Fixes blog category pages
2.8 KiB
title, description, logo, ha_category, ha_release, ha_iot_class, redirect_from
| title | description | logo | ha_category | ha_release | ha_iot_class | redirect_from | ||
|---|---|---|---|---|---|---|---|---|
| Eddystone Beacon | Instructions on how to integrate Eddystone beacons with Home Assistant in order to receive temperature data. | eddystone.png |
|
0.42 | Local Polling |
|
The eddystone_temperature sensor platform reads temperature information from Bluetooth LE advertisements transmitted by Eddystone beacons. Your beacons must be configured to transmit UID frames (for identification) and TLM frames (for temperature).
All beacons that support the Eddystone protocol, have a temperature sensor and can transmit TLM frames are compatible with this platform. For example Gimbal, Estimote or kontakt.io. For more manufacturers see this overview by Google.
Requirements
As this platform uses bluez to scan for Bluetooth LE devices a Linux OS with bluez installed is required. In addition to that, the libbluetooth headers need to be installed:
$ sudo apt-get install libbluetooth-dev
Scanning for Bluetooth LE devices also requires special permissions. To grant these to the python executable execute the following:
$ sudo apt-get install libcap2-bin
$ sudo setcap 'cap_net_raw,cap_net_admin+eip' $(readlink -f $(which python3))
To use your Eddystone beacon in your installation, add the following to your configuration.yaml file:
# Example configuration.yaml entry
sensor:
- platform: eddystone_temperature
bt_device_id: 0 # optional
beacons:
living_room:
namespace: "112233445566778899AA"
instance: "000000000001"
kitchen:
namespace: "112233445566778899AA"
instance: "000000000002"
{% configuration %}
bt_device_id:
description: The id of the Bluetooth device that should be used for scanning (hciX). You can find the correct one using hcitool dev.
required: false
default: 0
type: integer
beacons:
description: The beacons that should be monitored.
required: true
type: list
keys:
entry:
description: Name of the beacon.
required: true
type: list
keys:
namespace:
description: Namespace ID of the beacon in hexadecimal notation. Must be exactly 20 characters (10 bytes) long.
required: true
type: string
instance:
description: Instance ID of the beacon in hexadecimal notation. Must be exactly 12 characters (6 bytes) long.
required: true
type: string
name:
description: Friendly name of the beacon.
required: false
type: string
{% endconfiguration %}