Remote admin session
In a MeshCore client that supplies the sender timestamp, sync and then verify:
clock sync
clockMeshCore · temporary preset test
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. A stock node's one-minute temporary test profile then ends on that node's own saved radio settings.
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.
The Companion tempradioat2 scheduler uses UTC Unix time.
Run clock on every Companion 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.
In a MeshCore client that supplies the sender timestamp, sync and then verify:
clock sync
clockCopy this fresh, run it immediately, and then verify with clock:
time 0
clock
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 Companion tempradioat2 schedule again. The
reboot clears any pending scheduled entries.
clkrebootThe Companion 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.
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.
rxtx permits transmission on the second profile;
radio2.cross on copies ordinary Companion traffic across
the primary and temporary profiles.
Stock firmware has no tempradioat command, so a stock node
cannot be queued in advance. Return during the one-hour setup window and
use Option 1. A Companion can use the exact UTC epochs below to switch at
the common start and restore its saved configuration at the common end.
Stock firmware provides tempradio, but not
tempradioat. Use the immediate stock command in Option 1
after its setup window opens.
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.
A stock node can leave an active test as shown below. For a Companion
schedule, the all form removes 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 MeshCore has no normalradio command. This starts a
one-minute temporary session on this page's test profile without
saving over the node's configuration. When that minute ends, the node
restores whatever primary radio settings it had saved.
This replaces the current temporary timeout with 30 minutes, then restores the saved primary tuple automatically.
If get radio2.cross was not auto before the
test, restore that recorded value instead.
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).
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.
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.
tempradio command during the setup window. The Companion scheduling
commands require current full-parser firmware, and
tempradio2 and tempradioat2 require a build with
dual-radio-profile support. If a node reports an unknown command, use only a
method that its installed firmware documents.