Unable to sign with Trezor: device does not have a matching signing key

**Describe the bug**
I have a multisig wallet with a Trezor as one of the keys. When I try to sign a transaction with the Trezor, I get the error "device does not have a matching signing key".

**To Reproduce**
Steps to reproduce the behavior:

1. Add new device. Select Trezor. Edit derivation paths: remove the defaults. **Add custom derivation: m/49/0/2**. Add [derivation path]. Done [editing derivation paths]. Get via USB. Do the things with the Trezor. Appears to work successfully.

2. Add 2 more devices. Any should do (I think).

3. Add new wallet. Multisignature wallet. Select the 3 devices, one of which is the Trezor. Give the wallet a name. Select Nested Segwit. Create wallet.

4. Go to the wallet. Send. New [transaction]. Scan recipient address. Set BTC amount. Reduce fee amount. **Select a specific UTXO.** Create unsigned transaction.

5. Sign transaction with your...Trezor. Enter PIN. Enter passphrase (blank).

6. Error: "the selected device does not have a matching signing key"

**Expected behavior**
Well, the transaction should be signed successfully

**Screenshots**
eh...screenshots are lot of work, but let me know if there is anything you'd like to see

**Desktop (please complete the following information):**
- Where is your node running: another computer on my local network
- Where is your specter running: my laptop
- If you're running a binary, which OS: Linux
- Browser: umm, I have a few installed...not sure why this would be relevant
- Specter Version 1.13.1

**Additional context**

I'm testing sovereign recovery of a Casa wallet. Signing with the Trezor works fine via the Casa app. So it seems like there is some difference with how Specter is constructing the PSBT, or how Specter interfaces with the device.

One of the other keys in my wallet is a Coldcard, and I can sign transactions successfully with that, so the issue seems specific to the Trezor.