404 on /api/connection on MINI

[tommie]

/api/connection gives console errors about 404. I've tried figuring out where this is supposed to be, and it's not clear this ever worked.

• d006e34 added the api/connection fetch, on 2021-10-04.
• 9effde6 moved it to another file.
• 2170e3b moved it again.

On the Buddy side,

• looking around 2021-11-01, I see no mention of /api/connection: https://github.com/prusa3d/Prusa-Firmware-Buddy/blob/782cc77d0320009a9bd8ac20578f091b140e6569/lib/WUI/http/httpd.c#L2675
• prusa3d/Prusa-Firmware-Buddy@6a3944a suggests a 404 wasn't actually returned for Not Found when the commit above was made.
• prusa3d/Prusa-Firmware-Buddy@ba11021 added a stub of the /settings endpoint, suggesting firmware updates lag Link-Web by months. (It still just returns a static stub JSON.)
  • Spot-checking at commits around April 1 and July 1 also showed no endpoint, so it doesn't seem to be time skew.
• the routing has moved, but still no connection: https://github.com/prusa3d/Prusa-Firmware-Buddy/blob/f69118723a41ecef761be9df96205b9cf4571331/lib/WUI/link_content/prusa_link_api.cpp#L181
• also not as v1/connection: https://github.com/prusa3d/Prusa-Firmware-Buddy/blob/f69118723a41ecef761be9df96205b9cf4571331/lib/WUI/link_content/prusa_link_api_v1.cpp#L113

There is a trace in Buddy; an old integration test:

• https://github.com/prusa3d/Prusa-Firmware-Buddy/blob/f69118723a41ecef761be9df96205b9cf4571331/tests/integration_old/test_login.py#L69
  • this file hasn't changed since initial commit in 2019, so I'm not sure it even refers to the same endpoint.

Of course, this probably doesn't affect the printer, but it's an interesting mystery. Perhaps there's another firmware that does have the /api/connection endpoint?