[GH-ISSUE #167 ] [Bug]: Printer MQTT cant connect #106

Author

Owner

@cadtoolbox commented on GitHub (Jan 28, 2026):

Based on my experience, the firmware not being more recent is definitely the cause of this issue. I'm not sure of your network situation but without updated firmware, connecting outside of the current subnet is impossible.

@cadtoolbox commented on GitHub (Jan 28, 2026): Based on my experience, the firmware not being more recent is definitely the cause of this issue. I'm not sure of your network situation but without updated firmware, connecting outside of the current subnet is impossible.

BreizhHardware commented

Author

Owner

@LucHeart commented on GitHub (Jan 28, 2026):

its in the same subnet, and the printer is reachable, guess ill update afterall

@LucHeart commented on GitHub (Jan 28, 2026): its in the same subnet, and the printer is reachable, guess ill update afterall

BreizhHardware commented

Author

Owner

@cadtoolbox commented on GitHub (Jan 28, 2026):

@LucHeart The more recent firmware allows for offline updates using the SD card. The trick is getting it updated to the version that allows this if you're not on WAN to start with. I just had to do this recently by turning off LAN mode only and Wi-Fi on temporarily using my phone as a hotspot. Now that it's updated through, it's much easier in LAN mode using the SD card method.

@cadtoolbox commented on GitHub (Jan 28, 2026): @LucHeart The more recent firmware allows for offline updates using the SD card. The trick is getting it updated to the version that allows this if you're not on WAN to start with. I just had to do this recently by turning off LAN mode only and Wi-Fi on temporarily using my phone as a hotspot. Now that it's updated through, it's much easier in LAN mode using the SD card method.

BreizhHardware commented

Author

Owner

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

To debug the issue please attach a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging

@maziggy commented on GitHub (Jan 28, 2026): To debug the issue please attach a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging

BreizhHardware commented

Author

Owner

@LucHeart commented on GitHub (Jan 28, 2026):

To debug the issue please attach a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging

there is already one attached with relevant logs inside...

@LucHeart commented on GitHub (Jan 28, 2026): > To debug the issue please attach a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging there is already one attached with relevant logs inside...

BreizhHardware commented

Author

Owner

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

Oh...sorry. Shouldn't do that much things at the same time. Will check.

@maziggy commented on GitHub (Jan 28, 2026): Oh...sorry. Shouldn't do that much things at the same time. Will check.

BreizhHardware commented

Author

Owner

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

I also suspect the old firmware. MQTT connection is using SSL. Python's ssl.create_default_context() disables TLS 1.0 and TLS 1.1 by default for security reasons.

I'm sorry.

@maziggy commented on GitHub (Jan 28, 2026): I also suspect the old firmware. MQTT connection is using SSL. Python's ssl.create_default_context() disables TLS 1.0 and TLS 1.1 by default for security reasons. I'm sorry.

BreizhHardware commented

Author

Owner

@LucHeart commented on GitHub (Jan 28, 2026):

I will update and report back if that worked.

@LucHeart commented on GitHub (Jan 28, 2026): I will update and report back if that worked.

BreizhHardware commented

Author

Owner

@LucHeart commented on GitHub (Jan 28, 2026):

That did not fix it, same exact errors.

@LucHeart commented on GitHub (Jan 28, 2026): That did not fix it, same exact errors.

BreizhHardware commented

Author

Owner

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

There must be something wrong with your environment, there are already a lot of P1S users. Also the logs don't show any errors.

LAN mode is activated?
Developer mode is enabled?
Docker was started via Bambuddy's docker-compose.yml?
Can you ping the printer from the Docker container?

@maziggy commented on GitHub (Jan 28, 2026): There must be something wrong with your environment, there are already a lot of P1S users. Also the logs don't show any errors. - LAN mode is activated? - Developer mode is enabled? - Docker was started via Bambuddy's docker-compose.yml? - Can you ping the printer from the Docker container?

BreizhHardware commented

Author

Owner

@LucHeart commented on GitHub (Jan 28, 2026):

Yes
Yes
Yes
Yes

I can even open a mqtt connection to the printer with a script...

@LucHeart commented on GitHub (Jan 28, 2026): Yes Yes Yes Yes I can even open a mqtt connection to the printer with a script...

BreizhHardware commented

Author

Owner

@LucHeart commented on GitHub (Jan 28, 2026):

this is my current docker compose, printer is in the same network, all ports are open

services:
  bambuddy:
    image: ghcr.io/maziggy/bambuddy:latest
    container_name: bambuddy
    network_mode: host
    volumes:
      - ./data:/app/data
      - ./logs:/app/logs
      #
      # Share virtual printer certs with native installation
      # This ensures the slicer only needs to trust one CA certificate.
      - ./virtual_printer:/app/data/virtual_printer
    environment:
      - TZ=Europe/Berlin
      - PORT=8000
    restart: unless-stopped

i got curious and checked via a program if its really reachable from this vm, and yes it is. This outputs a json with various info about the printer, so the connection works.

use bambulab_mqtt::BambulabClient;
use bambulab_mqtt::request_command::*;
use std::env;

fn main() {
    let args: Vec<String> = env::args().collect();
    let host = args
        .get(1)
        .expect("Please provide a host as the first argument.");
    let password = args
        .get(2)
        .expect("Please provide a password as the second argument.");
    let serial = args
        .get(3)
        .expect("Please provide a serial as the third argument.");
    println!("Host: {}", host);
    println!("Password: {}", password);
    println!("Serial: {}", serial);

    let mut client =
        BambulabClient::new(host.to_string(), password.to_string(), serial.to_string());

    let get_version = RequestCommand::Info(Info::GetVersion(GetVersion::new()));
    let res = client.request(&get_version);
    match res {
        Ok(payload) => {
            println!("Payload: {}", payload);
        }
        Err(e) => {
            println!("Error: {}", e);
        }
    }
}

@LucHeart commented on GitHub (Jan 28, 2026): this is my current docker compose, printer is in the same network, all ports are open ``` services: bambuddy: image: ghcr.io/maziggy/bambuddy:latest container_name: bambuddy network_mode: host volumes: - ./data:/app/data - ./logs:/app/logs # # Share virtual printer certs with native installation # This ensures the slicer only needs to trust one CA certificate. - ./virtual_printer:/app/data/virtual_printer environment: - TZ=Europe/Berlin - PORT=8000 restart: unless-stopped ``` i got curious and checked via a program if its really reachable from this vm, and yes it is. This outputs a json with various info about the printer, so the connection works. ```rust use bambulab_mqtt::BambulabClient; use bambulab_mqtt::request_command::*; use std::env; fn main() { let args: Vec<String> = env::args().collect(); let host = args .get(1) .expect("Please provide a host as the first argument."); let password = args .get(2) .expect("Please provide a password as the second argument."); let serial = args .get(3) .expect("Please provide a serial as the third argument."); println!("Host: {}", host); println!("Password: {}", password); println!("Serial: {}", serial); let mut client = BambulabClient::new(host.to_string(), password.to_string(), serial.to_string()); let get_version = RequestCommand::Info(Info::GetVersion(GetVersion::new())); let res = client.request(&get_version); match res { Ok(payload) => { println!("Payload: {}", payload); } Err(e) => { println!("Error: {}", e); } } } ```

BreizhHardware commented

Author

Owner

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

So you ran the script in Bambuddy's Docker container?

Very curious.

Can you run it without Docker for a short test?

@maziggy commented on GitHub (Jan 28, 2026): So you ran the script in Bambuddy's Docker container? Very curious. Can you run it without Docker for a short test?

BreizhHardware commented

Author

Owner

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

And I would suggest to use branch 0.1.6-final.

@maziggy commented on GitHub (Jan 28, 2026): And I would suggest to use branch 0.1.6-final.

BreizhHardware commented

Author

Owner

@LucHeart commented on GitHub (Jan 28, 2026):

i'll try that

@LucHeart commented on GitHub (Jan 28, 2026): i'll try that

BreizhHardware commented

Author

Owner

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

Does it work?

@maziggy commented on GitHub (Jan 29, 2026): Does it work?

BreizhHardware commented

Author

Owner

@LucHeart commented on GitHub (Jan 29, 2026):

Soo i cloned main, set it up locally, works.
Funny enough, I delete the printer on my docker hosted one, re-add it, and it works.
Not sure what is going on here, couldnt have been the access code since i reapplied that one anyways after firmware updating. Maybe that didnt save? Or it was broken in some other way, it works now. Thanks for you help regardless, even though its very unsatisfying for the issue to just vanish after readding the printer.

@LucHeart commented on GitHub (Jan 29, 2026): Soo i cloned main, set it up locally, works. Funny enough, I delete the printer on my docker hosted one, re-add it, and it works. Not sure what is going on here, couldnt have been the access code since i reapplied that one anyways after firmware updating. Maybe that didnt save? Or it was broken in some other way, it works now. Thanks for you help regardless, even though its very unsatisfying for the issue to just vanish after readding the printer.

BreizhHardware commented