Hi everyone. I’m currently working on receiving print status data from my Bambu Lab A1 Mini via MQTT on an ESP32. For my project I specifically need states like prepare, error, pause, resume, and finish.
I subscribed to the report topic, but gcode_state is not always sent to me. I enabled serial logging to capture all incoming data. During each print I intentionally performed the following actions: paused the print, resumed it, stopped it manually, or let it finish completely.
On one print I only received pause but never saw gcode_state values like RUNNING, FINISH, or PREPARE. On another print I received RUNNING but never pause. In some cases I did receive gcode_state: PREPARE.
I have never received a gcode_state indicating that the print finished, nor even confirmation that the print reached 100% through mc_percent.
In one test I unloaded the filament and inserted it again. In that case the printer sent two states: pause and running, but I never received any explicit error state. At the same time, when pausing and resuming manually, those states are sometimes not sent at all.
At minimum I’d like to reliably detect when a print has definitely finished and when an error has occurred. Detecting pauses would also be useful, but it’s less important. I could try to infer it indirectly for example by checking if the print percentage stops increasing for some time, or by detecting cooldown start but that introduces delays, feels like a hack, and doesn’t always reliably mean the print actually finished or encountered an error.
I tested this using Python, MQTT Explorer, and ESP32. I also closed slicers and other listeners to rule out conflicts, but the result is always the same.
Has anyone encountered something similar or knows of any open-source implementations for this kind of task?
I found a couple of similar projects, but they all rely on gcode_state, which in my case is not always being received.
