That did it. I installed the button more than one year ago, it’s possible that the driver was different by then. The 1.6 button controller had no issue with it, but when I redid everything with 3.1 (what was I thinking...) it probably tripped on the missing attribute.
Thank you
1 Like
The trick with switching to virtual button, confirming the number of buttons and switching back to the native driver worked for me also. Thanks Mike @mike.maxwell
