Autonomous mode can't wait for a real fire to be tested. Instead, AR2 can replace its real sensor readings with a scripted scenario of simulated ones, and AR3 responds exactly as it would to real readings, driving the real relays (or TestSys's LEDs). This works on TestSys and on the production system.
Last checked: 7 November 2026.
Starting and stopping a test
- Test button (AR3, Module 4): hold for 3 seconds to start scenario 1. Any press of about a second during a test ends it (a very quick tap may not register). AR3 takes control at once, tells AR1 (so the dashboard's Autonomous Mode switch turns on by itself), and tells AR2 to start the scenario.
- From a computer connected to AR3 by USB: the serial commands TEST1 to TEST4 start scenarios 1-4; TESTSTOP ends a test.
- A test also ends by itself when the scenario finishes, or after 30 minutes at most.
- Switching Autonomous Mode off in Home Assistant ends a test and returns control to the dashboard within about 15-20 seconds. After a test that ended by itself or with the button, AR3 stays in Autonomous mode until the switch is turned off.
Simulated readings are labelled as such, and AR3 ignores them whenever no test is running; ending a test also clears the simulated fire from AR3's memory. So a test, or AR2 carrying on simulating after a lost stop command, cannot affect real control.
The scenarios
| No. | What it simulates | Length |
|---|---|---|
| 1 | A fire: outside temperature rises through every warm-up band to a 95 °C peak and falls again (cool-down), with a battery drop; then the tank falls through the gel level to the dry cutoff | about 9 minutes |
| 2 | The temperature sensors failing one by one during a fire (first outside, both outside, all three), then recovering - exercises the sensor-failure fallback | about 16 minutes |
| 3 | Outside held at 66 °C for 11 minutes, so one complete 3 min on / 7 min off cycle can be watched (pump on throughout; recirculation valve off while spraying, energised while recirculating) | 11 minutes |
| 4 | The tank gauge failing during a fire, then the flow meter failing and recovering, with exaggerated flow so the estimated level falls through the water-saving, gel and dry-cutoff levels | about 10 minutes |
What a successful scenario 1 looks like on TestSys: IDLE → 3/7 cycle → 5/3 → continuous high flow → cool-down continuous reduced → 3/5 → 3/8 → off → gel priority → dry cutoff with all outputs off; shed cooling pulsing from 47 °C.
Other test commands (USB)
| Command | Board | Effect |
|---|---|---|
| WDTTEST | any | Freezes the program; the hardware watchdog should restart the board within about 6 s |
| NOMQTT | AR1 | Drops MQTT until the next restart (tests the connection self-restart) |
| MUTE / UNMUTE | AR2 | Stops / restores AR2's WiFi messages |
| NOCLIENT | AR2 | Pretends AR3 has been away for 25 minutes |
Testing the backup link
Set the comms path control on System Health to BACKUP, check that commands still work (allow 2-4 seconds), then set AUTO: it returns to RS-485 after 60 seconds. See Communication protocols. To test the No data from shed warning, hold AR3 in reset: it appears about 1.5 minutes later and clears when AR3 restarts.
<< TestSys | | Commissioning checks >> |Table of Contents>
