Devices / ip-camera

Xiongmai IPG-X2-WQ-BL (XM530V200)

Also known as XM530V200_IPG-X2-WQ-BL_8M

Partial protocolAI assisted

Part of the protocol is documented (e.g. telemetry, not control).

Stock-firmware interoperability findings from one owner-controlled XM530V200 IPG-X2-WQ-BL camera. Native RTSP video, DVRIP PTZ/white-light controls, WFS SD recording, and an added authenticated local panel/key-only SSH were tested. Not OpenIPC or a universal flashable release; other board/sensor/Wi-Fi variants have not been established as compatible.

ID
xiongmai/ipg-x2-wq-bl
Category
ip-camera
Vendor support
Unknown
chips
XM530V200
Updated
2026-10-29
Edit this record on GitHubJSONClaim this device

Being worked on

No live claim. If you start working on this device, claim it so nobody duplicates your work.

Interfaces

InterfaceTransportStatusConfidenceSpec / notes
Native RTSP video and microphone audiowifidocumentedhighspec · TCP 554. Main HEVC/H.265 2304x1296 at 12 fps, secondary 800x448 at 12 fps; G.711 audio at 8 kHz observed. A native SD recording named .h264 contained HEVC video. Standard RTSP is not a new protocol discovery here.
Native DVRIP configuration, PTZ, white-light and SD querieswifipartialhighspec · TCP 34567 with the existing device account. Tested configuration read/write IDs 1042/1040, PTZ 1400 OPPTZControl (Preset 65535 start, -1 stop), 1450 OPWhiteLightControl (KeepOpen/Close; physical light confirmed), and 1440 OPFileQuery. Added local HTTP API sends stop after a 250 ms PTZ pulse. Software stop is best effort, not a hardware safety guarantee. This is a limited tested subset of an existing protocol, not a full DVRIP specification.
Local extension boot and native WFS SD recordingotherpartialmediumspec · Device-specific additions in user/custom partitions left the bootloader, kernel, root filesystem and original drivers in place. Two independent restarts verified internal panel/SSH boot and resumed native WFS recording; an older recording remained byte-identical and new data grew. No public flash installer or proprietary images are distributed. The route-removal guard is not an egress firewall. SD playback/download/delete UI is absent.

Projects

ProjectKindOriginLicenseFreedom
iCSee LocalModtoolcommunityMITStill non-free: stock firmware, vendor blobs, Wi-Fi, camera, bootloader · Cloud: unknownStock proprietary firmware/drivers remain. The documented operations were exercised locally with native device credentials; fresh provisioning without the vendor app and complete egress isolation were not established.
ICSee PTZ for Home AssistantintegrationcommunityMITnot stated
What "still non-free" and "cloud" mean

What stays proprietary or depends on the vendor's cloud once the project is in use, from the project's own documentation.

vendor blobs
proprietary files extracted from the stock firmware
stock firmware
the stock firmware stays on the device; the project only talks to it
modem
cellular modem firmware
GPU
graphics driver or firmware
Wi-Fi
Wi-Fi driver or firmware
Bluetooth
Bluetooth firmware
camera
camera driver or image processing
sensors
sensor hub or sensor drivers
bootloader
boot firmware
other
another proprietary part
Cloud: none
works fully locally
Cloud: only at setup
a vendor account is needed once, e.g. to obtain a local key
Cloud: optional
cloud features exist but are not needed
Cloud: required
does not work without the vendor's cloud
Cloud: unknown
not known

Verification

Provenance

AI-assisted Parts of this record were produced with AI tools (Codex); check the confidence of each interface.

Status and claims as of the build date (2026-11-04). Data licensed CC BY-SA 4.0; imported data keeps its upstream license.