MIT · core >=0.1.0-beta.1 · sink · linux_amd64, linux_arm64, darwin_arm64, windows_amd64 · 18096.4 KB · Nov 17, 2026
Maintenance for Prusa Connect counts the print hours of every printer and tells you when a maintenance task is due.
Each printer's page gets a Maintenance tab with its own counter: the hours this server saw, the value the printer's display shows, and one line per task with the interval, the hours since the last check and the point at which it reads as due soon. Typing the printer's own counter, as 343 or 14d 7h, sets the lead between the two, and both counters then move with every print.
The Maintenance page in the sidebar holds one schedule for the fleet, from the Prusa Knowledge Base: 200 hours for axes, belts, fans and extruder, 600 for the electrical connectors, 90 days for the linear rail and 5000 hours for a hardened steel nozzle. Changing an interval there carries it to every printer's task of that name, and the printer keeps its own hours.
Done asks first and anchors the next interval at the printer's current hours; Start over at 0 does the same without asking. A task that ships with the module cannot be removed, only changed; tasks you add can be removed. The setting alert_percent, 90 by default, sets when a task reads as due soon.
A printer's tab also says how many hours each tool ran. The module reads the G-code of the finished prints once, .gcode and .bgcode alike, deflate, heatshrink and MeatPack included, splits the print's length by the filament each tool pushed, and keeps the figure as an indication rather than a measurement. Each tool can be reset on its own after a nozzle change, and the printer's counter is not touched.
A dashboard card, Maintenance due, lists what is due now or due soon across the fleet, and the module publishes maintenance.task on the event bus whenever a task reaches due soon or due, ready for a webhook, MQTT, AMQP or Kafka sink.