Electrum just released a new version, 4.2.2. One of the "issues" they fixed wasn't actually an issue with Electrum, but rather an issue with a the crappy KeepKey hardware wallet.
# Release 4.2.2 - (May 27, 2022)
* Lightning:
- watching onchain outputs: significant perf. improvements (#7781)
- enforce relative order of some msgs during chan reestablishment,
lack of which can lead to unwanted force-closures (#7830)
- fix: in case of a force-close containing incoming HTLCs, we were
redeeming all HTLCs that we know the preimage for. This might
publish the preimage of an incomplete MPP. (1a5ef554, e74e9d8e)
* Hardware wallets:
- smarter pairing during sign_transaction (238619f1)
- keepkey: fix pairing with device using a workaround (#7779)
* fix AppImage failing to run on certain systems (#7784)
* fix "Automated BIP39 recovery" not scanning change paths (#7804)
* bypass network proxy for localhost electrum server (#3126)
As you can see from the release notes above (emphasis mine,) the pairing issue with KeepKey has been fixed "using a workaround." How do I know the issue is with the hardware wallet, and not Electrum? The same pairing problem is endemic with the KeepKey and any desktop client I've tried. The same problem with pairing is present with KeepKey's own bootloader and firmware update client. The issue started after a firmware update roughly 2 years ago (IIRC,) and until now KeepKey has been unable to resolve their issue. In order to pair a KeepKey with desktop clients one would have to run the application with administrator privileges.
I just tried the new version with one of my KeepKey HW wallets, and it pairs up smooth as silk. Kudos to the Electrum team for stepping up and taking care of their supporters.
