Activity on Cora Max
Cora Max shows the same activity log as the phone: every actuation request (every attempt to change something) and what became of it. A refused or unconfirmed request may never have reached the equipment at all, which is exactly why it is recorded.
Open it from the tank menu (tap the tank name in the top bar) or from Settings → Tank settings → [your tank] → Activity.
What each entry tells you
Each row names the action, the equipment and the time, then two things that matter more than either.
What asked for it: you at this screen, you on your phone, voice, the Assistant, an automation rule, a smart button, or your account. An entry made at the wall says so in as many words.
How it travelled: whether the command went across your own network or by way of your account, and which Cora carried it out. On a system with more than one Cora, this is how you tell which one acted.
The four outcomes
| Outcome | Means |
|---|---|
| Confirmed | The equipment reported back that it did it |
| Unconfirmed | Sent, but nothing reported back. This means we do not know, not it worked |
| Refused | Did not run. A safety rule, a lock, or the equipment itself declined it |
| No change | It was already in the state you asked for |
Why the outcome matters at the wall
A command that was sent but never acknowledged looks identical, at the moment you tap, to one that worked. This screen is where that difference becomes visible.
If something you asked for does not appear to have happened, look here before assuming the equipment has failed. The answer is usually that the request was refused, or that nothing ever reported back.
Reading it alongside the journal
Activity holds what the system did. The journal holds what you did by hand. Together they explain most surprises.
Written for Cora Max 0.28.60 and Cora Mobile 0.5.70. Last checked 2026-09-09.
Still stuck? Email cora@coraiq.tech and we'll help.