Notifications
Wallbot can tell you what it is doing by email and by push notification to your phone (ntfy). This page shows how to set both up, how to choose what you receive, and lists every notification the bot can send.
How notifications work
- Two channels, same events. Email and push use the same on/off switches under Settings → Notifications. Each channel has its own queue and its own hourly cap.
- Never in the way of trading. The bot only puts a message on a queue. A background thread sends it and retries after 5 s, 30 s and 120 s. If it still fails, the error is logged and the bot carries on.
- Clear titles. Every title starts with the mode,
[Wallbot PAPER],[Wallbot TESTNET]or[Wallbot LIVE]. Trade notifications add the group, e.g.[Wallbot PAPER][MOVERS] CLOSED .... - No secrets. Passwords, API keys and signatures are removed from every message. Push messages also hide account balances ("balance hidden"); a trade's own P&L is still shown.
Set up push (ntfy)
ntfy is a free push service. Your phone subscribes to a "topic" name, and anything published to that topic appears as a notification.
- Install the ntfy app on your phone.
- Pick a long, random topic name, for example 30 random letters and digits. Anyone who knows the topic can read it, so treat it like a password. Allowed characters: letters, digits,
_and-, up to 64. - Subscribe to that topic in the app.
- In Wallbot, open Settings → Account & keys → "Push notifications (ntfy)". Leave "Server" at
https://ntfy.sh(or your own ntfy server), enter the "Topic", tick "Send push notifications" and press "Save". - Press "Send test notification". A "TEST notification" should arrive within seconds.
Every critical-type notification (for example "STARTED PAUSED", "NOT SAFE TO STOP", "BINANCE KEY REJECTED", "ENTRY CANCEL NOT CONFIRMED" and "TRADING STOPPED") is pushed at high priority (ntfy priority 4) while ntfy_critical_high_priority is on (the default), and so is the "VPS rebooted" notification. Titles containing CRITICAL, LIQUIDATED, RATE LIMIT, RECORDING ERRORS, BOT EXITED or STOP FAILED are always high priority. Everything else is sent at normal priority (3). Email has no priority.
Set up email (SMTP)
Open Settings → Account & keys → "Email (SMTP)" and fill in "SMTP host", "Port", "Security", "User name", "Password (app password)", "From address" and "To address". Tick "Send email notifications", press "Save", then "Send test email".
The settings are encrypted on disk like the API keys. The password is write-only: it is never shown, returned or logged.
Gmail
| Field | Value |
|---|---|
| SMTP host | smtp.gmail.com |
| Port / Security | 587 with STARTTLS (or 465 with SSL/TLS) |
| User name | Your full Gmail address |
| Password | A Google app password, not your normal password |
To make an app password: Google Account → Security → 2-Step Verification (must be on) → App passwords. Create one for Wallbot and paste the 16 characters into the password field.
Choosing what you receive
Settings → Notifications holds one switch per kind of notification. All are on by default. They apply to email and push alike.
| Setting | Covers |
|---|---|
email_on_fill | Entry filled |
email_on_close | Position closed |
email_on_critical | Critical events and safety alerts (most of the table below) |
email_on_reboot | The server restarted unexpectedly and Wallbot was started by the @reboot entry (high priority) |
email_on_loss_reset | Today's loss count was reset |
email_on_disk | Disk budget warnings, recording paused and resumed |
email_on_start | Bot started |
email_on_settings | Settings changes, key changes and mode switches |
email_on_trade_updates | Re-anchoring, stop and take-profit changes, trailing moves |
email_on_daily | The daily summary, sent at email_daily_time (21:00, the local time of the PC or server the bot runs on) |
Warning. If you switch email_on_critical off, you will not hear about a stop that failed, an unprotected position or a loss cap being reached, on either channel. Keep it on for any instance in testnet or live, and watch the dashboard closely if you turn it off.
The hourly cap
notify_max_per_hour (30) limits how many messages each channel sends in any rolling hour. Critical alerts count too. Anything beyond the cap is not lost: it is collected and sent as one message, [Wallbot ...] DIGEST N events (notification cap reached), as soon as the cap allows. Some alerts also have their own repeat limit, listed in the table.
Every notification
Titles are shown without the [Wallbot MODE] prefix. SYM is the coin and side is long or short.
Trades and routine
| Switch | Title | When it fires | What to do |
|---|---|---|---|
| fill | FILLED SYM side 20x @ price | An entry filled. Body: entry, stop, leverage, margin, quantity, estimated liquidation, take profit, wall stack. | Nothing. Check the trade card if you like. |
| close | CLOSED SYM side +12.4% (reason) | A position closed. Body: entry and the actual average exit fill price, P&L (actual or estimated), fees, leverage, duration, the lock of the last trailing move, the best ROE reached (with its price) and how many ROE points the exit gave back (close_report_actual_exit), the funding fees (include_funding_in_pnl) and, in live and testnet, the result of the Binance check: verified, or corrected to Binance's values (validate_close_with_binance). | Nothing. Read the reason over time to learn how trades end. |
| start | STARTED mode on exchange (previous stop: clean) | The engine started. "ABRUPT" means the previous run did not shut down cleanly. | After "ABRUPT", check the log and, in live, the exchange. |
| daily | DAILY 2026-10-01: 5 trades, +1.20 USDT | Once a day at email_daily_time. Trades, wins and losses, P&L, fees, per-group lines, cancelled entries, restarts, critical events; in testnet and live a LIVE LEARNING section. | Read it. Investigate restarts and critical events. |
| settings | Settings changed | Any settings save (old → new values). | Make sure it was you. |
| settings | API key saved / API key removed | A key slot changed. | Make sure it was you. |
| settings | Mode switched to LIVE (or PAPER, TESTNET) | A mode switch. | Make sure it was you. |
Trade updates
| Title | When it fires |
|---|---|
RE-ANCHORED SYM side to wall lo-hi | The anchor wall was pulled but another confirmed wall still protects the stop; the trade stays. |
ABSORBED SYM side: re-anchored to lo-hi | The anchor wall was eaten by trades; the bot moved to the next confirmed wall. |
ABSORBED SYM side: stop to breakeven | Absorbed, no backup wall, in enough profit: stop moved to breakeven + fees + slippage. |
ABSORBED SYM side: stop unchanged (better lock) / no backup, stop unchanged | Absorbed; the stop stays (a better lock exists, or not enough profit). |
HOLDING SYM side: wall pulled, no backup, ... | The wall went, no backup, but the trade is in enough profit to hold, with the stop at breakeven or better. |
BREAKEVEN SYM side: no wall in front of the stop | No wall protects the position and it is in enough profit: stop moved to breakeven. |
STOP TIGHTENED SYM side old -> new | Walls of the stack disappeared; the stop moved closer behind the remaining wall. |
TRAILING SYM side: stop X locks +60% ROE | The trailing stop moved. |
TP SET / TP RETARGET / TP REMOVED | A take profit was set, moved to another counter wall, or removed. |
RE-PLAN SYM side: entry X, 20x | A pending entry was replaced by a new plan: on a closer wall, after the front wall was pulled, or after a wall of its stack was lost. |
RE-PLAN FAILED SYM side: entry cancelled | A wall of a pending entry's stack was lost and the re-plan from the remaining walls failed an entry check: the entry was cancelled and nothing new placed (replan_on_stack_loss). |
SIDE SWITCH SYM: long -> short | A pending entry was cancelled and a closer one placed on the other side of the coin (nearest_side_priority, off by default). |
SIDE SWITCH FAILED SYM | The old entry was cancelled for a side switch but the new one could not be placed. The old entry is not re-placed automatically. |
TRAILING STARTED SYM side (by you) | You pressed "Start trailing" on the trade card. |
These are informational. No action is needed unless something looks wrong.
Critical and safety alerts (switch: critical)
| Title | When it fires | What to do |
|---|---|---|
CRITICAL SYM message | Any event logged as critical without its own alert, for example: STOP FAILED (closing at market), POSITION NOT CONFIRMED ISOLATED, a stop that could not be re-armed after a restart or reconnect, a stop that cannot sit safely before Binance's liquidation, a failed market exit, an unconfirmed entry cancel, the daily loss limit, live safety cap reached, engine failed to start, shutting down while not safe. | Read the full message in the Activity log. In live, check the exchange right away. |
LIQUIDATED SYM side -1.95 USDT | A position was liquidated. | Review why the stop did not fill first. Consider pausing. |
TRADING STOPPED: loss cap reached | A live safety loss cap (total or daily) was reached. No new trades. | Review the losing trades. Then raise the cap or press "Count losses from now". |
STARTED PAUSED | The bot started with your manual pause still on. | Check reconciliation, then press "Resume entries" when ready. |
NOT SAFE TO STOP | Prepare to stop or a shutdown could not finish safely. | Check open orders, positions and stops on the exchange now. |
UNCONFIRMED ORDER CANCELS | At start-up, cancels from before the restart are still not confirmed. | Check the exchange's open orders. |
ENTRY CANCEL NOT CONFIRMED | An entry cancel is still unconfirmed after cancel_alert_after_s (60 s). Sent once per cancel. | Check the order on the exchange. The bot keeps retrying. |
UNPROTECTED POSITION SYM side | A bot position has no confirmed stop on Binance. At most every 10 minutes per position. | Check it on the exchange immediately and protect it if needed. |
LOST ORDER SYM | An untracked Wallbot order could not be cancelled yet. At most every 10 minutes per order. | Watch for it to clear; cancel it yourself if it stays. |
LOST POSITION ADOPTED SYM | An untracked position from a Wallbot order was taken over with its planned stop. | Check the position and its stop. |
LOST POSITION CLOSED SYM | Such a position was closed at market because its planned stop was no longer valid. | Check it is closed. If the body says the close FAILED, close it yourself now. |
MIXED POSITION SYM | A position includes a Wallbot fill but is mixed with manual trading. The bot does not touch it. | Protect and manage it yourself. |
BINANCE KEY REJECTED (-2015) | Testnet/live: Binance rejected the key 3 times within a minute. At most every 15 minutes; a new IP at once (": new IP ..."). | Add the reported IP to the key's allow-list. |
ENTRIES PAUSED: API KEY UNSTABLE (IP x) | Testnet/live: a -2015 or a burst of -1021 clock rejections engaged the key guard (key_unstable_guard). New entries pause; resting entries are cancelled at the first request that gets through. Once per episode. | Add the reported IP to the key's allow-list, or fix the PC clock. Check open positions and their stops. |
ENTRIES RESUMED: API KEY STABLE | Signed requests have been clean for key_stable_minutes (10): new entries allowed again. Lists the IPs Binance reported. | Nothing, unless an IP is listed that you do not recognise. |
CANNOT CONFIRM STOPS (key unstable) | While the key guard is engaged, Binance did not answer the 15-second check of an open position's stop. | Check the position and its stop on Binance now. |
LEVERAGE CHANGED SYM: Ax -> Bx | The coin's leverage on Binance differs from what Wallbot last set, so it was changed outside Wallbot. At most once per coin per hour. | See Leverage changed outside Wallbot. |
MAX LEVERAGE SYM: Ax -> Bx | Binance's maximum leverage for a watched or traded coin changed (leverage_bracket_refresh_min). At most once per coin per hour. | Nothing; the next plan uses the new maximum. |
MARGIN SYM: x reserved vs y planned | Binance reserves more than margin_reserve_alert_pct (20%) above the planned margin for Wallbot's orders and positions on the coin. Nothing is cancelled or closed. At most once per coin per hour. | See Reserved margin above plan. |
TRADE CORRECTED SYM side | Live/testnet: the Binance check of a close found different PnL, fees, funding, exit price or quantity. Binance's values are now the record; the daily totals and the loss caps use them (validate_close_with_binance). | Read the difference. Large ones are worth a look in the log. |
BINANCE KEY REJECTED (IP x) | Paper: the read-only key was rejected. At most once an hour. | Add the IP to the key's allow-list. |
BINANCE KEY OK AGAIN | Paper: the key works again. | Nothing. |
RATE LIMIT 429 back-off / RATE LIMIT IP BANNED (418) | Binance's rate limits were hit. New entries pause; protective orders still go out. At most every 10 minutes. | Usually clears on its own. If repeated, look for another program using the same IP. |
RECORDING ERRORS (N rows not written) | The market-data recorder could not write rows. At most once an hour. Trading is not affected. | Check free disk space. |
Server, disk and loss count
| Switch | Title | When it fires | What to do |
|---|---|---|---|
| reboot | VPS rebooted — Wallbot started paused, check positions | The server restarted (not by you) and the @reboot crontab entry started the Trading instance with new entries paused (reboot_start_paused). High priority. | Check open positions and their stops on Binance and on the dashboard, then press "Resume entries". |
| disk | DISK n% OF BUDGET | Everything Wallbot stores passed the warning (80%) or high (90%) mark of the disk budget (disk_guard). | Free space or raise the budget. |
| disk | DISK 95%: RECORDING PAUSED | The budget is nearly full: market-data recording paused. Trading continues. | Free space. Recording resumes by itself below the high mark. |
| disk | DISK OK: RECORDING RESUMED | Usage is back under the high mark. | Nothing. |
| loss_reset | Daily loss count reset (by owner) | Today's loss count was reset from the dashboard. | Make sure it was you. |
Launcher alert
| Title | When it fires | What to do |
|---|---|---|
BOT EXITED (code N), restarting / ..., launcher gave up | The bot exited unexpectedly. Sent by the launcher, not the bot, to every channel that is set up and enabled, whatever the switches say. The email includes the last 30 log lines. | Read the log lines. After "gave up", fix the cause and start the launcher again by hand. |
Test messages, TEST email and TEST notification, are sent only when you press the test buttons.