Weenat sensors can signal certain events when unusual behavior is detected in the field.
These automatic alerts are designed to help you quickly identify a potential issue — whether physical, electronic, or environmental — and address it easily.
In this article, you’ll find: a clear description of each detected event, the likely cause of the problem, and recommendations for effective action. 🙂
No message received
The sensor hasn’t sent any data for a while.
This event occurs when the app doesn’t receive any messages for 24 hours.
It is different from the event triggered by two consecutive missing data packets (~30 minutes). In that case, the last measurement time appears in red.Possible causes:
- Power outage (empty or disconnected battery)
- Sensor under dense vegetation cover (especially ground-level sensors): weak signal to relay antennas
- Network issue (Sigfox, LoRa, or NB-IoT depending on the model)
- Sensor malfunction or damaged antenna
Recommended actions:
- Check battery level; it should be 3.6 V
- Ensure the antenna is properly in place (machinery, animals...)
- Contact Customer Support if the issue persists: check network suitability or consider an antenna extension
Sensor moved
This event is triggered if the sensor was moved by at least 500 m and a new geolocation message was received.
Possible cause:
- The sensor was moved accidentally or intentionally
Recommended actions:
- If you moved it, reset it with a magnet on the right side of the casing (solid red LED)
- If not, check its location and reset it the same way
Sensor tilted
The sensor detects an abnormal tilt (it is no longer in an upright position). When this happens, it automatically enters wintering mode and stops taking measurements in order to preserve battery life.
This event is triggered as soon as the antenna is no longer facing upward.
However, some sensors, such as PAR sensors or pyranometers, can be installed upside down to measure reflected radiation. In such cases, the sensor incorrectly considers itself to be lying down.Possible causes:
- Support pole or stake collapse
- Sensor was hit or knocked over (wind, machinery, animals...)
- Sensor was deliberately stored for winter or transport
Recommended actions:
- Reposition the sensor upright and make sure it's secure
- Check the support’s stability (use a bubble level)
- Ignore the event if the sensor was purposely stored/transported
- Reset the sensor with a magnet after transport
Stuck tipping spoon
Applies only to sensors with rain gauges. The spoon is no longer tipping correctly: rainfall is not being recorded. The system detects if the spoon hasn't tipped for 4 hours.
The frequently stuck spoon event
is triggered if it occurs at least 10 times, meaning it's a recurring issue.
Possible causes:
- Debris (leaves, insects, dirt, nest...) blocking the mechanism
- Component failure in the tipping spoon system
Recommended actions:
- Gently inspect and clean the spoon (remove the bowl)
- Also clean the rain gauge bowl
- If it’s a nest, remove it and install the anti-debris grid and spikes
- Regularly inspect during dense vegetation and autumn
The events detected by Weenat sensors are designed to help you maintain the accuracy of your weather and agronomic measurements. They don’t always indicate a serious issue, but they do require your attention to ensure reliable monitoring and avoid data gaps.
Remember to perform regular visual checks on your sensors and ensure their integrity.
Ground-level sensors can be damaged by farm machinery. Make sure they are visibly marked (stakes, nets, PVC tubing) without blocking the antenna.
For any questions, you can contact Weenat Support directly through the app. 🙂