mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #583] [Bug]: Notification for Error 0300_0002 #380
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
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-maziggy-1#380
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 @FirstS0ul on GitHub (Mar 3, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/583
Originally assigned to: @maziggy on GitHub.
Bug Description
Hi,
Even with the latest 0.2.2b1 i get this anoying notifcations.
I know it should fixed in that Version, but Not for me.
My fix: Turn off error Notification, Bad idea 🤣
Restarted Bambuddy Server and Printer.
Expected Behavior
No false positv errors
Steps to Reproduce
Start print, setup notification, wait
Printer Model
P2S
Bambuddy Version
0.2.2b1
Printer Firmware Version
Latest
Installation Method
Manual (git clone)
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
Screenshots
bambuddy-support-20260303-193237.zip
Additional Context
Sorry Logs in Screenshots.
Checklist
@maziggy commented on GitHub (Mar 4, 2026):
Sorry, but this is finally fixed now in branch 0.2.2b1.
If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!
@FirstS0ul commented on GitHub (Mar 4, 2026):
Sorry. doenst work. same behaviour.
@maziggy commented on GitHub (Mar 4, 2026):
Are you sure you're running the latest code? Plese send me a new support package.
@FirstS0ul commented on GitHub (Mar 4, 2026):
Sure.
my update command:
cd /opt/bambuddy && git checkout 0.2.2b1 && git pull && source venv/bin/activate && pip install -r requirements.txt && cd frontend && npm ci && npm run build && sudo systemctl restart bambuddyand here ist the package.
bambuddy-support-20260304-110225.zip
@maziggy commented on GitHub (Mar 4, 2026):
There seems to be something wrong with your installation. The complete log is full of warning/error/failed messages for nearly any functions that are triggered. Furthermore your logs are showing errors, which are already fixed definitely.
To be honest: I think the easiest way to get this sorted out, is a complete clean reinstall.
@FirstS0ul commented on GitHub (Mar 4, 2026):
i thought of it. i will try. stay tuned.
@FirstS0ul commented on GitHub (Mar 4, 2026):
Deleted everything.
restarted server.
run
curl -fsSL https://raw.githubusercontent.com/maziggy/bambuddy/main/install/install.sh -o install.sh && chmod +x install.sh && ./install.shDefault settings.
at the end didnt start bambuddy.
run command
cd /opt/bambuddy && git checkout 0.2.2b1 && git pull && source venv/bin/activate && pip install -r requirements.txt && cd frontend && npm ci && npm run build && sudo systemctl restart bambuddystarted bambuddy.
restored my backup from zip file
restarted.
and... first notification was the error.
bambuddy-support-20260304-115734.zip
@maziggy commented on GitHub (Mar 4, 2026):
Don't restore your database for testing, it may be corrupted!
@FirstS0ul commented on GitHub (Mar 4, 2026):
ok.
Deleted everything.
restarted server.
run curl -fsSL https://raw.githubusercontent.com/maziggy/bambuddy/main/install/install.sh -o install.sh && chmod +x install.sh && ./install.shDefault settings.
at the end didnt start bambuddy.
run command
cd /opt/bambuddy && git checkout 0.2.2b1 && git pull && source venv/bin/activate && pip install -r requirements.txt && cd frontend && npm ci && npm run build && sudo systemctl restart bambuddystarted bambuddy.
added printer
configured notifications. nothing else.
after 2 minutes. the same problem.
event settings:
bambuddy-support-20260304-124251.zip
@maziggy commented on GitHub (Mar 4, 2026):
That means, that you've used an old install script, which may have changed in the meantime. If you want to do a clean install of the latest beta version, you need to install manually or use Docker by building the image locally.
@FirstS0ul commented on GitHub (Mar 4, 2026):
right, but i changed the git and installed the latest beta...
do you have a short tutorial for an manual installation?
@maziggy commented on GitHub (Mar 4, 2026):
https://wiki.bambuddy.cool/getting-started/installation/#manual-install
@FirstS0ul commented on GitHub (Mar 4, 2026):
Did it with git clone -b 0.2.2b1
On change. Same error.
I will Try tonight with a clean server
@maziggy commented on GitHub (Mar 4, 2026):
Yes, but you used an old install script.
@FirstS0ul commented on GitHub (Mar 4, 2026):
I know… and my comment was with the complete manual install.
@FirstS0ul commented on GitHub (Mar 4, 2026):
Okay. i have an clean manual install with 0.2.2b1 and its better BUT i think the error comes with the FIRST message, here print started, and with the LAST message, here print completed.
i have an log for starting the print.
bambuddy-support-20260304-205758.zip
@FirstS0ul commented on GitHub (Mar 5, 2026):
Found it!
Its Not a Bug, Its a Feature 🤣
I have the external chamber Fan and there is an sucking airfilter conected. Very interesting.