Start by identifying the task that fails. An offline label, a live-view error, a missing recording and a missing phone alert are different observations. This checklist helps you collect a useful record before following the instructions for your exact Nafnti unit. It does not prescribe a universal reconnect or reset sequence.
Match the unit and its current app
Keep the device label, selected configuration, supplied guide, current app name/version and your account role together. Note the firmware version if it is accessible through an already confirmed view. Do not enter a pairing flow simply to obtain it. Redact serial numbers, network names and account details from public examples.
The table describes the historical guide branches available for this draft. It is not a guarantee that a current batch uses the same app or bands.
| Feeder | App & Wi-Fi | Guide note |
|---|---|---|
| V11 | VicoNature · 2.4 GHz only | Use the instructions supplied with your feeder for hardware-specific steps. |
| V9 | VicoNature · 2.4 GHz only | Use the instructions supplied with your feeder for hardware-specific steps. |
| V8 · Blue or Green | O-kam Pro · 2.4 GHz + 5 GHz | Use the instructions supplied with your feeder for hardware-specific steps. |
| V10 | O-kam Pro · 2.4 GHz + 5 GHz | Use the instructions supplied with your feeder for hardware-specific steps. |
| V5 | VicoNature · 2.4 GHz only | Use the instructions supplied with your feeder for hardware-specific steps. |
| V7 | VicoNature · 2.4 GHz only | Use the instructions supplied with your feeder for hardware-specific steps. |
| Adjustable Camera Feeder | VicoNature · 2.4 GHz only | Use the instructions supplied with your feeder for hardware-specific steps. |
If the actual app is different, keep it on the unmatched-app branch and find the supplied guide. Multiple apps currently coexist. This table does not force a migration or establish an exhaustive app list.
Record the last successful task
Write down the exact message and local time, including the time zone. Avoid replacing an observed message with a diagnosis such as “the cloud is down.”
| What you observe | Useful next record | Follow-up branch |
|---|---|---|
| Setup has never completed | The last confirmed setup stage and matching guide | First setup |
| Device shown offline | Status/message, time and observable power condition | Continue this checklist; keep the cause open |
| Shown online, live view fails | The error and the last successful live-view attempt | Same-device comparison below |
| Live view works, clip absent | Visit time, recording mode/path if known, and where you looked | Missing-visit checks |
| Clip exists, phone alert absent | Clip time and actual notification observation | Matched app notification branch in missing-visit checks |
| Clip plays, saving fails | Source of playback and exact failed saving action | Saving/export guide |
An online label is not a completed live-view test. An alert is not a saved recording, and an AI label is not evidence that every stage worked.
Separate a phone check from a camera check
A phone can provide an initial indication that a network and Internet path are usable. Check which connection it is actually using; mobile data can make that observation irrelevant to the feeder's Wi-Fi route. A working phone still does not establish the camera's supported band, authentication, radio behavior or app access.
Cisco explains the wireless network connection and the router's Internet role. Intel's general Wi-Fi checks distinguish network/Internet checks and environmental factors. These explain why the observations should be kept separate. Intel's computer-driver and router-setting procedures are not Nafnti camera instructions.
Record the confirmed requirements for your unit before requesting a network change. Do not turn off security, assume every unit is 2.4 GHz-only or dual-band, or buy network equipment on the strength of this checklist.
Compare supported tasks at two permitted positions
If initial setup already works and the matching handling instructions allow moving the unit, compare the same camera at a known-working position and at the proposed site. Keep the app, account role and supported task the same. Preserve the approved power arrangement; do not improvise an extension or leave the unit unsecured.
Use the blank connection-stage comparison log:
- Record the time and position, and any other condition that changed.
- Check the device status, then live view if supported. Record the actual result separately.
- End live view before observing a later event if the matching instructions require it. Historical Vico Nature material for V9/V11 says viewing can interrupt motion/event behavior; do not impose that rule on O-kam Pro or another app.
- If a supported test clip exists, check the expected recording path. Record “not checked” when a step is not performed or unavailable.
- Repeat the relevant comparison when practical. A changed result helps scope the next question; it does not isolate distance, interference, power or a service fault by itself.
Keep the glass, framing and access review alongside this test. A successful live view is not approval to install at an unsuitable site.
Keep recording and service questions on their own branches
For historical O-kam Pro examples, use the O-kam missing-visit reference. For historical Vico Nature examples, use the Vico Nature reference. An unrecognized app belongs on the unmatched reference.
Do not assume that subscribing, formatting a card, deleting clips, changing accounts, unbinding or resetting is the next step. First match the recording source, permissions and the instructions for that operation. A card slot alone does not prove recording, playback or export without Wi-Fi or Internet. Current cloud availability, retention and identification behavior need their own evidence in the service-by-model reference.
Prepare a focused support question
Keep your record short: exact configuration and app version, last successful task, failed task/message, local time, recording path if known, and the two-position comparison if performed. Share private device/account details only through an appropriate support channel, not a public comment or social post.
Ask about the unresolved stage: “This unit opens live view at position A, but displays this message at B under the recorded conditions. Which matched next check applies?” If there is a wet or damaged connector, damaged seal or a cover that cannot close, pause charging and outdoor reinstallation and use the charging reference.
This draft contains no actual device test results. Current band/security support, reconnect/reset actions, offline recording and charging conditions remain explicitly open where the unit has not been matched.