[Bug] <X1C error near start of every print>

[dasb00ter]

Home Assistant Version

Installation method Home Assistant OS Core 2025.10.4 Supervisor 2025.11.2 Operating System 16.3 Frontend 20251001.4

Bambu Lab Integration Version

Version 2.2.12

Describe the bug

I get an error from the binary sensor on every single print near the start. Wondering if its the first layer scan...not sure where to find what exactly the error was as its not present on the printer assistant on the printer screen

alias: X1C error notifier
description: ""
triggers:
  - device_id: redacted
    domain: bambu_lab
    type: event_print_error
    trigger: device
  - trigger: state
    entity_id:
      - binary_sensor.x1c_00m09d542800744_hms_errors
conditions: []
actions:
  - device_id: redacted
    domain: mobile_app
    type: notify
    title: X1C issue detected
    message: >-
      Bambu X1C Print Error -
      {{states('binary_sensor.x1c_00m09d542800744_hms_errors') }}
    data:
      actions:
        - action: URI
          title: See possible solutions on Bambu Lab Wiki
          uri: |
            {{ state_attr('binary_sensor.x1c_hms_errors', '1-Wiki') }}
mode: single

To Reproduce

start any print on x1c look at binary sensor entity see error lasting 2 minutes that goes away

Expected Behaviour

No error reported

What device are you using?

X1C

Diagnostic Output

No response

Log Extracts

No response

Other Information

No response

[AdrianGarside]

The X1C reports the first layer inspection as an HMS error.

[dasb00ter]

Hmm alright, is there way to not notify on this specific error? The closes I can think of to the solution is the length of time the error is in an on state. Unfortunately the start of a print is a delicate time... I wonder how the handy app skips it?

[AdrianGarside]

I’m considering filtering it out in the integration. You could do the same in automations. I have no idea why Bambu would choose to do this given they have stages defined for this in other Mqtt fields that they then don’t use.

[dasb00ter]

Thanks for explaining the situation. Trying to understand what the filter would look like. Its a binary sensor. HA developer tools show off on states. Automation's page if using this as a device give as states: problem, OK, unknown, unavailable or am I looking at having to do something more advanced? In any case I guess I should probably watch my prints for the first little bit... but then I have toddler bent on self/world destruction or genius epiphanies, none of which I want to miss lol.

[AdrianGarside]

Toddlers are definitely a handful! I'll do plan to suppress this on the integration side. I've fixed most other outstanding bugs now so I might get to it soon now since it bugs me every time my X1C spams me that it's doing the first layer check from my home assistant phone notification (since I never got around to doing what I suggested above).