Settings / System Setup

The System Setup panel is the single place where you configure how SETI AI talks to the outside world — alert channels, alarm thresholds, battery limits, energy pricing, charge schedules, and solar inverter connections.

Where to find it

System Setup is a widget, not a separate page. Open the SETI STACK dashboard (from the Command Center top tabs, or by going straight to the dashboard), open the left palette, and under the palette look for System Setup (gear icon, CONFIG badge). Click it or drag it onto the canvas to spawn the panel. It can be moved, resized, and saved with the rest of your dashboard layout.

The panel is a stack of collapsible sections. The first section (Discord) is expanded on open; every other section starts collapsed — click a section heading to expand or collapse it. Each section has its own Save button, so you can configure one channel at a time. Channels that support it also have a Test button. A small toast in the corner confirms each save or test (green = ok, red = error).

All settings are stored server-side in the system_settings table (Postgres), so they persist across restarts and are shared by every browser. Saving calls POST /api/notifications/settings; the panel loads current values from GET /api/notifications/settings when it opens.

1. Discord

Send alerts to a Discord server, either through a webhook (simplest) or a bot (richer — supports a dedicated channel, a voice channel, and TTS).

Buttons: Save (writes Discord settings) · Test (sends a test message to the configured destination via POST /api/notifications/test).

Internal/private IPs and metadata addresses are blocked for webhook URLs (SSRF protection), so only real discord.com webhooks will work.

Stored keys: discord.enabled, discord.use_bot, discord.webhook_url, discord.app_id, discord.bot_token, discord.bot_channel, discord.voice_channel, discord.tts_enabled.

2. Slack

Buttons: Save · Test. Alerts post as a formatted Slack block message with a severity emoji header. Internal hosts are blocked (SSRF protection).

Stored keys: slack.enabled, slack.webhook_url.

3. Email (SMTP)

Send alerts by email over SMTP. Both a plain-text and an HTML version are sent; the HTML version is color-coded by severity.

Buttons: Save · Test. Email won't send unless Enable Email is on and both SMTP Host and To are set. Internal SMTP hosts are blocked.

Stored keys: email.enabled, email.smtp_host, email.smtp_port, email.smtp_tls, email.smtp_user, email.smtp_pass, email.from_addr, email.to_addrs.

4. Alert Thresholds

The trigger points that fire battery alarms. After every Victron/VRM poll, the live battery metrics are checked against these values and a notification fires (through every enabled channel) when one is breached.

Button: Save.

Stored keys: notify.low_voltage, notify.high_voltage, notify.low_soc, notify.high_temp, notify.cooldown_seconds, notify.on_critical, notify.on_warning, notify.on_info.

5. Battery SoC Limits

Operating window for the battery, used by automation/charge logic (distinct from the Low SoC alarm above).

Button: Save. Stored keys: battery.soc_floor, battery.soc_ceiling.

6. Energy Cost

Electricity pricing used for cost and savings calculations across the dashboard.

Button: Save. Stored keys: cost.rate_kwh, cost.peak_rate, cost.offpeak_rate, cost.peak_start, cost.peak_end (currency is USD).

7. Charge Schedules

Time-of-day rules that charge or discharge the battery automatically — for example, charge to 100% overnight on off-peak power, then discharge during expensive peak hours. See Charge Scheduling.

The section lists existing schedules; each row shows an up arrow (charge, green) or down arrow (discharge, orange), the name, the time window and SoC target, an enabled/disabled indicator, and a trash button to delete it.

Add Schedule prompts for, in order:

New schedules are created enabled. Backed by GET /api/schedules, POST /api/schedules/save, POST /api/schedules/delete.

8. Inverters

Connect a solar inverter so SETI AI can read live PV/grid/battery power. Pick a Brand, fill in the fields that brand needs, Save, then Test the connection. See Inverter Drivers for the full driver notes.

Panel fields (generic):

Test calls GET /api/energy/solar-inverter?brand=... and reports either the live PV power (connected) or a "not configured / driver pending" note. Settings save under inverter.<brand>.host, inverter.<brand>.api_key, inverter.<brand>.site_id.

Supported brands and what each needs

Brand names are normalized (case-insensitive, dashes/spaces stripped), so Sol-Ark, solark, and SOL ARK all resolve to the solark driver. Any unrecognized brand falls back to the Victron VRM cache.

9. Notification History

A read-only log of the most recent notifications (latest 15 shown), newest first. Each row shows the timestamp, a severity dot (critical red / warning yellow / info blue), the subject, and the delivery status (sent green / failed red / other). Backed by GET /api/notifications/history?limit=15; the full log lives in the notification_log table.

Quick reference — API endpoints

Related pages

• Command Center
• Notifications
• Inverter Drivers
• Charge Scheduling
• AI Agents