I want to direct my printer through my local wifi network instead of sending everything to the cloud. The software just won’t find it.
Scanning automatically won’t work.
IP Adress is not found.
Webpage version through ip:port DOES work.
All I got is the cloud and the app and I’m getting a little tired of having to send a print job five times because the cloud times out on me or not being able to actually check my stuff on the camera more quickly because, again, the cloud times out.
When you checked from LCD panel and verified that it was connected to your WIFI, was the IP address that it used to connect to your local WiFi on the same LAN as your computer?
When you pinged that IP address did you get a reply?
Although I agree with you, let me take their side for just a small - very small - moment.
This isn’t really a Creality problem. It’s a consequence of running a Klipper-based system on Linux.
Klipper itself has nothing to do with networking. IP addressing is handled at the Linux OS level using standard network management tools. I’m not aware of any consumer 3D printer manufacturer that exposes those Linux networking controls directly to end users.
Think about the risk that Creality and other 3D Printer companies would take if they added this feature. Exposing static IP configuration in the printer UI would only increase support load. Users would misconfigure settings, lose connectivity, and open support tickets. That creates reputational risk, higher support costs, and zero upside in printer or filament sales.
From a product standpoint, it’s a lose-lose proposition. That’s why manufacturers leave IP management to the router makers where the 3D printing company can pass responsibility for connectivity.
Now having made that argument, which is what the 3D Printer companies have claimed, I call bullshit! Why? Because all of my office printers, HP, Epson, Brother etc., have static IP options so why not a 3D printer? My answer was above; if it doesn’t impact sales, they simply won’t do it. That’s the Chinese business philosophy of "Chabuduo" (差不多) or “close enough”.
I can ping it and I can access the webpage version of the printer via the ip adress and port method in my browser. So it IS there. It’s just that the software just outright refuses to see it either on automatic scan or manual IP. It won’t show on other slicers over the network either somehow.
But it IS there and I CAN connect to it via the cloud.
Well at this point, troubleshooting 101, revert back to standard setup and see if it works with straight DHCP, if it does, then that points the problem to more likely how you have your network setup.
