Tracker Beacons Now In Stock

We now have some tracker Bluetooth beacons in stock. Tracker beacons are Bluetooth beacons designed specifically for tracking physical items or remote camera button-type applications but they can be used for other purposes. Unlike iBeacon, Eddystone and Sensor beacons, there’s no configuration app, the Bluetooth advertising data is fixed and can’t be re-configured.

Tracker beacons differ from (most) iBeacons in that they, once connected via Bluetooth GATT, allow the beacon to ring, can detect a beacon button press and the beacon can ring when it goes out of range.

Tracker beacons can also be used, without GATT connection, to detect presence by using their MAC address on Android/gateways, or peripheral id on iOS CoreBluetooth, to uniquely identify them.

There are many poor quality tracker beacons on the market that are unreliable. It has taken us a while to find quality tracker beacons that also have known Bluetooth Services/Characteristics for programming purposes.

Beacons and Vending Machines

We are seeing an increasing interest in using beacons in vending machines. This is probably driven by Coca-Cola’s recent partnership with Signal360.

Beacons not only provide the opportunity for easier purchasing, via apps, from vending machines but also facilitate reward programmes and targeted contextual content based on the user’s location.

Vending machine companies contacting us are asking the usual questions regarding range and size. However, a more specific requirement is the ability to be mains powered. One way to achieve this is to use a smartphone-type USB mains adapter (offering a standard USB socket) and a USB beacon. Alternatively, the vending machine hardware might already have, or be able to be fitted with, a USB slot.

Bluetooth Power Consumption in Phones

A growing use of beacons is for continually monitoring using sensor beacons. However, one concern is how continually reading a Bluetooth sensor beacon might affect phone battery life.

There’s a recent research paper by Kleomenis Katevas, Hamed Haddadi and Laurissa Tokarchuk of Queen Mary University of London, UK on Power use : SensingKit: Evaluating the Sensor Power Consumption in iOS devices. It looks into Bluetooth beacon (phone) power use and, as a baseline, compares this to phone battery power use by sensors in the phone. They evaluated beacon broadcasting and scanning modes separately and together.

Very few scenarios use the phone to broadcast so the pink dotted line probably has less relevance. Looking at the scanning test it can be seen that it consumes power of the same order of magnitude as other sensors in the phone itself. Bluetooth LE scanning isn’t especially power hungry. Nevertheless, the 25hrs hours operation time on battery might be a limitation for most sensing scenarios.

An omission in these tests is that they only considered scanning rather than connecting. Some beacons need to be connected to via Bluetooth GATT, to obtain sensor data, that uses more phone battery power because it requires the phone to transmit to the beacon instead of just listening to the advertising scan data.

In practice, sensing projects are often better served by using a WiFi gateway or a phone/tablet permanently plugged in rather than a user’s battery-powered phone. This allows the device receiving sensor data to be mains powered removing concerns regarding device power use.

Beacons in Outdoor Learning Spaces

If you are working in learning, you might want to take a look at a new research paper Designing Outdoor Learning Spaces With iBeacons: Combining Place-Based Learning With the Internet of Learning Things (pdf). It takes a long time to download because it’s part of a compendium of research from the 12th International Conference of the Learning sciences.

The paper discusses place-based science learning in the context of an arboretum. It describes the use of beacons for informal learning, place-based learning, and context-sensitive educational technologies. Content was delivered in the arboretum with question prompts and activities so as to encourage deeper learning of plants

The paper says it has:

“insights into designing for learner-centered mobile computing that moves beyond presenting just-in-time information to creating digital-physical spaces where learners engage each other and natural objects to support their interests in science.”

“Beyond presenting just-in-time information” is an interesting aspect in that it can be just as applicable to other beacon usecases.

Beacon Detection Faulty on iOS 10

We have had several companies contact us very recently regarding problems with beacon detection on iOS 10. Problems include not detecting beacons when the app is not running and, when the app is running, beacons suddenly not being seen when they are in range. Another reported symptom is beacons not being detected for a very long time. These problems are all with apps that previously ‘just worked’ under iOS 9. The problems are erratic in that everything works ok on some people’s phones.

We have done some tests with our apps and have reproduced the background scenario of a beacon not being detected on a phone running iOS 10.0.1 that is detected, at the same time, by the same app on iOS 9. Strangely, once the power/screen is manually activated on the iOS 10 phone, the beacon gets detected. Updating to the latest 10.1.1 doesn’t fix the problem.

There are related posts on the ‘Beacon Ranging Problem in 10‘ and ‘Beacon Ranging in background on iOS10 is not working‘ on the Apple forums suggesting similar problems.

This is just a public service announcement that if beacon detection isn’t working for you at the moment the problem is not necessarily with your implementation or the product/app you are using. We believe the problem has been reported to Apple and you will need to wait for an iOS update with a fix.

UPDATE: See https://openradar.appspot.com/29509635

UPDATE March 2017: Troubleshooting iBeacon Background Triggering

New INGICS Bluetooth Sensor Beacons

We have some new INGICS Sensor beacons in stock.

These are slightly different to our other beacons in that they don’t transmit iBeacon or Eddystone. Instead the Bluetooth advertising is wholly used for sensor and battery information. Hence, they are more suitable for sensing, security and IoT applications rather than retail-marketing type scenarios.

There are 4 models:
iBS01G – movement/fall sensor
iBS01H – magnetic (hall) sensor
iBS01RG – (raw) accelerometer sensor
iBS01T – temperature and humidity sensor

ibs01t_smaller

They derive power from 2xCR2032 or via a micro USB smartphone charger (not supplied). They all also have a detectable button press. While the manufacturer’s app shows the sensor data, you will probably need a custom app or gateway to scan and use the advertising data.

Beacon Location Accuracy

There’s some recent new research on ‘Analysis of Object Location Accuracy for iBeacon Technology based on the RSSI Path Loss Model and Fingerprint Map’ by Damian Grzechca, Piotr Pelczar, Łukasz Chruszczyk.

They evaluated RSSI and indoor positioning trilateration algorithms in order to determine location accuracy. After lots of experimentation and mathematics, they calculated the average error to be 1.09m for 1–9m and 1.75m for 1-20m and after trilateration an average error 2.45m was achieved.

The conclusions give some hints how better results might be achieved. For example, correlating the RSSI with accelerometer, gyroscope and other sensors. Other strategies might be to excluding areas where an object
cannot move, or filtering out situations where objects move but accelerometer measurements don’t match.

System-based Beacon Detection

The majority of beacon-based solutions are app-based and trigger information to be displayed to the user in response to being near specific beacons. If you read many platform provider sites you might think that’s all beacons can do. However, beacons are a technology and not solution. Beacons provide for many types of solution.

Another type of solution is the accounting for things (with beacons attached) within a larger system. Examples include class registration, stock checking, asset tracking, security and lone worker positioning. In these cases the thing that detects beacons can be can be an app or hardware.

The app can be relatively simple and scan for particular beacons and save information to a file and/or send them on to server. We recently implemented such a system for Malvern Instruments, with custom pre-configured beacons, that also allows search for particular ‘lost’ beacons:

malvernsolution

In the cases where the beacon detection doesn’t or shouldn’t move around, it’s possible to use gateways to forward on detected beacon data to a server.

igs01_smaller

IGS01 Wifi Beacon Gateway

Several of our clients are using this type of architecture to provide for automatic human registration/rollcall type solutions.

We believe even greater opportunities exist for IoT scenarios where sensor data in beacon advertising can be automatically forwarded on to servers.

Man-in-the-Middle Attacks on Beacons

There’s an interesting BtleJuice Bluetooth Smart (LE) Man-in-the-Middle framework on GitHub. It allows you to listen in on the Bluetooth GATT communication that goes on when an app connects to a beacon.

The majority of, scanning-type, apps don’t tend to connect via GATT and only read the advertising data that’s available to anyone. Connection usually only happens when configuring beacons or in advanced scenarios where the apps needs to read sensor or battery data. Some custom platforms’ apps also connect to beacons to perform platform related things such as remote setup, security or other such things specific to the platform.

The availability of a Man-in-the-Middle framework presents a security threat. The likelihood depends on the scenario. In the case of most beacons, the main GATT connection activity is one-off beacon setup by an administrator. In these cases the beacon communication interception is very unlikely.

The larger problem might be with platforms’ apps that connect to beacons where GATT connections happen regularly via users (platform apps) and not under control of an administrator. The implications of the communications data being able to be eavesdropped obviously depends on what’s being communicated. That being said, most current non-Beacon Man-in-the-Middle (WiFi) attacks usually have financial motivations. It’s difficult to think up beacon attacks that might lead to financial gain for the attackers. Nevertheless, if you work with such a system that regularly connects to beacons via GATT, you might like to think about the consequences of data and metadata (what’s being changed) eavesdropping.

A more positive use of BtleJuice might be to discover and reverse engineer Bluetooth GATT Services. As mentioned in a previous article, some of our beacon manufacturers haven’t documented their Bluetooth Service Characteristics. This means that while they are ok for scanning/proximity type applications, you can’t write your own app to, for example, change programatically the UUID, major and minor and must rely on the manufacturer’s configuration app or, in the case of the Sensoro beacon, their SDK. While this of no consequence for the majority of uses, more ambitious scenarios might want directly access the Bluetooth GATT services. BtleJuice provides a new way to reverse engineer those Bluetooth GATT Services.