snapmaker-2_skill

This skill lets you monitor, control, and manage Snapmaker 2.0 printers via HTTP API, including status, progress, and job operations.
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill snapmaker-2

  • _meta.json980 B
  • SKILL.md5.9 KB

Overview

This skill provides control and monitoring for Snapmaker 2.0 3D printers via the printer's HTTP API. It exposes status reporting, job management, live progress watching, and event detection so you can automate and monitor prints remotely. It includes safety checks to avoid interrupting active prints and supports notifications for completion, filament issues, and errors.

How this skill works

The skill speaks to the Snapmaker HTTP API (v1) using configured IP, port, and token. It can discover printers on the local network via UDP broadcast or probe a specific IP, then calls endpoints like /api/v1/connect, /api/v1/status, /api/v1/prepare_print, /api/v1/start_print, /api/v1/pause, /api/v1/resume, and /api/v1/stop. Commands validate printer state, require confirmation for destructive actions, and offer a --yes flag to skip prompts for automation. A watch mode polls status periodically to detect events and trigger notifications.

When to use it

  • Remotely start, pause, resume, or stop prints on a Snapmaker 2.0
  • Integrate printer status and progress into monitoring dashboards or alerting systems
  • Automate upload-and-start workflows from CI or print farms
  • Watch for print completion, filament runout, door open events, or error conditions
  • Discover Snapmaker printers on a local network or probe a specific device across subnets

Best practices

  • Create a snapmaker/config.json with ip, port, and token and keep the token secure
  • Use discovery first to verify the printer IP before sending jobs
  • Avoid using --force unless you understand the risks; use --yes only in trusted automation
  • Call /api/v1/connect (handled by the skill) before issuing other requests to avoid 401 errors
  • Poll status at sensible intervals (e.g., 5–15 seconds) for progress watching to limit load

Example use cases

  • CI pipeline uploads a G-code file and starts a print when a model build passes
  • Home automation sends a notification when remainingTime reaches zero (print complete)
  • Monitoring script alerts on filament runout or enclosure door open events during a print
  • Remote operator pauses a failing print, inspects, then resumes using the resume command
  • Periodic health check that logs temperatures, position, and print progress for analytics

FAQ

Open the Snapmaker Luban app, connect to the printer, and copy the token from connection settings into snapmaker/config.json.

Why do I get a 401 "Machine is not connected yet" error?

The API requires calling /api/v1/connect first. The skill handles this automatically; if calling raw curl, POST to /api/v1/connect?token=YOUR_TOKEN first.

Can I interrupt a print remotely?

Yes. Pause, resume, and stop commands are supported but destructive actions require confirmation unless you pass --yes. The skill enforces state checks and warns before stopping.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational