mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #1104] [Bug Report] When sending a print from archives that was previously sent to a different print #787
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#787
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 @maziggy on GitHub (Apr 23, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1104
Originally assigned to: @maziggy on GitHub.
When sending a print from archives that was previously sent to a different printer (same model, P1S) Bambu Studio gives a MQTT error and says "Please try updating Bambu Studio and then try again" (MQTT Command Verification Failed). The print file can be found on the printers device files, but no action is taken after it is sent.
Reporter Contact
Email: grussell@itape.com
System Information
Logs (sanitized): bambuddy.log
Submitted via BamBuddy Bug Report
@maziggy commented on GitHub (Apr 23, 2026):
Please upload a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging
@jrothsch-IPG commented on GitHub (Apr 23, 2026):
bambuddy-support-20260423-133406.zip
@jrothsch-IPG commented on GitHub (Apr 23, 2026):
It looks like this may impact any attempt to print from the archive, not only when the file was originally for another machine. On the screen of the P1S, we see "HMS_0500-0500-0001-0007", which matches the "MQTT Command Verification Failed" error we mentioned ealier.
@maziggy commented on GitHub (Apr 23, 2026):
Did you restart your printers after enabling developer mode? Who knows.... The error message usually means, that the dev mode is not enabled on printer.
@jrothsch-IPG commented on GitHub (Apr 23, 2026):
Good call! Looks like it was our bad. Various people were setting up these printers and it looks like some forgot about developer mode. Made sure this was enabled and restarted them and now it seems to be running fine!
@maziggy commented on GitHub (Apr 23, 2026):
If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!