maziggy ccbfcfa295 fix(ams): confirm drying start instead of trusting the firmware ack (#2533) ...

The Start Drying button gave no feedback at all and reported success on the
strength of the MQTT ack alone. On a P1S the firmware answers
ams_filament_drying with result=success and then silently declines, and
P1-family firmware never publishes dry_sf_reason — so the #971 reason guard
is inert there and the card just sat unchanged.

Both drying mutations now toast on success. After a start, the card watches
the unit's dry_status/dry_time (straight from the info bitmask, updated on
every push); firmware reaches DryStatus 1 within seconds of a real start, so
still sitting at zero 30s later means the cycle never began. Bambuddy now
says so and names the two causes: AMS power adapter not connected, or the
printer not idle. Unlike the dry_sf_reason guard this is model-agnostic.

2026-07-11 08:37:57 +02:00

..

index-blSspT6K.css

Dock Folder README as a collapsible right rail instead of a top block (#2520)

2026-07-09 07:32:24 +02:00

index-DMFedMEr.js

fix(ams): confirm drying start instead of trusting the firmware ack (#2533)

2026-07-11 08:37:57 +02:00