I ran your question into Venice and the answer returned was pretty good:
The issue you're experiencing is likely due to node connectivity/synchronization and derivation path mismatches, not a failure of your seeds. Here's a breakdown and actionable steps:
Core Problems
Node Accessibility:
Your Umbrel node is offline, so apps like Blue Wallet can’t connect to it. If Blue Wallet is set to use your local Umbrel node (default), it won’t sync transactions or show balances without node access.
Derivation Path Mismatch:
Umbrel’s Bitcoin Core (default wallet) uses a derivation path like m/84'/0'/0' (BIP-84 for segwit addresses). Blue Wallet might default to a different path (e.g., m/44'/0' for legacy addresses). If the path doesn’t match, funds won’t show up.
Syncing Issues:
Even if you restored the seed correctly, Blue Wallet might not have fully synced with the blockchain or your node, delaying transaction visibility.
Solutions
1. Temporarily Use a Public Node for Blue Wallet
Open Blue Wallet’s settings and switch from "Umbrel" or "Custom Node" to Public Node (under the "Node" or "Network" section).
This bypasses your offline Umbrel node and connects to a public Bitcoin node, allowing you to see your balance immediately (assuming your seed/path is correct).
2. Specify the Correct Derivation Path
During Blue Wallet’s seed restoration, explicitly set the derivation path to m/84'/0'/0' (the standard for Umbrel’s Bitcoin Core).
If you skipped this step earlier, you’ll need to restore the seed again with the correct path (back up your current Blue Wallet first!).
3. Verify Node Health
If you can access your Umbrel server:
Check Bitcoin Core’s logs (via system.log or the admin panel) for sync errors.
Restart Bitcoin Core or Umbrel if it’s stuck.
If the node is unreachable, prioritize fixing it (e.g., reboot hardware, check internet, ensure bitcoind is running).
4. Use an Alternative Wallet Temporarily
Install a lightweight wallet like Electrum (with "Standard" server) or Sparrow Wallet to confirm your balance. These can sync via public nodes and use your seed.
Export your wallet’s private keys or addresses from Blue Wallet (if possible) and check them on a blockchain explorer like blockchair.com.
5. Ensure Umbrel’s Bitcoin Core Is Fully Synced
If your node is back online, wait for Bitcoin Core to fully sync (could take hours/days). Blue Wallet depends on your node’s state.
Monitor sync progress via bitcoin-cli getblockchaininfo in the Umbrel terminal.
Why Seeds "Work Anywhere" But Sometimes Fail
Seeds are universal, but wallets must:
Use the correct derivation path (most issues stem from this).
Connect to a working node or blockchain explorer.
Be fully synced before displaying balances/transactions.
Final Steps
Prioritize restoring access to your funds via a public-node wallet (Blue Wallet or Electrum).
Fix your Umbrel node offline issue to regain control of your self-hosted setup.
Double-check derivation paths and sync status in all wallets.
If funds still don’t appear after these steps, verify the addresses on a blockchain explorer to confirm they’re correct. Let me know if you need help with any specific troubleshooting!