On air

—

Up next

WeBot last said

Nothing yet.

Stream server

CPU (container)—

Memory (server)—

Container: —
Sending: —
Quality: —
Load: —
Disk: —
Server up: —
Chat: —

Recent stream log

Show control

Costume

Talk

Voice

Show Radio

Chat

Weather

—

0TORNADO

0SEVERE

0FLASH FLOOD

0WATCHES

Snapshot Every 30 s

Press “Take snapshot” to see the stream right now.

Earlier on the stream

WeBot’s brain

What WeBot says, how long segments last, how chat works and what the radio plays. Saving sends it straight to the stream: no restart.

Loaded from the stream

Stream server

Picture quality, keys and access for the cloud server. Settings take effect after a restart (the stream blips for about a minute).

Picture quality

The map is drawn without a graphics card, so resolution costs a lot of CPU. On the current 4-core plan, 720p is the safe maximum; 1080p needs the 8-core plan (and Stream CPUs set to 6).

Server actions

Applies settings. About 1 minute off air.

Rebuilds with the code already on the server.

Who can open Live Control

All settings (.env) secrets stay hidden until you press Show

Code

Everything that runs the stream. Saving checks the code for mistakes and keeps a backup. Deploy sends your changes to the server.

Changed only

Pick a file

Files marked M are changed since the last saved version.

Logs

What the stream server is printing.

Live

Checks

Quick tests for when something seems off.

Connections

Can Studio reach the server, Live Control and the public status page?

Audio

Records 15 seconds of the stream’s sound and looks for dropouts (sputtering).

Mark server up to date

Tells Studio the server already has the code you have now (use after deploying by hand).

Help

Starting Studio

Double-click WeBot Studio on your desktop or open it from the Start menu (WeatherPower folder). It is its own program window; close it to stop Studio. The stream keeps running either way. If the program ever goes missing, run npm run build in the project's desktop folder to put it back (the old studio\WeBot Studio.cmd still works too and opens Studio in your browser).

Changing what WeBot says and does

Use Brain. Lines with {city} or {name} get the city or viewer’s name filled in. Segment weights decide how often each one comes up on calm days (0 turns it off). Press Save to stream: the stream picks it up within seconds. Reset all to defaults puts everything back the way it was built.

Live show buttons

The Overview’s Show control does the same as Live Control: skip, BRB, talk on/off, radio style, make WeBot say something.

Picture quality and keys

Server holds the stream settings (resolution, bitrate, YouTube keys). Save, then Restart stream. Every save keeps a backup of the old settings on the server (.env.bak-…, last 10).

Editing code

Open Code, pick a file, edit, press Ctrl+S. Studio checks it for mistakes and keeps a backup in studio\.backups.
Press Save version with a short note (this is a git commit, so you can always go back).
Press Deploy to server. Page-only changes go live with a quick page reload; anything else rebuilds the stream (about 1–2 minutes off air).

Broke something? In Code, Undo my changes puts a file back to the last saved version. To go back further, use History and deploy again.

If the stream looks wrong

Map blank or frozen: Reload stream page.
Sound sputtering: run Checks → Audio; if CPU is near its limit, lower the quality in Server.
Nothing works: Restart stream. Then check Logs → Problems.
Studio can’t connect: your home internet address may have changed. Add it on the server page from another network’s SSH, or ask for help.

Where things live

Brain settings: /opt/weatherpower/data/webot-brain.json on the server.
Stream settings: /opt/weatherpower/.env on the server.
Code: this project folder (git). Studio itself: studio\.