Important! Set up an Amazon Web Service (AWS) Account before beginning Gateway configuration
INGICS Gateway Set Up for Your Wi-Fi Network
Once you receive your INGICS IGS02E Ethernet BLE Gateway follow these steps to configure:
The gateway comes with an antennae and a Power Over Ethernet cable. The cable has a powered ethernet jack and a splitter to plug into the micro-USB input on the gateway to charge it.
It also has an ethernet cable that plugs into the gateway that uses your existing network to send the Bluetooth data it collects to the AWS IoT Core. If you are not using Power Over Ethernet you can still use this gateway by connecting the ethernet jack on the gateway to your router, and powering the gateway via a micro-usb cable and cell phone charging unit.
Set Up the Gateway on the AWS IoT Core
1. Log onto the AWS Console and select IoT Core under the Internet of Things heading. Select Get Started the first time you access this screen.
2. To create a Gateway policy, select Secure on the left hand menu, then select Policies on the sub-menu. Press Create.
3. On the next screen, name the policy.
4. Under Add Statements, use the Action box to create a general IoT policy. Start typing I…o…t and then select the first statement: “IoT:*” from picklist as the value in this field; this is a general policy for all IoT devices.
5. Clear out the string that auto-populates in the Amazon Resource Name (ARN) field and replace with a wildcard (*). The Resource ARN is the end point for this resource and acts as a general policy for any resource.
6. Under Effect, choose Allow.
7. Press Create.
8. Next Choose Manage → Things on the left menu. Press Create.
9. Choose Create a Single Thing.
10. Name the Gateway; add types and groups if you will have more than one Gateway and if you would like an attribute key and value. An example type is Ethernet Gateway. An example group is Gateways. *See note below on Naming Conventions.
11. Click Create a Type and fill in the appropriate information.
12. Choose One-Click certificate creation and click Create Certificate.
13. This is where you need to pay attention! Download the certificates and place them in a folder. In the next step we will get the “root certificate.” For now, press Activate.
14. Get the root certificate. Go to: https://docs.aws.amazon.com/iot/latest/developerguide/managing-device-certs.html#server-authentication
15. Click on Amazon Root CA 1 under the Amazon Trust Service Endpoints heading. Save the text that comes up in your browser as a file named ca.crt Use bbedit to save the file. http://www.barebones.com/products/bbedit/index.html
16. Return to the webpage where you activated the certificates and press Attach a Policy.
17. Choose the policy you created earlier and press Attach.
18. Choose Register Thing.
19. Go back to the main menu and select Manage → Things. Select your gateway and press Interact. This is where you will find the endpoint of your thing in the top field. Copy this value and save it.
Setting up the Gateway with Certificates and MQTT Publishing
1. Make sure you are on the network the gateway is attached to; log onto the admin console. You can download the Android app Fing to help you determine the IP address of the device to log onto the admin console.
2. Click on the Applications tab and choose MQTT Client under Applications. Enter the endpoint you saved when you set up the gateway on AWS in the Host/IP field and press Save. This will reboot the gateway.
3. Press the advanced tab. Use Choose File to pick the certificate and private key files you saved (Step 8). Press Upload Certificate and Upload Key after choosing the files and then press Reboot.
Checking MQTT Publishing at AWS
1. On the Applications Tab of the Gateway Admin tool you will see the default topic the gateway is publishing to. Change it to: /in/ac233fc01615/status so it is formatted correctly and press Save.
2. Log back on to AWS, choose the IoT Core under Service, choose Manage/Things and select the Gateway.
3. Choose Activity on the left menu.
4. Click on MQTT Client, paste the default topic into first text box and press Subscribe to Topic.
5. This gateway does not send JSON so you will just see the string.
Congratulations! You have now successfully configured your Gateway. Revolution11 is here to help you through the process of setting up your BLE Gateways, beacons and sensors. We have worked with many clients to automate processes so you can work smarter, not harder!
It is important to have a naming convention that allows our team to quickly identify the location, type, and manufacturer of the device when working with devices in the cloud. Revolution11 highly recommends the following naming convention, based on the useful information in this blog: https://www.netcraftsmen.com/device-naming-conventions/
The blog makes a great point in describing how your device names need to work easily in a Command Line Interface (CLI).
The only information that we have added to the standard in this blog is the addition of the manufacturer.
Best practice for naming looks like this:
- Location: Fort Bragg,
- Type of device: ble wi-fi gateway
- Manufacturer: Ingics
- Number: first of several devices at this location
Download a PDF of this blog: Configuring the INGICS Gateway