Yep, changing the password UX is high friction because you need to teach everyone how it works and nobody's existing tools will work with it.
If you're going to change this up it would make more sense to move to a better protocol than "provide this fixed shared secret".
It's also useful to think about what the "root of trust" is in authentication flows. That is, the thing that can reset the password.
This might reasonably be email, an OIDC provider or a cloud account linked to your device vendor.
IMHO what would be really nice would be a decent ecosystem around WebAuthn. So ways to plug different providers into your browser / operating system. This would let you choose some combination of hardware keys, your preferred password manager or keys linked to your icloud/google account, for 1-click auth everywhere.