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

Updated TuyaMCU (markdown)

blakadder 2019-10-28 02:46:41 +01:00
parent 1c4d32c09c
commit 524081f610
1 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
TuyaMCU.md

@ -126,7 +126,7 @@ Component| FunctionId|Note
-|-|-
Switch1 to Switch4 | 1 to 4 | Map only to dpId with on / off function
Relay1 to Relay8 | 11 to 18 | Map only to dpId with on / off function
Dimmer | 21 | only on dpId with dimming function
Dimmer | 21 | Only on dpId with dimming function
Power (in deci Watt) | 31 |
Current (in milli Amps) | 32 |
Voltage (in deci Volt) | 33 |
@ -183,11 +183,9 @@ After issuing serial command `55aa0006000501010001010e` (Device power (dpId=1) i
```
Above `TYA: fnId=11 is set for dpId=1` you can see the JSON response for that dpId. This JSON string displays the response MCU gave to our command.
"Data" field contains the complete response and the rest of the key/value pairs show the protocol broken into parts. "DpId", "DpIdData" and "DpIdType" are the ones we're most interested in since we can used them for `TuyaSend`.
"Data" field contains the complete response and the rest of the key/value pairs show the protocol broken into parts. "DpId", "DpIdData" and "DpIdType" are the ones we're most interested in since we can use them for `TuyaSend`.
> You can use command `SerialSend5 55aa0001000000` at any time to request statuses of all dpId's from the MCU.
> Use command `SerialSend5 55aa0001000000` at any time to request statuses of all dpId's from the MCU.
### Use in rules
This data can also be used as a trigger for rules using `TuyaReceivedData#Data=hex_string`