Maintain LoRaWAN sensors and use the local UART This maintenance lab uses activation by personalization, with separate server enrollments for the two sensor models. This model exposes reporting intervals in seconds and has no local console action in this interface. This model uses milliseconds for its local report interval and provides a local console. Deep sleep keeps the sensor powered on while stopping its radio work. Wake the sensor, then send a fresh uplink to confirm application delivery. Powering the sensor off is a separate action; its saved configuration remains available. Power it on and verify both its saved interval and a fresh application report. Clone the sensor to create an independent device with a new identity; the copy needs its own server enrollment. Change the copy’s report interval and confirm that the original sensor keeps its own setting. Open the local console and complete its password challenge privately before querying the report interval. Query the current interval, set a three-minute value and query it again; device settings show the same value in milliseconds. Relock the console using the command shown here; reopening the terminal requires another password challenge. Reboot also locks existing console access; configuration survives, but another unlock is required. Reopen the saved lab and verify the sensor measurements; the original and its independent copy retain their separate settings.