Closed phoenixswiss closed 2 months ago
Yes, that's the correct fix given the way the code currently works. There are alternative ways to identify the model from the serial number but that would be much more opaque. I see you changed X1C lookup to also check for AP05 when the name is 'ap' - was there a specific reason for that? It may be time to key first off the APxx entries since that's the current way is a little inverted and not been revisited with a fresh eye since it was originally written very early on.
I've just added the AP05 (X1C) as they may have changed the string for this model from rv1126 to ap for this printer too.
I suspected they might. I’ve rewritten the detection. Logic to be simpler and more forgiving so it will be resilient to that now.
Thank you for your hard work!
Yep, just updated my X1C:
{
"flag": 0,
"hw_ver": "AP05",
"name": "ap",
"sn": "**REDACTED**",
"sw_ver": "00.00.32.17"
}
Describe the bug
With the new firmware release 01.01.00.00, the Bambu Lab Printer X1E is no longer correctly recognised by the integration.
To Reproduce
Expected Behaviour
The device is correctly recognised as a Bambu Lab X1E
What device are you using?
X1E
Diagnostic Output
Log Extracts
No response
Other Information
It seems that with firmware version 01.01.00.00 the parsing strings "esp32" or "rv1126" don't exist any more for X1Es. A new string "ap" has been introduced.
I've modified the corresponding sections in custom_components/bambu_lab/pybambu/utils.py accordingly and it works now: