starred/bambuddy-maziggy-1

Fork 0

mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 08:25:54 +02:00

[GH-ISSUE #529] [Bug]: Vitual Printer queue mode: Getting a lot of HMS errors when starting a print #340

New issue

Closed

opened 2026-05-07 00:09:00 +02:00 by BreizhHardware · 10 comments

BreizhHardware commented

2026-05-07 00:09:00 +02:00

Owner

Originally created by @Dendrowen on GitHub (Feb 26, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/529

Originally assigned to: @maziggy on GitHub.

Bug Description

A lot of times when I start a print, I get an HMS error:

This happens more often on 'older' queue items. Don't know if it's related.
Removing the printfile and adding it to the queue again from within bambuddy 'fixes' the issue. So I assume it isn't the file itself that's the issue.

Expected Behavior

The error to not appear and start printing.

Steps to Reproduce

Slice file in bambu studio (or orcaslicer. I tried both)
Hit 'send'
Select the virtual printer in queue mode
Hit 'send' again
Wait for the print to be picked up (takes a minute. I assume due to the upload to the printer)
See the error arise.
'Stop' the print from within the queue (progress bar is full at that point)
Clear the HMS error
Re-add the print to the queue.
Print starts successfully.

Printer Model

P1S

Bambuddy Version

0.2.1 and 0.2.1b3

Printer Firmware Version

01.09.01.00

Installation Method

Manual (git clone)

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package

Screenshots

No response

Additional Context

No response

Checklist

I have searched existing issues to ensure this bug hasn't already been reported
I am using the latest version of Bambuddy
My printer is set to LAN Only mode
My printer has Developer Mode enabled

Originally created by @Dendrowen on GitHub (Feb 26, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/529 Originally assigned to: @maziggy on GitHub. ### Bug Description A lot of times when I start a print, I get an HMS error: <img width="821" height="456" alt="Image" src="https://github.com/user-attachments/assets/9d19ce5d-ce7d-4e3b-8bb4-21c2feb8ae67" /> This happens more often on 'older' queue items. Don't know if it's related. Removing the printfile and adding it to the queue again from within bambuddy 'fixes' the issue. So I assume it isn't the file itself that's the issue. ### Expected Behavior The error to not appear and start printing. ### Steps to Reproduce 1. Slice file in bambu studio (or orcaslicer. I tried both) 2. Hit 'send' 3. Select the virtual printer in queue mode 4. Hit 'send' again 5. Wait for the print to be picked up (takes a minute. I assume due to the upload to the printer) 6. See the error arise. 7. 'Stop' the print from within the queue (progress bar is full at that point) 8. Clear the HMS error 9. Re-add the print to the queue. 10. Print starts successfully. ### Printer Model P1S ### Bambuddy Version 0.2.1 and 0.2.1b3 ### Printer Firmware Version 01.09.01.00 ### Installation Method Manual (git clone) ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package ```shell ``` ### Screenshots _No response_ ### Additional Context _No response_ ### Checklist - [x] I have searched existing issues to ensure this bug hasn't already been reported - [x] I am using the latest version of Bambuddy - [x] My printer is set to LAN Only mode - [x] My printer has Developer Mode enabled

BreizhHardware

2026-05-07 00:09:00 +02:00

closed this issue
added the
wontfix
label

BreizhHardware commented

2026-05-07 00:09:00 +02:00

Author

Owner

@Dendrowen commented on GitHub (Feb 26, 2026):

bambuddy-support-20260226-081949.zip

Couldn't upload support package in the initial post.

@Dendrowen commented on GitHub (Feb 26, 2026): [bambuddy-support-20260226-081949.zip](https://github.com/user-attachments/files/25569655/bambuddy-support-20260226-081949.zip) Couldn't upload support package in the initial post.

BreizhHardware commented

2026-05-07 00:09:01 +02:00

Author

Owner

@Dendrowen commented on GitHub (Feb 26, 2026):

Might be related to #518. When retrieving the API data from api/v1/queue use_ams is set to true, but the ams_mapping is null. When re-adding it, ams_mapping is properly set.

{
  "id": 3,
  "printer_id": 1,
  "target_model": null,
  "target_location": null,
  "required_filament_types": null,
  "filament_overrides": null,
  "waiting_reason": null,
  "archive_id": 11,
  "library_file_id": null,
  "position": 1,
  "scheduled_time": null,
  "require_previous_success": false,
  "auto_off_after": false,
  "manual_start": false,
  "ams_mapping": null,
  "plate_id": null,
  "bed_levelling": true,
  "flow_cali": false,
  "vibration_cali": true,
  "layer_inspect": false,
  "timelapse": false,
  "use_ams": true,
  "status": "pending",
  "started_at": null,
  "completed_at": null,
  "error_message": null,
  "created_at": "2026-02-26T08:26:02Z",
  "archive_name": "TTRPG Starter Set - 20 Supportless Pack - 32mm - Plate 9",
  "archive_thumbnail": "archive/unassigned/20260226_082602_Starter Adventure Pack 0.2_plate_9.gcode/thumbnail.png",
  "library_file_name": null,
  "library_file_thumbnail": null,
  "printer_name": "P1S-001",
  "print_time_seconds": 7529,
  "filament_used_grams": 4.45,
  "filament_type": "PLA",
  "filament_color": "#CBC6B8",
  "layer_height": 0.06,
  "nozzle_diameter": 0.2,
  "sliced_for_model": "P1S",
  "created_by_id": null,
  "created_by_username": null
}

@Dendrowen commented on GitHub (Feb 26, 2026): Might be related to #518. When retrieving the API data from `api/v1/queue` use_ams is set to true, but the ams_mapping is null. When re-adding it, ams_mapping is properly set. ```json { "id": 3, "printer_id": 1, "target_model": null, "target_location": null, "required_filament_types": null, "filament_overrides": null, "waiting_reason": null, "archive_id": 11, "library_file_id": null, "position": 1, "scheduled_time": null, "require_previous_success": false, "auto_off_after": false, "manual_start": false, "ams_mapping": null, "plate_id": null, "bed_levelling": true, "flow_cali": false, "vibration_cali": true, "layer_inspect": false, "timelapse": false, "use_ams": true, "status": "pending", "started_at": null, "completed_at": null, "error_message": null, "created_at": "2026-02-26T08:26:02Z", "archive_name": "TTRPG Starter Set - 20 Supportless Pack - 32mm - Plate 9", "archive_thumbnail": "archive/unassigned/20260226_082602_Starter Adventure Pack 0.2_plate_9.gcode/thumbnail.png", "library_file_name": null, "library_file_thumbnail": null, "printer_name": "P1S-001", "print_time_seconds": 7529, "filament_used_grams": 4.45, "filament_type": "PLA", "filament_color": "#CBC6B8", "layer_height": 0.06, "nozzle_diameter": 0.2, "sliced_for_model": "P1S", "created_by_id": null, "created_by_username": null } ```

BreizhHardware commented

2026-05-07 00:09:01 +02:00

Author

Owner

@maziggy commented on GitHub (Feb 26, 2026):

VP was only missing plat_id. Fixed in branch 0.2.1. Please let me know how it goes.

@maziggy commented on GitHub (Feb 26, 2026): VP was only missing plat_id. Fixed in branch 0.2.1. Please let me know how it goes.

BreizhHardware commented

2026-05-07 00:09:01 +02:00

Author

Owner

@Dendrowen commented on GitHub (Feb 26, 2026):

Plate ID seems to be fixed. I have a print running for another 1.5h, will let you know after that.

@Dendrowen commented on GitHub (Feb 26, 2026): Plate ID seems to be fixed. I have a print running for another 1.5h, will let you know after that.

BreizhHardware commented

2026-05-07 00:09:01 +02:00

Author

Owner

@Dendrowen commented on GitHub (Feb 26, 2026):

Yes, the error disappeared, but it does select the wrong filament (first AMS slot as apposed to the correct color in the third slot)

@Dendrowen commented on GitHub (Feb 26, 2026): Yes, the error disappeared, but it does select the wrong filament (first AMS slot as apposed to the correct color in the third slot)

BreizhHardware commented

2026-05-07 00:09:01 +02:00

Author

Owner

@maziggy commented on GitHub (Feb 27, 2026):

Please try again with branch 0.2.1.

@maziggy commented on GitHub (Feb 27, 2026): Please try again with branch 0.2.1.

BreizhHardware commented

2026-05-07 00:09:01 +02:00

Author

Owner

@Dendrowen commented on GitHub (Feb 27, 2026):

I tested the new release and ams_mapping was still null in the data from the api. It gets fixed once I click edit and save in the queue.

@Dendrowen commented on GitHub (Feb 27, 2026): I tested the new release and ams_mapping was still null in the data from the api. It gets fixed once I click edit and save in the queue.

BreizhHardware commented

2026-05-07 00:09:02 +02:00

Author

Owner

@maziggy commented on GitHub (Feb 27, 2026):

Send me a new support package please. Debug logging should run during print queue/start.

@maziggy commented on GitHub (Feb 27, 2026): Send me a new support package please. Debug logging should run during print queue/start.

BreizhHardware commented

2026-05-07 00:09:02 +02:00

Author

Owner

@Dendrowen commented on GitHub (Feb 27, 2026):

bambuddy-support-20260227-131950.zip

@Dendrowen commented on GitHub (Feb 27, 2026): [bambuddy-support-20260227-131950.zip](https://github.com/user-attachments/files/25604957/bambuddy-support-20260227-131950.zip)

BreizhHardware commented

2026-05-07 00:09:02 +02:00

Author

Owner

@maziggy commented on GitHub (Feb 27, 2026):

Sorry, but there's something terrible wrong with your setup.

2026-02-23 21:49:15,751 ERROR [backend.app.services.virtual_printer.tcp_proxy] FTP proxy: cannot bind to port 990 (permission denied). Port 990 requires root or CAP_NET_BIND_SERVICE. Docker: add 'cap_add: [NET_BIND_SERVICE]' to docker-compose.yml. Native: use 'sudo setcap cap_net_bind_service=+ep $(which python3)' or redirect with iptables.

You are missing iptables rules.

2026-02-26 08:10:06,196 ERROR [backend.app.services.print_scheduler] Scheduler error: UPDATE statement on table 'print_queue' expected to update 1 row(s); 0 were matched.

Looks like the database is corrupt.

2026-02-23 21:22:11,034 WARNING [backend.app.services.virtual_printer.mqtt_server] MQTT auth failed for user 'bblp'

And last but not least: the virtual printer cannot work properly, because authentication failes due to a wrong password.

To be honest: completely delete your installation. Check your host for requirements (iptables, etc.) and do a clean new install.

@maziggy commented on GitHub (Feb 27, 2026): Sorry, but there's something terrible wrong with your setup. > 2026-02-23 21:49:15,751 ERROR [backend.app.services.virtual_printer.tcp_proxy] FTP proxy: cannot bind to port 990 (permission denied). Port 990 requires root or CAP_NET_BIND_SERVICE. Docker: add 'cap_add: [NET_BIND_SERVICE]' to docker-compose.yml. Native: use 'sudo setcap cap_net_bind_service=+ep $(which python3)' or redirect with iptables. You are missing iptables rules. > 2026-02-26 08:10:06,196 ERROR [backend.app.services.print_scheduler] Scheduler error: UPDATE statement on table 'print_queue' expected to update 1 row(s); 0 were matched. Looks like the database is corrupt. > 2026-02-23 21:22:11,034 WARNING [backend.app.services.virtual_printer.mqtt_server] MQTT auth failed for user 'bblp' And last but not least: the virtual printer cannot work properly, because authentication failes due to a wrong password. ----- To be honest: completely delete your installation. Check your host for requirements (iptables, etc.) and do a clean new install.