Thanks for the attention on this. It sounds like a feature that isn't widely used. I only found it extremely useful as it was a convenient method for me to move my settings between instances of Cura without uploading an actual profile file up to a file store and then download it at another location. Instead, I could access the web interface for my printer, OctoPrint in this case, and download the active gcode currently in the queue, and use it to import the most recent settings into whatever workstation I was running Cura on at the time. Now it appears that the concept of machine within the gcode's end profile data is causing me some issues.
IF this feature is truly just a debugging tool from days past and isn't valued very much anymore in its current state, could you perhaps remove the condition for machine ID from the gcode import function so that the core result of getting profile settings would work no matter what machine is being used?
Thanks.