The BoP can't see it because it follows BIP0039 standard where the gap limit is set to 20, see
https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki#address-gap-limitWallet software should warn when the user is trying to exceed the gap limit on an external chain by generating a new address.
What happens is that 3rd party wallet are not BIP0039 compliant in this detail, which cause confusion in compliant wallets like myTrezor. The remedy is as follows: fill the gap limit with several small transactions, so that the difference in path of two transactions in the account is always less then 20.
In this case we have payment on the address 44. It should be enough to send 0.001 BTC to address number 15 and 30.
I think you quoted without reading:
Ok I tested out your theory. I went back and used up every single address before m/0/44. My trezor is still showing the incorrect balance by 0.01btc. The balance on BTCReceive is showing correctly. So I'm guessing the only way to recover this lost btc would be to restore my seed to wallet32 app then send it somewhere else? I hope this is not the case.
If true then I think this may indicate a bug in the BoP implementation.
So here is an update on my situation. I checked mytrezor again this morning and the balance is now correct and the transaction in question is now showing up in the transaction list. I'm guessing the bop server needed a little time to refresh?
I kinda wanted to put this scenario to the test to see what would happen. Now I know.