Important! Set up an Amazon Web Service (AWS) Account before beginning Gateway configuration
Minew Gateway Set Up on a Wi-Fi Network
1. Open box and remove the gateway from it’s plastic cover. The gateway comes with a USB cable to plug into your computer, however, we recommend purchasing a charger.
2. Plug in and power up the gateway by pressing the on button, located next to the power plug. Look for the SSID Name in the format of GW-XXXXXXXXXXXX in your Wi-Fi networks (you can change this name later). Choose this network.
3. Open a browser and go to http://192.168.99.1 to connect the gateway. The initial username and password is admin/admin. You will be asked to change the password once you log onto the gateway.
4. Click on the Network tab and enable the “repeater” option by toggling the switch on the right side.
5. Choose a Wi-Fi Network to repeat, put in the password for that network, and press connect
6. After this change you will be asked to reboot. Press “Reboot”
Setting up the Gateway on the AWS IoT Core
1. Log onto the AWS Console and select the IoT Core Service
2. Create a policy to use for the gateway; choose Secure/Policies on the left hand menu and press Create
3. On the next screen, name the policy and create a general IoT policy as shown in the screenshot. Under Add Statements start typing I..O..T and choose IOT*. Select Allow under Effect and press Create
4. Next Choose Manage/Things in the menu to the left and press Create
5. Choose Create a Single Thing
6. Give the Gateway a Name (you can add types and groups if you will have more than one gateway) and if you would like an attribute key and value and press Next
7. On the next screen choose One Click Certificate Creation and click “Create Certificate”
8. This is where you need to pay attention! Download the certificates and put them in a folder. You will also need a “root certificate,” which we explain in the next step. For now, press Activate.
9. Get the root certificate. Go to https://docs.aws.amazon.com/iot/latest/developerguide/managing-device-certs.html#server-authentication
Choose the first option in the list: RSA 2048 bit key: Amazon Root CA 1. Save the text that comes up in your browser as a file named ca.crt. We use BBEdit to capture the text.
10. Return to the webpage where you activated the certificates and press Attach a Policy
11. Choose the policy you created earlier and press Attach
12. Go to 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. Save all of the certificate files onto a USB Drive, and insert the USB Drive into the Gateway
2. Make Sure you are on the Gateways Wi Fi and log onto the admin console at http://192.168.99.1
3. Choose the Service tab and make sure MQTT is chosen in the dropdown menu
4. Choose SSL in the URL dropdown and put in the name of the thing endpoint you saved when you set up the gateway on AWS.
5. Make sure USB is chosen in the “Upload Way” dropdown menu and type in the names of your key, certificate and root certificate.
6. Press all three upload buttons. A “Success” confirmation popup appears after each button press.
7. Save the changes to the gateway by pressing Apply
8. A Success popup appears
Checking MQTT Publishing at AWS
1. On the Service Tab of the Gateway Admin tool you will see the default topic the gateway is publishing to. Copy the topic.
2. Log back on to AWS, choose the IoT Service, choose Manage/Things and select the Gateway
3. Choose Activity
4. Click on MQTT Client, paste the default topic into first text box and press “Subscribe to Topic”
5. You should see the JSON coming in from the device, and any beacons it is picking up via MQTT.
Download a PDF of this blog here: Configuring the Minew Gateway
2 thoughts on “Configuring the Minew G1 Wi-Fi BLE Gateway”
Great article! It will surely save a lot of time for those who want to understand how to configure G1 since their documentation lacks any configuration related to public cloud integrations.
I was successful connecting it to AWS and got into a lot of troubles playing with GCP… Logically it sounds very similar, but I am failing to make it work after all.
Did you have a chance to try configuring G1 to work with GCP IoT Core on your side? I would appreciate if you can share your thoughts/ideas.
We will be getting to the GCP IoT core and MS Azure next. We are working on some serverless apps that will process the incoming data from AWS for these (Either Alerts or Time Series Data). Keep your eyes on the blogs as we will be releasing documetation over the summer and fall.