mirrors
/
Tasmota
mirror of https://github.com/arendst/Tasmota.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

added link to tuya protocols

blakadder 2019-10-24 14:59:49 +02:00
parent d5475df57c
commit 9a47cd5b15
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
TuyaMCU.md

@ -7,8 +7,8 @@ The TuyaMCU module introduces a new command [`TuyaMCU`](commands#tuyamcu) which
> Used only if your device is defined as module `TuyaMCU (54)` (formerly: `Tuya Dimmer (54)`) .
## DpId
All the components (relays, dimmers, switches) controlled by the MCU are identified by a DpId.
Whenever a command is sent to the MCU, this DpId dictates which relay or dimmer needs to be changed and same is used when the status is received from MCU.
All the components (relays, dimmers, switches, lights, sensors, etc) controlled by the MCU are identified by a DpId.
Whenever a command is sent to the MCU, this DpId dictates which component needs to be changed and same is used when the status is received from MCU.
There is no way the Wi-Fi module firmware knows the function of each DpId, so, just like [configuring GPIOs](Configuration-Procedure-for-New-Devices) for your device, you need to map DpId's with their functions.
@ -45,7 +45,7 @@ When no parameters are provided `TuyaMCU` prints the current mapped values.
## Identification of FunctionIDs and DpIds
As mentioned, the hardware is controlled by an MCU. The Wi-Fi module sends commands to MCU over serial to control the hardware. Each hardware component has a DpId which can have different functions on each model.
As mentioned, the hardware is controlled by an MCU. The Wi-Fi module sends commands to MCU over serial to control the hardware. Each hardware component has a DpId which can have different functions on each model. See [this list](tuya-protocols) for *possible* combinations.
We need to identify these DpIds: