mirror of https://github.com/arendst/Tasmota.git
Updated TuyaMCU (markdown)
parent
857692066a
commit
e4c1475ed6
|
@ -65,7 +65,7 @@ Use this procedure to determine which dpId's are available:
|
|||
4. Observe all lines printed as `TYA: FnId=0 is set for dpId=XXX` and note all dpId values.
|
||||
|
||||
Now that you have a list of usable dpId's you need to determine what their functions are:
|
||||
1. Consulting our [list of commonly used](#dpid-function-tables) dpId's and existing device configurations
|
||||
1. Consulting our [list of commonly used](tuya-protocols#dpid-function-tables) dpId's and existing device configurations
|
||||
2. Observing Tasmota logs while activating features of the device (with a remote or on device controls) and correlating log messages
|
||||
3. Extrapolating possible function of the dpId based on Data Type and Function Command, then testing using `TuyaSend<x>`
|
||||
|
||||
|
@ -88,7 +88,7 @@ Since the majority of devices have a power on/off functions on dpId 1 its mapped
|
|||
|
||||
***Mapping a relay or switch to a dpId that is not Data Type 0x01 (simple on/off) might result in unwanted power toggling (f.e. dpId sends value of 4 which toggles the relay to Power 4 aka blink mode***
|
||||
|
||||
### More on [TuyaMCU configuration of specific devices](tuyamcu-configurations)
|
||||
## [TuyaMCU configurations of specific devices](tuyamcu-configurations)
|
||||
|
||||
# TuyaSend
|
||||
**Requires latest development version, not supported in 6.7.1**
|
||||
|
|
Loading…
Reference in New Issue