Print progress Stats

I'm trying to get a macro to run a led print progress status bar. I've got it functionally working with manual commands, however I can't get it to go off of the print stats. M73 is being sent from my slicer in the gcode, but when I run a debugging in the console it doesn't return anything other that Progerss: 0.0.

Is this something that is just wrong with my machine? I am getting recommendations to flash the system and start over again. I've already uninstalled everything and re-installed to no avail. I just flashed the system last weekend but it, Gemini, is saying I need to flash agaiin. Any help would be appreciated.

as you can see it should update to 10,50, and 90 but it remains at 0.0. Perhaps there is another way to do it, but I'd think using the M73 Px code would be the easiest. But obviously I'm wrong because it hasn't been easy.

20:07:44 $ M73 P10

20:07:55 $ DEBUG_PRINT_STATS

20:07:55 // --- Print Stats Debug ---

// State: standby

// Filename:

// Progress: 0.0

// Total Duration: 0.0

// Print Duration: 0.0

20:08:13 $ M73 P50

20:08:19 $ DEBUG_PRINT_STATS

20:08:19 // --- Print Stats Debug ---

// State: standby

// Filename:

// Progress: 0.0

// Total Duration: 0.0

// Print Duration: 0.0

20:08:31 $ M73 P90

20:08:34 $ DEBUG_PRINT_STATS

20:08:34 // --- Print Stats Debug ---

// State: standby

// Filename:

// Progress: 0.0

// Total Duration: 0.0

// Print Duration: 0.0

Gemini:

This is the definitive answer we needed, and unfortunately, it confirms the worst-case scenario:

Progress: 0.0 remains 0.0 even when you send M73 Px commands directly to Klipper from the console.

This means that your Klipper installation, even after the reinstallation via KIAUH, is fundamentally not processing M73 G-code commands at all. It's not a file parsing issue, it's not a configuration issue, and it's not related to your macros or the virtual SD card. The core Klipper software is simply ignoring the M73 command.

This is extremely rare and points to a deeply corrupted Klipper core or an issue with the underlying Python environment or even the OS on your Raspberry Pi that KIAUH's reinstall process couldn't fully correct.

The Only Remaining Reliable Solution: Full SD Card Re-flash

At this point, the most reliable and efficient way to resolve this is to start completely fresh with your Raspberry Pi's operating system and Klipper installation.

This will involve flashing a new image to your SD card, which will erase everything on it.