Where it is used
All the cases below share one thing: the points are scattered, the readings are infrequent, and a cable to each point costs more than the measurement itself.
Water supply
A well, a tank and a pump between them. Level probes in both vessels, floats for emergency thresholds, a controller that starts and stops the pump. The rule lives in the server: below a threshold in the tank — run; above the upper one — stop; on dry running — stop and raise an alarm.
- Level in well and tank, in metres and in per cent
- Automatic and manual pump mode, with a record of who switched when
- Solenoid valves per branch
- Alarms on dry running, overflow and loss of power
Buildings and plant rooms
Temperature, humidity and the state of air-conditioning units on roofs and in technical rooms. A deviation shows up before it becomes a failure, and the history says whether the problem is new or returns every summer.
- Temperature and humidity by zone
- State and mode of air-conditioning units
- Energy consumed per panel
- Doors and cabinets opening
Farming and open ground
Soil moisture, air temperature, rainfall, level in an irrigation channel. The points are kilometres apart and without power — exactly the case the protocol was invented for.
Municipal infrastructure
Pumping stations, meter chambers, street lighting, equipment monitoring. One gateway on a tall building covers a significant part of a small town.
How a site starts
- Survey and range test. What is heard from where is established before equipment is ordered.
- Gateway installation. Height and antenna — that is what decides coverage.
- Devices in place. Each is registered in the server and checked live.
- Rules and alarms. Thresholds are set after a few days of real data, not from a catalogue.