evanevery

The trick is having a good collection of small screws!

Unfortunately, I don't have the newer hat. I would be glad to see what it would take to rework the design but I would obviously need the updated hat...

Thanks! But... I just tried your suggestion (in the example code above) and it doesn't appear to make a difference. BtnA is still "unstable"...

In M5Stack Community Forum, another user posted that this is an issue which is apparently a bug in the current IDF. Rolling back to a previous IDF apparently resolves it....

Seems to mitigate the issue in my "real world" sketch as well as my wifi test sketch. Its a simple work-around, but it costs 10ms. Hopefully it will help someone...

BTW - As I'm finding out - the 10ms delay helps but its not perfect. I'm still getting intermittant fake ButtonA presses every couple of minutes... I will try a...

BTW - I don't believe its a debounce issue at all. We are getting ButtonA notifications even if the button is never touched.... (These aren't "duplicate" notifications)

Why would debounce have anything to do with a false reading from a button which was NEVER pressed? Have you confirmed that changing the debounce mitigates the problem that simply...

1. Did you test your suggestion with the small posted example sketch to see if it works? What specific command did you use and where did you set it (setup()?)......

Well if your NOT going to test your theory with the sample sketch, tell us what you did to fix the sample sketch, and confirm that it actually works... How...