Bambu Lab Integration: Where to find your logs
When running the Bambu Lab integration client, it produces important logging information that it stores on the device you are running the client on. These log files include the raw MQTT data sent between the printer and the client, the raw data sent between the client and SimplyPrint and other additional logging information regarding the health and operation of the client.
Commonly, you'll be asked to send over these logs files in their entirety, but it is also possible to access them directly from the SimplyPrint panel with the "Get Logs" feature, but those are a bit more limited.
Most users will almost always prefer the first approach, but depending on the amount of log files you are downloading, it can be slower than the alternative methods.
In the Bambu Lab client dashboard there is a builtin log explorer you can use to select and download the log files that are relevant as a single zip file.
Then click "Download Selected as Zip", and wait for the file to finish downloading.
It is also possible to manually browse and select files from the log folder on your disk, this might be nice for large log collections where the native compression functionality can speed things up. Replace <USER> with the user running the Bambu Lab client.
Be sure to always include the BambuClient.log files (including backup files that are numbered). On macOS also include the stderr.log file as it contains extended information that might prove helpful.
You can view the journal logs for the Linux installation using the following command: journalctl -xeu simplyprint-bambu-lab --no-pager and optionally save it to a file with > logs.log.
These logs are especially generated when the client thinks there is something wrong with its ability to reach SimplyPrint, these logs exist in the log folder as seen in the table above in a directory called connectivity_reports.
Commonly, you'll be asked to send over these logs files in their entirety, but it is also possible to access them directly from the SimplyPrint panel with the "Get Logs" feature, but those are a bit more limited.
Most users will almost always prefer the first approach, but depending on the amount of log files you are downloading, it can be slower than the alternative methods.
From the Bambu Lab client dashboard
In the Bambu Lab client dashboard there is a builtin log explorer you can use to select and download the log files that are relevant as a single zip file.
Then click "Download Selected as Zip", and wait for the file to finish downloading.
Directly from the file system
It is also possible to manually browse and select files from the log folder on your disk, this might be nice for large log collections where the native compression functionality can speed things up. Replace <USER> with the user running the Bambu Lab client.
| Operating system | Log directory | Requires admin |
|---|---|---|
| Windows | C:\Users\<USER>\AppData\Local\SimplyPrint\Logs | No |
| Linux | /root/.local/state/SimplyPrint/log | Yes |
| macOS | /Users/<USER>/Library/Logs/SimplyPrint | No |
Important files to always attach
Be sure to always include the BambuClient.log files (including backup files that are numbered). On macOS also include the stderr.log file as it contains extended information that might prove helpful.
Extra logging from Linux
You can view the journal logs for the Linux installation using the following command: journalctl -xeu simplyprint-bambu-lab --no-pager and optionally save it to a file with > logs.log.
Connectivity report logs
These logs are especially generated when the client thinks there is something wrong with its ability to reach SimplyPrint, these logs exist in the log folder as seen in the table above in a directory called connectivity_reports.
Updated on: 08/03/2025
Thank you!