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 #171] [Bug]: X1C Status Doesn't Sync #109

New issue

Closed

opened 2026-05-07 00:06:19 +02:00 by BreizhHardware · 3 comments

BreizhHardware commented

2026-05-07 00:06:19 +02:00

Owner

Originally created by @stubbers on GitHub (Jan 29, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/171

Originally assigned to: @maziggy on GitHub.

Bug Description

X1C Successfully shows as 'Connected' but status is unknown. MQTT debug just shows nothing. I took a packet capture and can see the MQTT connection establish fine but no meaningful data is excahnged

Expected Behavior

Status correctly shown

Steps to Reproduce

1 - Connect X1C Printer
2 - Begin printing something
3 - Notice the status never changes from 'unknown'

Printer Model

X1 Carbon

Bambuddy Version

v0.1.6 (Final Branch)

Printer Firmware Version

01.11.02.00

Installation Method

Manual (git clone)

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package

See support package below

Screenshots

Additional Context

bambuddy-support-20260129-024547.zip

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 @stubbers on GitHub (Jan 29, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/171 Originally assigned to: @maziggy on GitHub. ### Bug Description X1C Successfully shows as 'Connected' but status is unknown. MQTT debug just shows nothing. I took a packet capture and can see the MQTT connection establish fine but no meaningful data is excahnged ### Expected Behavior Status correctly shown ### Steps to Reproduce 1 - Connect X1C Printer 2 - Begin printing something 3 - Notice the status never changes from 'unknown' ### Printer Model X1 Carbon ### Bambuddy Version v0.1.6 (Final Branch) ### Printer Firmware Version 01.11.02.00 ### Installation Method Manual (git clone) ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package ```shell See support package below ``` ### Screenshots <img width="1288" height="745" alt="Image" src="https://github.com/user-attachments/assets/b22623ae-0ff0-4d1a-81da-ad05b3d64089" /> ### Additional Context [bambuddy-support-20260129-024547.zip](https://github.com/user-attachments/files/24926122/bambuddy-support-20260129-024547.zip) ### 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-07 00:06:19 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

2026-05-07 00:06:19 +02:00

Author

Owner

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

@maziggy - Similar to #155

In my case I figured this out by throwing it all at Claude to sanity to check me. It pointed out that the printer serial had a minor typo in it. Maybe if the connection establishes but the MQTT messages are never recieved (because you subscribe to a topic with the S/N in it) there should be a message displayed suggesting the S/N is incorrect. Also given the S/N is included in the self signed cert response maybe some validation or auto-discovery of the S/N is called for because it's a long string and people make mistakes

In any case, this can be closed as resolved

@stubbers commented on GitHub (Jan 29, 2026): @maziggy - Similar to #155 In my case I figured this out by throwing it all at Claude to sanity to check me. It pointed out that the printer serial had a minor typo in it. Maybe if the connection establishes but the MQTT messages are never recieved (because you subscribe to a topic with the S/N in it) there should be a message displayed suggesting the S/N is incorrect. Also given the S/N is included in the self signed cert response maybe some validation or auto-discovery of the S/N is called for because it's a long string and people make mistakes In any case, this can be closed as resolved

BreizhHardware commented

2026-05-07 00:06:19 +02:00

Author

Owner

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

Why don't you use auto discovery?

@maziggy commented on GitHub (Jan 29, 2026): Why don't you use auto discovery?

BreizhHardware commented

2026-05-07 00:06:19 +02:00

Author

Owner

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

@maziggy - I'm one of those insane networking folks that are allergic to single layer 2 networks. The app and the printer are on different segments so autodiscovery doesn't work

@stubbers commented on GitHub (Jan 29, 2026): @maziggy - I'm one of those insane networking folks that are allergic to single layer 2 networks. The app and the printer are on different segments so autodiscovery doesn't work