We now have the INGICS iGS03E Bluetooth to Ethernet gateway in stock. This differs to the iGS02E in that it includes Power over Ethernet (PoE) without having to have an external PoE splitter.
Gateways look 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.
The iGS03E is one of the first gateways to also support Bluetooth 5 in Long Range mode (LE Coded PHY), although very few advertising devices support this yet.
It never been easier to collect Bluetooth sensor information and store it in the cloud. The INGICS gateways come with step-by-step instructions how to set up AWS IoT Core, Azure IoT Hub and Google IoT Core.
If you are rolling out many gateways, there comes a time when you start wondering if all of them are working and connected. While it’s possible to write a server side script/code to detect whether or not data has been received from the gateway in the last n seconds/minutes, this doesn’t work when there aren’t any Bluetooth devices in the vicinity of some gateways which won’t be sending payloads.
The INGICS gateways have a way of setting up a heartbeat that’s a dummy payload used to indicate a gateway is working and connected. It’s set up by telnet to the gateway and issuing the following command followed by a reboot:
> SYS HEARTBEAT 1 > REBOOT
The ‘1’ signifies every 1 minute and allows setting up to 255 minutes. A $HBRP data payload is to the server in the form:
The heartbeat functionality is available on firmware IGS01-v2.0.0 and IGS01S-v2.0.0 or later.
We have two new sensor beacons in stock. The iBS03TP is a waterproof temperature beacon with a 2m probe measuring -50C to 150C with an accuracy +- 0.5C.
The iBS02M2 measures on/off. This can be a switch or a voltage (0.5v to 50v is ‘on’).
The small PCB with a USB connector plugs into the main unit USB. The terminal block is used connect to anything that provides a switched or voltage output. This makes this beacon suitable for detecting a wide range of on/off scenarios.
The INGICS iGS01S (WiFi) and iGS02E (Ethernet) gateways support MQTT to send data to a server.
MQTT defines three levels of Quality of Service (QoS) that relate to whether requests are resent if not acknowledged:
0 – The broker/client will deliver the message once, with no confirmation.
1 – The broker/client will deliver the message at least once, with confirmation required.
2 – The broker/client will deliver the message exactly once by using a four step handshake.
The INGICS gateways only support QoS level 0. This is because these gateways have lower memory and processing capability. They don’t have enough memory to queue unacknowledged requests required of other QoS levels. The extra processing would also significantly impact the performance and hence throughput.
If you need a higher MQTT service level then try the Minew G1 that supports QoS levels 0 and 1.
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.