Use case
Remote temperature monitoring
A temperature sensor is only useful if someone hears about it when the reading goes wrong, and most cheap wifi sensors send an app notification to one phone, if that phone is on.
NoDisrupt is the alerting and history side. Any device that can make an HTTPS request, an ESP32, a Raspberry Pi or a gateway with a scripting hook, posts its readings to an asset monitor. You set the limits; escalation policies make sure a person actually responds.
Works on the Free plan. No card to start.
Start freeHow it works
- Step 1
Create an asset monitor
The app gives you a feed URL and a key for that one sensor, and waits for the first reading.
- Step 2
Post readings from the device
Send JSON with any metric names you like, for example temperature_c and humidity_pct. Each name becomes a metric on first sight.
- Step 3
Set the limits
Give each metric a threshold, such as temperature_c above 8. A reading outside it raises an incident.
- Step 4
Decide who gets woken up
Escalation policies send email first, then SMS or a phone call to the next person if nobody acknowledges.
curl -fsS -X POST "https://api.production.nodisrupt.com/monitor/<id>/feed" \
-H "Authorization: Bearer $FEED_KEY" \
-H "Content-Type: application/json" \
-d '{"metrics": {"temperature_c": 4.5, "door": "closed"}}'import json, os, time, urllib.request
FEED_URL = os.environ["FEED_URL"]
FEED_KEY = os.environ["FEED_KEY"]
def send(metrics):
req = urllib.request.Request(
FEED_URL,
data=json.dumps({"timestamp_s": int(time.time()), "metrics": metrics}).encode(),
headers={"Authorization": f"Bearer {FEED_KEY}", "Content-Type": "application/json"},
method="POST",
)
urllib.request.urlopen(req, timeout=10)
while True:
send({"temperature_c": read_temperature(), "humidity_pct": read_humidity()})
time.sleep(60)Typical readings
| Watch | Metric or check | Example alert |
|---|---|---|
| Air temperature | temperature_c | Outside the range you set |
| Relative humidity | humidity_pct | Above 60% |
| Door or lid state | door (text) | Equals open |
| Sensor battery | battery_pct | Below 20% |
| Sensor offline | no data received | No reading for 10 minutes |
- NoDisrupt does not sell sensors. You need a device that can send an HTTPS POST, directly or through a gateway.
- Readings arrive over HTTPS only. There is no MQTT, LoRaWAN or Bluetooth receiver.
- It is an alerting and history tool, not a certified compliance logger. If an inspector requires calibrated, certified equipment, keep that and use NoDisrupt for the alerts.
- Each sensor is one monitor, so Free covers 10 sensors with email alerts and 3 months of history. Paid plans keep up to 24 months and include SMS and phone credits.
Common questions
Which temperature sensors work with NoDisrupt?
Any sensor whose readings reach a device that can make an HTTPS request: an ESP32 or ESP8266 with a DS18B20 or SHT3x probe, a Raspberry Pi with a USB or I2C sensor, or a commercial gateway that supports webhooks or scripts.
Can I get a text message when the temperature is too high?
Yes. Paid plans include SMS and phone-call credits, and escalation policies decide who is texted and when the alert moves to the next person.
How often should a sensor report?
Once a minute is plenty for rooms, fridges and freezers. Set the no-data window a few readings longer, so one dropped packet does not page anyone.
What happens if the sensor itself stops working?
The monitor alerts. An asset monitor has a window in which it expects data, and silence past that window raises an incident, so a flat battery, a dropped wifi connection or a power cut is reported the same way a bad reading is.
Can I see the temperature history?
Yes. Every reading is stored and charted. History is kept for 3 months on Free, 12 on Core and 24 on Pro.