If you have any other means of pairing the controller and reading it's information, this may help. I just double-checked my source code and remembered that it uses the device name to decide which pincode to send. If your knockoff has some other name (official controllers begin with "Nintendo RVL"), then this would cause it to send the wrong pin and fail.Blinking goes on steadily for about 15 secs. until it stops trying. I know what you mean, but it doesn't do anything
I don't know about the WiiMote 1+2 syncing. It has always worked and syncing as/like a normal WiiU Pro controller on the WiiU.
I bought the 8bitdo dongle to use that particular controller, but it wouldn't take it either. So I was happy to see MissionControl could extract the id of it in hopes of supporting it in the future. Seems that might not be so easy after all.
I'm assuming getting the id/mac from somewhere else (if possible) wouldn't help, since it apperantly doesn't even try to talk with the Switch, or?
Eventually I might implement pairing in my companion app to allow people to observe the process for diagnosing these kind of issues. For now, if you could extract this information via some other means I may be able to help you more quickly