DSC-BRAIN USER GUIDE · USING THE DASHBOARD
Timed runs: Run for a while
A timed run asks one device to do something for a short, picked time. Automation pauses for that device and takes over again by itself. This page covers the picker, the quick buttons, space actions and what each result line means.
● Running on our test kit: 9.10.0 · kit firmware 9.0.0.0 · last report 22 Oct 2026
Status: Screen live. Until a device type is handed to the planner, a timed run switches nothing.
On this page
What works today
Timed runs go through the planner’s side of the brain. A device type switches only once it has been handed to the planner. No type has been handed over on the reference kit. So today a timed run ends in one of two ways:
- Planned only. The line reads “Planned only, nothing was sent: this kind of device is not switched by the new engine yet.” The brain records the whole plan, with its end time, but writes nothing to the device.
- Not applied. The brain refuses and says why. For a type still on today’s path, the reason says to use Take over until the type is handed over.
To run a device by hand today, use Take over on its tile. It holds the device for a time you pick, and Hand back gives it back. See Who is in charge and rolling back for how a type is handed over.
Where to find it
- Device tile. Open the line “Run for a while” under a tile.
- Device page. The “Run it now” section has the same picker. On the Devices screen, the “Run…” link goes there.
- Quick run. Some Issue cards, and some chips on Today, offer “Run 5 min”, “Run 15 min” and “Run 1 h”. Only the lengths allowed for that device are shown.
- Space actions. On a space page, “Space actions” starts one action for the whole space. See below.
The picker
| Choice | Options |
|---|---|
| What it should do | On, Off or Boost. |
| For how long | Some of 5, 15, 30 minutes, 1 hour and 4 hours, as the device type allows. Or “Until lights off”. Or “Hold (up to …)”, which runs to the type’s limit and never more than 4 hours. |
| Go | A button that reads your picks, for example “Turn on for 15 min” or “Turn off for 1 h”. |
Under the button: “Automation is paused for this device for that time only, and takes over again by itself.” Nothing is typed. Every choice is a button.
| Device type | Longest run |
|---|---|
| Heater | 30 minutes |
| Heat mat | 2 hours |
| Humidifier | 1 hour |
| Dehumidifier | 1 hour |
| Portable AC | 1 hour |
| Fan | 4 hours |
| Grow light | 4 hours |
| Pump | Never. A pump is never held on by a timed run. Use the supervised Run shot. |
The smart plug firmware carries the same limits, so a plug turns itself off at the end of a run even if the brain cannot be reached.
What happens during a run
- Safety wins. Before anything is written, the hub’s safety gate judges a switch on. A lamp is never raised in its space’s dark window, or when that window is unknown. A refused run says why.
- Conflicts are held back. A humidifier run holds the dehumidifier in the same air volume off for the same time. Both are restored together. The receipt says “Held back for the same time:” and why.
- Every start expects a reaction. The device’s own reading must show it within a window: 15 seconds for a hub fan, 30 for a Sonoff plug, 45 for a Tuya plug. If the reaction is not seen, the brain stops the device, marks it out of service with the possible causes listed, and raises an Issue.
- Back to plan, any time. Choose “Back to plan”. The device is shown restored only when it is seen restored.
- Cut short by safety. If safety needs the device off during a run, the run ends and the device is switched off. It is not resumed.
- A restart does not lose a run. Timers are stored, so after a brain restart the window is finished or the device is restored at once.
Reading the result line
| Line starts | What it means |
|---|---|
| Commanded, waiting up to N s for the device to confirm | Sent. It is not shown as on until the device says so. |
| Applied | The device’s own reading confirmed it. |
| Not applied: the device did not react | No reaction in the window. See above for what the brain then does. |
| Not applied: ... (a reason) | Refused before anything was written. |
| Planned only, nothing was sent | The type is not switched by the new engine yet. |
| Unconfirmed: no reply from the brain | Check the device before trying again. |
The quick run buttons show a stage word instead: COMMANDED, CONFIRMED, NOT APPLIED, PLANNED ONLY or UNCONFIRMED. When a run is over the line reads ENDED: “The brain no longer lists this run: it ran out or was handed back.” A button “Run again 15 min” then appears. After the end, the screen says whether the device was seen back in its planned state: “Back to plan” with “the device was seen restored”, “Handing back” while it waits, or “Restore not confirmed” with a link to the Issue.
Space actions
On a space page, “Space actions” starts one action for every device in the space, for 5, 15 or 30 minutes, or 1 hour. There are two:
- Working in the tent. Lamp on, humidifier off.
- Spraying. Humidifier off, dehumidifier off, circulation fan off. Only in the lit period. In the flower stage the brain may refuse and ask you to tick “The product label allows it”, or to pick a reason: “I checked the label / PHI myself”, “Biological control only (no residue)” or “Emergency: active outbreak”.
You get one receipt for the whole action. It lists every device changed, every device held back, every device left out (for example “not included” when its location is not known) and every refusal with its reason. “Back to plan” ends all of them together.
Everything running, in one place
The strip “Active overrides” lists every timed run in progress, with a live countdown and a “Back to plan” button. It also lists any run whose hand-back was not seen. When the hub’s Automation reads off, the status line on Today and Climate offers “Hand back to automatic”. One tap ends every timed run and hold and asks the hub to turn Full Auto back on. The line then says what each step’s own read-back showed.