[Bug] With latest P1P firmware we're sending a cancelled event followed by a failed event

[AdrianGarside]

Describe the bug

The latest P1P firmware adjusted the missing failed state. So now a cancel presents as a transient cancel state and then a persistent failed state. So I'm firing both events one after another.

To Reproduce

.

Expected Behaviour

.

What device are you using?

X1C

Diagnostic Output

.

Log Extracts

No response

Other Information

No response

[github-actions]

Stale issue message

[AdrianGarside]

X1C we get failed then cancelled but maybe that's the order I search for the states since it appears they came in a single payload:
2023-12-24 15:00:59.519 DEBUG (Thread-2 (mqtt_listen_thread)) [custom_components.bambu_lab.pybambu] Received data from: X1C
2023-12-24 15:00:59.519 DEBUG (Thread-2 (mqtt_listen_thread)) [custom_components.bambu_lab] EVENT: event_print_failed: {'device_id': '92be1c12489f8dbd568d9fdf9f920ef4', 'type': 'event_print_failed'}
2023-12-24 15:00:59.519 DEBUG (Thread-2 (mqtt_listen_thread)) [custom_components.bambu_lab] EVENT: event_print_canceled: {'device_id': '92be1c12489f8dbd568d9fdf9f920ef4', 'type': 'event_print_canceled'}

[AdrianGarside]

Yes, we check for print failed first then canceled. Need to swap so we can only fire the canceled event. On X1 at least.

[github-actions]

Stale issue message