Device troubleshooting

Possible solutions to Silvanet Gateway and Sensor alerts and warnings.

If a Silvanet device has connectivity, charging or other issues, troubleshooting messages are displayed the Device overview section of a Site.

Messages can be alerts, warnings or notifications.

Icon	Message type	Description
	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

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.

Issue: Connectivity strength poor

Connectivity issue (firmware update required - warning only)

Problem: Connectivity strength of device is poor

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.

Resolution: Check range, topology and/or deployment

Range

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.

Topology

Ensure a feature of Site topology is not preventing or hindering transmitting signals. This could be rocks or hill, a newly installed structure, or anything that might hinder a reliable connection.

Possible solutions include adding a Mesh Gateway to the Mesh Network or deploying the Mesh Gateway higher on the tree.

Deployment

Ensure each Mesh Gateway is connected to two or more other Gateways (Mesh or Border). This ensures redundancy should one of the Mesh Gateways needs charging.

This may require visiting the Site to visually inspect the device.

Issue: Device not charging for 72 hours

Device not charging for three days (72 hours)

Problem: The device not charging as expected for 72 hours

For the last 72 hours, the Silvanet device has not charged or has not fully charged and needs immediate attention to resolve the issue.

Resolution: Check power source, obstructions, damage, mounting

Border Gateway not charging.

Possible solutions:

Solar

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.

Mains

If PoE is used, ensure the Border Gateway has a power supply from a mains source.

If not, possible solutions include:

• Ensure the power supply has not been turned off or disconnected.

• Ensure the PoE has not been disconnected from the Border Gateway.

This may require visiting the Site to visually inspect the device.

Mesh Gateway not charging.

Possible solutions:

Obstructions

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.

Mounting

If the solar panel has no obstructions, check the device's mounting position:

• Ensure the Mesh Gateway is mounted at least 3 meters above the forest floor, or higher.

• Ensure the Mesh Gateway has been installed correctly (facing towards the sun at 12:00 noon).

This may require visiting the Site to visually inspect the device.

Wildfire Sensor not charging.

Possible solutions:

Obstructions

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.

Mounting

Ensure the Wildfire Sensor has been correctly mounted (facing the sun at 12:00 noon).

This may require visiting the Site to visually inspect the device.

Damaged

Inspect the Wildfire Sensor for vandalism or damage, especially the device's solar panel.

This may require visiting the Site to visually inspect the device.

Issue: Device not reachable

Device not reachable due to connectivity and charging issues

Problem: Silvanet Cloud could not reach device for 24 hours

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.

Resolution: Check charging, connectivity, mounting, damage

Charging

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 Charging issues.

Connectivity

If the device has inadequate connectivity, refer to Connectivity issues.

Mounting

Check if the device has been properly mounted on a tree or pole (solar panel facing towards the sun at 12:00 noon).

This may require visiting the Site to visually inspect the device.

Damaged

Inspect the device to ensure it has not been vandalized or damaged.

This may require visiting the Site to visually inspect the device.

Warnings

The underlying issues that triggered warnings need to be resolved as soon as possible.

Issue: Connectivity not optimal

Connectivity not optimal

Problem: The connectivity strength of this device is not optimal

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.

Resolution: Check range, topology and/or mounting

Range

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.

Topology

The topology of the deployment Site may interfere with the connectivity strength of a device. Possible solutions include:

• Check for obstructions that hinder signal strength such as rocks, hillsides, newly installed structures. If this is the case move the device.

• Add another Mesh Gateway to increase connectivity.

• Mount the device higher on the tree or pole for better connectivity.

Deployment

Adding another Mesh Gateway may improve connectivity. This ensures the Wildfire Sensors and other Mesh Gateways are within range.

Issue: Device not charging for 24 hours

Charging not optimal

Problem: Device not charging as expected for 24 hours

Resolution: Wait 24 hours then check

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 Charging issue above).

Issue: Firmware update required

Firmware update required

Problem: Device firmware requires updating

Resolution: Dryad Engineering or reseller schedules an update

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.

Issue: Device in calibration period and not activated

Problem: Wildfire Sensor is still calibrating

Resolution: Wait 14 days to allow the calibration to complete

During the calibration period, the Wildfire Sensor does not send usable data to the Silvanet Cloud.

Notifications

Notifications indicate issues currently affecting the device but do not require user actions to resolve.

Issue: Device communication pending

Problem: This device is experiencing delays in sending environmental data to the Cloud

Fire detection is still operational.

Resolution: No user-actionable response required

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.