What an Uncertain Command Means
A command is Unconfirmed when it may have reached the vendor, but nothing confirmed that the device acted. The platform does not guess, and it never sends the command again by itself.
Where you see it:
- Under the control you used: We couldn't confirm it happened. Check the device before trying again.
- In the device's Commands section, where the row's status is Unconfirmed, marked with a warning icon.
While a command waits for the device, the message under the control reads Waiting for the device…. After two minutes it reads Still waiting for the device. Check it directly.
Why it happens
- The vendor did not answer in time, or the connection dropped, after the request may already have been delivered.
- The vendor accepted the command, but the device did not report the new state within the time allowed.
- The device went offline between the command and its report.
A simple comfort action that a device can never report back is counted as Done once the vendor accepts it. For every other control, only a report from the device, or the vendor's own confirmation, makes a command Done.
What the platform does
- It shows Unconfirmed instead of success or failure.
- It never retries the command by itself. Sending it twice could, for example, unlock a door that someone has just locked again.
- It keeps watching for up to a day. If the device later reports the state you asked for, the command becomes Done. If the device reports a failure state, the command becomes Failed.
What you should do
- Look at the device itself, or ask someone nearby, before you decide.
- If you need the action, you can send it again. Try again appears on an unconfirmed command, under the control and in the Commands section, only for the person who sent it, within 10 minutes of the first request, once, and only for controls that are safe to repeat. Otherwise, use the control again.
- Either way, the new attempt is a new command. It goes through every check again, including any confirmation, password or second person.
- If it keeps happening for one vendor, see Fixing a Connection Problem.
Why this matters for safety
A control that seems to have worked when it did not is worse than one that says it does not know. Keep independent safety equipment in place. See IoT Is Not a Safety System.
