G30 action different when "play"ing from a file versus console command. How do I work around?

Smoothieware on a delta, generally works great. Thanks for your efforts!
I’m using an edge build from about a week ago.

I added a prox zprobe and am trying to set it up to auto-set Z0 at the start of each print.
Unsuccessfully so far, and I’ve tracked it down to G30 acting differently if it is run from the console versus "play"ed from a file:

The commands in question:
G28
G1 F8000 Z3.0
G30 z0.44

If I type these commands into pronterface, the effector
-Travels to z3.0
-Slowly probes down until the probe triggers and
-Stops. Z0.44 is set at that height. Yay!

If I put these same commands in a file and “play” it ("@play /sd/test.gc" in pronterface), the effector
-Travels to z3.0
-Slowly probes down until the probe triggers and
-RETRACTS BACK TO z3.0, and (<--not the same!)
-Stops. Z0.44 is set at that height (Z3.0). Less than useful.

Needless to say this prevents me from using G30 to set my Z0 automatically as part of the gcode file.

Am I doing something wrong? Can I make this work somehow?
Is there a reason for this change in behavior between console and file invocation?

Thank you for any help!

Imported from wikidot

@!#*@#*

Never mind, I just figured out my error. It’s a case issue.

Apparently pronterface converts lower case (such as “z”) to uppercase before sending. Playing the file directly doesn’t get that. Smoothie wants an uppercase Z. It was ignoring the “z”.