LODDON @ MURRAY VAL.
75.355 m 31/10/26, 12:00 AM AEST
Below minorOpen 7-day graph →
Councils lose gauges where the network stops. IoT builds the device, connects it over terrestrial, LEO satellite or GEO satellite from one SIM, and feeds it straight into the disaster management dashboard your coordinators already use.
The Bureau of Meteorology built Enviromon in 1996 and gave it to councils free for nearly thirty years. On 30 June 2026 the Bureau ended external support, stating it no longer meets basic cybersecurity, stability and resilience standards. It was not switched off. Nobody maintains it.
In October 2026, AusAlert goes live — the national cell-broadcast warning system replacing SMS-based Emergency Alert. It delivers the message. Someone still has to decide to send it.
So a council is running unsupported 1996 software at one end of its flood warning chain and a brand-new national system at the other. In Queensland, flood warning is a local government responsibility — which puts that gap on the smallest and least resourced level of government in the most disaster-prone state in the country.
IoT sits in the middle: the evidence a person needs before they decide to warn anyone.
A monitored floodway, river gauge, water quality point or environmental site — delivered as a managed service and fed straight into the disaster management dashboard your coordinators already use. No new console to learn during an event.
A solar-powered flood monitoring and traffic warning system mounted directly to a bridge or culvert. Combines an ultrasonic water-level sensor, battery storage and a flashing warning light to monitor rising floodwater and warn approaching motorists. Hardware $3,999 ex GST.
A solar-powered flood monitoring and traffic warning system installed on a dedicated pole beside roads, bridges and flood-prone crossings. Combines an ultrasonic water-level sensor, battery storage and a flashing warning light for ongoing monitoring and visible warnings to motorists. Hardware $9,999 ex GST.
Satellite connectivity $39 a month per device, billed separately from day one. One SIM roaming terrestrial and non-terrestrial on 3GPP — carrier where reachable, LEO or GEO where not. Managed SIM policy, device health and data quality included.
The council dashboard software we have built on ThingsBoard is free for councils to use — no software licence fees. See live water levels, flood class, gauge and warning-light status, and alerts on a ThingsBoard dashboard the council owns, or deliver the same readings into the disaster management system coordinators already use. Every reading is also written to a plain local database that stays with the council.
We have developed dashboard software on ThingsBoard that councils can use for free — no software licence fees. Coordinators see live water levels, flood class, gauge and warning-light status, and alerts on a ThingsBoard instance the council owns, consistent with the open IoTportal stack (Apache 2.0 on ThingsBoard CE) described below. Hardware remains the Bridge & Culvert-Mounted and Pole-Mounted systems; satellite connectivity is $39 a month per device.
A floodway does not move to suit the network. The connectivity has to come to it, and no single bearer reaches everywhere in Australia — let alone everywhere a catchment needs watching. So the node carries three paths, with edge buffering and local decision logic underneath.
A 3GPP roaming profile that registers on terrestrial carrier networks and on satellite NTN from the same SIM. No second module, no second subscription, no manual switch. Where terrestrial exists the device uses it; where it does not, the same SIM registers on satellite.
NTN roaming is carried under one agreement rather than per constellation, so the device is not tied to a single satellite operator. That keeps the architecture open as LEO and GEO footprints change.
Environmental telemetry is small and infrequent. Connectivity is billed on what is actually sent, which is what makes a heartbeat from a floodway economic at all.
Buffering, watchdogs and local thresholds on the node, so a device keeps measuring and keeps its data through a link outage and reports the gap when it returns.
Clustered near-real-time river levels from the Bureau of Meteorology Flood Warning Online network and Water Data Online, proxied through our same-origin API. Click a marker for the station reading and its online / intermittent / offline status; featured graphs below keep the BOM 7-day plot colours (Major / Moderate / Minor / Bridge).
BOM-style river height plots for Murweh, Quilpie, Canungra Creek, Gold Coast and Fraser Coast. White plot field, published flood-class lines, Brisbane midnight axis ticks.
Observations © Commonwealth of Australia (Bureau of Meteorology), CC BY 4.0. Basemap tiles © Esri.
National Water Data Online readings proxied through our API (BOM blocks browser CORS). Cards favour stations highest relative to their published minor/moderate/major thresholds — then other live river heights. Open any card for the 7-day graph on the gauges map.
Observations © Commonwealth of Australia (Bureau of Meteorology), CC BY 4.0.
FloodCheck Queensland, managed by the Department of Natural Resources, holds floodplain overlays, modelled flood extents and historical floodlines from 1893, 1974, 2010 and 2011. It is the best public record of where water has gone before. It is also, by its own terms, not for use during an event.
A flood study is a map of what happened. A gauge is a measurement of what is happening. Most Queensland catchments have the first and not enough of the second — and the councils with the largest floodplains are frequently the ones with the fewest instruments, because that is where the network stops.
Read a live gauge against a historical inundation extent and a disaster coordinator has something neither gives alone: the river is at 4.6 m and rising at 0.34 m/h, and here is what went under at that height in 2011. That is the pairing we build toward — the study as context, the gauge as evidence, and the age of every reading shown alongside it.
IoTportal, our open ingestion and federation platform, is built on ThingsBoard Community Edition and released under Apache 2.0. A council should not have to buy the ability to read data from gauges it already owns, and it should not be possible to lock one out of its own records. What legitimately costs money is somebody being accountable at 2am in February when the river is rising and a gauge goes quiet.
Decoders, provider adapters, the federation layer and the dashboard are open source. A council, a consultancy or a competing supplier can pick it up and run it without a licensing conversation. Wider adoption of a common open ingestion layer is worth more to everybody than controlling the derivatives.
No per-seat platform fee, no annual software licence, no renewal cliff. Every reading is also written to a plain local database the council keeps — readable by anything, exportable in open formats, and entirely theirs if the arrangement ends.
ALERT and ALERT2 are open, royalty-free protocols governed by the National Hydrologic Warning Council. OGC SensorThings, OGC API Features and WMO WIS2 are published standards. We implement the standard once, then a new network is a configuration entry rather than new code.
The most valuable contribution is not code — it is ten minutes of recorded output from a real base station, with the operator's permission. Receiver framing varies by manufacturer and configuration, and every validated capture makes the decoder safer for the next council.
Tell us where the gauge needs to go and what your disaster management team already runs. We will tell you what it costs, what it can and cannot do, and what has to be commissioned on site before anyone relies on it.
IoT provides monitoring, federation and decision support. It does not forecast and it does not issue warnings. Government and authorised agencies retain statutory warning responsibility in every jurisdiction shown here.