WEBVTT

1
00:00:00.050 --> 00:00:09.050
This maintenance lab uses activation by personalization, with separate server enrollments for the two sensor models.

2
00:00:11.600 --> 00:00:20.600
This model exposes reporting intervals in seconds and has no local console action in this interface.

3
00:00:24.600 --> 00:00:32.600
This model uses milliseconds for its local report interval and provides a local console.

4
00:00:35.200 --> 00:00:42.200
Deep sleep keeps the sensor powered on while stopping its radio work.

5
00:00:46.350 --> 00:00:53.350
Wake the sensor, then send a fresh uplink to confirm application delivery.

6
00:00:56.000 --> 00:01:03.500
Powering the sensor off is a separate action; its saved configuration remains available.

7
00:01:07.400 --> 00:01:15.400
Power it on and verify both its saved interval and a fresh application report.

8
00:01:20.150 --> 00:01:30.650
Clone the sensor to create an independent device with a new identity; the copy needs its own server enrollment.

9
00:01:33.750 --> 00:01:42.250
Change the copy’s report interval and confirm that the original sensor keeps its own setting.

10
00:01:48.700 --> 00:01:57.200
Open the local console and complete its password challenge privately before querying the report interval.

11
00:02:04.900 --> 00:02:15.900
Query the current interval, set a three-minute value and query it again; device settings show the same value in milliseconds.

12
00:02:19.100 --> 00:02:27.600
Relock the console using the command shown here; reopening the terminal requires another password challenge.

13
00:02:46.450 --> 00:02:55.200
Reboot also locks existing console access; configuration survives, but another unlock is required.

14
00:03:06.750 --> 00:03:17.250
Reopen the saved lab and verify the sensor measurements; the original and its independent copy retain their separate settings.
