For anyone running OrcaSlicer 2.4.1 with a K2 Pro, here’s what I’ve found on connection methods and what actually works.
The Setup That Works
-
Host Type: CrealityPrint
-
Printer Agent: CrealityPrint
-
Hostname:
192.168.1.xx:4408(your printer’s IP + port 4408)
See screenshot below.
What You Get
-
Device control through OrcaSlicer — printer status, temps, print management — all functional
-
CFS filament slots visible and manageable
-
Prints send and run without issue
What You Don’t Get
- Camera — the K2 Pro uses WebRTC architecture that OrcaSlicer cannot access regardless of connection method. This is a hardware/firmware limitation, not an OrcaSlicer issue.
Background
Prior to 2.4.x the only working OrcaSlicer path was Octo/Klipper at :4408, which gave device control but no CFS sync. The CrealityPrint host type added in 2.4.x adds CFS sync — and using :4408 in the hostname field is what restores device control alongside it.
Camera remains the outstanding limitation. If anyone has found a workaround post below.