Remote manual control depends on internet availability and the functioning of the house based systems. When that fails autonomous mode steps in. The autonomous operation mode engages when AR3 determines that manual control is unavailable or when explicitly requested. That request comes from the Autonomous Mode switch on the dashboard, which stops AR1's heartbeat (see The Heartbeat System and Mode Transitions). Once engaged autonomous mode implements a comprehensive fire defence strategy based on environmental conditions. The algorithm is formally codified as the Fire Defence System specification, with all numeric thresholds collected in a single section of the AR3 source code to facilitate review and tuning. The algorithm balances multiple competing objectives: providing adequate protection against fire threat, conserving limited water resources for maximum defence duration, protecting equipment from heat damage, and adapting strategy as fire conditions evolve through different phases.

The algorithm operates hierarchically, with water level providing the highest-priority constraints that override temperature-based decisions. At the most basic level, if water depth falls to or below 0.05 meters (50 millimeters), the system enters dry cutoff mode, forcing all outputs off to prevent pump cavitation and mechanical damage. This threshold represents the minimum water column height necessary for reliable pump intake operation - below this level, the pump would draw air, causing the diesel engine to overheat and potentially destroying the pump impeller through dry running.

Between 0.05 and 0.30 meters water depth, the system enters gel priority mode. In this band, expected to occur only during extended fire events when water consumption has been severe, the system activates the main pump continuously at low flow (high flow valve P3 forced off) with the gel injection valve P4 activated. This mode maximizes the effectiveness of remaining water by enhancing it with fire retardant gel, which adheres to surfaces and provides prolonged protection even after water has evaporated. Critically, gel priority mode does not disable shed cooling—peripheral P2 can still activate based on internal temperature, recognizing that equipment protection remains important even when sprinkler water conservation is paramount. Fire defence continues, but in a form optimized for the minimal water remaining.

Between 0.30 and 0.50 meters depth, the recirculation band activates. In this mode, the system runs a fixed intermittent cycle of three minutes sprinklers on, eight minutes off, using the recirculation valve (P1) rather than pump cycling to achieve the intermittent pattern. The pump runs continuously while P1 cycles between pass-through (water to sprinklers) and recirculation (water returns to tank). This conserves water while maintaining some defensive capability, and importantly, this mode overrides any temperature-based requests for continuous sprinkler operation. Even if external temperature exceeds 80 degrees Celsius indicating fire front arrival, water conservation takes absolute priority in this band. The system will cycle sprinklers on for three minutes every 11 minutes regardless of external conditions, preventing complete water exhaustion while providing periodic cooling.

Temperature: warm-up and cool-down

Above 0.50 meters water depth, the system implements full temperature-based autonomous behavior, where fire threat conditions rather than water availability determine defensive actions. This temperature-based logic operates in two distinct phases—warmup and cooldown—representing different stages of a fire event.

Warmup phase represents the assumption that fire is approaching or intensifying. The phase begins at system startup or whenever the cooldown detection criteria are not met. When external temperature exceeds 80 degrees Celsius, the system activates continuous sprinkler operation with the high flow valve P3 open, providing maximum water delivery to defend against an imminent or present fire front. The 80-degree threshold was chosen based on radiant heat studies showing that at this external ambient temperature, radiant heat from an approaching fire is sufficient to cause ignition of combustible materials even without flame contact.

Between 75 and 80 degrees Celsius, the system runs intermittent sprinklers with a cycle of five minutes on, three minutes off. This represents a transition zone where fire is close enough to require active defence but not yet at maximum intensity. The relatively short off time (three minutes) ensures that surface cooling doesn't completely dissipate between cycles, maintaining some protection throughout the interval.

Between 60 and 75 degrees Celsius, the cycle extends to three minutes on, seven minutes off. At these temperatures, fire is approaching but still distant enough that conservation becomes more important than continuous cooling. The seven-minute off time allows significant water savings while the three-minute on time provides periodic protection against ember ignition and surface preheating.

Below 60 degrees Celsius during warmup phase, no sprinkler activation occurs—the fire is too distant to justify water usage, though the system remains in a ready state, monitoring temperatures continuously and prepared to activate when thresholds are crossed.

The transition from warmup to cooldown phase represents a critical decision point in the fire event timeline. Cooldown indicates that the fire front has passed or is retreating, and that defensive water usage should wind down accordingly to preserve remaining resources. The system detects cooldown by watching how far both the external and internal temperatures have fallen from their peaks.

Once the outside temperature has reached at least 60 degrees Celsius - a fire-level rise - the system keeps track of the highest external and internal temperatures it has seen. When external temperature has dropped by at least five degrees Celsius below its peak AND internal shed temperature has dropped by at least two degrees Celsius below its peak, the system concludes that the fire is genuinely retreating rather than experiencing a temporary lull, and transitions to cooldown phase. Requiring the 60-degree rise first stops an ordinary hot day cooling in the evening from being taken as the fire passing.

The five-degree external drop threshold ensures that the temperature change represents a significant trend rather than normal atmospheric fluctuation. The additional requirement of a two-degree internal drop prevents false cooldown detection if external temperature drops due to a temporary wind shift while radiant heat continues warming the shed—internal temperature should also decline if the fire is truly retreating. The asymmetric thresholds (five degrees external, two degrees internal) reflect the fact that external temperature responds more quickly to fire movement while internal temperature changes more slowly due to thermal mass.

Once the system enters cooldown phase, it never returns to warmup phase during the current power-on session. This represents the recognition that bushfire events typically consist of a single fire front passage, and that conditions improving enough to trigger cooldown are unlikely to reverse. The system's strategy shifts from anticipating intensification to managing wind-down.

In cooldown phase, the temperature thresholds and sprinkler cycles change to more conservative values that recognize the fire's retreat. If external temperature is still above 80 degrees Celsius, sprinklers run continuously at reduced flow. External temperature between 70 and 80 degrees Celsius triggers a cycle of three minutes on, five minutes off—more conservative than warmup's five minutes on, three minutes off at the same temperature band. Between 60 and 70 degrees Celsius, the cycle becomes three minutes on, eight minutes off—again more conservative than warmup behavior. Below 60 degrees Celsius in cooldown phase, sprinkler operation ceases entirely. The fire threat has diminished to the point where water conservation becomes paramount, and the system enters a passive monitoring state, ready to log final temperatures but no longer actively defending.

This dual-phase approach prevents the system from oscillating between aggressive and conservative modes if temperature fluctuates around threshold values, and recognizes that identical temperature readings have different strategic meanings depending on fire trajectory. A temperature of 75 degrees during warmup suggests fire is approaching and might intensify further, calling for aggressive defence. The same 75 degrees during cooldown suggests fire is departing and will continue cooling, calling for conservative water use.

Shed cooling

Independent of sprinkler operation decisions, the system manages shed cooling on peripheral output P2 using a sophisticated thermostat mode designed to protect electronic equipment and prevent the shed itself from becoming an ignition source. The shed cooling draws on the same tank as the sprinklers, but can run by gravity from the elevated tank even when the pump is not running.

When internal shed temperature exceeds 60 degrees Celsius, P2 activates continuously to provide maximum cooling. This threshold represents the point at which electronic equipment begins experiencing reduced reliability and potential permanent damage, and where the wooden shed structure's auto-ignition temperature becomes a concern.

Below 60 degrees but above 47 degrees Celsius, the system implements pulse-based cooling with escalation logic. The thermostat first requires "arming" by observing internal temperature fall below 45 degrees Celsius. This two-degree deadband prevents repeated pulse initiation during small oscillations around 47 degrees. Once armed, when internal temperature rises to or above 47 degrees, the system initiates a one-minute cooling pulse—P2 activates for exactly 60 seconds then returns to off state.

The system tracks the time between pulse starts. If a new pulse begins less than two minutes after the previous pulse started, the system concludes that ambient cooling from brief pulses is insufficient and latches into continuous cooling mode, remaining continuously on until either the operator intervenes or internal temperature falls below 45 degrees for long enough to re-arm the system. This escalation prevents excessive relay cycling (which would eventually damage the relay contacts) while ensuring adequate cooling during sustained high-temperature conditions.

The shed thermostat continues in the gel priority band, recognising that equipment protection remains important even when sprinkler water is being conserved. At the dry cutoff, however, everything stops - shed cooling included - so that the last of the water is not drawn down.

An additional layer of decision-making addresses the question of how to deliver water during intermittent sprinkler cycles—should the main pump cycle on and off (pump cycling mode), or should the pump run continuously with the recirculation valve cycling (recirculation mode)? The choice has significant implications for battery consumption and diesel engine wear.

Pump cycling or recirculation

AR3 takes the battery voltage from AR1's reading (see Sensors). If no reading has arrived for 5 minutes, for example when the link to the house is down, AR3 treats the battery as unknown and uses recirculation mode, since there is more fuel than there are starts. During a test it uses the test's simulated values.

When battery voltage drops to or below 12.0 volts, the system exclusively uses recirculation mode for any intermittent sprinkler operation. The pump is commanded on when intermittent sprinkler mode first activates and remains on continuously throughout the intermittent period. The P1 recirculation valve cycles between pass-through (delivering water to sprinklers) and recirculation (returning water to tank) to create the intermittent pattern. This minimizes battery drain by avoiding repeated diesel starter motor activation—each pump start might draw 200 amperes momentarily, while continuous pump operation draws perhaps 10 amperes. With a compromised battery unable to reliably restart the pump, continuous operation with valve cycling becomes the only viable strategy.

When battery voltage exceeds 12.0 volts and the sprinkler cycle's off time exceeds 15 minutes, the system switches to pump cycling mode. The P1 valve remains in pass-through position continuously, and the main pump itself turns on during sprinkler-on phases and off during sprinkler-off phases. This mode is more efficient for very long off periods (with the present cycles this arises only in the last stage of the sensor-failure fallback, two minutes on and twenty off), allowing the diesel engine to cool and the battery to recover between sprinkler cycles. However, it requires adequate battery capacity to reliably restart the pump after each off interval.

For cycles with off times of 15 minutes or less, recirculation mode is used even with good battery voltage. The frequent cycling that would result from pump mode with short intervals would cause excessive diesel starter wear and wouldn't provide meaningful battery recovery time. The 15-minute threshold represents a balance point where pump cycling begins providing efficiency benefits that outweigh the disadvantages.

Continuous sprinkler operation always uses the main pump directly without valve cycling. When external temperature exceeds 80 degrees Celsius triggering continuous mode, the pump is commanded on and P1 is set to pass-through, providing maximum flow to the sprinklers for the duration of the fire front passage. No battery-based decisions apply to continuous mode—protection takes priority over battery conservation when fire is imminent.

The high flow valve P3 activates whenever external temperature exceeds 80 degrees Celsius, the same threshold that triggers continuous sprinkler operation. This valve, when energized, increases hydraulic pressure and flow to the sprinklers, improving coverage and cooling effectiveness. The choice to tie P3 exclusively to the 80-degree threshold rather than to TRISE (temperature rise rate): temperature rise rate is a less reliable predictor of immediate fire threat than absolute temperature level.

What Autonomous mode does not do

  • The ember detector raises an alert; it does not by itself start the sprinklers, in any mode.
  • There is no automatic detection of a failed gel dosing pump: gel simply follows the water-level band (see The Gel Injection System).
  • LOCK does not stop Autonomous mode: LOCK guards against remote starts only (see Output Control and Safety Interlocks).

Sensor Failure Fallback

A significant vulnerability to the automated system, and even manual control is the possibility that sensors key to the automated autonomous module may fail. The key sensors are those monitoring temperature and remaining water.

Detecting a failed temperature sensor. Arduino 2 checks every temperature reading. A sensor that does not answer, gives an out-of-range value, or reads exactly 85°C (the value these DS18B20 sensors give after a power glitch, unless it was already reading close to 85°C) is treated as failed. Arduino 2 then sends 0 for that sensor, so that it stands out on the dashboard, together with a failure flag for each sensor. Arduino 3 acts on the flag, not the value, so a failed sensor is never mistaken for a real reading: 0°C can be real on a winter night, and a sudden drop to 0 would otherwise look like the fire passing.

The Sensor status card in Home Assistant has a Temperature sensors row showing OK or which sensors have failed; it applies in manual and autonomous operation alike. At Fairhaven an email is sent when a sensor has been failed for 2 minutes (repeated at most every 12 hours) and again when the sensors recover.

Temperature sensor fallback

Two external sensors are included one at a distance from the pump shed, the second with the metal sensor end only protruding through the pump shed wall, and finally the internal sensor inside the shed. Anticipating the possibility of failure the system operates as follows:

Fallback Mode Logic

  • The outside temperature is taken from the first external sensor or, if it has failed, from the second.
  • If both external sensors have failed, the sensor inside the pump shed is used as a proxy, adding to it the difference between outside and inside temperature last measured while both were working.
  • If all three sensors fail for 1 minute the system enters fallback mode. This mode enables continued operation without temperature feedback by progressing through a predefined sequence of pump control modes, driven purely by elapsed time. During that minute the system carries on as it was, so the sprinklers do not stop while the failure is confirmed.
  • If no temperature rise had been seen before the sensors failed (the system had not yet started sprinkling), it stays idle and reports the failure rather than spending water.
  • If the sensors come back and read normally for 2 minutes, normal temperature-based control resumes.

Fallback Progression Sequence

Upon entering fallback, the system starts at the stage matching the mode it was in when the temperatures became invalid, and then runs from that point to the end of the sequence:

StageModeSprinklersStarted here if the system was in
1B3 min on, 7 min offwarm-up, outside 60-75°C
2C5 min on, 3 min offwarm-up, outside 75-80°C
3CONT_REDUCEDcontinuous, reduced flow-
4CONT_HIGHcontinuous, high flowwarm-up, outside above 80°C
5CONT_REDUCEDcontinuous, reduced flowcool-down, outside above 80°C
6G3 min on, 5 min offcool-down, outside 70-80°C
7H3 min on, 8 min offcool-down, outside 60-70°C
8L2 min on, 20 min off (held)cool-down, outside 60°C or below

Shed cooling follows the same stage: continuous in the continuous stages, otherwise the same on/off cycle as the sprinklers.

Timed Mode Transitions

Each stage lasts 5 minutes (1 minute on TestSys, so that a test runs in reasonable time) before the system advances to the next, until the final stage L is reached; L is then maintained indefinitely unless a shutdown is forced by water depletion. This short time interval in each mode is based on the premise that the most likely time for the sensors to fail is when the external temperature is already high, due to the near arrival of the fire front. The experience then (see Appendix 14) is that fire fronts pass quickly - usually in well under a quarter of an hour.

Shutdown Condition

The water-level rules continue to apply in fallback: between 0.50 and 0.30 m the sprinklers use the water-saving cycle (3 min on, 8 min off); below 0.30 m gel is injected with the pump on reduced flow; and at 0.05 m or below everything is turned off to conserve water and protect the pump. Obviously if diesel fuel is exhausted the pump stops through its own mechanical constraints. This logic ensures a structured fallback response that maintains protective operation and gracefully degrades water usage in the absence of temperature feedback.

The fallback can be exercised on TestSys with a simulated run in which the sensors fail one by one (see Test scenarios).

Tank level sensor fallback

The tank level gauge is a 4-20 mA sensor whose cable is necessarily exposed outside. It reads about 1.25 V at zero depth (4 mA). If the cable is cut or the sensor dies the voltage falls to about 0 V. Read naively, that would look like an empty tank - and an empty tank triggers the dry cutoff, which would switch everything off in the middle of a fire.

  • Detecting a failed gauge. Arduino 2 treats a reading below 0.9 V (cable cut or sensor dead) or above 4.6 V (short circuit) for 2 seconds as a failed gauge, and flags it.
  • Estimating the level. From the last good reading, Arduino 3 subtracts the water passing the pump-line flow meter (DN50) and adds mains refill through the in-feed meter (DN15), at 95 litres per centimetre of depth. The DN50 meter is after the recirculation valve, so only water actually used is counted, including shed cooling. The estimate is used for all the water-level rules (water-saving cycle below 0.50 m, gel below 0.30 m, dry cutoff at 0.05 m) and is sent to Home Assistant as the tank level.
  • If the flow meter also fails. If the DN50 meter reads nothing while the pump runs with the valve set to the sprinklers, it is taken as failed (after 1 minute) and the last measured flow for the valve setting in force (reduced or high) is assumed for as long as that remains the case. Arduino 3 keeps these averages from normal running, once the pump and valves have been steady for 20 seconds, so they follow any adjustment of the reduced-flow valve; until it has measured them it uses 147 L/min (reduced) and 217 L/min (high).
  • If there is no good reading to start from (the gauge has been dead since Arduino 3 started), the estimate starts from a full tank, so that the defence continues rather than stopping.
  • Recovery. When the gauge reads sensibly again for 2 minutes, its reading is used again.
  • Home Assistant. The tank level shown is the estimate while the gauge is failed - in manual as well as autonomous operation, although only Autonomous mode acts on it automatically. The Sensor status card shows a Tank level source row: Gauge, or a warning that the level is estimated (and whether a flow is being assumed). At Fairhaven an email is sent when the level has been estimated for 2 minutes, and again when the gauge recovers.

The fallback can be exercised on TestSys with a simulated run (scenario 4) in which the gauge fails, then the flow meter fails and recovers, while the estimate falls through the water-saving, gel and dry-cutoff levels (see Test scenarios).


Every threshold is also listed in Key data. Last checked against the code: 7 November 2026. The original design criteria: Development history: Autonomous mode.

<< The Heartbeat System and Mode Transitions | | Output Control and Safety Interlocks >>      |Table of Contents>


Page last modified on November 22, 2026, at 06:46 AM