--- title: Nile Field Notice: NFN-2025-08-08 slug: nile-field-notice-nfn-2025-08-08 createdAt: 2025-08-07T11:16:57.902Z --- ** Notice ID:** NFN-2025-08-08 **Date Issued:** 8th Aug, 2025 **Priority Level:** ⚠️ Critical **Applies To:** SEs | CSEs | Field Architects | PNEs | SDMs | Partners | Customers ** Applicable Nav App Version: **1.3.0 :::Heading{depth="3" indent="1"} **1.** **Summary** ::: NFN-2025-08-08 addresses the following: :::Paragraph{indent="1"} **1.1.** **Two system issues** have been recently identified: ::: :::Paragraph{indent="2"} ** 1.1.1.** NSW200: VHE macaddr calculation issue ::: :::Paragraph{indent="2"} **1.1.2.** NSW1000 HW Version 3.1: Board\_ID Discrepancy Issue ::: :::Paragraph{indent="1"} These issues are resolved automatically via BLE commands as you use **“Device Update” → “Check for Updates” in the Nile Nav app when prompted**. This step is **mandatory**. Important: To ensure the fixes remain effective, **do not perform a Factory Reset afterward**. Performing a reset will undo the applied fixes. ::: :::Paragraph{indent="1"} **1.2.** BLE support for NSW200 is different from all other platforms and is not fully implemented in the Nile Nav mobile app. User intervention is required when interacting with NSW200 devices during the following workflows: ::: :::Paragraph{indent="2"} ** 1.2.1. Device Update** ::: :::Paragraph{indent="2"} **1.2.2. Troubleshooting** ::: :::Paragraph{indent="1"} To ensure proper communication with the intended NSW200 device, **users must **ensure that **BLE dongle is plugged into only one of the NSW200s being activated at a time and manually select the correct BLE dongle** within the app during these flows and failure to do so may result in unsuccessful device pairing or communication issues. ::: :::Paragraph{indent="1"} **1.3.** While activation, if an **Access Switch (AS) still contains an old bringup.json configuration** and was deactivated without performing a factory reset at that point in time, the switch may fail to connect to the cloud, leading to disruption for additional devices on the same NSB. ::: :::Paragraph{indent="1"} To resolve this case, the user must check if an old bringup configuration exists on the   device via the app & if yes, manually perform a factory reset on the affected switch. ::: ### 2. Impact **2.1.** The system issues outlined in Section 1.1 affect the activation process for **all NSW200** and **NSW1000 devices with hardware version 3.1**. **NSW200 1.1.1** issue applies only when NSW200 is being used as a **Gateway (GW)**. **NSW1000 1.1.2** issue applies regardless of device role—whether the unit is deployed as a **Gateway (GW) or non-Gateway (non-GW)** **2.2.** **Manual BLE dongle selection**, as described in Section 1.2, is required for **all BLE interaction with NSW200 units **regardless of whether NSW200 is configured as **Gateway (GW) or non-Gateway (non-GW)**. This affects any Bluetooth-based interaction between the Nile Nav and the NSW200, including—but not limited to—BLE commands issued during the following workflows: **2.2.1.** **Device Update** **2.2.2. ** **Troubleshooting** ### 3. Actions Required Please find below steps to follow to address above issues: **3.1.** **Steps for NSW1000 activation with system issue fix** **3.1.1. ** When prompted during activation, always tap “Check for Updates” in the Device Update window. This step is mandatory to apply the system fix; do not skip or cancel. Nav app will automatically identify the Device Update commands to run for HW version 3.1. **3.1.2.** After updates complete, tap “Done”, then proceed to the next screen. **3.1.3.** When being used as a Gateway, on “Factory Reset Status Check” step, tap “NEXT” to SKIP the factory reset step. Do not proceed with a factory reset, as skipping this keeps the update in place.   **3.2. Steps for NSW200 activation with system issue fix** **3.2.1.** Only plug the BLE dongle into a single NSW200 device at a time during activation. **3.2.2.** When prompted during activation with “Device Update” pop-up, “Cancel” for now but to be revisited later **3.2.3.** Select the correct BLE dongle using “Select Dongle” or enter manually. **3.2.4.** Once done, the Device Update window will reappear. Now, tap “Check for Updates” to apply the fix. Do NOT skip or cancel this “Device Update” after dongle selection; skipping may cause issues with device activation. **3.2.5.** After updates, tap “Done” followed by “Next”. **3.2.6.** This applies to only when NSW200 is being used as a Gateway. On “Factory Reset Status Check”, tap “NEXT” to SKIP factory reset and keep the fix. Do not tap on “Proceed” **3.3.** **Manual BT Mac Entry for NSW200 troubleshooting** **3.3.1.** Until dongle selection capability is fully implemented for NSW200 in Nav, please either use manual entry to update the BT mac in the existing QR or re-generate new QR using the BT mac for the BLE dongle to connect to NSW200 **3.4.** **Access Switch with old bringup.json fails to connect to cloud** **3.4.1.** Navigate to activation In-progress screen on Nile Nav app **3.4.2.** Tap on “Troubleshoot” option **3.4.3.** Run the “Check NSB GW config” command. The command returns “GW Config exists” if an old bringup.json configuration is leading to cloud connectivity failure else it returns “GW Config does not exist” **3.4.4.** If “Check NSB GW Config” response is “GW Config Exists”, run the command labelled “6.1.1 Switch Factory Reset” for a manual factory reset **3.4.5.** Post a successful factory reset, device should automatically be able to connect to cloud and proceed with activation **3.4.6.** You may check factory reset status via troubleshoot command “6.1.8 to check factory reset status (In-progress/completed)” and check whether factory reset is required or not using troubleshoot command “6.1.6 check factory reset required (FALSE = FR done and no longer required; TRUE = FR still required)” ### 4. Next Steps / Resolution Plan **4.1. ** Re-sequencing the Nile Nav activation workflow and “Device Update” to be made mandatory. **4.2. ** BLE dongle selection in Nav for both “Device Update” and “Troubleshooting”. **4.3.** Include bringup.json presence check & removal in pre-activation device update. ### 5. Contact / Escalation Support Email: support\@nilesecure.com **Note:** All partners and field teams are requested to adhere to the above SOP to prevent Nile gateway activation failures until Nile Nav updates are released.