feat(printing): 3D printing infra stack + spec for Bambu P2S #3
No reviewers
Labels
No labels
lab-honing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
adam/foundry!3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "printing-infra"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
3D Printing Infra — Bambu Lab P2S
Self-hosted, cloud-independent management layer for the new Bambu Lab P2S AMS Combo. Printer runs LAN Only + Developer Mode; all tooling binds locally by IP + access code.
What's here
stacks/printing/— new git-backed stack:bambuddy(ghcr.io/maziggy/bambuddy) — command center: monitoring, multi-viewer camera fan-out, MQTT publish-out, Prometheus, per-print energy, HMS errors.network_mode: host(SSDP L2 multicast discovery), UI on:8000.spoolman(ghcr.io/donkie/spoolman) — filament inventory,7912→8000on dockernet. Bambuddy syncs to it.docs/plans/printing-infra.md— full spec.Decision recorded
Path B (flat stack on Unraid) now. IoT-VLAN segmentation deferred to its own future project that sweeps up the printer + the (in-rebuild) Home Assistant VM + other IoT together — the printer does not bootstrap a one-device VLAN. The spec keeps the full VLAN/VM design as the reference for that migration.
Verified against upstream (handoff had errors — corrected)
ghcr.io/maziggy/bambuddy+network_mode: host+:8000(handoff saidmaziggy/bambuddy,80:80)7912:8000(handoff said7912:7912)Deploy notes
bambuddy/,spoolman/).192.168.4.204; ha-bambulab vs Bambuddy-MQTT; Obico (recommend defer); Prometheus scrape.🤖 Generated with Claude Code