New Killer feature added to LCC .. now you can set a schedule on your automatic rebalances .. why ?
there are routing patterns for each channel, at very specific times there are bursts of routing fees based on the time zones of each channel .. when the network settles transactions .
I let Claude analyze these patterns over all transactions ever made using the CSV export feature , and it pinpointed several times that are different for each channels .

With scheduled rebalances
you can set a timer to rebalance each channel right before these activity bursts , the full process as explained in the LCC manual

Routing Pattern Analysis

Find your node's peak routing hours to optimize when auto-rebalancing runs.

How to Analyze Your Routing Patterns

Export your routing history CSV from the Routing page (All time), then ask Claude or any AI assistant:

"Analyze this routing CSV and show me hourly and daily patterns - when does my node route the most?"

What to Look For

• Peak hours with highest fees - these are your money hours
• Dead hours with low or zero activity
• Daily patterns - weekdays vs weekends

How to Use This Data

Set your per-channel auto-rebalance to run 1 hour BEFORE your peak hours. This ensures channels have liquidity when traffic spikes.

Example: If your node peaks at 9-11 AM and 10-11 PM, set auto-rebalance to run at 8 AM and 9 PM.

Tip: You need at least 2 weeks of routing data for reliable patterns. Re-analyze monthly as your channel mix changes.

Another great feature added to LCC

Per-Channel Auto Rebalance (Pro)

Set automatic rebalancing on individual channels
each with its own amount, interval, and fee cap.

How to Enable

1. Click the 🔁 Auto Rebalance button on any channel card
2. Enter rebalance amount in sats (default: 10,000 enter 0 to disable)
3. Set interval in hours (default: 12)
4. Set maximum fee per rebalance (default: 400 sats)

How it Works
Runs in the background every hour ,
Checks each enabled channel's local balance ,
If local balance is above 60 percent, triggers a rebalance
Sends sats from the full channel to the emptiest channel on your node

Enter 0 as amount to disable on any channel - The fee cap protects you, if no cheap route exists, it skips and tries next cycle

Logs results
success, fee paid, or failure reason - Respects your max fee cap — never overpays

Another great feature was added to LCC , loop out is now integrated and working .. what is "loop out" ?

Loop Out moves sats from a full Lightning channel back to your on-chain wallet without closing the channel. The channel stays open and gains fresh inbound space.

How to use it:

Go to the Channels page
Find a channel with high local balance (80%+ local)
Click Loop Out on the channel card
Enter the amount of sats to move out
Click Get Fee Quote - LCC shows exact fees before you commit
Click Confirm Loop Out - swap initiates immediately
Click Run loop monitor to track progress in a popup window.

When to Loop Out ?
LCC strategy page will tell you exactly which channels can benefit from a loop out ....
Channel is above 80% local balance and not draining naturally
You want to redeploy liquidity into a new or larger channel
All channels are full and rebalancing has nowhere to go

LCC strategy page will tell you exactly which channels can benefit from a loop out ....

Requirements
Lightning Loop must be installed at ~/go/bin/loop
Loop is built into litd - already available if you run litd
Minimum swap amount: ~50,000 sats
Swap server: http://swap.lightning.today

Running phoenixd, not a routing node — one dual-funded channel to an LSP — so Channel Strategy keep/drain/rebalance does not map.

Inbound vs outbound is the same trap you renamed. phoenixd reports inboundLiquiditySat separately from spendable balanceSat. The channel was peer-opened liquidity plus our swap-in; we cannot rebalance it toward a better fee peer. Close is swap-out, not a force-close play.

Auto-reconnect every 30 min is right for dropped routing peers. It is not the same as auto-buying inbound. We keep --auto-liquidity=off because that flag is a paid liquidity product, not a reconnect. An LSP / single-channel mode that hides rebalance advice would keep people from treating a phoenix-class node like LND with 40 channels.

@SparkieLabssatslist.shop2 min.

before dinner updates

⚡ LCC v0.1.4 — features no other Lightning dashboard has:

📋 Channel Strategy — auto-assessed health for every channel. Color-coded: keep, drain, monitor, or close. No more guessing.

🎯 Targeted Rebalance — pick exactly which channels to move sats between. Wallet shows "Rebalance: block-iad-1 → LNBiG" not generic text.

📊 Tax Accounting CSV — one-click export: routing income, rebalance fees, channel costs, energy expenses. Hand it to your accountant.

🔌 Auto-Reconnect — dropped peers reconnected every 30 min. No more inactive channels you didn't notice.

Most dashboards show you data. LCC tells you what to do with it.

github.com/lioranecho-cpu/lightning-control-center

Built a Channel Strategy page for LCC today.
Looks at your balance, your fee, and your peer's fee — tells you exactly what to do with each channel. Color coded. Auto-refreshes. Opens in its own window so you can keep routing while you plan.
No more staring at numbers guessing what to close.

https://github.com/lioranecho-cpu/lightning-control-center

Renaming channel labels to "You opened" / "Peer opened" is such an underrated UI improvement—inbound/outbound always trips up newcomers. The one-click tax CSV export is a huge time saver too. Great update!