Open LRomandine opened 1 month ago
binary_sensor.x1c_redacted_hms_errors Bambu X1C HMS errors off Count: 0
It's not being reported as an HMS error by the printer since the count of HMS errors is zero (HMS error details is in attributes on that sensor). See #515 for another case where a previously reported HMS error is now a transient state in the mqtt payloads.
The Bambu site says it is not a HMS error but just "error code". I was hoping Bambu exposed the error codes in MQTT under the 'print_error' or 'mc_print_error_code' fields.
According to this post, print_error should correlate to an error code from list of non-HMS error codes.
For #515 they set the value into the print_error field instead of the previous HMS error. But I think it's only there transiently. However, I haven't dug into that yet to confirm.
Thanks for the wiki link, that helps me understand a bit better how they're viewing the two overlapping ways to report problems. It's just a shame they aren't consistent. The print_error value for print canceled is definitely transient.
The integration has a download diagnostics button on the device. That will download information that includes the latest full mqtt payload. So that will help with cases like this as we can see if the data we need to improve the experience is present.
I manually caused an error by holding a spool in my AMS during a print and it worked, print_error was 117473286 (hex 07008006)
config_entry-bambu_lab-1618f47626cba3029574c51853e08c00.json
I downloaded the diagnostic file again after a few minutes and print_error was still there. After fixing the issue and hitting "retry" on the X1 touchscreen the print resumed. I downloaded the diagnostic file again and print_error was 0 and THEN my notification for HMS fired. In my file I uploaded HMS is blank so it looks like Bambu surfaces the print_error and when it clears it surfaces the HMS error.
Thanks. That’s very useful. And that new HMS behavior is bizarre.
Describe the feature
Add ability to read generic errors from the machine (list of errors)
These error codes are currently not reported to HA in any way I can see. Checking the Developer Tools -> States -> my printer I do not see any sensor picking up the error. Orcaslicer and Bambu Handy both pick it up.
What device is this for?
X1C
Other Information
Here is the output of all my x1c sensors. I encountered error 0500 4008 which you can see is not listed at all.