Skip to content

Releases

Release 0.1.0-beta.1

Release 0.1.0-beta.1 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 17 Nov 09:14

Prusa Connect 0.1.0-beta.1

Prusa Connect is a server you run on your own network. Your printers connect to it, and you use them from its web app and its API. Nothing goes through a cloud service.

Which file to download

your machine file
a Linux PC or NAS, 64-bit Intel or AMD prusa_connect_amd64
a Raspberry Pi Zero 2 W, 3, 4 or 5 with a 64-bit system, or another 64-bit ARM Linux machine prusa_connect_aarch64
a Raspberry Pi 2, Zero 2 W, 3, 4 or 5 with a 32-bit system prusa_connect_armv7
a Raspberry Pi Zero, Zero W or 1 prusa_connect_armhf
Windows on Intel or AMD prusa_connect_windows_amd64.exe
Windows on ARM prusa_connect_windows_arm64.exe
a Mac with an Intel processor prusa_connect_macos_amd64
a Mac with Apple silicon (M1 and later) prusa_connect_macos_arm64

These are the full build. Each one carries the web app, the HTTP API, the live event stream, MQTT, SQLite and PostgreSQL storage, and Prometheus metrics. MQTT, the metrics and PostgreSQL stay off until the configuration file turns them on.

The prusa_connect_minimal_* files are a smaller Linux build for the same four processors. It has the API and the printer connection, and it has no web app, no MQTT, no metrics and no PostgreSQL.

What changed

Security

  • Go 1.26.11 now builds the server and every container image, and it fixes GO-2026-6859 in net/http. Building from source needs Go 1.26.11

Changed

  • An install that cannot grant a permission says the module may still ask whether a person holds it.
  • Printers nearby lists a machine that runs a Prusa Connect server once, as that server. A printer that runs a server beside its PrusaLink is no longer offered under Add printer.
  • The camera beside a running print on a printer's Now tab shows its last picture and plays its live view only when you press play. It says it is live only while it plays, and the larger camera window is gone.
  • The camera card of a dashboard and the Cameras view of the printer list show the whole picture and play the live view, as a printer's Cameras tab does. The camera card's Picture setting is gone.
  • What a camera serves, and the addresses of a generic or MJPEG camera, now show beside its picture in the Cameras tab. The Edit button is gone.
  • The server log says at INFO when a printer's connection ends, and why.
  • The primary button, the selected item and checked controls show white text on the brand orange, as in the Prusa Design System, and darken on hover. The PRO skin takes the design system's Connect colours in the same way.
  • The fleet severity filter has no Needs hands tier: a paused printer is under Needs attention
  • Checkboxes, radios, switches and sliders paint the skin's on colour. Segmented controls and tabs paint its selected colour, and progress bars its progress colour. The Slicer and PRO skins show their own colours there.
  • The Official badge on Extensions is outlined, so the orange fill on a row is the Install button alone.
  • The systemd unit lets the server open a port below 1024, for the time server on UDP port 123. The modules the server starts do not get that right.
  • GET /api/v1/devices/{device_id}/files no longer waits for the printer. It used to wait on a folder it held nothing for, and on refresh=true, and failed with 409 or 504. It now answers 200 within about a second with the rows this server holds. While the printer reads the folder, the answer carries reading: true and reading_since, and items is empty if nothing was held. A read that failed answers 200 with fault, such as core.printer/LISTING_UNFINISHED for a read the printer did not finish. refresh=true starts a new read and answers the held rows at once. A client that checks only the status code reads an empty folder as an empty drive. Check reading and fault, wait for com.prusa.connect.device.files.changed for that folder, then ask again without refresh.
  • GET /api/v1/devices/{device_id}/storages?refresh=true waits at most about a second for the printer. It used to wait for a busy printer and fail with 504. It now answers 200 with what the printer last said. A later answer that differs is published as com.prusa.connect.device.storages.changed, so a client that needs the current drives listens for that event.
  • The container image carries the slicing extension in /opt/modules/server-slicing, with the module path github.com/prusa3d/server-slicing. It was /opt/modules/slicer with github.com/prusa3d/slicer, and a core.modules_local entry that names that pair finds no folder. Replace the entry with the new pair and switch the extension on again. It is a new module with a new data folder, so install the PrusaSlicer versions again.
  • [sdk] The type of every error response now points to https://beta.prusa3d.com/connect-local/docs/error-codes/ instead of https://prusa-connect.org/docs/error-codes/, a domain Prusa does not own. The anchor after # is unchanged. A client that compares the whole type updates the base, or compares code, which is the stable identifier.
  • Cameras are devices kept in the server's database, and no configuration file declares them. A camera used to be a camera resource: a resources.camera block of config.yaml, or an entry the interface wrote into config.d/resources.json through /api/v1/resources/camera/<name>, which now answers 422. Add, change and remove one with PUT and DELETE /api/v1/cameras/<name>, and read the settings with GET /api/v1/camera-settings; each camera has its own version to quote. The first start of this version moves the cameras of both files into the database with their grants and logs each one. A resources.camera block left in config.yaml after that start is logged and not read, so delete it. A backup of the database carries the cameras, and a copy of the files does not.
  • A camera's status events, com.prusa.connect.resource.state.changed on its own origin, reach whoever may see the camera. A grant on resource_kind:camera is still what lets a person change cameras.
  • [sdk] CameraSettings from @prusa/connect-ui/data reads and writes cameras through listCameraSettings, putCamera and deleteCamera, so the client it is given must carry them. declaredInFile is gone, because no camera is declared in a file.
  • The Extensions page lists only the official marketplace extensions until an organization administrator switches on Show community extensions in the marketplace settings. Installing or updating an unverified extension asks the person to accept the risk first, and every row shows its trust badge.
  • [sdk] A module.yaml must name the licence of the module under license, free text of at most 200 characters such as MIT. The server refuses to install or start a module whose manifest has none, so add the key to your manifest before you update the server.
  • [sdk] A module.yaml is refused when its license, or the why or sends of an egress entry, holds a control or invisible character. Such a character is a terminal escape, a reversal of the writing direction or a zero-width space.

Added

  • [sdk] The tool tree carries the material package instance a driver reports for a tool: its uuids, type, colour, full weight and profile temperatures, in Tool.Reported.
  • [sdk] connectorapi.ValidColor says whether a tool's colour is #rrggbb or #rrggbbaa, and ReadTools reads no other colour.
  • The PrusaLink-compatible xbuddy driver publishes the material package instance a printer reports for a tool, so the tool tree carries it. A spool the printer stops reporting leaves the tool tree.
  • [sdk] A module reads whether a device was removed or registered again under a new id, in deviceapi.Device.Retired.
  • [sdk] A module lists the actions it only asks access.check about under checks: in module.yaml, and the install withholds nothing for them. Materials asks so whether a person may operate a printer. The operator approves each one at install, as check <action>.
  • core.discovery.host_records: system lets another mDNS responder on the machine, such as Avahi, answer for its host name. The server then announces only its services, so discovery can stay on there without the machine being renamed to <hostname>-2.local.
  • Storage has a Shared column on a server with the Fractal module and its files block, and its switch shares a folder with the servers below. A card under it lists the folders that the servers above and below share.
  • [sdk] A module may name qr-code as the icon of a page or an action. The set a manifest may choose from is closed, and until now it held no glyph for a code a camera reads.
  • [sdk] A module can hand a JPEG to a push camera with camera.accept. The bytes travel on the call's own stream, and the call needs operate on the camera, the permission the HTTP push route takes.
  • A generic camera type takes the pictures a camera sends, or fetches them from an address, and can also stream over RTSP or MJPEG.
  • A printer's page has a Cameras tab with one card per camera. It shows the camera's last picture and plays its live view, MJPEG or H.264, when you press play, and it adds, changes and removes cameras.
  • [sdk] A module can draw a section for each camera in the Cameras tab, with the new camera-section slot.
  • [sdk] A module can offer camera types with camera_types in its manifest. A camera of such a type runs on the core's generic camera, and the module feeds it its pictures with no grant. The module can draw its live view in the new camera-view slot.
  • The camera listing names each camera's type, and GET /api/v1/camera-types lists the types a new camera may be declared as. The Cameras card offers them.
  • [sdk] The event com.prusa.connect.camera.frame.received tells a reader that a camera was handed a new frame.
  • [sdk] printcompat now warns when a file for a Core One with INDX does not name the INDX lock feature. Firmware 6.6.2 and newe...
Read more