A connectivity test is a mandatory step in the Silvanet Deployment App installation process for Generation 2 gateways. During installation, the app checks whether a Border or Mesh Gateway can successfully connect to the required networks before activation. This includes verifying the device’s connection to the local mobile network (LTE-M/NB-IoT) and your Silvanet site’s LoRaWAN network. Completing this step ensures that the gateway is positioned in a location with stable, reliable connectivity before it becomes active on your Silvanet site.
How It Works
When you initiate a connectivity test in the Silvanet Deployment App, the gateway performs one of two checks depending on its type and configuration:
1. Border Gateways (Cellular Connectivity Check)
For Border Gateways with cellular capability, the app verifies that the device can register with the local LTE-M or NB-IoT network. This confirms that the gateway can reliably send data to the Silvanet Cloud once installed.
If Ethernet (PoE) is used, the app verifies that the LAN connection is stable and active.
Please see our article Mesh Gateway Connectivity Test for step-by-step instructions
2. Mesh Gateways (LoRaWAN Connectivity Check)
Confirms the gateway can receive and transmit LoRa messages, and
Whether the surrounding environment provides sufficient line of sight for stable communication with nearby devices.
Please see our article Border Gateway Connectivity Test for step-by-step instructions
Result
If tests succeed, the Deployment App confirms that the gateway has safely been activated.
If tests fail, the app will display an error and prompt corrective action before installation can continue.
How the Connectivity Test Is Performed
The connectivity test is completed within the Silvanet Deployment App as part of the installation workflow. The steps are:
-
Install Device and Start the Test
Scan the device’s NFC tag to register it and begin the connectivity test.
-
Test Duration Displayed
The app will show the expected test duration:Border Gateway: up to 60 minutes
Mesh Gateway: typically around 15 minutes
-
Retrieve the Results
When the test is completed, scan the device’s NFC tag again. This retrieves the final connectivity results.
Failure to rescan the device will leave the test in and open state "Testing Connectivity" and the app will not notify user if the device becomes active.
-
View the Outcome
The app will display one of the following statuses:Deployed — the connectivity test was successful
Connectivity Test Failed — the device did not meet the required connectivity thresholds during the test
Note: The Deployment App is a support tool and only reflects the results of the connectivity test you performed at that moment. Devices may successfully connect after a failed test, but this will not be reflected in the Deployment App. Any later successful connections can be viewed in the Silvanet Site Management App.
What To Do If the Connectivity Test Fails
If a connectivity test fails, it indicates that the gateway cannot communicate reliably with the required networks. Use the guidance below to resolve the issue:
1. Check Installation Height & Positioning
Gateways must be mounted vertically and at least 3–4 meters high.
Increase height if the area has obstacles such as trees, rocks, or buildings.
Ensure antennas are correctly attached and not damaged.
2. Improve Line of Sight
Dense vegetation, terrain, or structures can obstruct LoRa signals.
Move the gateway to a position with a clearer line of sight.
Avoid placing the gateway behind hills, dense tree clusters, or metal structures.
3. Verify Power & Solar Charging
Low power can interrupt network registration.
Ensure the device has been charged in direct sunlight for at least 2–4 hours.
Confirm that the solar panel is securely connected and facing the sun at noon.
4. Confirm Cellular Coverage (Border Gateways)
If using the internal eSIM:
Move the gateway to an area with better LTE-M/NB-IoT signal strength.
Confirm the local network provider listed at the deployment location supports LTE-M/NB-IoT.
If using Ethernet (PoE):
Ensure the LAN cable is working and the port provides internet access.
Confirm the PoE injector is fully sealed and powered.
5. Retry the Test One Gateway at a Time
For accurate testing, only one gateway should be tested at a time.
Running tests on multiple gateways simultaneously can cause failures.
6. Contact Dryad Support if the Issue Persists
If all steps above have been checked and the test still fails, contact:
support@dryad.net, Include the device ID, site name, and screenshots of the error message.
Comments
0 comments
Please sign in to leave a comment.