Run Wizard on 3.2.0 final and when I repeat Live-Z test the extruder always seem to start from same height, but the shown Z offset stays at the value from previous run. Making the Z offset calibration unusable unless I hit it the very first time correctly?
I guess yes.
Do it only once. Then continue adjusting live z with a normal print. The Prusa Logo is fine for that for example
Encountered the same issue
Same here, with MK2.5 v3.2.0. First run was -650, second -1320, third run was -2050.
Same bug found here, ended up putting huge scratch and dent on spring steel sheet. Bummer!

Can you all provide which printer you are using as well? Just wondering if this is isolated to the Mk2/Mk2.5 or if it also affects the Mk3.
Mine is a MK3 and has the issue
Mine is also a MK3.
Get Outlook for iOShttps://aka.ms/o0ukef
From: alhazar313 notifications@github.com
Sent: Saturday, May 12, 2018 7:03:55 AM
To: prusa3d/Prusa-Firmware
Cc: layneok; Comment
Subject: Re: [prusa3d/Prusa-Firmware] 3.2.0 Wizard Live-Z "Try Again" bug (#732)
Mine is a MK3 and has the issue
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/prusa3d/Prusa-Firmware/issues/732#issuecomment-388557437, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AJalZ7v2M5NFSYFOxZJT1gVYQUBfwbDsks5txuvLgaJpZM4T7Iwi.
Same issue for me in a Mk3, after upgrading to 3.2.0 final.
Thank you for reporting this bug. PR https://github.com/prusa3d/Prusa-Firmware/pull/747 should fix this.
I have the same issue with a MK2.5 upgrade. When using the Wizard to calibrate the printer I've been asked if I want to retry the Live Z adjust and I said "Yes". The operation started from the beginning with the nozzle height unadjusted, but the value remained from the first try. I had to double the value effectively to get the results. On the first print the nozzle dragged across the bed scraping it. I've had to reset XYZ calibration and start over.
I tested with the 3.2.1-576 release and I confirm that the issue has been fixed.
Please close the issue.
It was fixed in 3.2.1: https://github.com/prusa3d/Prusa-Firmware/releases/tag/v3.2.1
Most helpful comment
Thank you for reporting this bug. PR https://github.com/prusa3d/Prusa-Firmware/pull/747 should fix this.