What changed
Confirm the ROMO 2 model, actual firmware and DJI Home mode entry first. DJI says enabling it keeps maps, images and other navigation/obstacle-avoidance data stored and processed on the robot, with core cleaning, customization and docking continuing offline. First mapping still involves an internet connection. Remote access, third-party automation and deletion of historical cloud records require separate evidence.
A September promise reaches an availability milestone in October
The October 29 release in DJI’s European newsroom makes Local Data Mode available first on ROMO 2 with the latest firmware supporting it, under Device Settings → Security Settings in DJI Home. Retain that event date rather than presenting this November 3 article as the feature’s launch.
This is not a renamed September launch story. The September 3 release supplied by DJI described the option but explicitly deferred availability until later in the year. October 29 adds a supporting-firmware and settings-entry milestone. It does not promise simultaneous delivery to every older ROMO model.
Preserve the meaning of each stage
- September 3
ROMO 2 launch preview
Local Data Mode was due later in the year, rather than delivered at that point.
- October 29
Mode availability announced
ROMO 2 needs supporting firmware and activation in Security Settings.
- November 3 check
Official materials reviewed
We have not installed firmware or operated the robot. A particular unit still needs its version and entry checked.
Separate first mapping, switching modes and routine cleaning
The ROMO page in DJI’s Trust Center describes an internet connection for mapping at first power-on. Activating Local Data Mode then disconnects DJI Home from the internet and keeps maps, images and associated data stored and processed on ROMO. That sequence distinguishes later local processing from a never-online requirement.
DJI says core navigation and obstacle avoidance continue without internet. The October release also lists starting and customizing cleaning and returning to the dock. These are manufacturer descriptions, not our measurements of cleaning, connection paths or network traffic, and they do not establish retention of every connected function.
| Stage | Official description or bounded scope | What to check |
|---|---|---|
| Initial preparation | First mapping connects online; install firmware supporting the mode | Model, firmware and setup path; this is not a never-online claim. |
| Enable Local Data Mode | Activate in Security Settings; DJI describes app disconnection and local processing | Actual mode state; treatment of existing cloud records needs a separate answer. |
| Routine local cleaning | Core navigation, avoidance and listed cleaning/docking capabilities continue offline | The needed operation actually completes; do not extend core capability to every remote function or automation. |
Four household requirements cannot share one supported label
The household, requests and decisions below are an original editorial exercise, not user feedback. It has a ROMO 2 with firmware still to be checked. One person wants cleaning during the day, another wants to inspect home from the office, and the family also requests never-online operation and removal of all historical cloud data. Each has a different acceptance object.
The reference decision is to evaluate local core cleaning after initial setup on a supported unit. The other requests do not pass with it. If never online is mandatory, the current description does not support the plan. If viewing from outside the home is the essential task, confirm its relationship with the mode before adopting it.
| Household request | Reference decision | Evidence needed next |
|---|---|---|
| Required local cleaning after initial setup | Described by DJI; not yet verified on this unit | Supporting firmware, mode state and an actual record of the needed cleaning/docking task. |
| The device has never connected online | Does not match the stated first-mapping connection | Reconsider the plan if mandatory; later local processing cannot satisfy it retroactively. |
| View or control home from the office | Not established by the mode description; app disconnection matters | Support for the specific remote function and authorization path; do not promise unchanged operation. |
| Delete every existing cloud record | A mode switch is not historical deletion evidence | Separate information or confirmation about record scope, deletion operation and result. |
Unverified does not assert that a function can never work. It identifies missing device evidence and avoids adding a promise the source has not supplied.
Photo display, obstacle avoidance and sharing control different things
The Trust Center separately explains that On-Site Photo controls whether obstacle images are uploaded to the app for display; turning it off does not disable obstacle detection or avoidance. It is not another name for Local Data Mode. Reducing a particular image display and changing map/other-data processing paths require separate settings, rather than simply checking that a photograph disappeared.
The distinction between Samsung fridge recognition and actual stock offers an adjacent lesson: seeing or not seeing a particular display does not establish the underlying task. In this ROMO case, image display, sensing and data processing occupy different layers.
Household permissions also need a separate check. DJI says device sharing does not automatically grant access to remote video and real-time photos; the receiving user needs in-person QR authorization with the primary holder through DJI Home. That sharing rule does not establish that remote viewing continues in Local Data Mode. Confirm access rights and mode-supported functions independently. Our shared-home-device privacy case helps list people, content and scenarios separately.
Ask three separate questions
How is data handled?
Inspect mode, initial preparation and subsequent storage/transmission, rather than only whether a picture appears.
Which display is disabled?
Keep On-Site Photo’s object precise; it does not establish disabled sensing or deletion of every record.
Who can view, in which mode?
Sharing authorization and operating mode are separate conditions. Passing one does not answer the other.
Keep a minimal acceptance record before adopting the mode for daily work
We have not operated a robot. The proposed record below deliberately leaves actual results unexecuted; it is not proof that the mode has passed in your home. Evaluate the actual unit using manufacturer instructions rather than substituting another model, someone else’s screenshot or a similarly named setting.
Record the model, firmware and app version, verify the actual entry and mode state, then use a supported control method to complete one needed cleaning and docking task. Keep expected and actual results plus failures. If remote control or a third-party integration is essential, obtain its own support information and acceptance evidence; a successful core-cleaning task cannot certify those processes.
Goal: evaluate local core cleaning after initial setup.
Model: to verify
Device firmware / DJI Home version: to record
Actual entry: Device Settings → Security Settings → Local Data Mode (to verify)
Mode state: not executed
Needed task: one cleaning and docking task; confirm the supported operation method for this unit
Manufacturer expectation: the named core capabilities continue offline
Actual result: not executed; do not mark passed
Separate open questions: remote access, sharing rights, third-party integration and existing cloud recordsOne operation record covers that task only. We have not captured packets, independently certified security or tested every mode combination.
Adopt an operating mode, not an unconditional privacy guarantee
If initial online preparation is acceptable and later local core cleaning is the main task, this is a concrete change worth evaluating on a supported device. If never-online operation, continuing remote viewing or proof of historical cloud deletion is essential, retain those conditions in the decision and obtain their evidence before choosing a mode.
The materials come from DJI’s European newsroom and public Trust Center. A region-routed URL on the latter does not establish retail, firmware or account availability throughout that country. The October release supplies no universal firmware number or country-by-country list we can verify here. Older ROMO support and the combinations of particular Matter or cloud functions are outside this local-cleaning reference answer.
We do not use an industry-first label as a purchasing argument or turn the vendor’s security discussion into a promise that a product cannot have problems. Retaining the task, satisfied conditions and unknowns shows which part of the choice this update actually improves.
