module process is shutting down, either because the module is being removed from the machine or because it is restarting during a reconfigure. on removal the module's status stops being tracked once shutdown completes; on restart it transitions -> state_starting
module is configured but viam-server has not yet attempted to start it (because e.g. a required package is still downloading) transitions -> state_starting after pre-setup completes
module has sent a Ready response, registered its models, and is running transitions -> state_unhealthy on bad exit
module process has been spawned and viam-server is waiting for it to send a Ready response and register its models transitions -> state_ready on success
module failed to start, exited unexpectedly, or is being restarted after a crash. any failure in any other state goes to this state
state is unknown or has not been set yet
Generated
from enum viam.robot.v1.ModuleStatus.State