Tuya mcu support

[shantur]

Description:

More and more Tuya MCU based devices are coming in the market and people requesting to support them. This patch makes Tuya module more configurable and easier to add new functionalities. Its not just a dimmer or a switch anymore.

After this Patch Tuya MCU module has a list of supported functions and the user would need to map the functionId to dpId of their device. Once mapped correctly the Tuya module will take care for handling proper function for dpId.

Currently functions supported are

1. Switches 1 to 4 : FunctionID 1 to 4
2. Relays1 to 8 : FunctionID 11 to 18
3. Dimmer : FunctionID 21
4. Power ( Deca Watt ) : Function ID 31
5. Current ( milli Amps ) : Function ID 32
6. Voltage ( deca Volts ) : Function ID 33
7. Inverted Relays1 to 8 : Function ID 41 to 48

The changes are

• Use a TuyaMCU command to map DPs to Functions instead of many different SetOptions. SetOption41, 44, 45, 46, 65 and many future ones won't be needed after this patch.
• Each Tuya device a maximum of 16 functions is supported
• TuyaMCU command takes argument like 11,1 which means Map Function id 11 (Relay1) to DPID 1
• Migrates old settings flags and options to new TuyaMap command
• Renames Tuya Dimmer module to Tuya MCU

A wiki page for new Tuya MCU implementation will be created once this PR is merged in.

As per plan each SetOption can be removed as well after this goes in.

Related issue (if applicable): fixes #6319

Checklist:

• The pull request is done against the latest dev branch
• Only relevant files were touched
• Only one feature/fix was added per PR.
• The code change is tested and works on core 2.3.0, 2.4.2 and 2.5.2
• The code change pass travis tests. Your PR cannot be merged unless tests pass
• I accept the CLA.

[arendst]

Many Thx

[shantur]

@arendst : Thanks for merging this in.

Given that this is now merged, I would suggest removal of SetOption41, 44, 45, 46, 65 in next stable development release. Given that SetOption 44, 45, 46 were added in 6.6.0.8+, these can be easily dropped.

[arendst]

Right.

I will investigate the consequences and get rid of them ASAP to make the user base as small as possible.

[arendst]

While preparing for clean up I came across Settings.flag3.tuya_disable_dimmer which still seems to be used in tuyamcu.ino lines 300 and 309.

Shouldn't they be replaced by the new functionality? If not then SetOption65 is still needed.

[shantur]

Yes, tuya_disable_dimmer needs to go. Its my bad, i will raise a PR with the change

[shantur]

Cleaned up in #6355

[vajonam]

@shantur this did work for some period, I left it alone for a while and the MCU stopped responding, is this a known issue? how can I help debug this?

[blackscreener]

Are you planning support for 2 channel tuya mcu dimmer?

[shantur]

@blackscreener : Open a new issue and post some logs

[blackscreener]

@shantur
#8663