iBeacon, Eddystone, Bluetooth, IoT sensor beacons, apps, platforms
We have two new wearable beacons in stock:
The W52 also includes a lanyard holder and lanyard so that it can be work around the neck.
The W59 is a fitness style-beacon that’s waterproof to IP67 and is rechargeable.
Both have buttons that can be used for on/off or button triggered advertising.
We have four new KKM waterproof Bluetooth beacons in stock.
The K8 is different in that it has tags for screw fixing. It also has an on/off button at the side that can also be used for triggering.
The K3 is one of our most waterproof beacons with an IP68 rating. The silicon case allows pressing of an internal button that can be used for button triggered broadcast.
The K5 has a hidden on/off button inside the case and is waterproof to IP67.
The K3 and K8 and K5 also have an accelerometer that can be used for advertising x, y z or to set up motion triggered broadcast.
The FSC-BP108 has been updated so that the battery is now replaceable.
Previously, the waterproofing was such that the beacon had to be ultrasonically sealed. A clever new twisting design allows the battery to be replaced while remaining waterproof.
Most coin cell beacons use either a CR2032 or CR2477 battery. CR2477 tend to be too large for keyfob beacons while CR2032 only last of the order of a year, depending on settings. This beacon uses an intermediate size battery, the CR3032 that more than doubles the battery life of CR2032 while keeping the size small and weight low. This beacon also uses the newer Dialog DA14531 that offers a battery life up to 6 years, depending on settings.
We have the new W7 security beacon in stock, suitable for use in places such as hospitals and prisons. It’s fitted with a security screwdriver and advertises an alert if the wristband is removed or cut off.
The W7 advertises iBeacon and Eddystone as well as acceleration (x y z) and body temperature. It’s waterproof to IP67 and is rechargeable via magnetic USB cable. The battery lasts up to a year on one charge, depending on settings.
There was a time when it was very easy to scan for beacons in background on Android. You just set up a service using the standard Bluetooth APIs. Over the years, Google has crippled the ability to perform reliable background processing to the point where it’s nearly as bad as on iOS. David Young says:
“Today, Android Services are often more trouble than they are worth”
David has an answer to the problem in the form of using Android BroadcastReceivers and threads. He explains the problem and solution on his blog. David also has a useful Github app demonstrating the technique.
We now have the Meeblue M52-PA in stock.
This Bluetooth beacon is similar to the M52-SA Plus with the addition of a much longer range of up to 180m.
This is achieved using an additional SKY 66111-11, a low-power, low energy range extender. This provides up to +13dBm while remaining Bluetooth Class 1 compliant.
We have two new KKM button beacons, the B1 and B2 in stock.
Both advertise iBeacon, Eddystone UID, Eddystone URL, Eddystone TLM and battery level to a range of up to 100m. They support button triggered (single/double/triple/long click) broadcast for detecting in apps or via Bluetooth gateways.
The B1 differs to the B2 in that the button is labelled ‘SOS’, has a larger CR2450, rather than CR2032, battery and also includes a wall mounting plate.
We now have the new MWC01 AoA beacon in stock.
AoA beacons advertise a constant tone extension (CTS) for angle of arrival detection as described by the Bluetooth Direction Finding standard. This beacon is rechargeable, using USB, via magnetic contact, has a battery life of up to 8 months (depends on how much it moves) and a range up to 150m.
Please see our post the MWL01 for insights that also apply to the MWC01.
We now have the KKM K11 beacon in stock.
It’s very small, wearable, inexpensive beacon supporting iBeacon and Eddystone. The button turns on/off and can also be used for button-triggered broadcasting for usecases such as SOS.
There are three main ways beacons can be integrated into existing systems:
1. Using Smartphone Apps
Beacons are usually stationary. Apps on users’ smartphone use the standard Bluetooth iOS and Android APIs to detect beacons and send information to your cloud or servers, typically via HTTP(S).
2. Using Ethernet/WiFi Gateways
Beacons are using moving. Gateways in fixed positions detect beacons and send information to your cloud or servers, typically via HTTP(S) or MQTT.
3. Using an Intermediate Platform Such as a Real Time Location System (RTLS)
This is a variant on #2 in that gateways send information to a system such as BeaconRTLS™ or PrecisionRTLS™. These systems have HTTP(S) APIs that can be used by your cloud or servers.
More information:
What are beacons?
Beacons for the Internet of Things (IoT)
If you need more project specific help we also offer consultancy and feasibility studies.