Notifications

OctoApp will notify you about events in your print:

• Print started
• Print paused (3s delay)
• Print resumed
• Print completed
• Print cancelled
• Print error (printer emergency stop or firmware error)
• Printer "beep" (OctoPrint only, can be turned off in app settings)
• First layer completed (can be turned off in app settings)
• Third layer completed (can be turned off in app settings)
• Filament required ("paused" on Klipper)
• User interaction needed ("paused" on Klipper)
• Prusa MMU plugin input needed (OctoPrint only)

Notifications can be customized on the device by changing their sound and behvior in the operating system settings for OctoApp, both iOS and Android.

Custom notifications

Printer type	Supported
OctoPrint	✅
Klipper/Moonraker	✅
BambuLab	❌
Elegoo Centauri	❌

OctoApp also allows you to send arbitrary notifications during a print, e.g. when you want to observe a specific moment of the print. Custom notifications are limited to 10 per print. If the limit is exceeded you get a notification telling you so and subsequent notifications are no longer send until the print is ended.

To send a custom notification you can use the following command for both OctoPrint and Klipper:

OCTOAPP_NOTIFY MESSAGE=Hello World!

Please be mindful with special characters, while they should work they might cause issues with other tools working with the Gcode.

Slicers allow you to place custom Gcode into your print files, e.g.

• Orca Slicer allows you to right-click the layer selector slider in the "Preview" screen and then insert custom code.

• Prusa Slicer lets you right click the + icon next to the layer selector slider to insert custom code

• For any other slicer, you can always open the generated Gcode file and search for the layer (check the layer start comments of the slicer), manually insert the notification Gcode, and then save the file again

Note

The OCTOAPP_NOTIFY can't be called from a macro on Klipper, it must be part of the Gcode file printed (see below)

Caution

Due to a bug, the OctoPrint PrintTimeGenius plugin will count any command with a G in it as an arbitrary move command. This means that the above Gcode will slightly impact the print time estimation of the plugin, so don't place hundreds of these commands into your print (also note the limit of 10)

Custom notifications in Klipper macros

The OCTOAPP_NOTIFY command does not work in Klipper macros out of the box. The reason is that the plugin detects the command in printed files. You can use the alternate command OCTOAPP_NOTIFY_STATUS after adding the below macros to your setup. This command will work when placed in files and when called from macros.

Note

This requires the OctoApp Plugin 2.1.13 or newer

[gcode_macro _OCTOAPP_STATUS]
variable_notify_message: ""
gcode:

[gcode_macro OCTOAPP_NOTIFY_STATUS]
description: Send a notification with a custom message and CPU time
gcode:
    {% set message = params.MESSAGE|default("") %}
    {% set cpu_time = printer["system_stats"].cputime %}
    {% set final_message =  message ~ "~~~" ~ cpu_time %}
    
    SET_GCODE_VARIABLE MACRO=_OCTOAPP_STATUS VARIABLE=notify_message VALUE="'{ final_message }'"

After the above macros are added you can use this command to send notifications to the app! OCTOAPP_NOTIFY_STATUS MESSAGE=Hello World!