Same here. No clue how it can happen to one group of people and not to the other.
There is an easy fix for it. This fix - to my mind - is minimum-invasive, but you need to amend and compile the source code of the tft screen for it:
-
There is a function in ‘usr/API/parseACK.c’ which suppresses specific messages coming from Marlin, i.e. these messages - although posted by Marlin - will not be shown on the tft screen
-
This function uses the array ‘knownEcho’ to specify which messages should be ignored. Now, if you add the M420 command to this array in line 39 it will be safely ignored:
{ECHO_NOTIFY_NONE, “Unknown command: "M420”}, // M420
Interestingly, there are a couple of other entries in this array already dealing with the the M420 command …
This fix works perfectly for me and is not dependant on what BTT / Marlin do with it. It should also work for the Repeat users. So, if this M420 message - for whatever reason - is thrown by Marlin, it will be suppressed. And if it is not thrown, well, then it won’t be shown anyway. The downside is that you will never see this message again on your tft, even if it is thrown by Marlin for a good reason. But I decided to live with this risk.
Alternatively, you can revert the change BTT introduced in Feb (see above). But because I don’t understand Marlin well enough I thought my second option would be better.