The iGS04 is a new keyring/keyfob style beacon only 6mm thin. It advertises continuously and the button is used to change a value in the advertising data.
The iGS01 is similar to our other iGS beacons except it has no sensors other than the being able to detect the button press.
These Bluetooth beacons are not iBeacon nor Eddystone beacons. The advertising data is instead wholly used for sensor data. You will need an (your own) app or gateway to scan and obtain the advertising data.
The iGS01S is a new version of the iGS01. It’s functionally compatible with the iGS01 in that you can replace an iGS01 with an iGS01S and it will behave similarly. Hence, it’s also compatible with BeaconServer™ and BeaconRTLS™.
iGS01 gateways allow you to scan for nearby Bluetooth devices and send the scanned data up to a server, including AWS IoT, via TCP, HTTP(S) POST or MQTT.
The main change is the case which the manufacturer has changed to allow commonality of parts with the Ethernet version, the iGS01E.
We now have the INGICS iGS02E Bluetooth to Ethernet gateway (without PoE) in stock.
This small device looks for Bluetooth LE devices and sends their advertising on to a server via TCP, HTTP(S) or MQTT including AWS IoT. If you use with sensor beacons, this provides a quick and easy way to provide for IoT sensing.
We have some early samples of the new INGICS iBS03 range of beacons in stock. They are functionally similar to the iBS01 range except are waterproof to IP67 and have a more robust case with 2m drop protection.
We stock three variants: iBS03T – Temperature sensor iBS03G – Motion (starting/moving/stopped) and fall detection iBS03RG – Accelerometer for raw xyz
There’s a type of beacon that doesn’t send out iBeacon or Eddystone advertising. Instead, it sends out standard Bluetooth 4.0 advertising containing sensor values. This means the data can be picked up via apps, gateways, Raspberry Pis or other devices that can see Bluetooth advertising.
An example of this is the INGICS iBS01 range of beacons.
The round bit in the middle is a button that can be pressed. Here’s an example for the data from the iBS01T temperature/humidity sensor:
Additionally, the ‘event’ data gives the state of the button press.
We have a new INGICS gateway, the iGS02, in stock that uses Ethernet rather than WiFi. This allows it to be used where WiFi isn’t present or where it’s considered that data needs to be sent via a more reliable wired connection. The use of Ethernet also allows for a greater throughput detection of up to 70 beacons per second (with MQTT).
The iGS02 comes with a POE adapter allowing it to be powered from the Ethernet connection for networks providing POE. Alternatively, it can be powered via the USB connection.
The MQTT/HTTP output is the same as the WiFi-based iGS01 allowing these devices to be used interchangeably.
Beacons can be used to detect if things or people are in a zone by either putting beacons on the moving things or having the beacons static in a zone.
For the beacons on things/people approach, a gateway or other scanning device looks for beacons in the vicinity and triggers actions. For the static beacons case, an app on peoples’ phone can detect beacon(s) in a zone and trigger actions.
We have some new beacons in stock that now provide a third way of detecting proximity. They use IR and PIR to detect the proximity of any item coming within range. For IR that’s <50cm and for PIR < 5m. These beacons transmit the current state via Bluetooth that can be picked up by an app or gateway.
Beacons can be used to detect when something is falling. The classic usecase is healthcare where patients can be monitored and an alert generated when they have fallen. However, fall detection can be used in other areas such as mountaineering and construction where human life is in jeopardy due to the high risk of a fall. It’s not just people that can be monitored. Fall detection can be used for valuable/fragile items in places such as warehouses, factories or even in transit.
Detecting falling uses an accelerometer in the beacon. Some sensor beacons generate x y z data that can be used to programatically detect the fall. The problem with this is you need relatively complex local processing such as a smartphone or single board computer to analyse the x y z data. A solution is the iBS01G that not only detects that the beacon is falling but also indicates when the beacon is moving, has gone from still to moving or moving back to still.
The advertising data event status shows the movement states:
The states can be logged or shown directly in an app or sent to a server via a WiFi gateway.