EZVIZ Sensors, A3 & Camera Compatibility

Hong Kong CCTV buying and setup guide. Sources checked 28 October 2026.

A sensor reports an event; a camera provides visual context

A door contact can report an opening, a PIR sensor can detect movement and a water sensor can report water at its detection point. A camera provides an image of its own field of view. Combining them can be useful, but a shared EZVIZ badge does not prove that every sensor can trigger every camera function. Start with a specific event, such as a stockroom door opening after closing. Then decide whether you need an app notification, an audible gateway alert, a camera clip or a supported automated action. These are separate outputs with different compatibility and storage requirements.

The gateway is part of the system, not an optional cable

The listed Zigbee sensor versions need their documented EZVIZ gateway path. They do not connect directly to an ordinary Wi-Fi router just because both use wireless technology. EZVIZ describes the A3 as the bridge between supported sensors and the app, with its own power and network requirements. Check the exact gateway model and regional support before ordering sensors. A3 and newer gateway variants should not be treated as identical in every detail. If the gateway is not already owned or its availability is unconfirmed, establish that first. A list of sensors alone is not a complete working system.

T1C is a PIR movement sensor with placement conditions

EZVIZ T1C uses passive infrared detection and is documented with an adjustable mount, a pet shield and a required gateway. Its stated detection coverage is subject to placement and the environment. The pet shield reduces a selected part of coverage; it is not identity recognition of a particular animal. Follow the manufacturer mounting guidance and assess the actual route people take. Avoid assuming that a sensor behind furniture sees through it or that an open-space distance applies unchanged across partitions. Check battery status and whether the desired alert schedule suits the household or shop before relying on its notifications.

T2C detects the relationship between its two parts

The T2C open/close sensor uses a sensor body and a magnet. It must be fitted to the intended door, window or cabinet in the documented arrangement, with suitable alignment and clearance. A changing contact state reports an opening condition; it does not tell you who opened the door or prove an intrusion. Camera footage can add context when a compatible and configured route exists. For a shop shutter or metal frame, inspect the physical arrangement and manufacturer guidance rather than assuming a contact intended for a normal door will fit any moving surface. Leave the parts accessible for battery replacement.

Do not confuse a Zigbee smart button with another T3C version

The shop-listed T3C in this guide is the Zigbee smart-button route requiring an appropriate gateway. An identical short model name on another regional page can refer to a Bluetooth version with a different integration path. Read the full model and protocol rather than purchasing from the name alone. A button can be useful for an agreed routine, but only documented actions should be promised. Do not describe it as a monitored emergency alarm, a guaranteed call button or a universal camera controller. Check who receives the action and what happens if the gateway, phone or internet connection is unavailable.

A leak sensor belongs at the place water can reach it

The store-listed T10C is a water-leak sensor requiring the documented gateway route. Its purpose differs from a camera trying to recognise a puddle in an image. Place a water sensor according to its own instructions at a relevant leak point, considering normal cleaning and access. Confirm the gateway compatibility and the notification path for the supplied version before promising a combined camera action. A water alert does not automatically close a valve, stop a washing machine or summon assistance. Those outcomes would need separately documented equipment and integration. Keep those limits clear when buying for a flat or unattended premises.

Camera-triggered recording has explicit limitations

The official T1C and T2C pages describe camera linkage through a gateway, recording conditions involving local storage or CloudPlay, and restrictions involving compatible wired EZVIZ cameras and firmware. They also retain older wording about C6 tracking and future expansion. Treat those qualifications seriously. They do not establish present support for every new camera, every battery model or automatic pan/tilt tracking. Obtain confirmation for the precise camera and firmware before recommending a combination. A five-second linked clip described on a source page is not the same as continuous recording, and a sensor trigger does not prove that the camera is aimed at the event.

Commission one event path at a time

Pair and name each supported device clearly, then test the intended event from sensor to final output. For a stockroom door, open it normally, inspect the app event time and confirm the intended camera clip if that linkage is supported. For a movement sensor, walk the normal route rather than waving directly in front of it. Verify armed and disarmed schedules, battery reminders and authorised sharing. If the app changes after an update, review the relevant settings. Record what actually passed and leave unresolved functions marked as unconfirmed instead of presenting an incomplete configuration as a verified security package.

Choose a modest, verifiable first combination

A useful first step is a defined doorway or leak-notification task, an appropriate supported gateway and the exact sensor suited to that event. Add camera linkage only after confirming it. Before buying, provide the complete gateway model, camera model, firmware and account region, plus the desired notification or recording action. Check whether the gateway is included or separately required and whether it is available for the intended region. This avoids collecting individually useful products that do not form the required system. The guide explains compatibility questions and documented roles; it does not claim Elechid has tested every sensor-camera pairing or operates an alarm-response service.

Check the full A3 gateway model

The cited A3 specification is for CS-A3-A0-W, not every A3 variant. It lists up to 32 battery-powered EZVIZ devices; the larger 64-device limit is conditional on adding wired devices. Do not use that larger figure as a battery-sensor limit or transfer these specifications to an A3-R200 kit. Verify the supplied gateway and each sensor before ordering.

Relevant products and checks before ordering

EZVIZ T1C PIR sensor：Requires a compatible gateway; any camera linkage must be verified separately.
EZVIZ T2C door/window sensor：For a suitable two-part contact installation and supported gateway.
EZVIZ T3C Zigbee smart button：Confirm the exact protocol version and supported actions.
EZVIZ T10C water-leak sensor：Confirm supplied-model gateway support and alert delivery; no automatic shut-off implied.

These recommendations use documented specifications rather than laboratory or site testing by Elechid. Before ordering, provide the full model, supplied regional version, hardware revision and firmware where available. Describe the existing power source, network, recording arrangement and the result you need. Confirm each required function separately: a shared brand, similar housing or matching connector does not establish compatibility. Check the individual product page for its supplied accessories, price, availability and warranty. Keep account passwords, verification codes and private camera access details out of any enquiry.

Manufacturer sources and evidence limits

The linked manufacturer pages support the documented features and limitations discussed here. Hong Kong scenarios, troubleshooting sequences and purchase comparisons are editorial guidance. A promised future update on an older page is not evidence that a feature is available now. Interfaces, supported devices and account-region services may differ; use the instructions for the equipment actually supplied. This guide does not promise on-site installation, monitored security response or services that are not listed.