mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-09-30 03:01:21 +02:00
maziggy
0c44db04dd
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. The start toast claims only that the command was sent, since that is all the ack proves; the amber countdown badge remains the signal that a cycle is genuinely live. 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.
