gadget-bambu-lab-p2s
Skill2.8k starsChanged 26 days agoApache-2.0View on GitHub
Read print status, grab chamber-camera snapshots, monitor a running print, and pause a clearly failing print on a Bambu Lab P2S through Muse Home Link, using the printer's LAN MQTT and RTSPS interfaces with LAN Only Liveview on and cloud mode kept. Not for starting prints or arbitrary control commands; for print starts, use the Bambu Lab printers skill.
Trending
More talk lately.thin dataabout the whole repository
Who's talking about facebookincubator/muse-gadget-sdk
- @j4ck.xyz“I still wouldn't trust Meta with my personal context for agents, but what they're doing with Muse is pretty …”Bluesky · Oct 2, 2026 · 7 likes
- A Hacker News story“Open source SDK to build Muse gadgets”Hacker News · Oct 3, 2026 · 2 points
- ComBba/muse-gadget-sdk“CI preflight: wait for the installer serial close before SDK token setup”GitHub · Oct 17, 2026 · 1 reactions
- @sarubot.bsky.social“muse-gadget-sdk — Metaが放つ、ESP32やラズパイをAIガジェットへ変貌させるSDK。今週スター急増中の注目作! …”Bluesky · Oct 7, 2026 · 1 likes
- aegisfleet/tool-survey-report“feat: add survey report for Muse Gadget SDK”GitHub · Nov 9, 2026
The biggest 5 of 14 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 14
Talked about on GitHub, Bluesky and Hacker News (14 times).
On GitHub · 11
- Oct 17, 2026CI preflight: wait for the installer serial close before SDK token setup — ComBba/muse-gadget-sdk1 reaction · 2 comments
- Nov 9, 2026feat: add survey report for Muse Gadget SDK — aegisfleet/tool-survey-report0 reactions · 4 comments
- Oct 14, 2026Fix S3-2.06 ES7210 microphone and native USB serial console — polygoku/waveshare-amoled-206-debug0 reactions · 5 comments
- Oct 12, 2026Integration blocker: native Muse gadget command invocation — 1chris2many/muse-portal-kit0 reactions
- Oct 12, 2026Integration blocker: authoritative per-device reply correlation — 1chris2many/muse-portal-kit0 reactions · 2 comments
6 more on GitHub
- Oct 11, 2026[fork CI preflight] #181 candidate a6fd89c — ComBba/muse-gadget-sdk0 reactions · 1 comment
- Oct 11, 2026[fork CI] #179 Use the custom avatar in the UI simulator — ComBba/muse-gadget-sdk0 reactions · 1 comment
- Oct 11, 2026[fork CI] #181 Add validated avatar restore and host status — ComBba/muse-gadget-sdk0 reactions · 1 comment
- Oct 11, 2026[fork CI] #180 Validate avatar candidates before replacing the current renderer — ComBba/muse-gadget-sdk0 reactions · 1 comment
- Oct 11, 2026[fork CI] #174 Reject incomplete bench screenshots without padding pixels — ComBba/muse-gadget-sdk0 reactions · 1 comment
- Oct 11, 2026[fork CI] #177 Abort bench screenshots when USB console output stalls — ComBba/muse-gadget-sdk0 reactions · 1 comment
On Bluesky · 2
- Oct 2, 2026I still wouldn't trust Meta with my personal context for agents, but what they're doing with Muse is pretty cool & fun icl… — @j4ck.xyz7 likes and reposts
- Oct 7, 2026muse-gadget-sdk — Metaが放つ、ESP32やラズパイをAIガジェットへ変貌させるSDK。今週スター急増中の注目作! ・C言語製のESP32/Linux用SDK。センサーやオーディオをMuseエコシステムに即統合 ・AIエージェント「Muse… — @sarubot.bsky.social1 likes and repost
On Hacker News · 1
- Oct 3, 2026Open source SDK to build Muse gadgets2 points
In this repository57 other files it gives its agents.
- esp32/AGENTS.mdAGENTS.md
- linux/AGENTS.mdAGENTS.md
- gadget-amazon-echoSkill
- gadget-apple-homepod-miniSkill
- gadget-apple-tv-4kSkill
- gadget-bambu-lab-printersSkill
- gadget-brother-printersSkill
- gadget-dyson-pure-hot-cool-hp04Skill
- gadget-ecowitt-gatewaysSkill
- gadget-elgato-key-lightSkill
- gadget-epson-printersSkill
- gadget-esphome-devicesSkill
- gadget-espsomfy-rtsSkill
- gadget-eufy-robovac-tuyaSkill
- gadget-freebox-player-popSkill
- gadget-google-castSkill
- gadget-google-home-maxSkill
- gadget-google-home-speakerSkill
- gadget-google-nest-audioSkill
- gadget-google-nest-hub-maxSkill
- gadget-google-nest-hubSkill
- gadget-google-nest-miniSkill
- gadget-google-nest-thermostatsSkill
- gadget-google-pixel-tabletSkill
- gadget-google-tv-streamerSkill
- gadget-homewhiz-laundrySkill
- gadget-hp-color-laserjet-pro-m254dwSkill
- gadget-insignia-fire-tvSkill
- gadget-irobot-roomba-braavaSkill
- gadget-lg-webos-tvsSkill
- gadget-logitech-squeezeboxSkill
- gadget-lutron-smart-bridgesSkill
- gadget-meross-smart-plugsSkill
- gadget-miele-g7566-dishwasherSkill
- gadget-moonraker-3d-printersSkill
- gadget-philips-hue-bridgesSkill
- gadget-pixoo-64Skill
- gadget-ratgdo-v32-garage-doorSkill
- gadget-roborock-vacuumsSkill
- gadget-roku-tvs-and-playersSkill
- gadget-samsung-tizen-tvsSkill
- gadget-shelly-plugsSkill
- gadget-sinricpro-cloud-devicesSkill
- gadget-sonoff-rf-bridgeSkill
- gadget-sonos-speakersSkill
- gadget-teslaSkill
- gadget-tplink-kasa-ep10Skill
- gadget-tplink-kasa-ep25Skill
- gadget-tuya-cloud-devicesSkill
- gadget-tuya-wifi-devicesSkill
- gadget-unifi-network-consolesSkill
- gadget-velux-klf200Skill
- gadget-vesync-humidifierSkill
- gadget-vizio-d40f-g9Skill
- gadget-wyze-rtsp-camerasSkill
- gadget-yi-hack-camerasSkill
- gadget-zigbee2mqtt-gatewaysSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Read and follow the Home Link networking and safety rules in ~/docs/devices/home_link.md.
- Distinctive: line 42
Before describing or attaching a snapshot, check that the client exited successfully and wrote a new file for this request, then view it.
- Distinctive: line 46
No cloud camera path: Bambu Handy is phone-only, and Bambu's cloud liveview uses a proprietary peer-to-peer ticket system that refuses …
- Distinctive: line 48
No starting prints, arbitrary G-code, temperature, speed, or light changes, and no resume or stop under a pause authorization.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Bambu Lab P2S
Use this skill when discovery or the user identifies a Bambu Lab P2S on the home network and the user wants print status, a camera snapshot, monitoring while a print runs, or a pause for a print that is clearly failing. The contributor verified live status and camera frames end to end on a P2S in cloud mode through Home Link, with Bambu Handy still working on its cloud path. For general Bambu status and owner-approved print starts on any model, see the Bambu Lab printers skill.
Identify the Device
- Get the printer's IPv4 address and 15-character serial number from the printer touchscreen or Bambu Handy. The P2S does not announce itself by name over mDNS or SSDP, so a network scan alone cannot identify it. Match the address from the touchscreen against the scan results.
- Confirm the model is a P2S before using the camera path. Other Bambu models differ: the P1 and A1 families stream low-rate JPEG frames instead of RTSPS, and those paths are not covered here.
Prerequisites
Read and follow the Home Link networking and safety rules in ~/docs/devices/home_link.md.
- On the printer touchscreen, set LAN Only to off and LAN Only Liveview to on. Liveview is a separate toggle from LAN Only Mode: with Liveview on and LAN Only off, the printer stays on Bambu Cloud, Bambu Handy and its live video keep working, and the local camera stream becomes available on the LAN. Verify Handy live video after changing the setting, and revert if it breaks.
- The printer's LAN access code and serial number. Store the access code with the host's other device credentials in a local file with restricted permissions, and have each client read it from there. Never put the code in a skill, a chat message, a log, a command-line argument, or a URL passed on a command line.
- A configured or pinned trust path for the printer's TLS identity, such as the printer's certificate recorded during setup. The printer uses a self-signed certificate, so the system trust store will not validate it. Both the MQTT and the RTSPS connections validate the printer against this trust path and fail closed on a mismatch; never disable certificate verification. If the printer's certificate changes, stop and ask the owner before trusting the new one.
- A client route through the Home Link HTTP CONNECT proxy for custom TCP: an MQTT client for status and control, and an FFmpeg-based client for camera frames, with RTSP forced to TCP transport so no UDP is needed. Both must be credential-aware: they read the access code from the restricted file in-process rather than taking it as an argument.
- For pausing, the user's explicit request for that job, or a standing authorization the user gave for monitoring with the failure criteria agreed in advance. That agreed failure pause is the only exception to the Bambu Lab printers skill's rule of pausing only on request for that job.
Workflow
- Read status over LAN MQTT. Connect to the printer on port 8883 over TLS, validating its certificate against the pinned trust path, and sign in as user
bblpwith the LAN access code read from the credential file. Subscribe todevice/<serial>/report, and publish{"pushing": {"sequence_id": "0", "command": "pushall"}}todevice/<serial>/requestto get a full report. Report the fields the printer returns:gcode_state(IDLE, PREPARE, RUNNING, PAUSE, FINISH, FAILED), job name,mc_percent,mc_remaining_time,layer_numagainsttotal_layer_num, nozzle, bed and chamber temperatures against targets,print_error, and AMS tray contents. If a connection attempt fails with a TLS timeout, retry once before reporting the printer unreachable; that failure is transient through the tunnel. A certificate mismatch is not transient: stop and report it. - Grab a camera snapshot over RTSPS. With LAN Only Liveview on, the chamber camera serves an H.264 stream over RTSPS on port 322 at path
/streaming/live/1(userbblp, password the access code; 1080p, 30 fps). The RTSPS client cannot use the proxy directly, so run a small local TCP forwarder that opens the connection through the proxy's CONNECT method. TLS still runs end to end between the client and the printer, so validate the printer's certificate against the pinned trust path rather than the forwarder's local address. Pull one frame with the credential-aware client: for example, a short script that reads the access code from the credential file, builds the stream URL in memory, and opens it with an FFmpeg-based library usingrtsp_transport=tcpand certificate verification on. Never pass a credential-bearing URL to a command such asffmpeg -i. Write each snapshot to a new file. Take snapshots only while a print is active if that is the user's rule. - Judge print health from the snapshot and telemetry. Healthy: the part is on the plate and adhered, layers stack cleanly, stringing is minor, and early first layers look flat and thin. Alert-worthy: spaghetti or a growing filament nest, a part detached, tipped over, or being dragged, an empty plate well past the first layers, a blob on the nozzle, an obvious layer shift, a non-zero
print_error, a FAILED state, an unexpected PAUSE, nozzle or bed temperature more than 15 degrees below target while running, or, while RUNNING, percent and layer both unchanged since the previous check for the same job. Attach a fresh snapshot to any alert when one can be taken, otherwise report the telemetry alone, and name the specific evidence. - Monitor a running print by polling. A workable pattern is a 20-minute interval check that reads status first, takes a snapshot only while
gcode_stateis PREPARE or RUNNING, and stays silent when nothing is printing, when the print is healthy, and when it finishes normally. A change to FAILED, an unexpected PAUSE, or a non-zeroprint_erroralways alerts, even though the print is no longer active. Keep the previous percent and layer in a state file so a stall is detectable, and suppress a repeat alert for the same job and problem for at least an hour. - Pause only a clear-cut visual failure (obvious spaghetti, a fully detached or dragged part, an empty plate well into the print, a large nozzle blob) when the user has authorized it. Publish
{"print": {"sequence_id": "0", "command": "pause"}}todevice/<serial>/request, once. Borderline or telemetry-only problems get an alert, not a pause.
Verify the Result
- A published MQTT command is not proof it took effect. After a pause, wait about 15 seconds, read status again, and report the pause as done only when
gcode_statereads PAUSE. - If status still reads RUNNING after a pause attempt, report the pause as failed and tell the user to pause in Bambu Handy right away. Control commands can be refused when the printer is not in LAN or Developer Mode, and pause acceptance in cloud mode has not been confirmed, so this verification is what makes the claim honest.
- Before describing or attaching a snapshot, check that the client exited successfully and wrote a new file for this request, then view it. Never describe an older image as the current view.
Limits
- No cloud camera path: Bambu Handy is phone-only, and Bambu's cloud liveview uses a proprietary peer-to-peer ticket system that refuses third-party clients (OrcaSlicer gets a 403 on cloud liveview while its cloud status works). LAN access through Home Link is the working route.
- This skill does not need LAN Only Mode or Developer Mode; both disconnect the printer from Bambu Cloud and break Handy. Changing modes is the owner's decision, never the agent's. For print starts, see the Bambu Lab printers skill.
- No starting prints, arbitrary G-code, temperature, speed, or light changes, and no resume or stop under a pause authorization. Resuming is the user's decision, and stop destroys the print.
- Timelapse recording is separate from liveview: the P2S has no microSD slot and records timelapses to a USB flash drive in the front USB-A port, which is not included in the box.
Sources
- Bambu Lab printers skill — the family skill for LAN status and owner-approved print starts.
- Building a Public Bambu Lab P2S Live Dashboard — the LAN Only Liveview configuration and the local RTSPS and MQTT paths, verified against a P2S.
- Bambu Lab forum: MQTT commands — the
pause,resume, andstopJSON commands ondevice/<serial>/request. - bambu-p2s-bridge PROTOCOL.md — P2S LAN protocol notes for MQTT state and control on port 8883 and the camera on port 322.
- OpenBambuAPI — community documentation of the Bambu MQTT and cloud HTTP protocols.
- ha-bambulab — the Home Assistant integration and its
pybambuclient, another working implementation of the same MQTT reports.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

