robotctl version

robotctl version

Always the first command when something is wrong.

It reports what every daemon is running against what is installed, and warns when they disagree.

Why it comes first

The official reasoning is specific: a daemon still serving old code after an update looks exactly like the fix you just shipped not working.

Ruling that out first saves an entire round of investigation pointed in the wrong direction — a wrong premise sends you hunting a bug that is not there, in code that is correct.

When they disagree

Most often after an update. robotd, configd and padd restart during it, while updaterd and btd wait five seconds past the reply. If those two restarts do not happen, they stay on the old binary.

The full sequence and the remedy are in the dev cheat sheet.