The Dragino D20S-NS is the D20 with the probe that is allowed into the ground: the same DS18B20, but in a TPE-sheathed cable that Dragino explicitly intends for burial in soil and in road surfaces. Two metres of cable take the probe to the depth where the question is decided — root zone, frost line, carriageway surface — while the IP66 enclosure stays up on the post and transmits. This version transmits without a gateway over NB-IoT onto the cellular network while being solar powered — the most demanding of the energy budgets, because cellular consumes more than LoRaWAN and the cell holds only 3000 mAh.
- −55 … 125 °Cprobe range
- ±0.5 °Ctypical, max. ±2.0 °C
- 2 m TPEburiable probe cable
- IP66enclosure, probe IP65
- 3000 mAhLi-ion, solar charged
What defines the D20S-NS
- The probe is built to be buried: Dragino explicitly describes the S version as “designed for use in soil or road” and names TPE for the cable. That is the difference from the D20 — there the cable material is left open; here it is named, and TPE is the sheath that neither hardens nor turns brittle in the ground.
- A measuring range that covers most applications: −55 to +125 °C is not a marketing figure but the DS18B20’s range. For soil temperature that is far more than needed — and precisely why the same article stays usable when the next measuring point is on a heating return.
- Two metres of cable take the probe down: the device stays up where it has coverage and remains reachable; the probe lies at twenty centimetres, at half a metre, or under the surface. On a compact sensor both would be in the same place — unthinkable for a soil measurement.
- A digital bus, not analogue technology: the DS18B20 delivers a digital value. There is no characteristic curve to store, no line loss to compensate and no calibration at commissioning — unlike PT100s or thermocouples.
- An alarm flag in every message: a dedicated bit shows whether the value has left a set threshold. Thresholds are set by downlink, and so is the minimum time between two alarm messages — a sensor sitting at the frost line therefore does not flood the network.
- Recording when the network drops: if coverage fails, the device writes timestamped readings to its own memory and sends them on once the network is back. At measuring points out in a field, where coverage fluctuates, that is no side issue.
- Device status travels along: cell voltage, device model, IMEI and serial number sit in the same message as the readings. For a fleet that means the inventory can be kept from the running data stream without querying the device — and the cell voltage doubles as the early warning before a battery change.
- No battery change planned in: the solar panel charges a rechargeable 3000 mAh Li-ion cell. With sufficient light the replacement cycle disappears — at hard-to-reach measuring points the larger item over the service life. It still supplies the cellular module’s short, high currents.
- Configuration without a network server: reporting interval and thresholds are set on the device or sent back through your own server. There is no LoRaWAN network server managing downlinks here — that responsibility sits with your platform.
- No gateway, no network server: the device transmits straight onto the cellular network and sends its data to your endpoint. No device profile, no join, no key management — but a SIM that wants managing.
- The same electronics, four probe variants: anyone measuring above ground takes the D20 with its stainless probe; two measuring points on one device, the D22; three, the D23. Decoder and integration stay the same.
Where the D20S-NS is used
- Soil temperature in arable farming: germination temperature, timing of cultivation, spring warming. The probe sits at sowing depth, the device at the field edge.
- Frost warning in orchards and vineyards: soil temperature leads air temperature and is therefore an earlier indication than the air sensor alone.
- Road and path maintenance: surface temperature for black-ice warning and gritting plans — Dragino names the road surface explicitly as a place for this probe.
- Sports turf and golf greens: root zone temperature drives fertilisation, irrigation and playability.
- Greenhouse and raised bed: substrate temperature rather than air temperature — the quantity that actually governs root growth.
- Compost and silage: the probe sits in the heap, the device on a post. Self-heating caught early is the difference between turning the pile and a fire.
- Ground collectors and infiltration systems: temperature at the laying horizon, over years and without excavation.
- Large rollouts: one article, one decoder, one spare — and through the D20S-LS, D20S-NB and D20S-CB variants the same measuring technology with a different form of power or radio.
That covers the purchase decision. What follows is the depth needed for installation, integration and operation.
What “buriable” demands in practice
The manufacturer’s statement is brief: TPE sheath, two metres, for soil and road surfaces. That is half the answer. TPE really is the right sheath for this purpose — it stays flexible in the cold, absorbs almost no water and withstands UV and hydrolysis considerably better than soft PVC. What the statement does not contain is everything beyond the sheath.
Consequence for installation: three things decide whether a buried measuring point lasts for years. First, strain relief at the enclosure — the cable should not carry the load; a loop and a fixing to the mast should. Second, protection against the next spade: most failures come not from ageing but from the next excavation, which is why the position belongs marked and the cable, where possible, run inside a conduit. Third, a depth that matches the question — sowing depth is five to ten centimetres, the frost line sits around eighty depending on the region, and both with the same probe is not possible.
Assessment from field practice, not a manufacturer statement: with soil temperature the sensor’s own error is rarely the problem; the spread between two measuring points in the same field regularly exceeds the DS18B20’s half a degree. Anyone wanting to judge an area gains more from two simple measuring points in different places than from one more accurate one. And the laying depth belongs on record — a soil temperature without a stated depth is not a usable figure.
Payload and integration
Without LoRaWAN the whole apparatus of ports, device profiles and decoders falls away: there is no FPort, no network server and no payload function for anyone to maintain. The device opens a connection to the cellular network and delivers the same values — cell voltage, measured quantities, alarm flag, device identity — straight to your endpoint.
Consequence for the integration: what was the decoder in the network server under LoRaWAN is here the receiver on your side. That is less infrastructure but the same work — the raw format has to be interpreted once. The exact field order is in the manufacturer’s cellular manual, linked under “Documents”; it differs from the LoRaWAN version and belongs held against a real message once at commissioning.
One point regularly overlooked on cellular devices: the device identity comes from the IMEI and serial number, not from a DevEUI. Anyone running a fleet of LoRaWAN and cellular devices together needs a key field that can take both.
No gateway — what that costs and what it saves
NB-IoT uses the cellular network that is there anyway. So there is no gateway infrastructure to build, no coverage to plan and no network server to run. In return every device needs a SIM card and a server that accepts the data — the costs do not disappear, they move from the initial investment into running expenses.
The arithmetic that comes first: a single sensor somewhere remote is a clear case for cellular — a gateway for one device never pays. Thirty sensors on one site are an equally clear case for LoRaWAN. The boundary lies, depending on tariffs, somewhere between five and ten devices per site, and it shifts with the question of whether anyone is there to look after a gateway.
Assessment from field practice, not a manufacturer statement: what is regularly underestimated is not the radio technology but the SIM. Many standard data cards are not enabled for NB-IoT at all, and that only shows when the device fails to get onto the network at the site. On top comes administration: a hundred LoRaWAN devices hang on one network server, a hundred NB-IoT devices on a hundred SIM contracts with terms and invoices. That is not a technical but an organisational argument — and on larger fleets it decides more often than range does.
Connecting to your own server
The device speaks MQTT, MQTT over TLS, TCP and UDP. MQTT with TLS is the right choice for most applications: widespread, economical and encrypted. UDP is more economical still and therefore kinder to the battery, but offers no delivery guarantee — usable where individual lost messages are tolerable.
Server, port, credentials and topic are set on the device. There is no network server decoding the payload; the device sends straight to your endpoint. Decoder maintenance falls away, and responsibility for reachability and certificates rests with you.
Solar and cellular — the tightest energy budget
Solar and cellular are each manageable on their own; together they are the most demanding combination. A cellular module draws short, high currents when establishing a connection and, over the day, needs considerably more than a LoRaWAN transmitter, and the solar cell has only 3000 mAh, a good third of the lithium primary cell’s capacity. What works effortlessly in summer can tip over in December.
Consequence for planning: the reporting interval is not a comfort parameter here but the decisive lever — and radio quality at the site shifts the balance again, because a device at the edge of coverage transmits with more power and stays awake longer. Anyone combining solar and cellular plans the interval around winter.
Assessment from field practice, not a manufacturer statement: for this version Dragino gives neither a battery life nor a minimum irradiation — consistent, with three independent variables. What is usable instead is the cell voltage that comes with every message: anyone watching it through the first winter knows afterwards whether the site carries.
Data at a glance
| Sensing element | 1 × Dallas DS18B20, IP65, 2 m cable with TPE sheath, for burial in soil or road surface |
| Temperature | −55 … +125 °C · ±0.5 °C typical, up to ±2.0 °C maximum · resolution 0.1 °C |
| Operating temperature | −40 … 85 °C (device) |
| Radio | NB-IoT via Quectel BC660K-GL · B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85 in H-FDD |
| Protocols | MQTT · MQTT over TLS · TCP · UDP |
| SIM | GE version: without SIM · nano-SIM slot · 1T version: 1NCE SIM, 500 MB over 10 years |
| Payload | raw format straight to your own endpoint · no FPort, no network-server decoder · field order in the manufacturer’s cellular manual |
| Configuration | on the device or through your own server’s return channel · Bluetooth 5.1 on site · firmware update over the air |
| Power | solar panel with rechargeable 3000 mAh Li-ion cell · no battery-life figure from the manufacturer |
| Enclosure | IP66 · 200 × 120 × 55 mm · 372 g |
| Versions | D20S-LB LoRaWAN battery · D20S-LS LoRaWAN solar · D20S-NB NB-IoT · D20S-NS NB-IoT solar · D20S-CB LTE-M and NB-IoT · D20S-CS LTE-M and NB-IoT solar |
What the manufacturer does not state: a maximum laying depth, any statement on rodent resistance and a dimensioned drawing of the probe are all missing; the diameter and length of the sensing head appear neither on the product page nor in the manual. Whether the probe may sit permanently in groundwater is also unanswered — IP65 is specified for jets of water, not for permanent submersion. We are asking the manufacturer and will add it here.

Reviews
There are no reviews yet.