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.
+ test early. A stock node's one-minute temporary test profile then ends
+ on that node's own saved radio settings.
@@ -65,10 +66,10 @@ tuple; no source edit is required.
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.
+ 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.
@@ -108,8 +109,8 @@ clock
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.
+ and then add the Companion tempradioat2 schedule again. The
+ reboot clears any pending scheduled entries.
clkreboot
@@ -117,9 +118,10 @@ clock
- 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.
+ The 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.
@@ -160,22 +162,25 @@ clock
-
Option 2: schedule it in advance
+
Option 2: schedule a Companion 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 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 repeater, room server, or sensor
- Primary schedule
+ No advance schedule
-
-
-
+
+ Stock firmware provides tempradio, but not
+ tempradioat. Use the immediate stock command in Option 1
+ after its setup window opens.
+
@@ -197,28 +202,24 @@ clock
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.
+ 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 · 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.
+ 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.
Leave in 30 minutes
@@ -385,7 +386,9 @@ clock
-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.
+Stock firmware does not support advance TempRadio scheduling; use its immediate
+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.
diff --git a/mkdocs.yml b/mkdocs.yml
index f19d8731..2217f561 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -30,4 +30,4 @@ extra_javascript:
- _javascript/telemetry_decoder.js
- _javascript/management_decoder.js
- _javascript/filter_tool.js
- - _javascript/preset_test.js?v=20260916-5
+ - _javascript/preset_test.js?v=20260919-1
diff --git a/test/test_preset_test.js b/test/test_preset_test.js
index d3aea8df..17b87487 100644
--- a/test/test_preset_test.js
+++ b/test/test_preset_test.js
@@ -13,6 +13,10 @@ assert.doesNotMatch(
pageSource,
/tempradioat<\/code> command/);
+assert.doesNotMatch(pageSource, /data-command="stock-scheduled"/);
+assert.doesNotMatch(pageSource, /Stock · before it starts/);
+assert.doesNotMatch(pageSource, /Normal return profile/);
const query =
"?start=2026-09-21T17:00:00-07:00" +
@@ -73,10 +77,8 @@ assert.strictEqual(tool.remainingMinutes(config, setupOpens), 2940);
const commands = tool.commandsFor(config, active);
assert.strictEqual(commands.stockNow, "tempradio 910.1,500,8,7,2880");
-assert.strictEqual(
- commands.stockScheduled,
- "set tempradioat 910.1,500,8,7,1790035200,1790208000\nget tempradioat"
-);
+assert.strictEqual(commands.stockScheduled, undefined);
+assert.strictEqual(commands.stockCancelBefore, undefined);
assert.strictEqual(
commands.companionNow,
"set radio2.cross on\nset tempradio2 910.1,500,8,7,rxtx,2880"
@@ -90,7 +92,7 @@ assert.strictEqual(
assert.strictEqual(commands.stockLeaveIn30, "tempradio 910.1,500,8,7,30");
assert.strictEqual(
commands.stockCancelDuring,
- "reboot"
+ "tempradio 910.1,500,8,7,1"
);
assert.strictEqual(
commands.companionLeaveIn30,
@@ -178,6 +180,10 @@ assert.strictEqual(
tool.commandsFor(changed, changed.startMs).stockNow,
"tempradio 915.25,125,10,5,2880"
);
+assert.strictEqual(
+ tool.commandsFor(changed, changed.startMs).stockCancelDuring,
+ "tempradio 915.25,125,10,5,1"
+);
const shared = new URL(tool.configuredUrl(
changed,