ZAQ 8-12 Bulb Camera Setup, Wiring, JXLCAM App Pairing, Faults, and ONVIF Support

User question

bezplatny softver pre tuto kameru ZAQ 8-12

Artificial Intelligence Response

Direct answer to the question

• The free software used most often for the ZAQ 8-12 “bulb” camera is JXLCAM (Android/iOS). Some units instead require V380 Pro or iCam365. Use the app printed on the camera label or manual; basic functions are free (live view, SD-card recording, motion alerts). Cloud storage, if offered, is optional and paid.
• For PC viewing: if your unit is a V380 variant, use the free V380 PC client. If it’s a JXLCAM variant (common) and there is no official PC app, use ONVIF/RTSP–capable free tools (when supported) or run the mobile app inside a free Android emulator.

Key points

• Identify the correct app by QR code/label or by the camera’s temporary Wi‑Fi SSID during pairing (e.g., “IPC-JXLCAM…”, “MV…”, “iCam365…”).
• Works only on 2.4 GHz Wi‑Fi. Core apps are free; avoid paying for cloud unless you want it.
• Some units expose ONVIF/RTSP (then you can use VLC/Agent DVR/ONVIF Device Manager); many do not.

Detailed problem analysis

• Generic model family: “ZAQ 8-12” is a generic “panorama bulb” camera sold under many names. Hardware looks similar, but firmware differs. The firmware determines the required mobile app and whether open standards (ONVIF/RTSP) are available.
• App-to-firmware coupling: You cannot pick software arbitrarily; you must use the family the device was built for. Most units sold as ZAQ 8-12 pair with JXLCAM. Others ship with V380 Pro or iCam365 firmware. Less commonly, YCC365 Plus or Tuya/Smart Life variants exist.
• Mobile-first workflow: Initial onboarding (Wi‑Fi credentials, password, timezone) is always done via the mobile app. After first setup, you can explore PC/NVR viewing if the camera supports ONVIF/RTSP.
• PC viewing paths:
  • V380 firmware: vendor’s free V380 PC client (multi‑camera CMS).
  • JXLCAM firmware: typically no official Windows client. If ONVIF/RTSP is present, use free third‑party tools (VLC, Agent DVR/iSpy, ONVIF Device Manager). If ONVIF/RTSP is absent, use an Android emulator (BlueStacks/LDPlayer) and run the mobile app on your PC.
• “BulbCam” desktop utilities: Some Windows programs called “BulbCam” exist for certain vendor bundles. They are not universal and may be outdated or not truly free. Treat them as vendor-specific, not a guaranteed solution for ZAQ 8‑12.

Current information and trends

• Most recent user reports and quick guides point to JXLCAM as the primary free app for ZAQ 8‑12, with pairing done via QR or AP/Hotspot mode on 2.4 GHz Wi‑Fi and with all phone permissions enabled during setup.
• Community experience shows a minority of units need V380 Pro or iCam365 instead; the label/QR and the SSID broadcast in AP mode are the best indicators.
• Windows “BulbCam” viewers exist but are inconsistent across vendors; core mobile apps remain the supported, free baseline.

Supporting explanations and details

How to identify the correct free app

• Check the camera’s label, packaging, or manual for the app name/QR.
• Reset the camera (hold RESET ~10–12 s until voice prompt). During pairing, the camera creates a temporary Wi‑Fi SSID; its pattern usually reveals the app family:
  • “IPC-JXLCAM-xxxx” → JXLCAM
  • “MV-xxxx” → V380 Pro
  • “iCam365-xxxx” → iCam365
  • “CLOUDCAM-xxxx” → YCC365 Plus
• Install the indicated app from the official store (Google Play / App Store). Core functionality is free.

Recommended free mobile apps (use the one your unit requires)

• JXLCAM (most common for ZAQ 8‑12)
• V380 Pro
• iCam365
• YCC365 Plus (some clones)

Pairing checklist (works similarly across the apps)

• Power the bulb cam in an E26/E27 socket (avoid dimmers).
• Wait ~30–40 s for the “waiting for network” voice prompt; if absent, perform a reset.
• Ensure you are on 2.4 GHz Wi‑Fi, not 5 GHz. Keep phone, router, and camera within a few meters during onboarding.
• App → Add device → choose QR mode (show QR to the lens, phone brightness max) or AP/Hotspot mode (connect to the camera’s SSID, then provide your home Wi‑Fi credentials).
• After connecting, immediately set a strong device password, set timezone, and if desired insert/format a microSD (Class 10, up to 64–128 GB depending on firmware).

Free PC/NVR options (if your unit exposes ONVIF/RTSP)

• ONVIF Device Manager (Windows): discovers the camera, shows profiles/RTSP URLs.
• VLC Media Player: open network stream for quick live view.
• Agent DVR / iSpy (free for local use): multi‑camera recording/alerts.
• Typical RTSP paths (examples; vary by firmware):
  • rtsp://[camera-ip]:554/live/ch0
  • rtsp://[camera-ip]:554/h264/ch1/main/av_stream
  • Credentials are usually the username/password you set in the app. If ONVIF/RTSP is not available
• Use a free Android emulator on Windows and run the required mobile app there.

Troubleshooting

• “Device offline” during add: wrong app family or wrong Wi‑Fi band. Verify app by label/SSID; force 2.4 GHz; move closer to router.
• QR won’t scan: increase phone brightness, reduce glare, hold 15–25 cm from lens, retry.
• App cannot find camera: allow camera/location/storage permissions in the phone OS; temporarily disable mobile data during onboarding.
• Stuttering video: check RSSI (aim for stronger than −70 dBm), switch router channel, or use wired AP closer to the camera.

Ethical and legal aspects

• Change default credentials; avoid exposing the camera to the internet via port forwarding. Prefer LAN-only or vetted cloud access.
• Place cameras responsibly. In the United States, audio recording and recording in private areas are restricted by state and federal laws; obtain consent where required and post notices as appropriate.
• Keep firmware up to date; segment IoT devices on a guest/VLAN network for privacy.

Practical guidelines

• Start with the label-driven app (likely JXLCAM). Complete setup, then test for ONVIF/RTSP with ONVIF Device Manager.
• If ONVIF/RTSP exists, integrate with VLC/Agent DVR for free desktop viewing/recording.
• If not, use an Android emulator for PC viewing.
• Use a quality microSD (e.g., 32–64 GB, Class 10) for free loop recording; enable motion-triggered recording to extend retention.
• Avoid third‑party APK sites; install only from official app stores.

Possible disclaimers or additional notes

• Not all ZAQ 8‑12 units support ONVIF/RTSP. Some are cloud‑only via their app.
• Do not attempt to flash firmware from a different app family (e.g., V380 firmware onto a JXLCAM unit); this can permanently brick the device.
• “BulbCam” Windows programs found online are vendor-specific and may not be truly free or compatible with your unit.

Suggestions for further research

• Check the exact text on your camera’s sticker/QR (or the SSID after reset) to confirm the app family.
• After setup, open the app’s device info/advanced settings and look for ONVIF/RTSP toggles or stream URLs.
• Use your router’s DHCP client list to note the camera’s IP address for ONVIF/RTSP testing.

Brief summary

• Install the free app required by your camera’s firmware—most ZAQ 8‑12 units use JXLCAM; some use V380 Pro or iCam365. Core features are free; cloud storage is optional.
• For PC viewing, use the V380 PC client (if V380 firmware), or ONVIF/RTSP with free tools (VLC/Agent DVR) when available. If unsupported, run the mobile app inside a free Android emulator.
• Prioritize security (strong password, updates, VLAN) and follow local recording laws.

If you can share a photo of the label/QR or the temporary Wi‑Fi name the camera broadcasts after reset, I’ll tell you exactly which free app to use and the quickest pairing method.

User question

PTZ kod bullcam ZAQ8-12

Artificial Intelligence Response

Direct answer to the question

• There is no PTZ “code” (Pelco‑D/P, RS‑485 address, etc.) for the BULBCAM ZAQ8‑12. It is an IP camera; PTZ (if the hardware supports it) is controlled digitally via the mobile app or over ONVIF from an NVR/VMS.
• If you are adding it to a DVR/NVR or PC software, select ONVIF, not analog PTZ.
  • Protocol: ONVIF (Profile S; try Profile T if available)
  • Port: 8899 or 80 are most common on these firmwares; some variants use 5000 or 8080
  • Username: admin (typical)
  • Password: the device password you set in the phone app (not your app account password)

Key points

• Many ZAQ8‑12 units are fisheye “panoramic” bulb cams with ePTZ (software pan/tilt/zoom only; no motors). Some newer “robot head” bulb variants do have small pan/tilt motors.
• App most often: JXLCAM. Other firmwares exist (V380 Pro, iCam365, Tuya/Smart Life). Use what’s printed on the label or hinted by the Wi‑Fi SSID after reset.

Detailed problem analysis

• Why no PTZ “code”: Classic PTZ codes (Pelco‑D/P over RS‑485) apply to analog CVBS/AHD/TVI/CVI cameras. The ZAQ8‑12 is a Wi‑Fi IP device; movement commands are IP messages (app → camera, or ONVIF PTZ service). Therefore you never set an “address” or “PTZ code.”
• Hardware types you may encounter under “ZAQ8‑12” marketing: 1) Panoramic fisheye bulb (most common): fixed lens, no motors. App provides de‑warping and ePTZ. In NVRs, video works via RTSP/ONVIF, but there is no true PTZ because there are no motors. 2) Mini‑PT (robot‑style head) bulb: has tiny pan/tilt motors. App PTZ works; ONVIF PTZ may or may not be exposed depending on firmware.
• Control paths:
  • Mobile app: Always supports whatever the hardware/firmware can do (ePTZ or motor PT).
  • ONVIF: Needed for NVR/VMS PTZ. Some low‑cost firmwares expose only video (no PTZ service), even if the app can move the camera. In that case, your NVR won’t move it.
  • RTSP: Video only, no PTZ control by design.
• Identifying the correct ecosystem:
  • Check the sticker or pairing QR in the box.
  • After a factory reset, note the temporary Wi‑Fi SSID:
  • “IPC‑JXLCAM‑xxxx” → JXLCAM
  • “MV‑xxxx” → V380 Pro
  • “iCam365‑xxxx” → iCam365
  • Tuya variants pair in Tuya/Smart Life.
• Network specifics commonly seen on these chipsets:
  • IP: DHCP from your router (find it in the router’s client list).
  • ONVIF port: 8899 is frequent on JXLCAM/V380 families; 80/5000/8080 also occur.
  • RTSP (if needed for live view in NVR): patterns vary by firmware. Examples often used on similar bulbs:
  • JXLCAM: rtsp://admin:PASS@IP:554/11 (main) or /12 (sub) or port 10554 on some builds
  • V380: rtsp://IP:port/live/ch00_0 (main), ch00_1 (sub)
  • These URLs are not guaranteed; verify with the app/device info or ONVIF scanner.

Current information and trends

• Recent production runs frequently ship with JXLCAM firmware; some batches are migrating to Tuya/Smart Life ecosystems. Behavior also varies by seller/lot, which is why checking the label/SSID is essential.
• Some firmwares force cloud relay by default; local ONVIF/RTSP may be limited or off until you enable it in settings (if available).

Supporting explanations and details

• ePTZ vs true PTZ: ePTZ is just cropping/de‑warping within the sensor’s wide image (no motors). True PTZ requires the camera to physically move; only those units will respond to ONVIF PTZ commands.
• Why NVR PTZ may fail while the phone app works: the vendor app can use private APIs the NVR does not know. If the ONVIF PTZ service isn’t exposed, the NVR can’t send move commands.

Ethical and legal aspects

• Change the default device password immediately; avoid sharing cloud accounts.
• Inform occupants/visitors where laws require notice of video recording. Respect audio‑recording consent rules in your jurisdiction.
• Place cameras only where you have a legal right to record.

Practical guidelines

• If you only need a “code” to enter into an NVR:
  • Add camera as ONVIF
  • IP: [camera’s LAN IP]
  • Port: try 8899 first; if discovery fails, try 80, 5000, then 8080
  • User: admin
  • Password: device password set in the app
  • Test PTZ in the NVR UI; if it doesn’t move but video works, your unit either lacks motors (fisheye) or doesn’t expose ONVIF PTZ.
• Verifying hardware type in 30 seconds:
  • Open live view in the app; swipe to pan. If the camera physically turns or you hear tiny servos, it’s motorized. If the image view changes but the housing does not move, it’s ePTZ only.
• Stable setup tips:
  • 2.4 GHz Wi‑Fi only; avoid dimmer sockets (can cause power instability).
  • In the US, most sockets are E26; these bulbs accept 110–240 Vac, but confirm the label.
  • If pairing fails, factory‑reset (hold reset ≈10–12 s), then use the app’s AP/hotspot or QR method.

Possible disclaimers or additional notes

• ZAQ8‑12 is a marketplace/white‑label designation; ports, ONVIF exposure, and app ecosystems differ by batch. Not all units provide ONVIF PTZ even if the app has a PTZ screen.
• Some lots are cloud‑only for advanced functions; local PTZ via NVR may be unavailable.

Suggestions for further research

• Tell me your exact goal (app only vs NVR/Blue Iris/iSpy), the app shown on your sticker, and the NVR/VMS model. I can give you the precise add‑camera steps and, if needed, probe with ONVIF Device Manager to confirm PTZ services and stream URLs.

Brief summary

• There is no RS‑485/PTZ “code” for the BULBCAM ZAQ8‑12. Use the mobile app or ONVIF. Try ONVIF with port 8899/80, admin + your device password. If the unit is fisheye/ePTZ, NVR PTZ will not work because no motors exist; video will still add via ONVIF/RTSP. If you share your firmware/app/NVR details, I’ll tailor exact settings.