MCU Integration Protocol for Gateway Pro

This topic describes the serial protocol that is used to implement serial communication between Tuya’s Wi-Fi module and the third-party MCU.

The following figure shows how the serial communication works.

Serial communication

• Baud: 115200
• Data bit: 8
• Parity check: none
• Stop bit: 1
• Data flow control: none
• MCU: microcontroller unit. Your MCU communicates with Tuya’s modules through the serial port.

Frame format

Field	Length (byte)	Description
Header	2	It is fixed to 0x55aa.
Version	1	The firmware version number of your MCU.
Command	1	A specific command to instruct the hardware to act and perform certain tasks.
Data length	2	Data in big-endian format.
Data	N	The payload.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Basic protocol

Query product information

Product information consists of the product ID and the MCU software version number.

• Product ID (PID): a unique identifier assigned to each product created on the Tuya Developer Platform for storing product information in the cloud.
• MCU software version number: It is expressed in dot-decimal notation x.x.x. x is a decimal digit between 0 and 99.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x01 Gateway pro only supports getting the PID, without the default PID.
Command	1	0x01
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Example: 0x55aa 00 01 0000 00

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x01
Command	1	0x01
Data length	2	N
Data	N	See the example
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Example: {"v":"1.0.0", "m":0, "cap":0, "p":"mhnmpqzf7ntzm***", "s":0,}

• v: the MCU firmware version. For example, 1.0.0.

• m: the pairing mode. The gateway pro only supports the default pairing mode.

  • 0: the default pairing mode.

  Note: active pairing. For the first-time use, the module automatically enters the pairing state. If you do not pair the module to change its network state, the module will stay in the pairing state.

• cap: the capability that a gateway has. The value of this parameter is a decimal value to which a hexadecimal value converts. The feature represented by each bit:

  • Bit0: support for local groups (Gateway pro supports this feature by default).
  • Bit2: support for data point (DP) (Gateway pro supports this feature by default).
  • Bit4: support for updating MCU’s firmware.
  • Bit5: support for group control command sub_id.
  • The unused bits are padded with zeros.

    Note: Assume a gateway does not support the local group control (bit0 is 0) but supports the data point (bit2 is 1). The value of cap is 0000 0000 0000 0100 in hex, which is 4 in decimal.

• p: the product ID (PID). In the example, the PID is mhnmpqzf7ntz****.

• (Optional) s: specifies whether a gateway supports the security feature. Its value defaults to 0.

  • 0: a common gateway, without the security feature.
  • 1: a gateway with the security feature.

• (Optional) a: the extension capability that a gateway has. The value of this parameter is a decimal value to which a hexadecimal value converts. The feature represented by each bit:

  • Bit0: indicates whether a gateway with the security feature supports the display of alerts. 0: not support. 1: support.
  • Bit1: supports multiple network connection modes. The default priority is wired > Wi-Fi > 4G.
  • Bit2: the button feature is processed by the module. The buttons on the hardware circuit are controlled by the specified pins of the module. For more information, see the specified module hardware solution.
  • Bit3: the light feature is processed by the module. The indicator lights on the hardware circuit are controlled by the specified pins of the module. For more information, see the specified module hardware solution.
  • Bit4 to 7: reserved.
  • The unused bits are padded with zeros.

Report network status

• The device only supports a Wi-Fi network connection. In the command 0x01-query product information, Bit1 of the field a is disabled.
• When the Wi-Fi network status changes, the module will proactively send the current status to the MCU.

Network status	Description	Status value
Status 2	Pair a gateway in AP mode.	0x01
Status 3	The Wi-Fi network is set up, but the device is not connected to the router.	0x02
Status 4	The Wi-Fi network is set up, and the device is connected to the router.	0x03
Status 5	The device is connected to the router and the cloud.	0x04

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x03
Data length	2	0x0001
Data	1	Valid values that represent the Wi-Fi network status: 0x01: Status 2 0x02: Status 3 0x03: Status 4 0x04: Status 5
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Example: 0x55aa 00 03 0001 00 03

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x03
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Example: 0x55aa 00 03 0000 02

Reset a gateway locally

After a gateway is unbound from the mobile app, it will enter the AP pairing mode (status value 0x01). Disconnecting means the gateway removes its connection with a sub-device but does not delete the data of this device. After pairing with the original home again, the information of the sub-device will be resumed and synced to the app.

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x04
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Example: 0x55aa 00 04 0000 03

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x04
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Example: 0x55aa 00 04 0000 03

Allow sub-devices to join network

The app sends a command to the gateway to allow a sub-device to join the network within a specified time period.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x06
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x06
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Disallow sub-devices to join network

The app sends a command to the gateway to stop allowing a device to join the network.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x07
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x07
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Connect sub-devices to gateway

• The MCU sends a joining request to the module.
• (Optional) pk_type: default to 1.
• channel is required if you enable the OTA update feature for the sub-device. Its value defaults to 10. Log in to the Tuya Developer Platform, and choose Hardware Development > Add Custom Firmware > Update Channel to set the channel for OTA update.
  • The current version of the SDK does not support updating sub-devices by using OTA.
  • Incorrect configuration of the update channel might cause the OTA feature to fail.

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x08
Data length	2	N
Data	N	Example: { “pk_type”:xx “sub_id”:“xxxx”, “pid”:“xxxx”, “ver”:“x.x.x”, “channel”:xxx, “ota”:x } Parameter description (Optional) pk_type: the custom product type. sub_id: the unique identifier of a sub-device with up to 25 characters. You can use the MAC address or the chip ID as the sub_id but cannot use the common identifier that represents the gateway functionality such as 0000.0000. pid: the PID of the product. ver: the firmware version number, such as 1.0.0. channel: the OTA update channel. Its value must match the update channel you configure for the custom firmware on the Tuya Developer Platform. The value defaults to 10. ota: specifies whether a sub-device supports the OTA update feature. The value defaults to 0. 0: not support. 1: support.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x08
Data length	2	0x0001
Data	1	0x00: request accepted. 0x01: request rejected. To determine whether a sub-device joins the network successfully, check the result of adding sub-devices.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Delete sub-devices

The module sends the MCU the information about deleting a sub-device.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x09
Data length	2	N
Data	N	Example: { “sub_id”:“xxxx”, “devkey”:“xxx”, “tp”:xx } Parameter description sub_id: the ID of the sub-device to delete. (Optional) devkey: the device key, used to remove a sub-device. tp: 0: Remove a sub-device. 1: Restore a sub-device to factory settings.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x09
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Heartbeat check

The module sends a heartbeat packet to the MCU regularly to check the status of its connection to sub-devices. The interval of heartbeat checks depends on the number of target sub-devices. A higher number of sub-devices increases the frequency of heartbeat checks.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x0A
Data length	2	N
Data	N	Example: { "sub_id":"xxxx" } sub_id: the ID of the sub-device.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns the following data.

The online device must respond to the heartbeat packet. If the module does not receive a response in two consecutive intervals, it will declare that the device is offline.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x0A
Data length	2	N
Data	N	Example: { "sub_id":"xxxx","lp":x, "hb_time":0 } Parameter description sub_id: the ID of the sub-device. lp: the power consumption type of the sub-device. 0: standard power 1: low power hb_time: the heartbeat interval in seconds. Use this field if users want to manage heartbeats themselves. When hb_time is 0, it means the device is always online, and 0x2A is used to report the sub-device status.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Query status

This module sends this command to the MCU to get the current status of the sub-device.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x0B
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns status by using the status reporting command.

Send commands

The module sends a command to instruct the MCU to perform a specific task.

• All available data types except for the raw type are the object types.
• The module can send commands of multiple DPs to the MCU.
• Asynchronous communication applies when the module sends control commands and the MCU reports status.

The following table lists the data format of DP commands.

Data segment	Length (byte)	Description
dpid	1	The identifier of a DP (DP ID).
type	1	It indicates the data type of a DP defined on the Tuya Developer Platform. raw: Represents a DP of raw data type. The module transmits the raw data to the receiver. Value: 0x00 Length (byte): N bool: Represents a DP of Boolean data type. The valid values are 0x00 or 0x01. Value: 0x01 Length (byte): 1 value: Represents a DP of integer data type, in big-endian format. Value: 0x02 Length (byte): 4 string: Represents a DP of string data type. Value: 0x03 Length (byte): N enum: Represents a DP of enum data type, ranging from 0 to 255. Value: 0x04 Length (byte): 1 bitmap: Represents a DP of fault data type. Data greater than one byte is transmitted in big-endian format. Value: 0x05 Length (byte): 1, 2, or 4
len	2	The length is the number of bytes of the value, in big-endian format.
value	1/2/4/N	Represented in hexadecimal format. Data greater than one byte is transmitted in big-endian format.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x0C
Data length	2	N
Data	N	Example: id_len(1byte) + sub_id(nbyte)+ datapoint Parameter description id_len: the length of the sub-device ID. sub_id: the ID of the sub-device. If sub_id is 0000, it means this command is sent to the gateway itself rather than to the sub-device. datapoint: the collection of DPs.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Report status

• The sub-device responds to a status query from the gateway or proactively sends the current status of DPs to the module on the gateway.

The following table lists the data format of DP commands.

Data segment	Length (byte)	Description
dpid	1	The identifier of a DP (DP ID).
type	1	It indicates the data type of a DP defined on the Tuya Developer Platform. raw: Represents a DP of raw data type. The module transmits the raw data to the receiver. Value: 0x00 Length (byte): N bool: Represents a DP of Boolean data type. The valid values are 0x00 or 0x01. Value: 0x01 Length (byte): 1 value: Represents a DP of integer data type, in big-endian format. Value: 0x02 Length (byte): 4 string: Represents a DP of string data type. Value: 0x03 Length (byte): N enum: Represents a DP of enum data type, ranging from 0 to 255. Value: 0x04 Length (byte): 1 bitmap: Represents a DP of fault data type. Data greater than one byte is transmitted in big-endian format. Value: 0x05 Length (byte): 1, 2, or 4
len	2	The length is the number of bytes of the value, in big-endian format.
value	1/2/4/N	Represented in hexadecimal format. Data greater than one byte is transmitted in big-endian format.

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x0D
Data length	2	N
Data	N	Example: id_len(1byte) + sub_id(nbyte)+ datapoint Parameter description id_len: the length of the sub-device ID. sub_id: the ID of the sub-device. If sub_id is 0000, it means this command is sent to the gateway itself rather than to the sub-device. datapoint: the collection of DPs.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Add a sub-device to a group

Add a sub-device to a local group.

• When adding a sub-device to the group, the module sends the group ID to the MCU. And then, the MCU forwards it to the sub-device for local storage.
• When the group executes commands, the module sends the group ID and DPs to the MCU. And then, the MCU notifies all sub-devices via a broadcast command.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x0E
Data length	2	N
Data	N	Example : the sub-devices 12, 34, and 56 join group 01. The payload is { "gid":"01", "cids":["12","34","56"] }. Parameter description gid: the ID of the group. cids: the collection of IDs of sub-devices that join the group.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x0E
Data length	2	N
Data	N	Example: { "gid":"12", "cids":["12","34","56"], "rets":[0,0,0] } Parameter description gid: the ID of the group. cids: the collection of IDs of sub-devices that join the group. rets: the operation results. 0: The sub-device is added successfully. 1: Hit the maximum number of groups that are saved locally. 2: The sub-device times out. 3: The specified value is out of range. 4: Write-error occurs. 5: Other errors occur.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Delete sub-devices from group

The module instructs the MCU to remove a sub-device from a group. When deleting a sub-device from the group, the module sends the group ID to the MCU. And then, the MCU forwards it to the sub-device for local deletion.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x0F
Data length	2	N
Data	N	Example: The sub-device 12 is deleted from the group 01. { "gid":"01", "cids":["12"] } Parameter description gid: the ID of the group. cids: the collection of IDs of sub-devices.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x0F
Data length	2	N
Data	N	Example: { "gid":"01", "cids":["12"], "rets":[0] } Parameter description gid: the ID of the group. cids: the collection of IDs of sub-devices to be removed from the group. rets: the operation results. 0: The sub-device is deleted successfully. 1: Hit the maximum number of groups. 2: The sub-device times out. 3: The specified value is out of range. 4: Write-error occurs. 5: Other errors occur.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Get the GMT

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x10
Data length	2	0x0000
Data	0	Example: 0x55aa 00 10 0000 0F
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x10
Data length	2	0x0007
Data	7	Example: 0x55aa 00 10 0007 01 10 04 13 05 06 07 50 indicates the time 05:06:07 on April 19, 2016 in GMT. Parameter description Data[0]: indicates whether the time is obtained successfully. 0: failure 1: success Data[1]: indicates the year. 0x00 indicates the year 2000. Data[2]: indicates the month, ranging from 1 to 12. Data[3]: indicates the day, ranging from 1 to 31. Data[4]: indicates the hour, ranging from 0 to 23. Data[5]: indicates the minute, ranging from 0 to 59. Data[6]: indicates the second, ranging from 0 to 59. The day of the month is represented as an integer from 1 to 31, which is 01 to 1F in hexadecimal. For example, 13 in hex is 19 in decimal, which means the 19th of the month.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Get local time

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x11
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x11
Data length	2	0x0008
Data	8	Example: 0x55aa 00 10 0007 01 10 04 13 05 06 07 02 54 indicates the time 05:06:07 on April 19, 2016, Tuesday in GMT. Parameter description Data[0]: indicates whether the time is obtained successfully. 0: failure 1: success Data[1]: indicates the year. 0x00 indicates the year 2000. Data[2]: indicates the month, ranging from 1 to 12. Data[3]: indicates the day, ranging from 1 to 31. Data[4]: indicates the hour, ranging from 0 to 23. Data[5]: indicates the minute, ranging from 0 to 59. Data[6]: indicates the second, ranging from 0 to 59. Data[7] indicates the day of the week, ranging from 1 to 7, with Monday as 1.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Add devices in bulk

Add sub-devices with the same PID in bulk. Up to 32 sub-devices can be added at a time.

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x12
Data length	2	N
Data	N	Example: { “pid”:" xxxx", “cids”:[“12”,“34”,“56”], “ver”:“x.x.x”, “channel”:xxx, “ota”:x } Parameter description pid: the product ID (PID). cids: the collection of IDs of sub-devices. ver: the firmware version number, such as 1.0.0. channel: the OTA update channel for sub-devices. Its value must match the update channel you configure for the custom firmware on the Tuya Developer Platform. The value defaults to 10. ota: specifies whether a sub-device supports the OTA update feature. The value defaults to 0. 0: not supported. 1: supported.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x12
Data length	2	0x0001
Data	1	0x00: data is received successfully. 0x01: failed to receive or parse data.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Return the result of adding sub-devices

The module sends the result of adding sub-devices to the MCU.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x13
Data length	2	N
Data	N	Example: { “cids”:[“12”,“34”,“56”], “rets”:[0,0,0], “key”:[“xxxx”,“xxx”], “virt_id”: [“xxxx”,“xxx”] } Parameter description cids: the collection of IDs of sub-devices. channel: the OTA update channel for sub-devices. Its value must match the update channel you configure for the custom firmware on the Tuya Developer Platform. The value defaults to 10. ota: specifies whether a sub-device supports the OTA update feature. The value defaults to 0. 0: not supported. 1: supported. (Optional) key: the secret key. Only Bluetooth Low Energy devices support this field currently. (Optional) virt_id: the virtual ID. Only Bluetooth Low Energy devices support this field currently.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x13
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Send group control commands

The following table lists the data format of DP commands.

Data segment	Length (byte)	Description
dpid	1	The identifier of a DP (DP ID).
type	1	It indicates the data type of a DP defined on the Tuya Developer Platform. raw: Represents a DP of raw data type. The module transmits the raw data to the receiver. Value: 0x00 Length (byte): N bool: Represents a DP of Boolean data type. The valid values are 0x00 or 0x01. Value: 0x01 Length (byte): 1 value: Represents a DP of integer data type, in big-endian format. Value: 0x02 Length (byte): 4 string: Represents a DP of string data type. Value: 0x03 Length (byte): N enum: Represents a DP of enum data type, ranging from 0 to 255. Value: 0x04 Length (byte): 1 bitmap: Represents a DP of fault data type. Data greater than one byte is transmitted in big-endian format. Value: 0x05 Length (byte): 1, 2, or 4
len	2	The length is the number of bytes of the value, in big-endian format.
value	1/2/4/N	Represented in hexadecimal format. Data greater than one byte is transmitted in big-endian format.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x14
Data length	2	N
Data	N	Example: id_len(1byte) + grp_id(nbyte)+ datapoint Parameter description id_len: the length of the group ID. grp_id: the group ID. datapoint: the collection of DPs.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x14
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Test Wi-Fi functionality

The module scans the router whose SSID is tuya_mdev_test and returns the scanning result and signal strength in percentage.

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x15
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x15
Data length	2	0x0002
Data	2	Data[0]: 0x00: failure. 0x01: success. Data[1]: If Data[0] is 0x00: Data[1] is 0x00, indicating that the module failed to scan the designated SSID. Data[1] is 0x01, indicating that the license is not flashed to the module. If Data[0] is 0x01: Data[1] indicates the signal strength, ranging from 0 to 100, 0 for the weakest and 100 for the strongest.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Get Wi-Fi status

• The device only supports a Wi-Fi network connection. In the command 0x01-query product information, Bit1 of the field a is disabled.
• The module on the gateway does not respond to the network status query until the network initialization is completed.

Network status	Description	Status value
Status 2	Pairing in AP mode.	0x01
Status 3	The Wi-Fi network is set up, but the device is not connected to the router.	0x02
Status 4	The Wi-Fi network is set up, and the device is connected to the router.	0x03
Status 5	The device is connected to the router and the cloud.	0x04

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x16
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x16
Data length	2	0x0001
Data	1	Valid values that represent the Wi-Fi network status: 0x01: Status 2 0x02: Status 3 0x03: Status 4 0x04: Status 5
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

(Optional) Restore factory settings

After a local factory reset, Bluetooth sub-devices will be directly deleted from the app rather than added to the device list on the home page of the app.

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x17
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Report the removal status

After receiving a command to disconnect from or perform a factory reset on a sub-device, the module will report the removal status to the MCU.

• Disconnecting means the gateway removes its connection with a sub-device but does not delete the data of this device. After pairing with the original home again, the information of the sub-device will be resumed and synced to the app.
• A factory reset means the gateway removes its connection with a sub-device and deletes the data of this device.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x18
Data length	2	0x0001
Data	1	0x00: local factory reset 0x01: remote device removal 0x02: local device removal 0x03: remote factory reset 0x04: factory reset when the gateway changes homes and is activated
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Delete sub-devices locally

The MCU sends a command to the module to delete a sub-device.

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x19
Data length	2	N
Data	N	Example: { "sub_id":"xxx" }
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x19
Data length	2	0x0001
Data	1	0x00: success 0x01: failure
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Allow/disallow adding sub-devices locally

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x1A
Data length	2	0x0003
Data	3	Data[0]: 0x00: Disallow adding sub-devices. 0x01: Allow adding sub-devices. Data[1]: Allow adding timestamp, in big-endian format. Data[2]: Allow adding timestamp, in little-endian format.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x1A
Data length	2	0x0001
Data	1	0x00: success 0x01: failure
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Query the list of sub-devices

The MCU can query all the sub-devices connected to the gateway. If the length of the list is greater than 255 bytes, the payload will be delivered in multiple packets.

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x1C
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x1C
Data length	2	N
Data	N	Example: id(1byte)+sub_num(1byte)+sub1_len(1byte)+sub1_id+….. subn_len(1byte)+subn_id(1byte) Parameter description id: 07: false: all the addresses of sub-devices have been sent. true: there is still data left, which will be sent in the next packet. 00 to 06: the sequence number of the packet, starting with zero. sub_num: the number of sub-devices included in this packet. sub1_len: the length of the sub-device ID. sub1_id: the ID of the sub-device.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

OTA update

You can choose the desired update options for the OTA firmware update. The module only serves as the channel for OTA data transmission, without any data parsing operation.

After the Wi-Fi module completes the update transmission, it will send the MCU the command 0x01 to request the product information. The MCU must reply with the software version number and the new MCU software version number within one minute. The new version number should be consistent with that configured on the Developer Platform.

• The update options:

  • Update notification: Users receive a firmware update notification on the app and choose whether to install updates.
  • Forced update: Users receive a firmware update notification on the app and have no option but to update the firmware.
  • Check for updates: Users will not receive a firmware update notification on the app but need to manually check for new updates.

• Automatic update (previously named silent update): Users will not receive any update notification. The module checks for firmware updates within the specified time period (for example, one minute) after power on and install updates if any are available. The module checks for updates every 24 hours after the first-time power on.

• The following flowchart shows how the OTA firmware update works.

  

Initiate an update

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x1D
Data length	2	0x0004
Data	4	The size of the update, in big-endian format.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x1D
Data length	2	0x0001
Data	1	The options for the maximum size of each packet: 0x00: 256 bytes. It is the default value and is compatible with legacy firmware. 0x01: 512 bytes. 0x02: 1,024 bytes. 0x03: 128 bytes.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Transfer update package

• Data format: packet offset (unsigned short) + payload data.
• When the MCU receives a frame with a length of four bytes and the fragment offset is equal to or greater than the size of the firmware update, the transfer is completed.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x1E
Data length	2	0x0004+m m: the offset in bytes.
Data	offset_addr(4byte) + pack(mbyte)	offset_addr: the offset address. pack: the payload.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Assume that the size of the update is 530 bytes. The MCU does not need to respond to the last packet.

• For the first packet, the packet offset is 0x00000000, and the packet length is 256 bytes.

  0x55aa 00 1e 0104 00000000 xx…xx XX

• For the second packet, the packet offset is 0x00000100, and the packet length is 256 bytes.

  0x55aa 00 1e 0104 00000100 xx…xx XX

• For the third packet, the packet offset is 0x00000200, and the packet length is 18 bytes.

  0x55aa 00 1e 0016 00000200 xx…xx XX

• For the last packet, the packet offset is 0x00000212, and the packet length is 0 bytes.

  0x55aa 00 1e 0004 00000212 XX

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x1E
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Initiate sub-device update

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x1F
Data length	2	N
Data	N	Example: id_len(1byte) + sub_id(nbyte)+ file_size(4byte) Parameter description id_len: the length of the sub-device ID. sub_id: the ID of the sub-device. file_size: The size of the update, in big-endian format.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x1F
Data length	2	0x0001
Data	1	The options for the maximum size of each packet: 0x00: 256 bytes. It is the default value and is compatible with legacy firmware. 0x01: 512 bytes. 0x02: 1,024 bytes. 0x03: 128 bytes. 0x04: 64 bytes. 0x05: 32 bytes.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Transfer the update

• Data format: packet offset (unsigned short) + payload data.
• When the MCU receives a frame with a length of four bytes and the fragment offset is equal to or greater than the size of the firmware update, the transfer is completed.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x20
Data length	2	N
Data	N	Example: id_len(1byte) + sub_id(nbyte)+ offset_addr(4byte)+ pack(mbyte) Parameter description id_len: the length of the sub-device ID. sub_id: the ID of the sub-device. offset_addr: the offset address. pack: the payload.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Assume that the sub_id is 1234 and the size of the update is 530 bytes. The MCU does not need to respond to the last packet.

• For the first packet, the packet offset is 0x00000000, and the packet length is 256 bytes.

  0x55aa 00 20 0109 04 31 32 33 34 00000000 xx…xx XX

• For the second packet, the packet offset is 0x00000100, and the packet length is 256 bytes.

  0x55aa 00 20 0109 04 31 32 33 34 00000100 xx…xx XX

• For the third packet, the packet offset is 0x00000200, and the packet length is 18 bytes.

  0x55aa 00 20 001B 04 31 32 33 34 00000200 xx…xx XX

• For the last packet, the packet offset is 0x00000212, and the packet length is 0 bytes.

  0x55aa 00 20 0009 04 31 32 33 34 00000212 XX

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x20
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Query the version number of the sub-device

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x21
Data length	2	N
Data	N	Example: {"sub_id":"xxx"} sub_id: the ID of the sub-device.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x21
Data length	2	N
Data	N	Example: {"sub_id":"xxx", "ver":"xx.xx.xx"} Parameter description sub_id: the ID of the sub-device. ver: The firmware version number of the sub-device.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Send group control commands (with sub_id)

The following table lists the data format of DP commands.

Data segment	Length (byte)	Description
dpid	1	The identifier of a DP (DP ID).
type	1	It indicates the data type of a DP defined on the Tuya Developer Platform. raw: Represents a DP of raw data type. The module transmits the raw data to the receiver. Value: 0x00 Length (byte): N bool: Represents a DP of Boolean data type. The valid values are 0x00 or 0x01. Value: 0x01 Length (byte): 1 value: Represents a DP of integer data type, in big-endian format. Value: 0x02 Length (byte): 4 string: Represents a DP of string data type. Value: 0x03 Length (byte): N enum: Represents a DP of enum data type, ranging from 0 to 255. Value: 0x04 Length (byte): 1 bitmap: Represents a DP of fault data type. Data greater than one byte is transmitted in big-endian format. Value: 0x05 Length (byte): 1, 2, or 4
len	2	The length is the number of bytes of the value, in big-endian format.
value	1/2/4/N	Represented in hexadecimal format. Data greater than one byte is transmitted in big-endian format.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x22
Data length	2	N
Data	N	Example: grp_len(1byte) + grp_id(nbyte)+ sub_len(1byte) + sub_id(mbyte)+ datapoint Parameter description grp_len: the length of the group ID. grp_id: the group ID. sub_len: the length of the specified sub-device’s ID. sub_id: the ID of the sub-device. datapoint: the collection of DPs.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x22
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Query the status of DPs

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x29
Data length	2	N
Data	N	Example: { "sub_id":"xxx", "dpid":[xx,xx,xx] } Parameter description sub_id: the ID of the sub-device. dpid: the array of DP IDs.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns status by using the status reporting command.

Update the connection status of sub-devices

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x2A
Data length	2	N
Data	N	Example: {"all":0,"cids":["xxx","xxx"],"state":1} or {"all":1,"state":1} Parameter description all: 0: only the cids data is included. 1: the data of all sub-devices is included. The field cdis is not needed. cids: the collection of IDs of sub-devices. state: 0: offline 1: online
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x2A
Data length	2	0x0001
Data	1	0x00: success 0x01: failure
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Get the MAC address of the module

The module returns the MAC address of the wireless network interface.

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x2B
Data length	2	0x0000
Data	0	None
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x2B
Data length	2	0x0007
Data	7	Data[0]: indicates whether the MAC address is obtained successfully. 0x00: success 0x01: failure Data[1] to Data[6]: the MAC address of the module.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Report the status of time-dependent DPs

• For time-dependent sub-devices such as door locks, the MCU must have the timestamp when an event occurred contained in the payload when it reports status to the module.
• This is a synchronous command. The MCU reports DP status and then waits for the result from the module.

The following table lists the data format of DP commands.

Data segment	Length (byte)	Description
dpid	1	The identifier of a DP (DP ID).
type	1	It indicates the data type of a DP defined on the Tuya Developer Platform. raw: Represents a DP of raw data type. The module transmits the raw data to the receiver. Value: 0x00 Length (byte): N bool: Represents a DP of Boolean data type. The valid values are 0x00 or 0x01. Value: 0x01 Length (byte): 1 value: Represents a DP of integer data type, in big-endian format. Value: 0x02 Length (byte): 4 string: Represents a DP of string data type. Value: 0x03 Length (byte): N enum: Represents a DP of enum data type, ranging from 0 to 255. Value: 0x04 Length (byte): 1 bitmap: Represents a DP of fault data type. Data greater than one byte is transmitted in big-endian format. Value: 0x05 Length (byte): 1, 2, or 4
len	2	The length is the number of bytes of the value, in big-endian format.
value	1/2/4/N	Represented in hexadecimal format. Data greater than one byte is transmitted in big-endian format.

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x2C
Data length	2	7 + N
Time	7	Data[0]: indicates whether the event timestamp is contained in the payload. 0x00: the event timestamp is not reported. 0x01: the event timestamp in local time is reported. 0x02: the event timestamp in GMT is reported. 0x03: the timestamp, in seconds. If Data[0] is 0x01 or 0x02 Data[1]: indicates the year. 0x00 indicates the year 2000. Data[2]: indicates the month, ranging from 1 to 12. Data[3]: indicates the day, ranging from 1 to 31. Data[4]: indicates the hour, ranging from 0 to 23. Data[5]: indicates the minute, ranging from 0 to 59. Data[6]: indicates the second, ranging from 0 to 59. If Data[0] is 0x03 Data[1] to Data[4]: a 4-byte timestamp, in big-endian format. Data[5] to Data[6]: padded with zero.
Data	N	Example: { id_len(1byte)+sub_id(nbyte)+datapoint} Parameter description id_len: the length of the sub-device ID. sub_id: the ID of the sub-device. If sub_id is 0000, it means the MCU reports the status of DPs of the gateway itself rather than those of the sub-device. datapoint: the collection of DPs.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x2C
Data length	2	0x0001
Data	1	0x00: success 0x01: failure
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Query the binding status of sub-devices

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x2D
Data length	2	N
Data	N	Example: {"sub_id":"xxx", "d_link":x "e_val":"xxx"} Parameter description d_link: indicates whether a sub-device can be bound with both the mobile app and the gateway. 0: not supported. 1: supported. (Optional) e_val: the encrypted value.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x2D
Data length	2	N
Data	N	Example: {"sub_id":"xxx", "ret":x} Parameter description sub_id: the ID of the sub-device. ret: the current binding status. 0: the sub-device is successfully bound with the gateway. 1: the sub-device is not bound with the gateway but its record is stored on the gateway. This might be because this sub-device is being bound or has no record stored in the cloud. 3: the sub-device is bound with the mobile app but not with the gateway. 4: the sub-device is not bound with the gateway and its relationship with the mobile app is unknown.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Query the information of sub-devices in a group

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x2E
Data length	2	N
Data	N	Example: { "gid":"xxx", "idx":xx} Parameter description gid: the ID of the group. idx: the sequence number of the sub-device to query. For example, 0 means the first sub-device.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x2E
Data length	2	N
Data	N	Example: {"gid":"xxx","sub_id":"xxxx" }
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Report the status-updated DP in a group

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x2F
Data length	2	N
Data	N	Example: {"gid":"xxx", "dpid":xx} Parameter description gid: the ID of the group. dpid: the ID of the DP whose status is updated locally. After the module receives the reporting message, it will query the current status of this DP.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x2F
Data length	2	0x0001
Data	1	0x00: success 0x01: failure
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Extended features

Weather service

• The weather service feature can be used to get weather information on the device pairing address or home address. If you want to get the weather information of your home address, you need to add the request parameter w.a.new, and request the real-time weather and forecast weather separately. If you request both simultaneously, only the forecast weather will be returned.
• The MCU can proactively get the weather information and enable the module to update the weather information regularly.
• If the return parameters are less than the request parameters, check whether the request parameter name is correct or supported.
• For more information about the weather service data, see Appendix 1.
• For more information about the city service data, see Appendix 2.
• For more information about data types of the weather forecast service, see Appendix 3.
• For more information about weather data in UTF-8 encoding, see Appendix 4.
• For more information about the wind direction code, see Appendix 5.

Enable regular requests of weather data

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x33
Data length	2	(1+1+(L+K)+(L+K)…)
Data	N	Subcommand: 1 byte, 0x00. Interval of regular updates: 1 byte. 0x00: disable regular updates of the weather data. 0xFF: Set the update interval to 24 hours. Others: Unit: in minutes. The minimum update interval is 10 minutes. Considering the real-time nature of weather data, the maximum interval is 240 minutes. A standard update interval of 60 minutes is recommended. For example, 0x1E means updating every 30 minutes. L: a 1-byte value, representing the length of K. For example, L:0x06. K: the name of the request parameter. For more information about the supported parameter, see Appendix 1. For example, K:w.temp.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Example: 55 AA 00 33 00 09 00 1E 06 77 2E 74 65 6D 70 BA

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x33
Data length	2	0x0002
Data	2	Subcommand: 1 byte, 0x00. Data[0]: 0x00: success 0x01: failure
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Send weather data

With the regular update of weather data enabled, the module will regularly send weather data to the MCU. After the regular update is successfully enabled, the data will be sent immediately, and then sent at the set interval.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x33
Data length	2	(1+1+(LKTLV)+(LKTLV)+…) or 0x0003
Data	N	Subcommand: 1 byte, 0x01. Indicates whether the MCU receives the data. Failed to receive the data, with 2 bytes: 0x00: failure. Error codes: 0x01 indicates that the internet is unavailable, and 0x02 indicates an HTTP error. Received the data successfully: 1 byte, 0x01. L: a 1-byte value, representing the length of K. For example, L:0x06. K: the name of the request parameter. For more information about the supported parameter, see Appendix 1. For example, K:w.temp. T: parameter type. 0x00: integer 0x01: string L: the length of the field name. V: the value of the field.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Example: 55 AA 00 33 00 0F 01 01 06 77 2E 74 65 6D 70 00 04 00 00 00 06 AE

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x33
Data length	2	0x0001
Data	1	Subcommand: 0x01
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Proactively request weather data

The module only uses this command to confirm a request and sends weather data still through the command 0x3301.

The MCU sends the following data.

Field	Length	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x33
Data length	2	(1+(L+K)+(L+K)…)
Data	N	Subcommand: 1 byte, 0x02. L: a 1-byte value, representing the length of K. For example, L:0x06. K: the name of the request parameter. For more information about the supported parameter, see Appendix 1. For example, K:w.temp.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Example: 55 AA 00 33 00 08 02 06 77 2E 74 65 6D 70 9D

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x33
Data length	2	0x0002
Data	1	Subcommand: 0x02
	1	The returned result. 0x00: success 0x01: failure
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Examples of weather data requests

Request the real-time data of the current day

• The MCU sends the request: {"w.temp","w.humidity"} or {"w.temp","w.humidity","w.currdate"}.

• The module returns the following data.

  {
      "w.temp":13,
      "w.humidity":100
  }
  

Request the weather forecast of the current day only

• The MCU sends the request: {"w.humidity","w.date.1"}.

• The module returns the following data.

  {
      "w.humidity.0":100
  }
  

Request daily forecasts

• The MCU sends the request: {"w.humidity","w.date.3"}.

• The module returns the following data.

  {
      "w.humidity.0":100,
      "w.humidity.1":100,
      "w.humidity.2":100
  }
  

Request weather data with sunset and sunrise time

• GMT (taking UTC +8 time zone as an example)

  • The MCU sends the request: { "w.humidity","w.sunrise","w.sunset","t.unix","w.date.3" }.

  • The module returns the following data.

    {
        "w.humidity.0":100,
        "w.sunrise.0":"2019-12-27 00:05",
        "w.sunset.0":"2019-12-27 10:54",
        "w.humidity.1":100,
        "w.sunrise.1":"2019-12-28 00:05",
        "w.sunset.1":"2019-12-28 10:54",
        "w.humidity.2":100,
        "w.sunrise.2":"2019-12-29 00:05",
        "w.sunset.2":"2019-12-29 10:54"
    }
    

• Local time (taking UTC +8 time zone as an example)

  • The MCU sends the request: { "w.humidity","w.sunrise","w.sunset","t.local","w.date.3" }.

  • The module returns the following data.

    {
        "w.humidity.0":100,
        "w.sunrise.0":"2019-12-27 08:05",
        "w.sunset.0":"2019-12-27 18:54",
        "w.humidity.1":100,
        "w.sunrise.1":"2019-12-28 08:05",
        "w.sunset.1":"2019-12-28 18:54",
        "w.humidity.2":100,
        "w.sunrise.2":"2019-12-29 08:05",
        "w.sunset.2":"2019-12-29 18:54"
    }
    

Request daily forecasts and measured air data

• The MCU sends the request: { "w.temp","w.humidity","w.pm10","w.pm25","w.date.3" }.

• The module returns the following data.

  {
      "w.pm10.0":14,
      "w.pm25.0":7,
      "w.humidity.0":100,
      "w.humidity.1":100,
      "w.humidity.2":100
  }
  

  If the value n you specified for the parameter w.date.n is greater than 7 or not greater than 0, the server takes it as an input parameter error and returns nothing.

Restart a gateway locally

The MCU instructs the module to restart.

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x34
Data length	2	0x0001
Data	1	Subcommand: 0x09
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x34
Data length	2	0x0002
Data	2	Data[0]: the subcommand 0x09 Data[1]: the operation result. 0x00: success 0x01: failure
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Turn on/off 4G feature locally

This command only applies to modules that support 4G network.

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x72
Data length	2	0x0002
Data	2	Data[0]: the subcommand 0x01 Data[1]: indicates the 4G network status. 0x00: turn off 4G. 0x01: turn on 4G.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x72
Data length	2	0x0002
Data	2	Data[0]: the subcommand 0x01 Data[1]: the operation result. 0x00: success 0x01: failure
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Report network status of multi-NIC devices

• The device supports multiple network connection methods. In the command 0x01-query product information, Bit1 of the field a is enabled.
• When the network status of the multi-NIC device changes, the module will proactively send its current status to the MCU.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x72
Data length	2	0x0003
Data	3	Data[0]: the subcommand 0x02. Data[1]: the network status. 0x00: offline (not connected to the cloud) 0x01: online (connected to the cloud) Data[2]: the network currently connected to the cloud. 0x00: none 0x01: wired network 0x02: Wi-Fi network 0x03: 4G network
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x72
Data length	2	0x0001
Data	1	Subcommand: 0x02
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Request network status of multi-NIC devices

The device supports multiple network connection methods. In the command 0x01-query product information, Bit1 of the field a is enabled.

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x72
Data length	2	0x0001
Data	1	Subcommand: 0x03
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x72
Data length	2	0x0003
Data	3	Data[0]: the subcommand 0x03. Data[1]: the network status. 0x00: offline (not connected to the cloud) 0x01: online (connected to the cloud) Data[2]: the network currently connected to the cloud. 0x00: none 0x01: wired network 0x02: Wi-Fi network 0x03: 4G network
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Request IPV4 network details

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x72
Data length	2	0x0002
Data	2	Data[0]: the subcommand 0x04. Data[1]: the NIC name. 0x00: wired network 0x01: Wi-Fi network 0x02: 4G network
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x72
Data length	2	0x0002 or 0x0013
Data	2 or 19	Data[0]: the subcommand 0x04. Data[1]: the operation result. 0x00: success 0x01: failure The following data is returned when the operation is successful: Data[2]: indicates whether to enable DHCP. 0x00: turn on DHCP 0x01: turn off DHCP Data[3] to Data[6]: the IP address. For example, 192.168.1.100: 0xC0 0xA8 0x01 0x64 Data[7] to Data[10]: the subnet mask. For example, 255.255.255.0: 0xFF 0xFF 0xFF 0x00 Data[11] to Data[14]: the default gateway. For example, 192.168.1.1: 0xC0 0xA8 0x01 0x01 Data[15] to Data[18]: the DNS server address. For example, 8.8.8.8: 0x08 0x08 0x08 0x08
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Query signal strength of sub-devices

The panel displays the network topology of the sub-devices. When there is a relay sub-device, the MCU will return the IDs and signal strength of the terminal sub-device and the relay sub-device in sequence.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x72
Data length	2	1 + N
Data	1	Subcommand: 0x05
	N	Example: { "sub_id":"xxxx" } sub_id: the ID of the sub-device
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0x72
Data length	2	1 + N
Data	1	Subcommand: 0x05
	N	Example: [{ "sub_id":"xxx", "rssi":x }, ..., {}] If the network topology looks like this: terminal sub-device A – relay sub-device B – relay sub-device C – gateway, the array elements returned by the MCU have filled in the following order: [ {“sub_id”:“sub-device A’s ID”,“rssi”:sub-device A’s rssi}, {“sub_id”:“sub-device B’s ID”,“rssi”:sub-device B’s rssi}, {“sub_id”:“sub-device C’s ID”,“rssi”:sub-device C’s rssi}, … ] Parameter description sub_id: the ID of the sub-device. rssi: the received signal strength indicator (RSSI). 1: poor 2: good 3: excellent
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Extended protocol for security features

This section describes the commands specific to the security feature. For more information about implementing the feature, see Security Gateway MCU Development.

Set the arm mode

This command is used to arm or disarm the security system.

• If the system is being armed, to edit the arm mode, you need to disarm the system first.
• The arm delay set by using this command is not valid. You need to set its value to 0. The arm delay setup on the mobile app prevails.
• sub_id: NULL means the gateway itself.

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0xC0
Data length	2	1 + N
Data	1	Subcommand: 0x00
	N	Example: { "mode":"xxx", "sub_id":"xxxxx", "delay":xx} Parameter description mode: the arm mode. 0: disarm 1: arm stay 2: arm away sub_id: the ID of the sub-device. delay: the delay time before the system enters arm status. 0: reads the delay time set by the mobile app. Other values: the specified delay time, in seconds.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0xC0
Data length	2	0x0002
Data	2	Data[0]: the subcommand 0x00. Data[1]: the operation result. 0x00: success 0x01: failure
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Request the current security status

The MCU sends this command to get the current status of the security system.

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0xC0
Data length	2	0x0001
Data	1	Subcommand: 0x01
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0xC0
Data length	2	1 + N
Data	1	Subcommand: 0x01
	N	Example: {operation result} + {"mode":"xxx", "alarm":x, "countdown":x} Parameter description The operation result. 0: success 1: failure mode: the arm mode. 0: disarm 1: arm stay 2: arm away alarm: the alarm status. 0: an alarm is triggered with a delay. Other values: no alarm is triggered. countdown: the arm delay. 0: arm delay is running. Other values: arm delay is not set.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Sync the security mode settings

After receiving the security mode settings from the mobile app, the module uses this command to sync the information with the MCU.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0xC0
Data length	2	1 + N
Data	1	Subcommand: 0x02
	N	Example: {"mode":"xxx", "delay":xx, "sound":x} Parameter description mode: the arm mode. 0: disarm 1: arm stay 2: arm away delay: the delay time before the system enters arm status. 0: arm delay is not set. Other values: the specified delay time, in seconds. sound: specifies whether to play sounds. 0: playing sounds. Other values: not playing sounds.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0xC0
Data length	2	0x0001
Data	1	Subcommand: 0x02
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Sync security events

The module syncs the security events with the MCU by using this command.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0xC0
Data length	2	1 + N
Data	1	Subcommand: 0x03
	N	Example: { "status":x, "data":"xxx" } Parameter description status: the event. 0: disarm 1: arming 2: a false alarm triggers sound playing 3: start countdown data: the event information. 0: no countdown timer is set Only after the alarm delay is enabled, the countdown timer returns the time left.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0xC0
Data length	2	0x0001
Data	1	Subcommand: 0x03
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Set alarm status

The MCU syncs the alarm status with the module through the DP 32.

The MCU sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0xC1
Data length	2	0x0002
Data	2	Data[0]: the subcommand 0x00. Data[1]: the alarm status. 0: no alarm is triggered Other values: alarming
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The module returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0xC1
Data length	2	0x0002
Data	2	Data[0]: the subcommand 0x00. Data[1]: the operation result. 0x00: success 0x01: failure
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Sync the alarm delay status

When alarm delay is running, the module syncs the current alarm status to the MCU.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0xC1
Data length	2	0x0002
Data	2	Data[0]: the subcommand 0x03. Data[1]: the alarm delay status. 0: alarm delay is not created. 1: alarm delay is running. 2: alarm delay is completed.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0xC1
Data length	2	0x0001
Data	1	Subcommand: 0x03
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Sync alarm information (new)

This is a new command used to sync alarm information. It works with bit0 of the a field in the 0x01 command. If bit0 is enabled, processing 0xc101 and 0xc102 is not necessary.

• The GP field is not supported.
• Non-environmental sensing devices: indicates devices that are not used to sense and monitor the environment.
• Environmental sensing devices: indicates devices that can sense and monitor the environment.
• The payload content depends on the enabled features.

The gp field is reserved for the feature of multi-protection areas. The MCU does not return the value of this field.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0xC1
Data length	2	1 + N
Data	1	Subcommand: 0x04
	N	Example: { “type”:x, “sub_id”:“xxx”, “dp_inf”:“xxx”, “gp”:“xxxx” } Parameter description type: the device type that triggers an alarm. 0: non-environmental sensing devices 1: environmental sensing devices sub_id: the ID of the sub-device. dpinf: the information of the DP that triggers an alarm, in cJSON format. gp: reserved for the feature of multi-protection areas.
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0xC1
Data length	2	0x0001
Data	1	Subcommand: 0x04
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Sync the alarm status (new)

This is a new command used to sync alarm status. It works with the enabled bit0 of the a field in the 0x01 command.

The module sends the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0xC1
Data length	2	0x0002
Data	1	Data[0]: the subcommand 0x05. Data[1]: the alarm status. 0: cancel alarming 1: the system is alarming
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

The MCU returns the following data.

Field	Length (byte)	Description
Header	2	0x55aa
Version	1	0x00
Command	1	0xC1
Data length	2	0x0001
Data	1	Subcommand: 0x05
Checksum	1	Start from the header, add up all the bytes, and then divide the sum by 256 to get the remainder.

Appendices

Appendix 1: Weather data in ASCII

Parameter	Meaning	Mainland China	Other countries/regions	Weather forecast	Length	Hexadecimal value
w.temp	Atmospheric temperature in °C	Supported	Supported	7-day forecast (except for mainland China)	6	77 2e 74 65 6d 70
w.humidity	Air humidity	Supported	Supported	7-day forecast	10	77 2e 68 75 6d 69 64 69 74 79
w.conditionNum	Weather condition No.	Supported	Supported	7-day forecast	14	77 2e 63 6f 6e 64 69 74 69 6f 6e 4e 75 6d
w.pressure	Atmospheric pressure in mbar	Supported	Supported	7-day forecast (except for mainland China)	10	77 2e 70 72 65 73 73 75 72 65
w.realFeel	Apparent temperature	Supported	Supported	N/A	10	77 2e 72 65 61 6c 46 65 65 6c
w.uvi	Ultraviolet index	Supported	Supported	7-day forecast	5	77 2e 75 76 69
w.sunrise	Sunrise	Supported	Supported	7-day forecast	9	77 2e 73 75 6e 72 69 73 65
w.sunset	Sunset	Supported	Supported	7-day forecast	8	77 2e 73 75 6e 73 65 74
t.unix	GMT, used with sunrise (w.sunrise) and sunset (w.sunset)	-	-	-	6	74 2e 75 6e 69 78
t.local	Local time, used with sunrise (w.sunrise) and sunset (w.sunset)	-	-	-	7	74 2e 6c 6f 63 61 6c
w.windSpeed	Wind speed in m/s	Supported	Supported	7-day forecast	11	77 2e 77 69 6e 64 53 70 65 65 64
w.windDir	Wind direction	Supported	Supported	7-day forecast	9	77 2e 77 69 6e 64 44 69 72
w.windLevel	Wind scale	Mainland China only	Not supported	7-day forecast	11	77 2e 77 69 6e 64 4c 65 76 65 6c
w.aqi	Air quality index, US EPA standard: 0 to 500	Supported	Supported	Current day only	5	77 2e 61 71 69
w.rank/w.quality	AQI details and national ranking	Mainland China only	Not supported	Current day only	6	77 2e 72 61 6e 6b / 77 2e 71 75 61 6c 69 74 79
w.pm10	PM10 (inhalable particulate matter) in µg/m³	Supported	Supported	Current day only	6	77 2e 70 6d 31 30
w.pm25	PM2.5 (fine particulate matter) in µg/m³	Supported	Supported	Current day only	6	77 2e 70 6d 32 35
w.o3	Ozone level in µg/m³	Supported	Supported	Current day only	4	77 2e 6f 33
w.no2	Nitrogen dioxide level in µg/m³	Supported	Supported	Current day only	5	77 2e 6e 6f 32
w.co	Carbon monoxide level in µg/m³	Supported	Supported	Current day only	4	77 2e 63 6f
w.so2	Sulfur dioxide level in µg/m³	Supported	Supported	Current day only	5	77 2e 73 6f 32
w.thigh	The highest temperature in °C	Supported	Supported	Forecast only	7	77 2e 74 68 69 67 68
w.tlow	The lowest temperature in °C	Supported	Supported	Forecast only	6	77 2e 74 6c 6f 77
w.date.n	Number of forecast days, represented by n with 1 ≤ n ≤ 7	Supported	Supported	-	8	77 2e 64 61 74 65 2e 6e
w.currdate	Current weather	Supported	Supported	-	10	77 2e 63 75 72 72 64 61 74 65

Appendix 2: City service data in ASCII

Parameter	Description	Type	Length	Hexadecimal value
c.area	County or district name	String	6	63 2e 61 72 65 61
c.city	City name	String	6	63 2e 63 69 74 79
c.province	Province	String	10	63 2e 70 72 6f 76 69 6e 63 65

Appendix 3: Weather forecast service

Parameter	Description	Type	Real-time weather	Weather forecast
w.temp	Temperature	Integer	Yes	Supported (except for mainland China)
w.humidity	Humidity	Integer	Yes	Yes
w.conditionNum	Weather condition No.	String	Yes	Yes
w.pressure	Air pressure	Integer	Yes	Supported (except for mainland China)
w.realFeel	Apparent temperature	Integer	Yes	No
w.uvi	Ultraviolet index	Integer	Yes	Yes
w.windDir	Wind direction	String	Yes	Yes
w.windLevel	Wind scale	Integer	Mainland China only	No
w.windSpeed	Wind speed	String (format example: 1.0; 0.5)	Yes	Yes
w.sunrise	Sunrise time	String (format example: 2017-04-24 05:24)	Yes	Yes
w.sunset	Sunset time	String (format example: 2017-04-24 18:32)	Yes	Yes
w.aqi	Air quality index	Integer	Yes	No
w.pm25	PM2.5	Integer	Yes	No
w.so2	Sulfur dioxide level	Integer	Yes	No
w.rank/w.quality	Air quality rating	String (format example: 447/609)	Mainland China only	No
w.pm10	PM10	Integer	Yes	No
w.o3	Ozone (O3) level	Integer	Yes	No
w.no2	Nitrogen dioxide (NO2) level	Integer	Yes	No
w.co	Carbon monoxide (CO) level	Integer	Yes	No
w.qualityLevel	Air quality rating	Integer	Yes	No
w.thigh	The highest temperature	Integer	No	Yes
w.tlow	The lowest temperature	Integer	No	Yes

Appendix 4: Weather data in UTF-8 encoding

w.conditionNum in ASCII code	Hexadecimal value	Weather conditions
120	31 32 30	Sunny
101	31 30 31	Heavy rain
102	31 30 32	Thunderstorm
103	31 30 33	Sandstorm
104	31 30 34	Light snow
105	31 30 35	Snow
106	31 30 36	Freezing fog
107	31 30 37	Rainstorm
108	31 30 38	Isolated shower
109	31 30 39	Dust
110	31 31 30	Thunder and lightning
111	31 31 31	Light shower
112	31 31 32	Rain
113	31 31 33	Sleet
114	31 31 34	Dust devil
115	31 31 35	Ice pellets
116	31 31 36	Strong sandstorm
117	31 31 37	Sand blowing
118	31 31 38	Light to moderate rain
119	31 31 39	Mostly clear
121	31 32 31	Fog
122	31 32 32	Shower
123	31 32 33	Heavy shower
124	31 32 34	Heavy snow
125	31 32 35	Extreme rainstorm
126	31 32 36	Blizzard
127	31 32 37	Hail
128	31 32 38	Light to moderate snow
129	31 32 39	Partly cloudy
130	31 33 30	Light snow shower
131	31 33 31	Moderate snow
132	31 33 32	Overcast
133	31 33 33	Needle ice
134	31 33 34	Downpour
136	31 33 36	Thundershower and hail
137	31 33 37	Freezing rain
138	31 33 38	Snow shower
139	31 33 39	Light rain
140	31 34 30	Haze
141	31 34 31	Moderate rain
142	31 34 32	Cloudy
143	31 34 33	Thundershower
144	31 34 34	Moderate to heavy rain
145	31 34 35	Heavy rain to rainstorm
146	31 34 36	Clear

Appendix 5: Wind direction code

Code (string)	Hexadecimal value	Description
N	4e	North
NNE	4e 4e 45	Northeast by north
NE	4e 45	Northeast
ENE	45 4e 45	Northeast by east
E	45	East
ESE	45 53 45	Southeast by east
SE	53 45	Southeast
SSE	53 53 45	Southeast by south
S	53	South
SSW	53 53 57	Southwest by south
SW	53 57	Southwest
WSW	57 53 57	Southwest by west
W	57	West
WNW	57 4e 57	Northwest by west
NW	4e 57	Northwest
NNW	4e 4e 57	Northwest by north