
CLOVER Agriculture Sensor
The CLOVER Agriculture Sensor is is the ideal solution to streamline and simplify the collection of key soil and environmental metrics for crops, residential and commercial lawns and gardens and golf courses.The device provides a straightforward and easy to deploy solution for soil moisture and temperature, air temperature and humidity, and outdoor light monitoring. Enjoy increased crop yields and decreased operating expenses with the deployment of this versatile device. The CLOVER utilizes a ruggedized IP-67 enclosure for use in the most challenging outdoor environmental conditions. An integrated C-Cell LTC battery provides substantial battery life up to 10 years with a battery status indicator for easy reference.
About this device
The CLOVER Agriculture Sensor is is the ideal solution to streamline and simplify the collection of key soil and environmental metrics for crops, residential and commercial lawns and gardens and golf courses.The device provides a straightforward and easy to deploy solution for soil moisture and temperature, air temperature and humidity, and outdoor light monitoring. Enjoy increased crop yields and decreased operating expenses with the deployment of this versatile device. The CLOVER utilizes a ruggedized IP-67 enclosure for use in the most challenging outdoor environmental conditions. An integrated C-Cell LTC battery provides substantial battery life up to 10 years with a battery status indicator for easy reference.
The CLOVER Agriculture Sensor supports 7 regional frequency plans and operates as a Class A LoRaWAN device. A payload codec is published in the repository, so uplinks are decoded automatically when you onboard it to The Things Stack.
Key features
- Sensors: moisture, temperature, humidity.
- LoRa Alliance certified, verified interoperability with The Things Stack and other LoRaWAN network servers.
- Payload codec included, uplink decoder ready for one-click activation.
- 7 frequency plans supported: AS923, AU915-928, EU863-870, IN865-867, KR920-923, RU864-870, US902-928.
- Battery powered (C-Cell LTC).
Vendor
At a glance
Hardware specifications
| Model ID | t00059xx-clover |
| Dimensions | 58 × 93 × 120 mm |
| IP rating | IP67 |
| Operating temperature | -40 °C to 65 °C |
| Power | Battery — C-Cell LTC |
Sensors & capabilities
Certifications & compliance
| Safety | 60950-1 — IEC |
| Safety | 60950-1 — UL |
Standards
Network profiles
Capabilities are defined per firmware version and frequency plan, exactly as published in the repository.
Firmware 1.0
| Frequency plan | MAC | Reg. params | Class | Join | Max EIRP | Certified |
| AS923 | 1.0.2 | RP001-1.0.2-RevB | A | OTAA | 16 dBm | ✓ Yes |
| AU915-928 | 1.0.2 | RP001-1.0.2-RevB | A | OTAA | 30 dBm | ✓ Yes |
| EU863-870 | 1.0.2 | RP001-1.0.2-RevB | A | OTAA | 16 dBm | ✓ Yes |
| IN865-867 | 1.0.2 | RP001-1.0.2-RevB | A | OTAA | 30 dBm | ✓ Yes |
| KR920-923 | 1.0.2 | RP001-1.0.2-RevB | A | OTAA | 14 dBm | ✓ Yes |
| RU864-870 | 1.0.2 | RP001-1.0.2-RevB | A | OTAA | 16 dBm | ✓ Yes |
| US902-928 | 1.0.2 | RP001-1.0.2-RevB | A | OTAA | 30 dBm | ✓ Yes |
Frequency plan coverage
Live decoder playground
Decode any hex payload client-side with the device's published codec, the exact code The Things Stack runs.
// pick an example or paste a payload, then Decode
Example uplink from The Things Stack
The full JSON message your application receives via MQTT or webhook when this device sends the payload above, raw bytes, decoded fields and radio metadata included.
// decode a payload above to see the full envelope
Codec source
// loading codec…
Add to The Things Stack
Manual setup
Create an application
In The Things Stack console, go to Applications → Create application and pick a unique application ID.
Register an end device
Choose From the LoRaWAN Device Repository and search for “CLOVER Agriculture Sensor”. Select your firmware version and frequency plan.
Enter device credentials
Provide the DevEUI, JoinEUI and AppKey printed on the device label or QR code.
Power on & verify uplinks
Within a few minutes you'll see the join request and decoded uplinks in the Live data tab.


