[GH-ISSUE #49] [Bug]: P1S does not seam to archive prints

BreizhHardware commented

2026-05-06 12:24:49 +02:00

Owner

Originally created by @mathse on GitHub (Jan 2, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/49

Originally assigned to: @maziggy on GitHub.

Bug Description

I saw that the functionality with P1S printers need to be testet. Luckely I have one.
Looks like there are some problems with it

Expected Behavior

When i am printing a plate via BambuStudio Bumbuddy recognize the print in the Printers dialog but the print does not get archived.
Quick Stats does not get updated.
Maintenance gets updated tough.

Steps to Reproduce

have a P1S
print from BambuStudio
wait for the print to finish

Printer Model

P1S

Bambuddy Version

v0.1.6b4

Printer Firmware Version

01.09.00.00

Installation Method

Docker

Operating System

Docker

Relevant Logs

log.txt

Screenshots

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

Originally created by @mathse on GitHub (Jan 2, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/49 Originally assigned to: @maziggy on GitHub. ### Bug Description I saw that the functionality with P1S printers need to be testet. Luckely I have one. Looks like there are some problems with it ### Expected Behavior When i am printing a plate via BambuStudio Bumbuddy recognize the print in the Printers dialog but the print does not get archived. Quick Stats does not get updated. Maintenance gets updated tough. ### Steps to Reproduce 0. have a P1S 1. print from BambuStudio 2. wait for the print to finish ### Printer Model P1S ### Bambuddy Version v0.1.6b4 ### Printer Firmware Version 01.09.00.00 ### Installation Method Docker ### Operating System Docker ### Relevant Logs [log.txt](https://github.com/user-attachments/files/24406708/log.txt) ### Screenshots <img width="569" height="480" alt="Image" src="https://github.com/user-attachments/assets/55c4edc2-52bd-4898-94cb-a61131184dc6" /> <img width="588" height="454" alt="Image" src="https://github.com/user-attachments/assets/47eb0074-0baa-4fd5-adda-2c35c740f824" /> ### 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

BreizhHardware

2026-05-06 12:24:49 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

2026-05-06 12:24:50 +02:00

Author

Owner

@maziggy commented on GitHub (Jan 2, 2026):

Thanks for pointing this out!

Please use branch 0.1.6b5, test again and send me the logs.

@maziggy commented on GitHub (Jan 2, 2026): Thanks for pointing this out! Please use branch 0.1.6b5, test again and send me the logs.

BreizhHardware commented

2026-05-06 12:24:50 +02:00

Author

Owner

@mathse commented on GitHub (Jan 3, 2026):

Hm, no luck.
But it looks more like a firewall problem on my side.
I cannot browse the files on the printer. Seams like port 2024, 2025 and 6000 need to be open between bambuddy and the printer.
Maybe this is worth mentioning in the documentation

@mathse commented on GitHub (Jan 3, 2026): Hm, no luck. But it looks more like a firewall problem on my side. I cannot browse the files on the printer. Seams like port 2024, 2025 and 6000 need to be open between bambuddy and the printer. Maybe this is worth mentioning in the documentation

BreizhHardware commented

2026-05-06 12:24:50 +02:00

Author

Owner

@maziggy commented on GitHub (Jan 3, 2026):

https://wiki.bambuddy.cool/getting-started/first-printer/?h=firewall#check-these-first

@maziggy commented on GitHub (Jan 3, 2026): https://wiki.bambuddy.cool/getting-started/first-printer/?h=firewall#check-these-first

BreizhHardware commented

2026-05-06 12:24:50 +02:00

Author

Owner

@mathse commented on GitHub (Jan 3, 2026):

8883 and 900 are open and accessible

@mathse commented on GitHub (Jan 3, 2026): 8883 and 900 are open and accessible

BreizhHardware commented

2026-05-06 12:24:50 +02:00

Author

Owner

@maziggy commented on GitHub (Jan 3, 2026):

Send the logs!

@maziggy commented on GitHub (Jan 3, 2026): Send the logs!

BreizhHardware commented

2026-05-06 12:24:50 +02:00

Author

Owner

@mathse commented on GitHub (Jan 3, 2026):

bambuddy.log
here you go

@mathse commented on GitHub (Jan 3, 2026): [bambuddy.log](https://github.com/user-attachments/files/24415781/bambuddy.log) here you go

BreizhHardware commented

2026-05-06 12:24:50 +02:00

Author

Owner

@maziggy commented on GitHub (Jan 3, 2026):

You printer is behaving weird....

The Problem:

Your P1S is stuck reporting gcode_state: FAILED continuously. Looking at the logs:

gcode_state: FAILED, gcode_file: , subtask_name: 1_plate_1

This state is being reported over and over - the printer never transitions to IDLE (when not printing), RUNNING (during a print), or FINISH (when complete). In the entire log, there are only 14 state updates total, and they're all FAILED.

Because Bambuddy never sees:

RUNNING → no print start detected → no archive created
FINISH → no completion detected → statistics don't update

Additional issues noticed:

Camera connection failing on port 6000: failed to connect to 10.83.40.39:6000
MQTT connection going stale periodically (no messages for 65-88 seconds)

What to try:

Clear the stuck state on the printer:
- On the printer's touchscreen, go to print history and clear/acknowledge any failed prints
- Or start a short test print and let it complete (or cancel it) to reset the state
Check network connectivity:
- Port 6000 (camera) appears blocked - ensure it's open from Bambuddy → printer
- The stale connections suggest possible network instability between Bambuddy and the printer
Restart both:
- Restart the P1S printer
- Restart Bambuddy after the printer is back online

After doing this, start a test print and check if Bambuddy now sees RUNNING state. You can verify by watching the printer status in the Bambuddy UI - it should show "Printing" with progress.

Please send the test logs again.

@maziggy commented on GitHub (Jan 3, 2026): You printer is behaving weird.... The Problem: Your P1S is stuck reporting gcode_state: FAILED continuously. Looking at the logs: gcode_state: FAILED, gcode_file: , subtask_name: 1_plate_1 This state is being reported over and over - the printer never transitions to IDLE (when not printing), RUNNING (during a print), or FINISH (when complete). In the entire log, there are only 14 state updates total, and they're all FAILED. Because Bambuddy never sees: - RUNNING → no print start detected → no archive created - FINISH → no completion detected → statistics don't update Additional issues noticed: - Camera connection failing on port 6000: failed to connect to 10.83.40.39:6000 - MQTT connection going stale periodically (no messages for 65-88 seconds) What to try: 1. Clear the stuck state on the printer: - On the printer's touchscreen, go to print history and clear/acknowledge any failed prints - Or start a short test print and let it complete (or cancel it) to reset the state 2. Check network connectivity: - Port 6000 (camera) appears blocked - ensure it's open from Bambuddy → printer - The stale connections suggest possible network instability between Bambuddy and the printer 3. Restart both: - Restart the P1S printer - Restart Bambuddy after the printer is back online After doing this, start a test print and check if Bambuddy now sees RUNNING state. You can verify by watching the printer status in the Bambuddy UI - it should show "Printing" with progress. Please send the test logs again.

BreizhHardware commented

2026-05-06 12:24:51 +02:00

Author

Owner

@mathse commented on GitHub (Jan 3, 2026):

the problem of the failed print is indeed a failed print ;-) its stuck 10km away at the moment, i simply forgot to mention ;-)

@mathse commented on GitHub (Jan 3, 2026): the problem of the failed print is indeed a failed print ;-) its stuck 10km away at the moment, i simply forgot to mention ;-)

BreizhHardware commented

2026-05-06 12:24:51 +02:00

Author

Owner

@Stooovie commented on GitHub (Jan 4, 2026):

Running in something similar after b5, succesful prints do not appear in archive and also the Success rate in Statistics is calculated wrongly:

I'd send logs if I knew where they are, this is my docker compose:

services:
  bambuddy:
    image: ghcr.io/maziggy/bambuddy:latest
    build: .
    # Usage:
    #   docker compose up -d           ^f^r pulls pre-built image
    #   docker compose up -d --build   ^f^r builds from source
    container_name: bambuddy
    network_mode: host  # Required for printer discovery
    volumes:
      - bambuddy_data:/app/data
      - bambuddy_logs:/app/logs
    environment:
      - TZ=Europe/Berlin  # Your timezone
    restart: unless-stopped

volumes:
  bambuddy_data:
  bambuddy_logs:

and .env

DEBUG=true

# Log level (only used when DEBUG=false)
# Options: DEBUG, INFO, WARNING, ERROR
LOG_LEVEL=INFO

# Enable file logging (logs written to logs/bambutrack.log)
LOG_TO_FILE=true

@Stooovie commented on GitHub (Jan 4, 2026): Running in something similar after b5, succesful prints do not appear in archive and also the Success rate in Statistics is calculated wrongly: ![Image](https://github.com/user-attachments/assets/3536ff76-9e60-49d3-bc86-c89855c0e961) I'd send logs if I knew where they are, this is my docker compose: ``` services: bambuddy: image: ghcr.io/maziggy/bambuddy:latest build: . # Usage: # docker compose up -d ^f^r pulls pre-built image # docker compose up -d --build ^f^r builds from source container_name: bambuddy network_mode: host # Required for printer discovery volumes: - bambuddy_data:/app/data - bambuddy_logs:/app/logs environment: - TZ=Europe/Berlin # Your timezone restart: unless-stopped volumes: bambuddy_data: bambuddy_logs: ``` and .env ``` DEBUG=true # Log level (only used when DEBUG=false) # Options: DEBUG, INFO, WARNING, ERROR LOG_LEVEL=INFO # Enable file logging (logs written to logs/bambutrack.log) LOG_TO_FILE=true ```

BreizhHardware commented

2026-05-06 12:24:51 +02:00

Author

Owner

@maziggy commented on GitHub (Jan 4, 2026):

Please first update to the latest version.

@maziggy commented on GitHub (Jan 4, 2026): Please first update to the latest version.

BreizhHardware commented

2026-05-06 12:24:51 +02:00

Author

Owner

@Stooovie commented on GitHub (Jan 4, 2026):

I did, b6 now, problem persists. Prints aren't added to the archive anymore. Network, firmware and Bambu Studio hasn't changed.

@Stooovie commented on GitHub (Jan 4, 2026): I did, b6 now, problem persists. Prints aren't added to the archive anymore. Network, firmware and Bambu Studio hasn't changed.

BreizhHardware commented

2026-05-06 12:24:51 +02:00

Author

Owner

@maziggy commented on GitHub (Jan 5, 2026):

Please enable debug logging (https://wiki.bambuddy.cool/getting-started/installation/?h=debug#development-settings). Then test and send me the complete logs. You can copy the logfile from Docker container to your local machine via

docker cp :/app/logs/bambuddy.log .

@maziggy commented on GitHub (Jan 5, 2026): Please enable debug logging (https://wiki.bambuddy.cool/getting-started/installation/?h=debug#development-settings). Then test and send me the complete logs. You can copy the logfile from Docker container to your local machine via docker cp <container>:/app/logs/bambuddy.log .

BreizhHardware commented

2026-05-06 12:24:51 +02:00

Author

Owner

@maziggy commented on GitHub (Jan 5, 2026):

If you use branch 0.1.6b7 you could use the new "export debug logs" function.

https://wiki.bambuddy.cool/features/system-info/#support-bundle

@maziggy commented on GitHub (Jan 5, 2026): If you use branch 0.1.6b7 you could use the new "export debug logs" function. https://wiki.bambuddy.cool/features/system-info/#support-bundle

BreizhHardware commented

2026-05-06 12:24:51 +02:00

Author

Owner

@mathse commented on GitHub (Jan 5, 2026):

turns out, that the camera port was blocked (firewall openend ->fixed)
the access to the files is still problematic. the docker host is able to contact port 990, the container does not
the container is in bridge mode

@mathse commented on GitHub (Jan 5, 2026): turns out, that the camera port was blocked (firewall openend ->fixed) the access to the files is still problematic. the docker host is able to contact port 990, the container does not the container is in bridge mode

BreizhHardware commented

2026-05-06 12:24:51 +02:00

Author

Owner

@maziggy commented on GitHub (Jan 5, 2026):

Without debug logs I cannot do anything.

@maziggy commented on GitHub (Jan 5, 2026): Without debug logs I cannot do anything.

BreizhHardware commented

2026-05-06 12:24:51 +02:00

Author

Owner

@mathse commented on GitHub (Jan 5, 2026):

bambuddy.txt

@mathse commented on GitHub (Jan 5, 2026): [bambuddy.txt](https://github.com/user-attachments/files/24432537/bambuddy.txt)

BreizhHardware commented

2026-05-06 12:24:51 +02:00

Author

Owner

@mathse commented on GitHub (Jan 5, 2026):

i was able to fix it by issuing a iptables -t nat -I PREROUTING 1 -s 172.23.0.2/32 -p tcp --dport 990 -j DNAT --to-destination printer-ip:990

@mathse commented on GitHub (Jan 5, 2026): i was able to fix it by issuing a ``` iptables -t nat -I PREROUTING 1 -s 172.23.0.2/32 -p tcp --dport 990 -j DNAT --to-destination printer-ip:990```

BreizhHardware commented

2026-05-06 12:24:52 +02:00

Author

Owner

@maziggy commented on GitHub (Jan 5, 2026):

Very good! Let me know if you need any help.

@maziggy commented on GitHub (Jan 5, 2026): Very good! Let me know if you need any help.

BreizhHardware referenced this issue

2026-05-06 12:32:18 +02:00

[GH-ISSUE #1019] [Bug Report] Unable to select correct spool to assign to AMS B Slot 2 on printer Vic H2C, eve #716

BreizhHardware referenced this issue

2026-05-06 12:33:51 +02:00