Wrong balance shown on Albyhub/Umbrel

[Funman2]

When running the Albyhub app on Umbrel, with my umbrel lightning node as a backend for Albyhub, in Wallet or in AlbyGo it displays the wrong lightning spending balance(about 0.1 btc missing...) Whereas when i use the nwc app and connect to alby extensoin the balance is correct...

[rolznz]

Please ignore the above comments, they are spam.

[rolznz]

@Funman2 is it possibly the channel reserves? we do not include the unspendable part within your balance.

[Funman2]

@Funman2 is it possibly the channel reserves? we do not include the unspendable part within your balance.

No, Thunderhub for instance shows about one third more available sats for transacting ( about 1m sats) and only 15000 sats ( in lightning wallet)reserved as not available, not talking about the onchain balance...
Also alby extensoin connected through the NWC app by alby shows the correct available balance, as well as Zeus...

[Funman2]

Checked and tested today with a new seperate docker Installation of Alby hub with latest Master package 1.13.0 ... and connected to my lnd of my umbrel lnd node, had the exact same result: 2m Sats balance shown instead of the correct 3.5m Sats available balance...

[rolznz]

@Funman2 you can go to settings -> debug tools -> get balances and see if you can find the discrepancy, this would be very helpful.

[Funman2]

under the "get node status" command i got this error message: API Response: {"fileName":"http://192.1.........:...87/assets/index-RpciCtZq.js","lineNumber":116,"columnNumber":14247,"message":"500 rpc error: code = ResourceExhausted desc = grpc: received message larger than max (6399710 vs. 4194304)"}

otherwise, with get balance i get the same wrong spendable output, but with alby NWC app on umbrel, I get the right output ( 3.464.999 spendable)....
API Response: {
"onchain": {
"spendable": 100561,
"total": 100561,
"reserved": 100000,
"pendingBalancesFromChannelClosures": 0,
"pendingBalancesDetails": [],
"internalBalances": {
"balances": {
"total_balance": 100561,
"confirmed_balance": 100561,
"reserved_balance_anchor_chan": 100000,
"account_balance": {
"default": {
"confirmed_balance": 100561
}
}
},
"pending_channels": {}
}
},
"lightning": {
"totalSpendable": 2614616000,
"totalReceivable": 83437169000,
"nextMaxSpendable": 1268808000,
"nextMaxReceivable": 15676059000,
"nextMaxSpendableMPP": 2614616000,
"nextMaxReceivableMPP": 57582444997
}
}

[rolznz]

@Funman2 it looks like you omitted the individual channel balances in the response, are you able to include those and just hide the counterparty IDs / channel IDs, etc (anything you think is sensitive?).

[rolznz]

@im-adithya any chance you could look into the issue above with getting the node status? why is the payload so big?

[Funman2]

@Funman2 it looks like you omitted the individual channel balances in the response, are you able to include those and just hide the counterparty IDs / channel IDs, etc (anything you think is sensitive?).

What i posted was the total output of get info command, nothing left out/ommitted...

I can paste the list channels command here if you like, but it has indeed many sensitive info, i don't reall would like to expose...

[rolznz]

@Funman2 that's ok. We will try to reproduce the issue