UP AND RUNNING BASICS
Below are a few pointers to help you setup (a.k.a. pair) your new gateway when it arrives:
• Make sure you have the latest version of the SensorPush app from the Apple App Store or Google Play Store.
• Once you've downloaded or updated the app, remove the gateway and power adapter from the packaging.
• Verify that your WiFi network is using 2.4GHz or is in "dual band" mode (both 2.4GHz and 5GHz). 2.4GHz is the most common type of WiFi, so if you are unsure, you likely already have 2.4GHz.
• Locate the Gateway somewhere central to the sensors you want to monitor so the Gateway has the best chance of picking up the signals coming from the sensors. Power up the Gateway and raise the antenna.
• Open the SensorPush app to the main screen (the main screen says "Devices" at the top) and tap the Add button. This is the same button previously used to add sensors. Now it will present you with a choice to add a sensor or a gateway. Tap the Add Gateway option.
• Now the phone will form a temporary connection to the gateway. This might take a minute or two. If it takes longer than that, please try restarting the phone and gateway and trying again. If you still cannot connect, let us know and we'll be happy to help.
• Once you're connected, you'll be prompted to create an account (or log in if you have already created one).
• Next, choose a WiFi network and enter a password (if necessary). After the gateway has connected you should see a green checkmark next to the network in the list.
Note: If you have an older router and a Hex Based WEP password, you must have the prefix "0x" in front of the password (and the "0" in "0x" is a zero).
• You can also connect via Ethernet instead of using WiFi. Just plug in the Ethernet cable (DHCP is required) and wait for the "Connected via Ethernet" message to appear on the Gateway configuration screen. There is a known issue where in some situations plugging or unplugging Ethernet while the device is running interrupts the sensor scanning. We're working on tracking down the issue and will be pushing out an update soon. In the meantime, if you are affected, please power-cycle the gateway after plugging or unplugging Ethernet.
• Give your gateway a name if you like and you're all set.
• Please try to keep the app up to date for best performance.
If you have sensors that also need setup, refer to the sensor setup instructions.
You should now be able to monitor your sensors over the internet. You can test this by turning the Bluetooth off on your mobile device. Provided all of the sensors are in range to the Gateway, you should be able to see them update in the app roughly once per minute. A small icon shaped like the Gateway will appear to the right of the sensor's name if the sensor is communicating via the Gateway. You can also verify that the information is up to date by looking at the "Last seen" time right beneath the sensor's name on the list of devices in the main screen of the app. readings should be within the last couple of minutes of the current time if the sensor is communicating normally through the Gateway.
The app while open can update automatically, but you can also refresh the data by doing a pull-down refresh (a.k.a. "swipe-down-to-refresh") on the main screen of the app. A pull-down refresh is the same thing you can do in an email app where you use a finger to pull down on the screen to check the server for new emails. This should load any new sensor and Gateway data from the SensorPush cloud.
You may want to experiment a bit with the placement of your gateway and the antenna and sensor orientations for optimal coverage in your particular situation. Give the gateway some time (half an hour or so) in each configuration to scan and communicate with all of the sensors before evaluating it or trying something else. The initial download takes longer than the following incremental updates, so while you should start to get current conditions very quickly, it might take some time for the gateway to catch up with the available history stored on the sensor.
With all of your sensors now within range of your Gateway, the app no longer needs to use Bluetooth so Bluetooth access is automatically toggled for the SensorPush app, specifically. This will not turn off the Bluetooth of your mobile device in general. Some customers might like to temporarily use a sensor outside the range of the Gateway (e.g. taking it on a hike). When doing this, you simply need to turn the Bluetooth back on inside the SensorPush app itself in order to monitor the sensor directly while away from the Gateway. The sensors readings captured via Bluetooth are not pushed up to the and saved to the cloud, but they will get saved to that instance of the app. Here is how to turn Bluetooth access on and off inside the sensorpush app:
• Open the app, and from the main "Devices" screen and select the button in the top left to open app settings.
• Once in app settings you'll notice a section called "Configuration" with a switch for Bluetooth access.
Finally, as always, we're here to help. Let us know if anything isn't working as you expect or is unclear or confusing. We're always working to improve our products and your feedback is critical to make them the best they can be. Contact us at: support@sensorpush.com
NEXUS 6P WIFI DIRECT ISSUES
Please note: There is currently an issue with the Nexus 6P and WiFi Direct. This issue prevents the Nexus 6P from being able to configure the G1 WiFi Gateway.
The system will work normally with the Nexus 6P otherwise, but you will need to use a different device to set up your gateway. Once finished, you can log into the account you create during setup from the SensorPush app settings on your Nexus 6P. Access this screen using the button in the upper-left corner of the main screen of the app. Then tap "Log In" and enter the email address and password you created during gateway setup.
We apologize for any inconvenience. For more information, please see these resources: Android Issue Tracker (232695) | Android Issue Tracker (232714).
Android forum member reported that the Android 7.1.2 beta resolves this issue, so it is likely no longer a problem. Furthermore, this does not apply to the majority of our customers as most devices use a newer version of Android.
