Fork: 0
root / gnexus-book
Transfer to URL with SHA Find file
Newer
Older
gnexus-book / 10-systems / hardware / 3d-printers.md
@Eugene Sukhodolskiy Eugene Sukhodolskiy 1 day ago 2 KB Document Klipper printer endpoints
Raw Blame History

owner: gmikcon status: active last_reviewed: 2026-05-10 review_interval: 180d confidence: medium

source_of_truth: owner-described-and-network-observed

3D Printers

This document records the known 3D-printing devices in the home infrastructure. It is intentionally high-level until exact IP addresses, management UIs, and operational workflows are confirmed.

Inventory

Modified Creality Ender 2 V3

  • Inventory id: klipper-3d-printer.
  • Base model: Creality Ender 2 V3.
  • Modification level: deep.
  • Controller: Raspberry Pi.
  • Firmware/control stack: Klipper.
  • Network: home-lan.
  • Address: 192.168.1.102.
  • Management UI: Mainsail at http://192.168.1.102/.
  • API: Moonraker at http://192.168.1.102:7125/.
  • SSH: 192.168.1.102:22, credentials not documented.

Observed Moonraker status:

  • klippy_connected: true.
  • klippy_state: ready.
  • Moonraker version: v0.10.0-9-g3fbe6ee.
  • API version: 1.5.0.
  • Registered directories: config, logs, gcodes, config_examples, docs.

Bambu Lab A1

  • Inventory id: bambulab-a1-3d-printer.
  • Vendor/model: Bambu Lab A1.
  • Type: 3D printer.
  • Network: local network, exact address not yet documented.
  • Management UI/API: not yet documented.

The Bambu Lab A1 should be treated as a closed appliance, not as a normal Linux host. SSH access is not expected. Local control, when enabled, is normally based on Bambu's LAN/access-code flow and Bambu Studio-compatible tooling rather than direct shell access.

There are community reports of FTPS support on some Bambu Lab printer series using the printer access code, but this must be verified against this specific A1 before documenting it as active.

Documentation Policy

3D printers are infrastructure-relevant because they are networked devices with local management surfaces and physical side effects.

Document:

  • static or reserved IP addresses;
  • management UI/API endpoints;
  • controller host details for the Klipper printer;
  • update and backup procedures for printer configuration;
  • whether the device requires internet/cloud access;
  • firewall or network-isolation constraints.

Do not document account passwords, API tokens, cloud credentials, or printer access secrets.

Open Questions

  • Which network each printer uses: home-lan or home-iot-lan.
  • Whether either printer has a static DHCP lease.
  • Exact IP addresses and hostnames.
  • Klipper UI stack: Mainsail, Fluidd, OctoPrint, or another interface.
  • Whether Bambu Lab A1 is used only locally or through Bambu cloud features.
  • Bambu Lab A1 IP address.
  • Whether Bambu Lab A1 exposes LAN-only or FTPS endpoints in the current firmware.