mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #332] [Bug]: Telegram notification shows raw ** instead of bold title formatting #209
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy#209
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Sllepper on GitHub (Feb 11, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/332
Originally assigned to: @maziggy on GitHub.
Bug Description
When receiving Telegram notifications from Bambuddy, the message title displays raw asterisks (**) instead of rendering bold text.
For example:
🔷 Print 75% Complete
🟣 Printer Error: Print/Task Error
The ** characters are visible in the message instead of formatting the title as bold.
This affects print progress notifications and printer error notifications.
It looks like Markdown formatting is either:
being wrapped twice (double * added somewhere), or
parse_mode is not enabled in Telegram send_message.
Expected Behavior
The title should render in bold without showing **.
Expected display in Telegram:
🔷 Print 75% Complete
🟣 Printer Error: Print/Task Error
No visible asterisk characters should appear.
Steps to Reproduce
Configure Telegram notifications.
Set title template like:
🔷 Print {progress}% Complete
or
🟣 Printer Error: {error_type}
Trigger a print progress or printer error event.
Observe that Telegram shows:
🔷 Print 75% Complete
instead of bold formatting.
Printer Model
Not printer-related
Bambuddy Version
v0.1.8.1
Printer Firmware Version
new
Installation Method
Manual (git clone)
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
Screenshots
Additional Context
Checklist
@maziggy commented on GitHub (Feb 11, 2026):
This is actually working as intended — Bambuddy automatically wraps the notification title in bold formatting when sending to Telegram. It looks like your custom title templates already include asterisks (🔷 Print {progress}% Complete), which causes the double-wrapping you're seeing.
To fix this, just remove the * from your title templates:
🔷 Print {progress}% Complete
🟣 Printer Error: {error_type}
Bambuddy will add the bold formatting for you automatically.
@Sllepper commented on GitHub (Feb 11, 2026):
if i remove * from title templates it will show like this
*🔷 Print {progress}% Complete*@Sllepper commented on GitHub (Feb 11, 2026):
@maziggy commented on GitHub (Feb 11, 2026):
Then it's perhaps the colored dot. Don't know. I'm using Telegram and don't have any issues.
@Sllepper commented on GitHub (Feb 11, 2026):
I did some additional testing and noticed a pattern.
If the notification body does NOT contain underscores (
_), the bold formatting works correctly and the title is displayed properly in Telegram.However, if the body contains underscores — for example:
then sometimes the notification appears with literal asterisks (
*Title*) instead of rendering bold formatting.It seems the issue is related to Markdown parsing being skipped or broken when underscores are present in the body.
You can see in the screenshots:
I'm not sure if this is caused by Markdown parsing behavior or conditional parse_mode logic in the code, but I consistently observe this behavior on my setup.
I'm using Telegram mobile and desktop, and I can reproduce it reliably.
I tried modifying the formatting logic but haven't found a clean solution yet.
Please let me know if you’re able to reproduce this or if there’s a recommended way to handle underscores safely.
@maziggy commented on GitHub (Feb 12, 2026):
Good catch! Fix in branch 0.2.0b.
If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!
@Sllepper commented on GitHub (Feb 12, 2026):
Thanks for the quick fix!
@maziggy commented on GitHub (Feb 12, 2026):
Not within the next days.