-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TuyaMCU Update #9330
TuyaMCU Update #9330
Conversation
oops
Great! |
Good news! I'm just anxious to try it this night at home! Thank you @effelle |
Will probably need some extra polish but since is a big update any feedback will be really appreciated. |
sure! don't worry. I will give you some feedback during this week. |
Nice job! I'll have to check this out this weekend when I have time to play. |
@arendst |
Nope. No change on my side. |
I have been trying to get XMCosy string lights working -- with the latest build it seems like the RGB control to dpid 5 doesn't work. The only format that works that I can find is RRGGBB as the type3 string. Have we seen other tuya controllers which might only work with RGB, or is there something else that I could try? https://www.amazon.com/Outdoor-String-Lights-Colored-Waterproof/dp/B08614LWZK?ref_=ast_sto_dp |
Yes I have. Tuya folks have nothing to do then there are two different setup to pass the RGB color and at this point I don't exclude there are more out there. TUYASEND3 = 5,140100ffff6464 If is working means you need a string with |
I suspect it is what you point out, since when I do a send0 and read back dpid 5 when color is blue, the value is 0000FF00006464. Looking forward to the update! |
Ok, I'll try to find some time for it. |
do you think it will require a parameter to control the format, or can you auto-detect somehow? |
23:19:35 CMD: Group 0, Index 3, Command "TUYASEND", Data "5,140100ffff6464" |
No there will be another fnId for the RGB becasue the most common (fnId 24) is the one already implemented. |
Awesome! Will try
…On Sun, Nov 8, 2020, 4:27 AM Federico Leoni ***@***.***> wrote:
#9769 <#9769>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#9330 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAATJQ4X7XAIRKJR76QTD6TSO2FDDANCNFSM4RPJLAGA>
.
|
Please report your findings and... Good luck! |
I build and tested this:
Good news: color works!
However, when I set this I now see the color selector, color temp and mode
go away on the UI -- and it's replaced with 3 RGB sliders.
There is no longer access to CW on the menu.
Could this be that I have configured something wrong?
11:41:29 RSL: stat/tasmota_7FFA57/RESULT =
{"TuyaMCU":[{"fnId":11,"dpId":1},{"fnId":21,"dpId":3},{"fnId":26,"dpId":2},{"fnId":24,"dpId":5}]}
[image: Screen Shot 2020-11-14 at 10.41.55 AM.png]
…On Mon, Nov 9, 2020 at 2:10 PM Federico Leoni ***@***.***> wrote:
Please report your findings and... Good luck!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#9330 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAATJQ2OZ26BQIBAIMY7ZBTSPBSGHANCNFSM4RPJLAGA>
.
|
Also if I try and set 23->4 (CT channel) then it removes the RGB setting
(24,5).
…On Sat, Nov 14, 2020 at 10:42 AM Richard McDougall ***@***.***> wrote:
I build and tested this:
Good news: color works!
However, when I set this I now see the color selector, color temp and mode
go away on the UI -- and it's replaced with 3 RGB sliders.
There is no longer access to CW on the menu.
Could this be that I have configured something wrong?
11:41:29 RSL: stat/tasmota_7FFA57/RESULT =
{"TuyaMCU":[{"fnId":11,"dpId":1},{"fnId":21,"dpId":3},{"fnId":26,"dpId":2},{"fnId":24,"dpId":5}]}
[image: Screen Shot 2020-11-14 at 10.41.55 AM.png]
On Mon, Nov 9, 2020 at 2:10 PM Federico Leoni ***@***.***>
wrote:
> Please report your findings and... Good luck!
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#9330 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAATJQ2OZ26BQIBAIMY7ZBTSPBSGHANCNFSM4RPJLAGA>
> .
>
|
Description:
Changelog:
1: To enable a dual dimmer setup assign the following functions (fnId):
Tasmota will automatically enable
SetOption68
and the dimmers will respond toChannel1
andChannel2
commands.Obs.: The use of
SetOption68
is limited to two channels and will be automatically disabled if any other combination of lights will be used.2: Special lights:
To enable an CT light assign the following functions (fnId):
To enable an RGB light assign the following functions (fnId):
To enable an RGB+W light use the RGB configuration and append fnId 25 to the correct dpId.
Last but not least, for an RGB+CT light use the RGB configuration and append fnId 23.
obs.: At the present time the use of
SetOption68
for more than two channels and the light split option (SetOption37 >= 128) are not supported.3: The majority of TuyaMCU devices with an RGB+W or an RGB+CT light needs a button to switch between White and colored light.
Is now possible enable the ModeSet selector adding the function 26. A button on the WebUI will be available.
When the ModeSet function is enabled will not be possible to update both lights at the same time. The possible values are 0 (white) and 1 (colorful).
4: To setup a fan controller select one of the available functions:
Obs.: Different from other fan controllers like the Ifan03, the value
0
desn't mean OFF. A TuyaMCU will consider a0
as the lowest speed possible. ON/OFF states for a fan are always managed by another dpId, then you need to add the correct relay function.5: Single Shutter or double shutters devices can be managed with a normal dimmer setup, for devices that have the face plate buttons reporting to another dpId like the Zemismart WiFi Tuya Roller Shade, enable:
6: Some extra functions were enabled and are still a work in progress:
The last one is useful only if you don't want to manage the dpId assigned to the MCU. Enabling the dummy will let you remove the first relay (fnId 11) added by default in any configuration.
7: Use
TuyaSend9
without any payload to toggle aSTAT
topic reporting the equivalentTuyaSend<x>
command needed to update a dpId, for example:Disabled by default, the topic can be easily grabbed by any home automation system.
8: Instead of using
SerialSend5 55aa000100000
to get all the device information, you may want to useTuyaSend8
command or useTuyaSend0
to query just the state of the dpId.@arendst : I've reused the old 33F on settings.h.
Related issue (if applicable): fixes #8880 and #8663
Checklist:
NOTE: The code change must pass CI tests. Your PR cannot be merged unless tests pass