Articles on: Managing your printers

Printer notifications on Creality, Anycubic, and other printers

Printer notifications on Creality, Anycubic, and other printers


Printer notifications - the errors and alerts your printer reports about its own health - are not just for Bambu Lab. Any printer connected to SimplyPrint can surface the device errors and status messages it raises, so you can see them across your fleet and act on them.


This guide covers what you get on Creality, Anycubic, and other connected printers today, how SimplyPrint receives those notifications, and how the picture is growing.


Notifications work for every connected printer

The way SimplyPrint receives printer notifications is brand-agnostic. Whatever connection your printer uses - the SimplyPrint Client, a brand integration like Creality or Anycubic, or a firmware plugin - the error and status events it reports stream up to SimplyPrint in real time and are recorded against that printer.


So on a connected Creality or Anycubic printer you get the same panel experience described in the printer notifications overview, to the extent the integration reports each event:


  • A notification bell per printer with a red badge counting unresolved alerts.
  • A dropdown listing each event, grouped by day, with a resolve button.
  • A red error banner on the printer's control panel and grid card when the printer reports a top-severity error, with a Dismiss button.
  • Automatic resolution when the printer reports the issue is fixed, and auto-cleanup of anything left unresolved for more than 7 days.


Each notification is tagged with the connection it came from, so SimplyPrint interprets the message correctly and knows which brand it belongs to. What each brand actually reports varies by integration - some surface rich, coded errors, while others report only a handful of status messages.


What "device errors" look like

Different brands report different things. A printer might raise a thermal warning, a filament-runout alert, a homing or leveling fault, a fan-speed warning, or a generic error with a code. SimplyPrint stores each with a severity (info, warning, or error), a title, and a message, and surfaces it the same way regardless of brand. Errors can also tell SimplyPrint that they paused or cancelled the print, or blocked AutoPrint from starting the next job, so you understand why a job stopped.


You do not configure anything to receive these. As long as the printer is connected and reporting, the notifications appear.


Mapping to maintenance: Bambu-first, growing

There is one part that does differ by brand today: turning a reported code into an automatic maintenance task.


SimplyPrint can match specific printer-reported codes to maintenance task templates, so a code becomes a maintenance trigger. That built-in code-to-task mapping covers Bambu Lab's HMS today. Mapping for Creality, Anycubic, and other brands is on the roadmap and will be added over time as their device-error codes are mapped.


Capability

Bambu Lab

Creality

Anycubic

Other connected printers

Notifications shown on the bell

✓

Where reported

Where reported

Where reported

Error banner on the control panel

✓

Where reported

Where reported

Where reported

Built-in code-to-maintenance mapping

✓

Not yet

Not yet

Not yet


The bell and banner display whatever notifications an integration reports, so coverage depends on how much each brand surfaces. Support varies by integration.


The maintenance system, including notification-based triggers, is part of the Print Farm, School, and Enterprise plans. Receiving and viewing the notifications themselves is not plan-gated.


What to do today on non-Bambu printers

Even before a brand's codes are mapped for automatic maintenance, the notifications are useful:


  • Watch the bell and banner to catch errors as they happen across the fleet, from one screen.
  • Resolve and clear alerts you have handled so each printer's bell reflects what still needs attention.


As your printer raises a recurring error you want to act on automatically, that condition is a candidate for a maintenance trigger as brand coverage expands. The roster of brands whose codes drive maintenance is growing, so it is worth revisiting your maintenance task templates over time.




Updated on: 26/06/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!