Skip to content

Improve device management and monitoring#42

Merged
temiroff merged 1 commit into
masterfrom
agent/device-management-and-monitoring
Jul 26, 2026
Merged

Improve device management and monitoring#42
temiroff merged 1 commit into
masterfrom
agent/device-management-and-monitoring

Conversation

@temiroff

Copy link
Copy Markdown
Owner

What changed

  • Clarifies compute-device, robot, deployment, SSH, update, and lifecycle controls in the editor.
  • Adds responsive Runtime + Robot Hardware reports and durable version reporting.
  • Adds selectable live robot monitoring for idle Hardware and active deployments.
  • Improves stored-deployment restart behavior, torque reporting, progress handling, and related documentation.

Why

Device ownership, service versions, deployment persistence, and physical torque were presented through overlapping controls and transient status. This made it difficult to tell which robot was targeted and whether a workflow remained installed.

Impact

Operators can manage each robot from a clearly separated card, inspect reliable service versions, restart stored deployments, and view live joint telemetry from the current hardware owner.

Validation

  • python -m unittest discover -s tests (438 passed, 8 skipped)
  • cd editor && npm run build
  • Editor device API tests (70 passed)

@temiroff
temiroff marked this pull request as ready for review July 26, 2026 06:21
@temiroff
temiroff merged commit eef9140 into master Jul 26, 2026
4 checks passed
@temiroff
temiroff deleted the agent/device-management-and-monitoring branch July 26, 2026 06:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant