Device troubleshooting
Possible solutions to Silvanet Gateway and Sensor alerts and warnings.
Last updated
Was this helpful?
Possible solutions to Silvanet Gateway and Sensor alerts and warnings.
Last updated
Was this helpful?
If a Silvanet device has connectivity, charging or other issues, troubleshooting messages are displayed the section of a Site.
Messages can be alerts, warnings or notifications.
Alert
The Silvanet device requires immediate action to resolve the underlying issues.
Warning
The Silvanet device is not performing optimally. The underlying issue should be resolved, but the device is still functioning normally.
Notification
No user-actionable resolution required. Information only.
Alerts require your immediate attention. The device is not functioning properly. it is necessary to resolve the underlying issues as soon as possible to ensure continued monitoring.
Alerts need to be immediately resolved to ensure continued monitoring.
Ensure the Silvanet device has been deployed within its maximum range. Possible solutions include adding a Mesh Gateway or moving the Mesh Gateway closer to the sensors that are out of range.
This may require visiting the Site to visually inspect the device.
Border Gateway not charging.
Possible solutions:
If the solar panel(s) are the only power source, ensure it is charging the Border Gateway.
If not, possible solutions include:
Ensure the solar panel is still connected to the Border Gateway.
Inspect the solar panel to determine if it has been vandalized or tampered with.
Ensure the solar panel has been installed correctly (facing towards the sun at noon, no obstructions).
This may require visiting the Site to visually inspect the device.
Mesh Gateway not charging.
Possible solutions:
If the Mesh Gateway's solar panel is not charging the device, possible solutions include:
Ensure the solar panel is not obstructed by an overhanging branch or new growth on the tree.
Ensure the solar panel is not obstructed by a new structure blocking access to sunlight.
Inspect the solar panel for damage or vandalization.
This may require visiting the Site to visually inspect the device.
Wildfire Sensor not charging.
Possible solutions:
Ensure the Wildfire Sensor is not obstructed by overhanging branches or new growth on the tree.
This may require visiting the Site to visually inspect the device.
For the last 24 hours, the Silvanet Cloud has been unable to reach the device. Resolve this issue immediately to ensure reliable environmental monitoring.
Firmware updates cannot be performed. If the problem persists, contact Customer Support.
The underlying issues that triggered warnings need to be resolved as soon as possible.
The connectivity is at two bars of strength. The device's connectivity strength is not optimal, which may affect features such as firmware updates or environmental monitoring.
Even if a device is within the specified range, decreasing the distance between Mesh gateways or between Mesh Gateways and Wildfire Sensors may improve connectivity.
This issue has been identified, Dryad has been notified and a firmware update has been scheduled. Dryad has been notified and will plan an update to the device's firmware.
During the calibration period, the Wildfire Sensor does not send usable data to the Silvanet Cloud.
Normal communication should be reestablished soon.
If connectivity remains a problem, this will change to a Warning or Alert, depending on the duration and type of connectivity.
Connectivity is at one bar of strength. Resolve the issue as recommended. The device's connectivity strength affect features such as firmware updates or environmental monitoring.
For the last 72 hours, the Silvanet device has not charged or has not fully charged and needs immediate attention to resolve the issue.
If the device has not been charging for an extended period (such as beyond three days), it cannot send a "is alive" message. Refer to .
If the device has inadequate connectivity, refer to .
If the device is still not charging after 48 hours and especially after 72 hours, the cause must be resolved immediately. In this case an alert is sent (see above).
