Klipper Cloud Remote Agent
The Klipper Cloud remote agent is used to connect networked FLYOS-FAST devices to Klipper Cloud, allowing the current host machine to be bound and remotely accessed in the cloud platform. The FLYOS-FAST v1.4.0 beta image generates local credentials on first boot, but remote access is disabled by default and must be actively enabled by the user.
This feature is currently only confirmed in the FLYOS-FAST v1.4.0 beta image. Once enabled, the device will actively connect to the remote service; keep it disabled when remote access is not needed.
Device IDs, local credentials, agent configuration, and logs containing these items must not be posted to forums, group chats, or other public locations.
Before moving, heating, or executing G-code remotely, you must confirm that the printer's on-site environment is safe and retain the ability to cut power or perform an emergency stop immediately. Network latency, connection interruptions, or state desynchronization may affect operational results. It is not recommended to start prints remotely when unattended and unable to handle exceptions.
Feature Description
- Once the remote agent is enabled, you can bind the current host machine as prompted by the Klipper Cloud platform.
- Disabling the remote agent only stops the cloud remote connection; it does not affect LAN access to Fluidd, Mainsail, Moonraker, or SSH.
- The presence of an agent process in the background does not mean remote access is enabled; the agent process may also simply be waiting for user authorization.
- The device ID is used to identify the current host machine. It is not the motherboard USB ID, CAN UUID, or the MCU ID in the printer configuration.
Full Enablement Process
1. Enable Remote Service
Execute via SSH:
/data/klipper-cloud-agent/klipper-cloud-agent --enable-remote
If the command completes without errors, wait for the agent to connect to the cloud. Do not repeatedly execute the enable command in succession.
2. Query Device ID
Ensure the cloud service is enabled and the host machine can access the internet, then execute:
/data/klipper-cloud-agent/klipper-cloud-agent --device-id
After the command returns the device ID normally, follow the Klipper Cloud platform prompts to bind the device. When copying, select only the device ID itself—do not send full terminal screenshots to others.
The image above shows a terminal operation example, with the device ID hidden. Always refer to the actual output from your own device.
3. Complete Cloud Platform Binding
Open Klipper Cloud Device Management and log in with your own account. On first use, please read the usage notes, service agreement, and privacy rules on the page.
After logging in, locate the device addition field in the My Devices section on the left:
- Enter the full device ID returned by
--device-idinto Enter KD-… Device ID. - Click Add.
- Wait for the device to appear in the left-side list and confirm the status shows Online.
- Click the device to open the remote device management interface in the page; click Open in New Window in the top-right corner if a separate window is needed.
The account, device name, device ID, and remote printing interface in the device management page screenshots have all been hidden. Do not publicly post page screenshots containing real information.
After binding, verify the following:
- The device shown on the cloud platform matches the current host machine.
- The remote page can read the current printer status.
- Fluidd or Mainsail on the LAN remain accessible.
Do not use device IDs provided by others, and do not bind your own device to untrusted accounts.
Disabling Remote Service
Execute the following when remote access is no longer needed:
/data/klipper-cloud-agent/klipper-cloud-agent --disable-remote
After disabling, LAN access to local Fluidd, Mainsail, Moonraker, and SSH remains unaffected. If you plan to transfer, repair, or reinstall the device, you should also unbind the device on the Klipper Cloud platform; executing the disable command alone does not remove the cloud platform account association.
Unbinding from the Cloud Platform
When preparing to transfer, repair, or stop using the current device, you should disable the device-side remote service and remove the platform binding simultaneously:
- First execute
--disable-remotein SSH. - Right-click the device on the left side on a computer; long-press the device on a phone or touch device.
- Select Delete/Unbind.
- Enter the current device name as prompted on the page to confirm.
Unbinding removes the association between the current account and the device. Device-side saved configuration, print files, and LAN access will not be deleted as a result.
Command Quick Reference
| Operation | Command | Prerequisites |
|---|---|---|
| Check agent program | test -x /data/klipper-cloud-agent/klipper-cloud-agent && echo "klipper-cloud-agent is installed" | Execute after logging into SSH |
| Enable remote service | /data/klipper-cloud-agent/klipper-cloud-agent --enable-remote | Host machine is connected to the network |
| Query device ID | /data/klipper-cloud-agent/klipper-cloud-agent --device-id | Remote service enabled and network normal |
| Disable remote service | /data/klipper-cloud-agent/klipper-cloud-agent --disable-remote | Execute when cloud access is no longer needed |