Casa supports both the Trezor One, Trezor 3 and the Trezor Model T. See our list of supported devices for a full list of the devices we support.
Whether you are adding the Trezor, performing a health check, or sending funds from your Casa vault, you interact with the Trezor API, a web interface that allows you to add a signature for your keyset easily.
You must download and install the Trezor Suite desktop app on your computer and keep it open in the background during the health check and transaction signing process.
If you have installed Trezor Suite recently, you do not need also to install Trezor Bridge. However, if you are running an older version of Trezor Suite, your version of Trezor Suite may not have come with Trezor Bridge, and you may need to download Trezor Bridge separately.
See this article for a detailed explanation of Trezor Suite.
The vast majority of Trezor errors are browser-related. We recommend using Chrome, but Brave or Firefox may also work. If you have tried one, please try a different one, especially if you have not yet tried Chrome. Please also make sure your browser is up-to-date.
Some other common Trezor errors include:
Trezor's website gets stuck on "Loading..." or a blank screen.
"This device is not part of your wallet."
"TrezorConnect is not defined/is undefined"
“Input does not match scriptPubKey”
All backends are down
Trezor's website gets stuck on "Loading..." or a blank screen.
Please ensure you have cookies enabled for regular or Incognito mode, depending on which mode you're using. Trezor's website does need to be able to store a cookie to link the device.
Make sure to use Chrome. You may run into this when using Firefox and/or Brave.
"This device is not part of your wallet."
Possible solutions: Make sure you are using the correct hardware device to sign the transaction or complete a health check.
If you are using passphrase protection on the device, you will need to enter that passphrase when prompted or you will receive this error. If you are not using a passphrase, leave this field blank.
"TrezorConnect is not defined/is undefined"
Possible solutions: Try another cable. Not all USB cables are rated for data transfer, so make sure that the USB cable you're connecting is the one that came with the Trezor, or is otherwise rated for data transfer (not just a charging cable).
Make sure to close anything else that would also be trying to communicate with the Trezor such as a watch-only wallet like Electrum.
An ad blocker or browser setting is probably doing this. Solutions reported by users:
- As of June 2020 we’ve known of at least one case where Privacy Badger blocked Trezor Connect.
- Turn off Firefox's Enhanced Tracking protection
"Session not found"
Possible solutions: Please make sure that there are no ad blockers or privacy browser settings that can trigger this error. Things like Privacy Badger should be turned off.
This is a vague, intermittent connection issue:- https://github.com/trezor/trezor-suite/issues/3225
- https://github.com/trezor/trezord-go/issues/197
- Try different USB cable, different port, etc. This is not a bug in Trezor Suite, but in communication with the device.
- Are you using any other software that might communicate with Trezor while you are signing TX with Electrum? (such as a Browser with http://wallet.trezor.io/ or http://suite.trezor.io/ open, a Trezor Connect enabled wallet or Trezor Suite desktop app)
- Try another cable
- Close anything else that would also be trying to communicate with the Trezor
- Update the firmware (Only do this after health checking your other keys, as there is a slight chance that the device wipes itself after the update)
"Interaction timeout"
This can happen if you are attempting to sign a transaction with too many inputs. If this happens, you can always try sending a transaction that sends from fewer UTXOs in your keyset. The Casa app does have the ability to send from specific addresses. See: Sending from specific addresses
Hanging window/non-responsive window
This indicates a browser error. Please try a different browser or try to clear your cache.
If you've tried the above steps and are still having issues, please reach out to our support team, and we're happy to assist.
“Input does not match scriptPubKey”
Try to close out of the window completely and restarting the flow from clicking the link in the email again.
“Wrong previous session”
This occurs when you do not enter PIN or connect the Trezor before launching Trezor connect flow. Restart the entire flow, connect Trezor and unlock PIN (if using Model T) then it will work.
“Signature not found”
Send a new signature request from the Casa App. This is the result of exiting the signing flow in the Casa App (ex. hitting the back button from the mobile screen shown below)
Error"all backends are down"
When we see that error it is usually because a VPN is interfering with the Trezor's ability to communicate with your browser when it is trying to receive the signature message from Casa. Turn off the VPN and try again.