Skip to content

Commit 5b70fe1

Browse files
authored
Merge branch 'docusaurus-version' into auto-translate/pr-4245
2 parents 140d83f + 329c8b1 commit 5b70fe1

File tree

1 file changed

+84
-0
lines changed

1 file changed

+84
-0
lines changed

sites/en/docs/Network/Meshtastic_Network/Wio_Tracker_L1/get_started_with_wio_tracker_l1.md

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -337,6 +337,90 @@ If you want to restore to the default settings, you can do the factory reset. Th
337337
- Click the `Factory Reset` Button on the App. The device will reboot with the factory configuration automatically.
338338
<p style={{textAlign: 'center'}}><img src="https://files.seeedstudio.com/wiki/SenseCAP/Meshtastic/Factory.png" alt="pir" width={400} height="auto" /></p>
339339

340+
### NodeDB Reset
341+
342+
NodeDB is the local database that stores information about nodes discovered in the current Mesh network, including:
343+
344+
- **Node ID**
345+
- **User Name**
346+
- **Location Information**
347+
- **Signal Information (SNR)**
348+
- **Last Seen Time**
349+
350+
**When to reset**
351+
352+
Reset NodeDB when:
353+
354+
- The node list contains outdated, duplicate, or invalid entries.
355+
- You move to a different Mesh environment and want to rediscover nearby nodes.
356+
- Node information in the app appears incorrect or incomplete.
357+
358+
:::danger
359+
Resetting NodeDB only clears the node database stored on the device. It **does not perform a factory reset** and **does not remove the device's basic configuration**.
360+
:::
361+
362+
**Method 1: Reset from the Device**
363+
364+
1. Open the menu on the device.
365+
2. Go to **Node Actions / Settings**.
366+
3. Select **Reset NodeDB**.
367+
4. Confirm the reset.
368+
369+
**Example Screens**
370+
371+
Step 1: Press the device button to enter the menu.
372+
373+
<p style={{textAlign: 'center'}}><img src="https://files.seeedstudio.com/wiki/SenseCAP/wio_tracker/L1nodeDB1.png" alt="Device button to enter the menu" width={300} height="auto" /></p>
374+
375+
Step 2: Find `Reset NodeDB` in the menu.
376+
377+
<p style={{textAlign: 'center'}}><img src="https://files.seeedstudio.com/wiki/SenseCAP/wio_tracker/L1nodeDB2.png" alt="Reset NodeDB option in the device menu" width={300} height="auto" /></p>
378+
379+
**Method 2: Reset from the App**
380+
381+
1. Open the app and connect to the target device.
382+
2. Go to **Settings**.
383+
3. Tap **Device**.
384+
4. Scroll to the bottom of the **Device Config** page and find **Reset NodeDB**.
385+
5. Tap it and confirm the action.
386+
387+
**App Path**
388+
389+
`Settings > Device > Reset NodeDB`
390+
391+
**Example Screens**
392+
393+
Step 1: Open **Device** from the **Settings** page.
394+
395+
<p style={{textAlign: 'center'}}><img src="https://files.seeedstudio.com/wiki/SenseCAP/wio_tracker/L1nodeDB3.png" alt="Device entry in Settings" width={300} height="auto" /></p>
396+
397+
Step 2: Tap `Reset NodeDB` on the **Device Config** page.
398+
399+
<p style={{textAlign: 'center'}}><img src="https://files.seeedstudio.com/wiki/SenseCAP/wio_tracker/L1nodeDB4.png" alt="Reset NodeDB button in Device Config" width={300} height="auto" /></p>
400+
401+
:::tip
402+
Please note the difference between the following options:
403+
404+
- **Reset NodeDB**: Only clears the node database.
405+
- **Factory Reset**: Restores the device to factory settings and removes more configuration data.
406+
:::
407+
408+
**What happens after reset**
409+
410+
After **Reset NodeDB** is executed, the device clears the currently stored node list. As the device continues running, it will rediscover and record nearby nodes again.
411+
412+
You may observe the following:
413+
414+
- The node list may temporarily become empty or smaller.
415+
- Nodes will gradually reappear as the device continues operating.
416+
- Previously stored historical node records will no longer be available.
417+
418+
**Notes**
419+
420+
- Before resetting, make sure the issue is actually related to an abnormal node list.
421+
- If the problem is only a delay in node display, wait for a while first to see whether it recovers automatically.
422+
- If the issue remains after resetting NodeDB, continue troubleshooting the device configuration or other possible causes.
423+
- Use **Factory Reset** carefully to avoid accidentally removing device configuration.
340424

341425
### Signal Quality
342426

0 commit comments

Comments
 (0)