Notifications¶

Get notified about print events via WhatsApp, Telegram, Discord, Email, Home Assistant, and more.

Supported Providers¶

Adding a Provider¶

1. Go to Settings > Notifications
2. Click Add Provider
3. Select provider type
4. Enter configuration
5. Click Send Test to verify
6. Configure event triggers
7. Click Add

Provider Setup Guides¶

ntfy (Easiest)¶

Simple topic-based notifications - no account needed!

1. Choose a unique topic name (e.g., my-printer-xyz123)

2. Subscribe on your phone:

3. Install ntfy app (Android / iOS)

4. Subscribe to your topic

5. In Bambuddy, enter:

Per-event priority¶

ntfy supports a Priority header that controls how the receiving device escalates an alert (sound, vibration, do-not-disturb override, banner persistence). Bambuddy lets you map each enabled event to one of five levels:

After enabling the events you want, scroll to the ntfy Priority section in the Add / Edit Notification dialog. Each enabled event gets its own dropdown — events left at Default fall through to whatever the ntfy server is configured to send. Disabled events don't appear in the section.

Switching the provider type away from ntfy hides the section; the priorities are still saved if you switch back.

WhatsApp (CallMeBot)¶

Free WhatsApp notifications:

1. Add CallMeBot to contacts: +34 644 51 95 23

2. Send via WhatsApp: I allow callmebot to send me messages

3. You'll receive an API key

4. In Bambuddy, enter:

Discord¶

Via channel webhooks:

1. In Discord, go to channel settings
2. Navigate to Integrations > Webhooks
3. Click New Webhook
4. Customize name/avatar
5. Click Copy Webhook URL
6. In Bambuddy, paste the URL

Pushover¶

Professional push notification service:

1. Create account at pushover.net
2. Install Pushover app on your device
3. Create an Application in dashboard
4. In Bambuddy, enter:

Bark (iOS)¶

Open-source push notifications for iPhone/iPad via the Bark app — no account needed, self-hostable:

1. Install the Bark app from the App Store
2. Copy your device key from the app (shown on the main screen)
3. In Bambuddy, add a provider and select Bark:

Telegram¶

Via Telegram Bot:

1. Message @BotFather
2. Send /newbot and follow prompts
3. Save the Bot Token
4. Message @userinfobot to get your Chat ID
5. In Bambuddy, enter:

Forum Topics¶

If the target group has Topics enabled, Bambuddy posts to the General topic unless you tell it otherwise. Set Forum Topic ID to route the notifications into one specific topic instead — useful for giving each printer its own topic inside a single group rather than running a separate chat per printer.

To find the ID, open the topic in Telegram and copy its link. The last number is the topic ID:

https://t.me/c/1234567890/25
                         ^^ Forum Topic ID

The field takes a plain number and may be left empty. Two things to watch for:

• The bot needs permission to post in the group, and Topics must actually be enabled on it. Bambuddy passes the ID through unchanged and reports back whatever Telegram answers, so a wrong ID surfaces as a Telegram error.
• Deleting and recreating a topic gives it a new ID, so the notifications will need repointing.

Use Test in the provider dialog to confirm the message lands where you expect before saving.

Email (SMTP)¶

Send via email:

Gmail Setup¶

1. Enable 2-Factor Authentication
2. Generate an App Password
3. Use: smtp.gmail.com, Port 587, STARTTLS

Home Assistant¶

Zero-config notifications if Home Assistant is already connected:

1. Ensure HA is configured in Settings > Network > Home Assistant
2. Add a notification provider and select Home Assistant
3. No additional fields needed — click Send Test to verify

Notifications appear as persistent notifications in your HA dashboard.

Custom data fields. When targeting a notify service, the optional Data (JSON) field is forwarded as the service call's nested data object — the same place HA automations put mobile push options:

{"priority": "high", "ttl": 0, "channel": "3D Printing", "group": "printers"}

ttl: 0 + priority: high make Android pushes arrive immediately; channel creates a dedicated Android notification channel so you can give printer alerts their own sound. See the HA Companion notification docs for all supported keys. Leave the field empty when using the default persistent notification — it doesn't accept custom data.

The field is passed to Home Assistant exactly as you write it, so anything the notify service accepts works here — including nested objects and lists, not just the flat values above. Action buttons are the common case:

{
  "ttl": 0,
  "priority": "high",
  "group": "3D Printer",
  "actions": [
    {"action": "SNOOZE_PRINT_FINISHED", "title": "Snooze 20 min"},
    {"action": "BED_COOL_NOTIFY_ON", "title": "Notify on Bed Cool"}
  ]
}

Two things decide whether those buttons appear and do anything, and neither is set here:

• Pressing a button does nothing until Home Assistant listens for it. The Companion app fires a mobile_app_notification_action event carrying your action string; you need an HA automation triggered on that event to act on it.
• On iOS, a bare actions list is ignored. iOS renders buttons only for a notification category you have registered in the Companion app, so send "category": "your_category" instead. Android renders the list directly.

Webhook (Custom)¶

For custom integrations:

All webhook payloads use a standardized format with title, message, timestamp, source, an event field identifying the event type, and all event-specific variables as structured fields. This makes it easy for automation tools (n8n, Node-RED, Home Assistant, etc.) to parse event data without extracting information from the message text.

Print complete example:

{
  "title": "Print Complete",
  "message": "Workshop X1C: benchy.3mf completed in 2h 15m",
  "timestamp": "2026-04-02T14:30:00.123456",
  "source": "Bambuddy",
  "event": "print_complete",
  "printer": "Workshop X1C",
  "filename": "benchy.3mf",
  "duration": "2h 15m",
  "filament_grams": "15.2",
  "filament_details": "AMS-A T1 PLA: 15.2g"
}

Failed/stopped prints include additional fields:

{
  "title": "Print Failed",
  "message": "Workshop X1C: benchy.3mf failed at 50%",
  "timestamp": "2026-04-02T15:15:00.123456",
  "source": "Bambuddy",
  "event": "print_failed",
  "printer": "Workshop X1C",
  "filename": "benchy.3mf",
  "duration": "0h 45m",
  "filament_grams": "7.6",
  "filament_details": "PLA: 7.6g",
  "progress": "50",
  "reason": "Filament runout"
}

Simpler events include fewer fields — only what's relevant:

{
  "title": "Printer Offline",
  "message": "Workshop X1C is offline",
  "timestamp": "2026-04-02T14:30:00.123456",
  "source": "Bambuddy",
  "event": "printer_offline",
  "printer": "Workshop X1C"
}

When a camera snapshot is available (e.g. First Layer Complete, Print Started, Print Completed), the payload includes a base64-encoded JPEG image in the image field:

{
  "title": "First Layer Complete",
  "message": "Workshop X1C: benchy.3mf — Layer 1/200 done",
  "timestamp": "2026-04-02T14:30:00.123456",
  "source": "Bambuddy",
  "event": "first_layer_complete",
  "printer": "Workshop X1C",
  "filename": "benchy.3mf",
  "total_layers": "200",
  "image": "/9j/4AAQSkZJRg..."
}

Event Triggers¶

Print Events¶

Printer Events¶

AMS Events¶

Print Queue Events¶

Enable/disable each event per provider.

Quiet Hours¶

Suppress notifications during sleep:

1. Enable Quiet Hours toggle
2. Set Start Time (e.g., 22:00)
3. Set End Time (e.g., 07:00)

Notifications during quiet hours are silently skipped.

Per-Printer Filtering¶

Limit notifications to specific printers:

1. Open provider settings
2. Find Printers section
3. Select specific printers or "All"

Only events from selected printers trigger notifications.

Daily Digest¶

Batch notifications into a summary:

1. Enable Daily Digest toggle
2. Set Digest Time (e.g., 08:00)

How It Works¶

• Events are collected (not sent immediately)
• At digest time, one summary is sent
• Includes counts and details

Example Digest¶

Daily Print Summary (Dec 14)

✅ 3 prints completed
❌ 1 print failed
⏱️ Total time: 8h 45m
🧵 Filament used: 245g

Details:
- Benchy (2h 15m) ✅
- Phone Stand (45m) ✅
- Cable Clip (15m) ✅
- Prototype v3 (3h 30m) ❌

Message Templates¶

Customize notification messages:

Accessing Templates¶

1. Go to Settings > Notifications
2. Click Templates tab
3. Select event type to edit

Variables¶

Insert dynamic content with {variable}:

Print Events:

• {printer} - Printer name
• {filename} - Print filename
• {duration} - Print time
• {filament_grams} - Total filament used in grams (scaled by progress for failed/stopped prints)
• {filament_details} - Per-filament breakdown (e.g., "PLA: 15.2g" or "PLA: 10.0g | PETG: 5.0g")
• {estimated_time} - Estimated duration (e.g., "1h 23m")
• {eta} - Wall-clock completion time (e.g., "15:53" or "3:53 PM"), respects your time format setting
• {progress} - Completion percentage (available for failed/stopped prints)
• {reason} - Failure reason
• {finish_photo_url} - Camera snapshot URL (print_complete, print_failed, print_stopped). Email special-case (#1792): if your Email template references {finish_photo_url} in the body, the rendered URL also triggers an inline embed — the HTML part replaces the URL with the snapshot rendered inline at exactly that position, while the plain-text part keeps the URL as a clickable link. Place the variable WHERE you want the image to appear. If the template doesn't reference it, the email stays text-only — no surprise attachment.

Printer Events:

• {printer} - Printer name
• {error_type} - HMS error type
• {error_detail} - Error description

First Layer Complete:

• {printer} - Printer name
• {filename} - Print filename
• {total_layers} - Total layer count

Bed Cooled:

• {printer} - Printer name
• {bed_temp} - Current bed temperature
• {threshold} - Configured threshold
• {filename} - Print filename

Sensor Alert:

• {printer} - Printer name
• {sensor} - Sensor display name
• {state} - State that triggered the alert (open, 41.2 °C)

Missing Spool Assignment:

• {printer} - Printer name
• {missing_slots} - Comma-separated slot labels (e.g., "A1, A3")
• {missing_slot_details} - Per-slot breakdown with expected profile (e.g., "- A1: PLA Basic")

AMS Events:

• {printer} - Printer name
• {slot} - AMS slot
• {remaining_percent} - Filament left
• {humidity} - Humidity level
• {ams_label} - Which unit (e.g. "AMS-A")
• {threshold} - The configured threshold the reading is measured against
• {cycles} - Drying cycles that ended above the threshold (Auto-Drying Suspended only)

Common:

• {timestamp} - Event time
• {app_name} - "Bambuddy"

Reset to Default¶

Click reset to restore original template.

Finish Photos¶

A camera snapshot can reach your notification either as a link you click or as an image attached to the message itself. Which one you get depends on the channel, not on a setting — see the table below.

Both paths are gated on Settings > General > Archive Settings > Capture finish photo. With that off, no snapshot is taken and nothing is attached or linked.

Attached image¶

ntfy, Pushover, Telegram and Discord receive the photo as a real attachment whenever one was captured — you do not need {finish_photo_url} in the template for this, and no External URL is required, because the image bytes are uploaded with the message.

Attachments are capped at 2.5 MB. A larger snapshot is skipped and the message is sent as text — the reason is written to the log.

Snapshots are not limited to completed prints: Print Started, Print Progress, First Layer Complete and printer-error notifications capture a live frame at the moment they fire.

Linked URL¶

{finish_photo_url} is available on the print_complete, print_failed and print_stopped events, and needs a reachable server address:

1. Go to Settings > Network
2. Set External URL to your Bambuddy server's address (e.g., http://192.168.1.100:8000)
3. Edit your template to include {finish_photo_url}

Example template:

Print completed!
Printer: {printer}
File: {filename}
Filament: {filament_details}
Photo: {finish_photo_url}

For Email, that same variable also switches the message to an inline embed — the photo is rendered at exactly the position you placed the variable. See the {finish_photo_url} entry under Variables for the details.

Testing¶

Always test before relying on notifications:

1. Configure provider
2. Click Send Test
3. Verify you receive the message
4. Check message formatting

Quick Disable¶

Quickly disable all notifications:

1. Find the Quick Disable button
2. Click to toggle all notifications off
3. Click again to re-enable

Useful during maintenance or troubleshooting.

Tips¶

:material-account-bell: Per-User Email Notifications¶

When Advanced Authentication is enabled, individual users can receive email notifications for their own print jobs. This is separate from the provider-based notification system above — it sends emails directly to the user who submitted the print.

Requirements¶

• Advanced Authentication must be enabled
• SMTP must be configured
• "User Notifications" must be enabled in Settings → Notifications
• User must have an email address on their account
• User must have the notifications:user_email permission (Administrators and Operators by default)

Supported Events¶

Setup¶

1. Enable User Notifications in Settings → Notifications
2. Click Notifications in the sidebar
3. Toggle each event type on or off
4. Click Save

See Authentication → Per-User Email Notifications for full details.