Alert Types and Possible Causes of Alerts


Created: ; updated: .

If your system has been setup with Alerts you may see some of the following alerts sent through to you:

device comms timeout

Device Comms Timeout alerts mean that the system can no longer see a device that is attached to one of your Observant units (C3 or Solo).

Level at Tank is very high

"Level at site x is low or high"

This is a very common alert and is one that could come in several formats. In this instance a very high alert will be due to the measured level of the water in a tank reaching a pre-determined height.

Observant can create alerts for the up to four different level for most tank sensors:

  • Very Low
  • Low
  • High
  • Very High 
This alert means that the water level at the site has gone above or below the pre-set points set by Observant Support
 If this is not expected, investigate the cause such as a burst or blocked pipes, faulty pipes or excess water usage from the tank . 
Pressure is very high

Where a pressure sensor has been input into Observant Unit it is possible to create a pressure alert much like a tank level alert (above). The pressure alerts will be at predetermined levels and will require support from Observant to create.

Estop engaged

This alert will be sent out only when a customer's M2 has been stopped using the emergency stop button on the front of the M2 panel. In most cases pressing the e-stop button can be cleared simply by popping the button back out to its normal position.

No Flow

This alert is sent from a flow meter connected to an Observant unit. The flow meter can only be given one alert. The alert is a "No flow for 'x' hours". 

For example, most customers use an alert: No flow for 24 Hours.

low battery level

"Power at site x alert: Low Battery Level"
The Observant units will by default alert a customer (with alerts enabled, please see our alerts article: Creating SMS and Email Alerts) when their units reach 40% charge level.

This means the Observant field unit has a low battery. This could be caused by insufficient sun or perhaps the field unit is powering something external that is draining the battery e.g.: a pump control relay.
The battery should recover within 24 hours.Most customers find that after a single day of sun the units charge back up. If it doesn’t, please submit an "I need help with Observant Global" Support Ticket to the Observant Help Desk.
See: How to Diagnose a Low Battery on a C3 Field Unit

riser at Bay 21 error: Insufficient power

This alert is sent out to customers with iRiser products. This indicates that the unit received a command to open or close, however it did not have enough power to complete the required command.

Conduit not connected

This alert refers only to 3G units. This means that the 3G unit is no longer connected to the Telstra network, and by extension Observant Global. Without a connection the unit will not be able to give any update or support any UHF or 900MHz units that need it to connect.

Typical reasons for this unit not connecting are:

  • Telstra Tower is down.
  • Observant unit is not powered on (low battery).
  • Observant unit has damage (usually antenna, but possibly the unit itself)

For more information see the articles, 

Equipment connection error
Usually this alert means the problem relates to the wiring between the communications device and the Observant field unit. This indicates the Observant equipment is not drawing power.

Sometimes there can be problems with the connection between the Observant equipment and what it is connected to (e.g. camera, level sensor etc.). This is usually reported as a device communication error, or that the device is not “drawing power as expected". The cause will often be a failure in the cabling.
Other Alerts
If you receive a different type of alert that is unclear, please click on 'Submit a request'  and send an "I need help with Observant Global" 'Support Ticket' to our Support Team.
Have more questions? Submit a request
Powered by Zendesk