Eddystone problems

Configuration
1

Has anyone managed to get eddystone working? I bought a ruuvitag from their kickstarter and have the eddystone firmware on it. I’ve configured the paramaters and my sensor.yaml looks like this:

- platform: eddystone_temperature
  beacons:
    living_room:
      namespace: "68D6E2338413518730B1"
      instance: "B11AE34A7453"
      name: "RuuviTag"

Nothing seems to happen. I’ve double checked the namespace and instance and they are ok. I seem to able to configure various “slots” on my tag. Does it matter which is the TLM?

edit: I see this in the log - DEBUG (Thread-4) [homeassistant.components.sensor.eddystone_temperature] Warning: start() called, but scanner is already running

Presumably that is one of the other sensors I use locking bluetooth during its scan.

edit2:
17-04-12 20:04:00 DEBUG (Thread-3) [homeassistant.components.sensor.eddystone_temperature] Setting up…
17-04-12 20:04:48 INFO (Thread-4) [homeassistant.components.sensor.eddystone_temperature] Starting scanner for eddystone beacons
17-04-12 20:04:48 DEBUG (Thread-4) [homeassistant.components.sensor.eddystone_temperature] Warning: start() called, but scanner is already running

That last log was over 35 minutes ago. Does it give up?

2

Hi, i have the same problem.
My sensor is a Board with the NRF51822 Chip from Nordic Semiconductor. (7$)
It is working fine, but Home Assistant cannot find it.
The Eddystone Beacon is working fine.
I am using the hassbian image on an Raspberry 2 with a Bluetooth Dongle (CSR Chip).
I tried the Xioami Plant Sensor and is working fine with Bluetooth.
I tried the eddystone with the UID on Slot0 and TLM on Slot1, but nothing.
I will try it with TLM on Slot0 and UID on Slot 1.
BlueZ is 5.23. Perhaps it is a newer BlueZ required.