Creality Sonic Pad (klipper) not showing up in Device tab

[rlabusiness]

I've been using SoftFever 1.4.4 (and recent versions) with a Creality Sonic Pad (a turn-key device running klipper / moonraker / fluidd / mainsail). The software connects successfully and sends prints to it over the network.

However, something that has never worked is loading the fluidd/mainsail interface in the Device tab like I've seen other people do on youtube. Instead, I get the following error (screenshot also attached):

{"error": {"code": 404, "message": "Not Found", "traceback": "Traceback (most recent call last):\n\n File \"/usr/share/moonraker-env/lib/python3.7/site-packages/tornado/web.py\", line 1681, in _execute\n result = self.prepare()\n\n File \"/usr/share/moonraker/moonraker/app.py\", line 818, in prepare\n raise tornado.web.HTTPError(404)\n\ntornado.web.HTTPError: HTTP 404: Not Found\n"}}

I'm not sure if it's as simple as a port or path mismatch (since I'm seeing a 404 in that error message), but I haven't been able to figure it out. Does anyone have any suggestions or solutions for this?

[rlabusiness]

I did some more digging and I think I may know what's happening.

The Sonic Pad can support multiple printers, and the network port you use to access each printer's klipper/moonraker instance is pre-configured. This network port is somehow also coupled to each physical USB port on the device. For instance:

Printer 1: Port 7125 - Bound to physical USB Port 1
Printer 2: Port 7126 - Bound to physical USB Port 2
Printer 3: Port 7127 - Bound to physical USB Port 3 (where I have my printer plugged in)
And so on...

What the slicer's Device tab is trying to do is load <ip_address>:7127, which is the port I use to successfully send files to the printer, but that's not where the web interface is. The page I need to load is served from the Sonic Pad via port 80.

Additionally, I plan to make this web interface accessible via an encrypted reverse proxy soon so that I can access it via a URL like https://host.domain.com (which would use port 443).

To fix this compatibility issue and give users a bit more flexibility over their web access configuration, it appears that we may need a field to override the Device tab's URL if it is different from the Octoprint/moonraker API URL.

I'll log a request for this in the bug/enhancement area.

Edit: I've now logged Issue #451 too keep track of this.

[rlabusiness]

There's one other thing I'll add.

I believe the web interface available on the SonicPad at <ip_address>:80 is fluidd. I just discovered that Mainsail also runs pre-configured on the Sonic Pad at port 8819. Using that port, the printer tested as "connected" just now, and the Device tab actually does load the Mainsail UI using that same port.

Since I have a print going at the moment, I can't test that it will actually send the print job to this printer (plugged in to USB Port 3 and accessible via port 7127), but if it does work, it might be a good workaround for now.