Printer Setups & Firmware | SoLoPrint Help Center

Connecting an OctoPrint instance to SoLoPrint (Auto-Discovery)

The Standard Protocol If you run OctoPi on your 3D printer, adding the machine to SoLoPrint takes seconds. The Bridge connector auto-discovers OctoPrint instances responding on your local network (e.g. octopi.local). 1. Generating your OctoPrint API Key 1. Open your local OctoPrint web interface (usually http://octopi.local). 2. Click the Wrench icon to open Settings. 3. Navigate to Application Keys. 4. Click Generate and type "SoLoPrint". 5. Copy the resulting long alphanumeric string. 2. Linking the Printer in SoLoPrint 1. Head to the Printers page in the SoLoPrint cloud dashboard. 2. Click Add Printer. 3. The wizard will prompt you to select the Bridge running on the local subnet. 4. The Bridge will report back any available OctoPrint IP addresses. 5. Select your machine, paste the Application Key, and hit Save. Your printer's telemetry and live video will instantly appear in the cloud!

Last updated on Mar 31, 2026

Connecting a Klipper (Moonraker) instance to SoLoPrint

High-Speed Firmwares SoLoPrint fully supports Klipper via its underlying API daemon: Moonraker. Regardless of whether your frontend is Mainsail or Fluidd, the Moonraker port (typically 7125) must be accessible to the Bridge. 1. Discovering Moonraker If you installed the Bridge directly onto the Klipper-host Pi, discovery is automatic. 1. Go to the Printers tab on your SoLoPrint dashboard and click Add Printer. 2. Select Klipper/Moonraker. 3. Choose your Bridge. 4. If discovery fails, explicitly enter the local IP address (e.g., 192.168.1.55) and port 7125. 2. Entering the API Key If your Moonraker is secured with an API key (common for internet-exposed or secure arrays), paste it into the wizard. Otherwise, you can leave it blank. 3. Connect Click Connect. You should see live nozzle and bed temperatures appearing inside the SoLoPrint dashboard immediately.

Last updated on Mar 31, 2026

Connecting a Bambu Lab printer using Native LAN-Only Mode

Fully Local Bambu Integrations Bambu Lab’s cloud isn’t meant for enterprise control. By switching to LAN-Only Mode, SoLoPrint routes the G-Code exclusively through your local network Bridge, bypassing externally synced Chinese servers entirely. 1. Preparing the Machine 1. Walk to your physical Bambu printer (X1C, P1S, A1, etc.) and tap the Settings gear icon. 2. Tap the Network tab. 3. Switch LAN Only Mode to ON. 4. Note the displayed IP Address and the Access Code (PIN) shown on the screen. 2. SoLoPrint Integration 1. Go to Printers > Add Printer in the SoLoPrint Dashboard. 2. Select Bambu Lab (Native LAN). 3. Enter the IP Address and the Access Code you noted earlier. 4. Ensure you select the Bridge located on the same logical subnetwork as the Bambu machine (otherwise the multicast protocol will fail). 3. Verification You will instantly see native Bambu Lab features load into the SoLoPrint UI, including their proprietary camera streams routed through our WebRTC tunnel.

Last updated on Mar 31, 2026

Enabling MQTT protocols on your Bambu Lab X1C / P1S for SoLoPrint integration

Real-time Telemetry for Bambu SoLoPrint communicates with Bambu Lab printers over MQTT (Message Queuing Telemetry Transport), not HTTP. We essentially subscribe to a continuous stream of metrics broadcast by the machine itself. Is MQTT enabled? MQTT is permanently enabled on modern Bambu firmwares, but requires the Access Code for decryption. If you see 0°C for your temperatures, your Access Code is incorrect, or the printer is ignoring the MQTT handshake from the SoLoPrint Bridge. Ensure that you are not running two competing control interfaces (like HomeAssistant and Bambu Studio simultaneously) dragging down the physical printer's processing threads. Sometimes rebooting the physical Bambu Lab printer solves a stale MQTT connection.

Last updated on Mar 31, 2026

Linking multiple physical printers to a single SoLoPrint Bridge

The Hub-and-Spoke Model You do NOT need a separate Raspberry Pi or Bridge software installation for every printer. One Bridge can confidently handle the network proxying for dozens of 3D printers on the exact same subnet. How to link multiple 1. Install the SoLoPrint Bridge on a centralized computer or a dedicated Raspberry Pi on your local network (like a server closet). 2. Navigate to Printers > Add Printer in the dashboard. 3. Select that exact same Bridge from the dropdown. 4. Simply input the diverse IP Addresses of your scattered OctoPrint or Moonraker nodes (e.g., 192.168.1.5 and 192.168.1.6). The single Bridge securely fetches the HTTP/WebSocket strings from multiple endpoints and tunnels them all securely up to our cloud backend! Enjoy a much cleaner physical setup.

Last updated on Mar 31, 2026

Passing custom G-Code macros from the cloud to your local Klipper firmware

Controlling the Firmware Power users love writing custom macros in printer.cfg. SoLoPrint natively supports triggering these directly from the cloud UI. 1. Locating the Terminal Open the expanded view for your connected Klipper printer. Click the Terminal tab. 2. Macro Execution You can type standard G-Code commands directly (e.g. G28 to home) and watch the printer react in real-time on the camera feed. If you have custom macros listed in Klipper, type their exact name (e.g., CLEAN_NOZZLE or HEAT_SOAK). SoLoPrint's terminal instantly forwards this string through the Bridge's WebSocket to Moonraker, kicking off your custom sequence.

Last updated on Mar 31, 2026

Calibrating Z-Offset and Babystepping directly from your mobile dashboard

Mid-Print Perfect First Layers You no longer need to run back to the printer physical screen to fix a bad first layer squish. During an Active Print If your printer is connected and printing via OctoPrint or Klipper: 1. Open the SoLoPrint dashboard on your mobile device. 2. Tap the active printer. 3. Switch to the Controls tab. 4. Look for the Babystep (Z-Offset) up/down widgets. The Impact Tapping these buttons issues real-time micro-commands to the firmware (commonly M290 Z-0.01). You can watch the nozzle descend live onto your WebRTC camera interface, dialing in the perfect first layer completely from your couch.

Last updated on Mar 31, 2026

[Coming Soon] Connecting PrusaLink / PrusaConnect hardware

The Prusa Ecosystem For users deploying Prusa MK4s or XLs with the native PrusaLink board, integrating with SoLoPrint is currently under development. Our Upcoming Approach We are actively writing a native plugin component for the SoLoPrint Bridge that implements the PrusaLink HTTP digest authentication standard. Once live, you will be able to treat Prusa firmware exactly like OctoPrint or Bambu, seamlessly ingesting Live Z parameters, MMU statuses, and sending toolpaths from the Cloud Slicer directly to the Prusa board without switching software paradigms.

Last updated on Mar 31, 2026