Method D · Devices to Your Gateway

ZIGBEE 3.0 · ZCL CLUSTER LISTS

OWON Zigbee end devices join your gateway and exchange data with it only — no OWON cloud anywhere in the loop. Every device model is documented as a ZHA Clusters and Attributes sheet: endpoints, device ID, and for each cluster the attribute IDs, data types, mandatory/optional flags, defaults, read/write and reportable bits, plus commands received and generated. Two published examples below show the format you will design against — one battery sensor on standard clusters, one controller that adds an OWON-specific cluster.

Example · DWS332 Door/Window Sensor

CLUSTERS & ATTRIBUTES v0.1.0

A sleepy battery sensor built entirely from standard HA-profile clusters — the easiest OWON device to bring up on a third-party coordinator.

Endpoint 0x01 · Profile 0x0104 (Zigbee Home Automation) · Device ID 0x0402 Endpoint 0x00 · Profile 0x0000 (Zigbee Device Profile)

Cluster	Name	Role	What you get
0x0000	Basic	Server	Device identity: ZCL/stack versions, manufacturer "OWON", model "DWS332", power source.
0x0001	Power Configuration	Server	Battery voltage and remaining percentage (reportable) — drives low-battery maintenance.
0x0003	Identify	Server	Identify / Identify Query commands for pairing and commissioning flows.
0x0020	Poll Control	Server	Check-in interval, long/short poll intervals, fast-poll timeout — the sleepy-end-device keep-alive contract with your coordinator.
0x0500	IAS Zone	Server	Zone state/type (0x15 contact switch), ZoneStatus bitmap, IAS CIE address, enroll request/response, ZoneStatusChangeNotification.

IAS ZoneStatus bitmap (0x0500 / 0x0002)

The bit layout your coordinator parses to turn a single report into open/close, tamper and battery alarms — reproduced from the device document:

Bit 0 Alarm 1 1 = opened / alarmed

Bit 1 Alarm 2 1 = opened / alarmed

Bit 2 Tamper 1 = tampered

Bit 3 Battery 1 = low battery

Bit 4 Supervision report 1 = reports

Bit 5 Restore reports 1 = reports restore

Bit 6 Trouble 1 = trouble / failure

Bit 7 AC (mains) 1 = AC fault

Bit 8 Test 1 = test mode

Bit 9 Battery defect 1 = defective battery detected

Zone type defaults to 0x15 (contact switch). The device sends ZoneEnrollRequest and pushes ZoneStatusChangeNotification on state change — your gateway answers with ZoneEnrollResponse.

Example · AC201A Multi AC IR Controller

CLUSTERS & ATTRIBUTES v0.4.0

Shows the second pattern: standard Thermostat/Fan clusters for interoperability, plus an OWON-specific cluster that carries capabilities the Zigbee specification does not define — IR learning, brand search and one-to-many AC control.

Endpoint 0x01 · Profile 0x0104 (ZHA) · Device ID 0xC204 · Thermostat & Fan clusters bind with the gateway

Cluster	Name	Role	What you get
0x0000	Basic	Server	Manufacturer "OWON", model "AC201A".
0x0003	Identify	Server	Commissioning identify commands.
0x0004	Groups	Server	Full group add/view/remove membership handling.
0x0005	Scenes	Server	Scene storage on the device.
0x0201	Thermostat	Server (bind with gateway)	LocalTemperature, heat/cool setpoint limits, deadband, ControlSequenceOfOperation, SystemMode, ThermostatRunningMode; weekly-schedule and RelayStatusLog reports.
0x0202	Fan Control	Server (bind with gateway)	FanMode and FanModeSequence, both configurable.
0xFFAD	OWON Specific — Multi AC Control	Server	Manufacturer-specific cluster (OWON code 0x113C): the whole IR business below.

OWON cluster 0xFFAD — command map

Manufacturer code 0x113C. Client-to-server commands and the responses the device generates:

Command IDs	Function	Notes
0x00 / 0x01	Read / Write multi pairing codes	Map up to 5 ACs (Device Id 1–5) to IR pairing codes
0x02 / 0x03	Read / Write AC status	Set or query target temperature, mode, fan per AC
0x04	AC status update	Device pushes current AC state
0x10–0x19	IR learn mode & learned-data management	Enter learning, read groups/buttons, rename, clear
0x1F	Send learned data	Transmit a learned IR command
0x40 / 0xC0	Search mode / raw IR data	Brand search and raw IR waveform transmit
0x50 / 0x52	Brand searching / one-key pairing	Response + status/result updates (0x70 / 0x80)

Parameter-level formats for every 0xFFAD command (pairing-code tables, learned-data group/button structures, search and raw-IR payloads) are in the companion “Self-Defined Cluster Commands” document.

How to Read Any OWON Cluster Document

Attribute table columns

ID · Name · Type · M/O (mandatory/optional) · MFG (manufacturer-specific) · PER (persistent) · Default · R/W · REP (reportable) · Description.

Commands received / generated

Per cluster, split by direction, with IDs and M/O flags — enough to implement the coordinator side of pairing, control and reporting without guesswork.

Cluster Lists for Your Device Mix

The two documents above are the published format. Tell us which models you plan to integrate — smart plugs, meters (Electrical Measurement 0x0B04 / Metering 0x0702), thermostats, sensors, panic buttons — and our engineering team sends the matching cluster documents for each one.

Request Cluster Documents

Running Home Assistant or Zigbee2MQTT as your gateway? See open-platform notes. Command formats for gateway-hosted setups live in the Gateway API / MQTT path.