Creator 5 Pro: "Failed to establish temporary connection" even with LAN-only mode enabled (v1.0.5-alpha.8)

[Andaru20-cpu]

Environment

• FlashForgeUI version: 1.0.5-alpha.8
• OS: Windows
• Printer: FlashForge Creator 5 Pro
• LAN-only mode: enabled on the printer before testing

Steps to reproduce

1. Add Printer -> Scan Network -> printer is discovered correctly as "Creator 5 Pro" with the correct IP and serial number.
2. Double-click the discovered entry to connect -> fails with "Failed to establish temporary connection".
3. Also tried Add Printer -> Enter IP Address manually with the same IP -> same result: it shows "Detecting printer type..." briefly, then "Failed to establish temporary connection".
4. No pairing/check-code prompt is ever shown before the failure, in either flow.

Debug log

With Debug Mode + Enable Network Logging turned on, network-debug-*.txt shows both attempts going straight to legacy TCP port 8899:

[2026-08-11T12:14:06.716Z] [Connection] Attempting connection to printer
  IP: 192.168.100.196
  Port: 8899
  Additional Data: { "printerType": "known" }

[2026-08-11T12:15:43.008Z] [Connection] Attempting connection to printer
  IP: 192.168.100.196
  Port: 8899
  Additional Data: { "printerType": "discovered" }

No further lines are written after these - the app just shows the error toast and returns to the "Welcome" screen. The general debug-*.txt log for the same session was empty (0 bytes).

Expected behavior

Per the v1.0.5-alpha.2 changelog note ("These models are HTTP-only (no legacy TCP on 8899)"), I expected the Creator 5 Pro to be detected/connected over the HTTP API rather than probing TCP 8899 - especially since Scan Network already correctly identifies the model as "Creator 5 Pro" via discovery before the temporary-connection step even runs.

Additional notes

• The printer is otherwise fully reachable on the network: OrcaSlicer's built-in FlashForge print-host connects to the same IP over the local HTTP API without any issue ("Connected to Flashforge local API successfully").
• v1.0.4 was not tested as a comparison since it doesn't support this model at all per the README support table.
• This looks related to Failed to establish temporary connection Adventurer 3C #54 - happy to run a similar diagnostic script against this printer if that would help narrow it down.

[GhostTypes]

Hello!

Updating to 1.0.5 alpha 11 should resolve your issues, this specific behavior was fixed in 1.0.5 alpha 9.
I also need to update the versions in the readme, apologies for the confusion

Printer detection for all modern models (5M/AD5X/C5) is now HTTP-only, and since then there's been a few more Creator 5 specific fixes.

Lastly as heads up, starting local jobs will unfortunately not be possible on your printer model, but uploading new .3mf files will continue to work. FlashForge made some changes in the firmware which removed the ability to do "material matching" through the local API.