Skip to content

Temporary radio test command generator

Use this page to join the shared temporary radio test without overwriting the node's saved primary radio settings. The default window is Monday, September 21, 2026 at 5:00 PM through Wednesday, September 23 at 5:00 PM Pacific time (48 hours), using 910.1 MHz, 500 kHz, SF8, CR7.

The page reads the complete test definition from its URL. Change the query parameters to reuse it for a different window, display time zone, or radio tuple; no source edit is required.

MeshCore · temporary preset test

910.100 MHz / 500 kHz / SF8 / CR7

Scheduled
Starts in — —
Start
End
Display time zone
Firmware epochs

Bridges and early-revert plan

The test will include bridges. If the Puget Sound area experiences a widespread power outage or loss of cellular service, we will end the test early and revert to the normal 910.525 MHz channel.

Before changing a radio

Run get radio and record the saved primary tuple. Both primary TempRadio methods return to that saved tuple; they do not store a return tuple inside the temporary command. On a Companion, also run get radio2 and get radio2.cross so you can restore any non-default secondary-profile setup.

Check the node clock before scheduling

tempradioat and tempradioat2 use UTC Unix time. Run clock on every node and compare it with the browser UTC time below. It should agree to within about a minute. A wrong clock can start late, start immediately, or cause the schedule to be rejected.

Browser UTC now —
Browser Unix time —

Remote admin session

In a MeshCore client that supplies the sender timestamp, sync and then verify: 

clock sync
clock

Local USB or browser console

Copy this fresh, run it immediately, and then verify with clock:

time 0
clock

If the clock is ahead and cannot move backward

If setting the correct time returns ERR: clock cannot go backwards, run the command below. It resets the clock to an older fallback date and reboots the node immediately, so it sends no reply. After the node reconnects, copy and run the fresh local clock command above, verify with clock, and then add the tempradioat schedule again. The reboot clears any pending scheduled entries. 

clkreboot

The schedule must be queued while both its start and end are in the future and within the firmware's roughly 24-day scheduling horizon. Scheduled entries are held in RAM and disappear if the node reboots.

Option 1: switch during the setup window

The immediate commands become available one hour before the official start. Their timeout shrinks so every node still returns at the same end time. Before that setup window, the command text and copy controls stay unavailable.

Stock repeater, room server, or sensor

Primary radio

Companion using both frequencies

Dual profile

rxtx permits transmission on the second profile; radio2.cross on copies ordinary Companion traffic across the primary and temporary profiles.

Option 2: schedule it in advance

Use this only after checking the clock above. The exact UTC epochs are built into the commands, so the node switches at the common start and restores its saved configuration at the common end.

Stock repeater, room server, or sensor

Primary schedule

Companion using both frequencies

Dual-profile schedule

Crossing is saved independently and remains on after the temporary second profile ends. Restore its previous value after the test; auto is the normal default.

Cancel or leave the test

Use the command for the node type and timing. The all forms remove every temporary schedule in that family. To preserve another schedule, first run the corresponding get command and replace all with its displayed entry number.

Stock · before it starts

Stock · while it is running

Leave now · stock compatible

Stock MeshCore has no normalradio command. This reboots the node, which clears TempRadio and returns to its saved radio settings. The command sends no reply; reconnect after the node starts.

Leave in 30 minutes

This replaces the current temporary timeout with 30 minutes, then restores the saved primary tuple automatically.

Companion · before it starts

Companion · while it is running

Leave now

If get radio2.cross was not auto before the test, restore that recorded value instead.

Leave in 30 minutes

These commands clear any absolute second-profile schedule and give the test profile a fresh 30-minute lease. The saved second profile returns at expiry, but crossing remains on; afterward, restore the value you recorded before the test (auto is the normal default).

Build a link for another test

Enter the test times in the selected time zone and choose the radio tuple. The generated URL converts the times to exact UTC instants, keeps the date punctuation readable, and keeps tz so the page displays them in the organizer's local time zone.

Selected time zone Detecting browser time zone…

Loading time zone map…

Click a region to select its IANA time zone. The initial selection comes from tz= when present; otherwise it uses your browser's time zone. Map design inspired by zones.arilyn.cc; boundaries from Timezone Boundary Builder and © OpenStreetMap contributors.
Test radio profile
Open generated page

Advanced use: start and end also accept ISO-8601 timestamps with explicit UTC offsets or Unix epoch seconds. If tz is omitted, the page uses the browser's time zone. The other URL parameters are freq, bw, sf, cr, and estimate-only tx.

The scheduled commands require current full-parser firmware. Companion tempradio2 and tempradioat2 require a build with dual-radio-profile support. If a node reports an unknown command, update it or use only a method that its installed firmware documents.