owner: gmikcon status: active last_reviewed: 2026-10-11 review_interval: 180d confidence: high
This document records the known 3D-printing devices in the home infrastructure. Both printers are networked devices with local management surfaces and physical side effects.
klipper-3d-printer.ender, user gmikcon.v0.13.0-562-g7a4472649.home-lan.192.168.1.102.http://192.168.1.102/.v0.10.0-9-g3fbe6ee (API 1.5.0) at http://192.168.1.102:7125/, no authorization required on LAN.192.168.1.102:22, credentials not documented.printer.cfg in Moonraker config root; gcodes root holds ~35 gcode files (recent: hatch controller box, cover_ABS, single relay cover top v1.1).Observed Moonraker status (2026-10-11):
klippy_connected: true, klippy_state: ready.standby, bed 23.0 C, extruder 22.9 C.bambulab-a1-3d-printer.03919D581204930 (from TLS certificate CN).home-lan, address 192.168.1.251.8883, login bblp + LAN access code. Publish device/{serial}/request, subscribe device/{serial}/report. Self-signed BBL CA certificate — client must skip verification.990, login bblp + LAN access code. Roots: model (factory 3MF samples), cache (sliced gcodes and owner projects), timelapse, image, logger, recorder, ipcam.Bambu Lab A1 (LAN). Do not copy the code into this repository.3D printers are infrastructure-relevant because they are networked devices with local management surfaces and physical side effects.
Document:
Do not document account passwords, API tokens, cloud credentials, or printer access secrets.