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 1 KB Seed smart home and 3D printer knowledge
Raw Blame History

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

source_of_truth: owner-described

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

Klipper 3D Printer

  • Inventory id: klipper-3d-printer.
  • Type: 3D printer.
  • Controller: Raspberry Pi.
  • Firmware/control stack: Klipper.
  • Network: local network, exact address not yet documented.
  • Management UI: not yet documented.

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.

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.