There are a few things that could cause your Sonicu Meter or Gateway to be able to appear on your network, but not populate on your SoniCloud Dashboard. It is recommended to work with Sonicu and your Local IT Department to resolve these issues.
1. Network Requires 802.1x Authentication - Sonicu Meters and Gateways do not support 802.1x authentication at this time. If your local network requires 802.1x Authentication, Sonicu meters will not be able to connect to the server. 802.1x is often referred to WPA2-Enterprise, and is commonly found on Enterprise Networks. This type of authentication requires each individual user to enter a username and password to be able to be granted access to the Network. Since Sonicu meters only send packets of data, they do not have the ability to enter a unique user ID and passkey to get through the local firewall to AWS servers.
2. Network Requires Approval Through Captive Portal - If your local network employs a captive portal to grant users access to the internet, Sonicu meters will not be able to connect to the server. A captive portal is a Web page that the user of a Public-Access Network is obliged to view and interact with be access is granted. Captive portals are typically used in Business Centers, Airports, Hotels, Hospitals, Restaurants, and other venues that offer free Wi-Fi hot spots for internet users. Our meters do not have the ability to accept network terms, therefore cannot function if a Captive Portal is in place. If a Captive Portal is in place, Sonicu devices will need to be whitelisted to get through them (See #5).
3. HTTP Redirects to HTTPS - For Sonicu meters to connect to our servers, they must be able to speak to a specific web address. If your network is set to automatically redirect any web traffic from an HTTP address to an HTTPS address, our meters will not connect. HTTP traffic must be allowed on your network for Sonicu meters to connect to and receive data from AWS servers. If you cannot enable HTTP on your network, these devices can be reconfigured to Binary (see #4).
4. Network Does Not Allow Binary Traffic - Newer Sonicu meters are, by default, set to send data as HTTP traffic on your network. This makes the data packets sent by Sonicu meters appear as normal web traffic on your network. An alternate data transmission method can be enabled to communicate as binary TCP traffic instead of HTTP compliant TCP packets. Binary traffic uses TCP to transmit data to a destination (port 80) that is encoded but may be filtered out by traffic inspection devices. If your internal traffic inspection devices require valid HTTP payloads when using TCP and port 80, binary traffic must be allowed on your network or the specific MAC addressed may need to be whitelisted.
5. Network Requires Whitelisting - Some networks require Whitelisting to communicate on your network. There are 2 different possible stages of Whitelisting. First, specific MAC addresses may need to be whitelisted on your network to allow them to send traffic through or receive traffic from the server. Second, the specific server domain may need to be whitelisted to allow traffic to go from your network to that specific address. If either the server domain, or the meters are blocked, they will not be able to connect to AWS Servers.