logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda
UV printer on your desk?
UV printer on your desk? Discover eufyMake E1 »
ADVERTISEMENT
Dostępna jest polska wersja

Czy wolisz polską wersję strony elektroda?

Nie, dziękuję Przekieruj mnie tam

New firmware for WT5 Multi-Channel LED controller with RF - TuyaMCU?

Kinsi55 13278 107
Best answers

Can I flash alternative firmware on a WT5 multi-channel LED controller and use it as a TuyaMCU device with RF still working?

Yes — the WT5 was identified as a TuyaMCU-style device, so flashing the WB3S Wi‑Fi module is supported, and the RF side should keep working because the RF is handled by the secondary MCU, not by the Wi‑Fi firmware [#20687286][#21364024] A working OpenBeken setup was posted with `startDriver TuyaMCU`, `tuyaMcu_setBaudRate 115200`, `tuyaMcu_defWiFiState 4`, and `tuyaMcu_setupLED 24 0`, and users confirmed that OBK works on these WT5/TuyaMCU LED controllers [#20785808][#20838429] The device’s TuyaMCU protocol was also captured and mapped to dpIDs like 20 for on/off, 22 for brightness, 23 for color temperature, and 24 for RGB color, so OBK can control the light through those TuyaMCU values [#20885149][#20884346] One remaining issue was that OBK could overwrite the MCU’s saved startup state, but that was later addressed with `tuyaMcu_enableAutoSend 0` to suppress automatic sending during boot [#21619412]
Generated by the language model.
ADVERTISEMENT
Report a violation of the law
Reply | New topic
  • #61 20873958
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14631
    Help: 655
    Rate: 12647
    So, I will just try to add the feature you requested and we will see if it helps
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #62 20884069
    alvaroconsuegra
    Level 7  
    Posts: 12
    Help: 1
    Rate: 2

    I have a Tuya WT5, but mine has the CB3S / BK7231N module and the SC95F8615P MCU.
    I have successfully flashed it with Esphome but I have no RGB working. I have the Tuya firmware backup, but some dp_id are not extracted. I have all the dp_id's reported in Tuya IoT Cloud:
    Code: text Expand Select all Copy to clipboard
    
      {
        "code": "switch_led",
        "custom_name": "",
        "dp_id": 20,
        "time": 1703708024378,
        "value": false
      },
    
        "code": "work_mode",
        "custom_name": "",
        "dp_id": 21,
        "time": 1703706249327,
        "value": "white"
      },
      {
        "code": "bright_value",
        "custom_name": "",
        "dp_id": 22,
        "time": 1703706258813,
        "value": 1000
      },
      {
        "code": "temp_value",
        "custom_name": "",
        "dp_id": 23,
        "time": 1703706271490,
        "value": 514
      },
      {
        "code": "colour_data",
        "custom_name": "",
        "dp_id": 24,
        "time": 1703689075163,
        "value": "00fb03e8024b"
      },
      {
        "code": "scene_data",
        "custom_name": "",
        "dp_id": 25,
        "time": 1703689008964,
        "value": ""
      },
      {
        "code": "countdown",
        "custom_name": "",
        "dp_id": 26,
        "time": 1703705830888,
        "value": 0
      },
      {
        "code": "music_data",
        "custom_name": "",
        "dp_id": 27,
        "time": 1703689008964,
        "value": ""
      },
      {
        "code": "control_data",
        "custom_name": "",
        "dp_id": 28,
        "time": 1703689008964,
        "value": ""
      },
      {
        "code": "debug_data",
        "custom_name": "",
        "dp_id": 29,
        "time": 1703689008964,
        "value": ""

    The ID 24 is the color and I have tried to code it in the YAML without success.
    Can anybody confirm if the open beken firmware works with RGB and CCT?
    If the Tuya firmware is of any help, I can attach it. Thanks
  • ADVERTISEMENT
  • #63 20884346
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14631
    Help: 655
    Rate: 12647
    It's hard to say for certain, but even if there is an issue with OBK, we can resolve it quickly for you. Please flash, also maybe provide more info about your device and we will try to configure it. In worst case, we will have to do TuyaMCU capture again if Tuya has changed something in their communication protocol.

    EDIT: If you have the same WT5 as other users, most likely this config can work:
    https://www.elektroda.com/rtvforum/topic3994996-30.html#20785808
    Helpful post? Buy me a coffee.
  • #64 20884355
    alvaroconsuegra
    Level 7  
    Posts: 12
    Help: 1
    Rate: 2

    I will flash openBK and test it with the autoexec from your link.
    If it don't work, I will flash tuya firmware again to capture serial traffic from CB3S to MCU and from MCU to CB3S in response to actions in tuya app.
  • #65 20884408
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14631
    Help: 655
    Rate: 12647
    Please try, we will do our best to make sure it will work for you.

    By the way, here is our TuyaMCU analyzer: https://www.elektroda.com/rtvforum/topic3970199.html#20528459
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #66 20884460
    alvaroconsuegra
    Level 7  
    Posts: 12
    Help: 1
    Rate: 2

    Nice.
    I have successfully installed openbk and configured the connection to my wifi AP.
    I can't see where to write the autoexec.bat...

    Added after 2 [minutes]:

    OK, found it.
    I have to create a new file and copy the content.

    Added after 24 [minutes]:

    Screenshot of OpenBK7231N control panel with LED settings.
    OK, as in esphome, CCT part is working, but RGB part has no effect.
    I think that it has to do with DP 21, which should allow to select from CCT or Color.
    BTW, in the web app, under led tools, I can turn on 100% R, G, B, WW, and CW, so it looks like CB3S can send all necessary DP to MCU[/img]

    Added after 6 [minutes]:

    Oops, it looks like RGB is working. The problem was that once the color dialog is open, only the first selection is applied.
  • #67 20884645
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14631
    Help: 655
    Rate: 12647
    So, everything works as expected in OBK? Well, I am happy to hear that, considering that it's a handcrafted software, made mostly by me. Please double check if everything is okay and whether you are happy with the results, if not, I can try to help/improve the driver if it's required.

    PS: The color picker is kinda out of our control so I am not sure if we can improve that, maybe we could just create our own custom picker.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #68 20885032
    alvaroconsuegra
    Level 7  
    Posts: 12
    Help: 1
    Rate: 2

    What I have found until now is:
    - Switch (DP20) is updated in openbk when I toggle it from RF remote.
    - Color (DP24), Temperature (DP23), and Bright (DP22) are not updated in openbk when modified in RF remote.

    As a side effect, when you toggle light off from remote and back on, the values of color, temperature, and bright are set to the values in openBK.
    For example, if you configure in openbk as Cold white at full bright and then modify by remote to warm white low bright, if you toggle light switch (DP20) off and back on (no matter if you toggle it by openBK or remote), the light is turned on at cold white, full bright.
    Now I will try to integrate it in HA (need to read some how-to) and from tomorrow I will flash it with original Tuya firmware to test if all actions in remote are correctly reported in the app. If so, then I can capture the serial communication to and from MCU with each action to find out the differences between openbk and Tuya firmware.
    Thank you for your help and I hope you get a good beginning to 2024 :-)
  • #69 20885079
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14631
    Help: 655
    Rate: 12647
    Wait.
    alvaroconsuegra wrote:

    - Color (DP24), Temperature (DP23), and Bright (DP22) are not updated in openbk when modified in rf remote.)

    Please open OBK web app log, clear the log, and change, let's say, first color, and tell me what kind of data is received by OBK TuyaMCU driver. Then do the same for temperature, brightness, etc.

    I am asking for that because I would like to know whether is there anything sent on RF change at all to OBK. This is because I have already tested similiar device and I was suprised to find that actually no temperature/brightness updates are sent via MCU to WiFi module, but that may not be the case here.

    Once you do this test, let me know, I can easily update OBK to parse incoming data if only this data is being sent,
    Helpful post? Buy me a coffee.
  • Helpful post
    #70 20885149
    alvaroconsuegra
    Level 7  
    Posts: 12
    Help: 1
    Rate: 2
    OK, 1st a picture of the board and remote:
    Electronic board with connected wires and Tuya module.
    Remote control with a color ring for light adjustment and function buttons.

    Added after 2 [minutes]:

    Now for the logs:
    Push on and imediately off on RF remote:
    Code: text Expand Select all Copy to clipboard
    Info:TuyaMCU:TUYAMCU received: 55 AA 03 03 00 00 05 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 3 (WiFiState) with 7 bytes
Info:TuyaMCU:TUYAMCU received: 55 AA 03 00 00 01 01 04 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 0 (Hearbeat) with 8 bytes
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 14 01 00 01 01 25 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 20, dataType 1-bool and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 1
Info:TuyaMCU:Color is sent as 0000000003E8
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 14 01 00 01 01 25 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 20, dataType 1-bool and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 1
Info:TuyaMCU:Color is sent as 0000000003E8
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 10 18 03 00 0C 30 30 30 30 30 30 30 30 30 33 45 38 A0 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 23 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 24, dataType 3-str and 12 data bytes
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 10 18 03 00 0C 30 30 30 30 30 30 30 30 30 33 45 38 A0 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 23 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 24, dataType 3-str and 12 data bytes
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 14 01 00 01 00 24 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 20, dataType 1-bool and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 0
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 14 01 00 01 00 24 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 20, dataType 1-bool and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 0



    With light on, Press CCT on remote an then color:
    Code: text Expand Select all Copy to clipboard
    Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 01 86 B5 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 390
Info:TuyaMCU:TUYAMCU received: 55 AA 03 00 00 01 01 04 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 0 (Hearbeat) with 8 bytes



    Type bright button on remote an then swipe in CW the CCT/RGB weel:
    Code: text Expand Select all Copy to clipboard
    Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 DE 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 DE 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 DE 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 DE 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 DE 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 DE 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 DE 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 DE 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 DE 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 DE 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 DE 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 DE 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 DE 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 DE 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TUYAMCU received: 55 AA 03 00 00 01 01 04 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 0 (Hearbeat) with 8 bytes
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 DE 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 DE 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 DE 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 DE 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 DE 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 DE 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:GEN:dhcp=0 ip=192.168.0.74 gate=192.168.0.2 mask=255.255.255.0 mac=c4:82:e1:34:7a:dd
Info:GEN:sta: 1, softap: 0, b/g/n
Info:GEN:sta:rssi=-47,ssid=acopen,bssid=50:c7:bf:8b:39:de,channel=13,cipher_type:CCMP


    Pushing R, G or B button has no efect on log

    In CCT mode, swipe CW the weel:
    Code: text Expand Select all Copy to clipboard
    Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 00 55 83 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 85
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 00 90 BE 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 144
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 00 A4 D2 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 164
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 00 C3 F1 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 195
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 00 DE 0C 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 222
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 320
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 01 67 96 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 359
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 01 8E BD 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 398
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 01 9A C9 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 410
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 01 A1 D0 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 417
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 01 B5 E4 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 437
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 01 C1 F0 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 449
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 01 C9 F8 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 457
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 01 DC 0B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 476
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 01 FB 2A 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 507
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 02 07 37 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 519
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 02 0F 3F 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 527
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 02 22 52 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 546
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 02 2E 5E 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 558
Info:TuyaMCU:TUYAMCU received: 55 AA 03 00 00 01 01 04 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 0 (Hearbeat) with 8 bytes


    In CCT mode, and brigt, swipe CW
    Code: text Expand Select all Copy to clipboard
    Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 27 54 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 39
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 4E 7B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 78
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 55 82 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 85
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 61 8E 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 97
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 7D AA 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 125
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 90 BD 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 144
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 A4 D1 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 164


    Added after 3 [minutes]:

    The buttons from the upper row (cloud and >>) dos not produce any log
    R, G and B in the last row does not produce any log, but changes the light color.
  • #71 20886019
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14631
    Help: 655
    Rate: 12647
    Thank you, so I added a receive for dpIDs 22 and 23.
    However, I have not tested it, especially for the "send back" case.

    Can you download "build artifacts" zip here:
    https://github.com/openshwprojects/OpenBK7231T_App/pull/1017
    Update your device and test the new feature?

    Please note that it may not work good at the first try, so I need your help with testing it several times, maybe I will have to improve that.
    Helpful post? Buy me a coffee.
  • #72 20886051
    alvaroconsuegra
    Level 7  
    Posts: 12
    Help: 1
    Rate: 2

    Hi, here I am again.
    I am not familiar with GitHub.
    The link looks like a differences file for the source code.
    I assume I have to download sources, apply the differences, and compile?
    I don't know how to do it...
    If you can give me some instructions, I will do it.
    Thanks
  • #73 20886054
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14631
    Help: 655
    Rate: 12647
    Click details here:
    Overview of build results in the GitHub Actions panel with the Details button highlighted.
    It opens a page like that:
    https://github.com/openshwprojects/OpenBK7231...tions/runs/7376088134/job/20068590834?pr=1017
    Then click summary:
    Screenshot showing GitHub interface with Summary button selected.
    Then scroll down and you see:
    Screenshot of GitHub Actions showing the build section and artifacts for OpenBK7231T_App.
    And you can download a package:
    https://github.com/openshwprojects/OpenBK7231.../actions/runs/7376088134/artifacts/1141679109


    Please check this build, especially for "ping pong" edge case where TuyaMCU sends change to WIFI module and WiFI module sends it back to the MCU and MCU sends it again.. .etc etc. Maybe backup your config first, if you are in doubt.
    Helpful post? Buy me a coffee.
  • #74 20886107
    alvaroconsuegra
    Level 7  
    Posts: 12
    Help: 1
    Rate: 2
    Thanks for the detailed instructions.
    I have updated by OTA in web application:
    IoT device information with MAC address and software version.
    It still restore the values left in the web UI.
    Attached log is selecting only tuya MCU.
    With the brigtness bar at full, in the remote i select brigtness, reduce the value and toogle off an then on.
    The stripe when i toogle off whas on with low bright, and when i tooble back on, it is full bright, with values from web UI.
    Code: text Expand Select all Copy to clipboard
    Info:MAIN:Time 97, idle 80846/s, free 60040, MQTT 1(1), bWifi 1, secondsWithNoPing 25, socks 4/38 POWERSAVE
Info:TuyaMCU:TUYAMCU received: 55 AA 03 00 00 01 01 04 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 0 (Hearbeat) with 8 bytes
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:MAIN:Time 98, idle 78250/s, free 60040, MQTT 1(1), bWifi 1, secondsWithNoPing 26, socks 4/38 POWERSAVE
Info:MAIN:Time 99, idle 82125/s, free 60040, MQTT 1(1), bWifi 1, secondsWithNoPing 27, socks 4/38 POWERSAVE
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:MAIN:Time 100, idle 76857/s, free 60040, MQTT 1(1), bWifi 1, secondsWithNoPing 28, socks 4/38 POWERSAVE
Info:GEN:dhcp=0 ip=192.168.0.74 gate=192.168.0.2 mask=255.255.255.0 mac=c4:82:e1:34:7a:dd
Info:GEN:sta: 1, softap: 0, b/g/n
Info:GEN:sta:rssi=-46,ssid=acopen,bssid=50:c7:bf:8b:39:de,channel=13,cipher_type:CCMP
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:MAIN:Time 101, idle 64883/s, free 51432, MQTT 1(1), bWifi 1, secondsWithNoPing 29, socks 5/38 POWERSAVE
Info:TuyaMCU:TUYAMCU received: 55 AA 03 00 00 01 01 04 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 0 (Hearbeat) with 8 bytes
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:MAIN:Time 102, idle 142351/s, free 60040, MQTT 1(1), bWifi 1, secondsWithNoPing 30, socks 4/38 POWERSAVE
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 03 D0 00 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 976
Info:MAIN:Time 103, idle 83106/s, free 60040, MQTT 1(1), bWifi 1, secondsWithNoPing 31, socks 4/38 POWERSAVE
Info:MAIN:Time 104, idle 82545/s, free 60040, MQTT 1(1), bWifi 1, secondsWithNoPing 32, socks 4/38 POWERSAVE
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 14 01 00 01 00 24 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 20, dataType 1-bool and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 0
Info:MQTT:Publishing val 0 to obkE1347ADD/led_enableAll/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obkE1347ADD/led_enableAll/get
Info:MAIN:Time 105, idle 73574/s, free 60040, MQTT 1(1), bWifi 1, secondsWithNoPing 33, socks 4/38 POWERSAVE
Info:TuyaMCU:TUYAMCU received: 55 AA 03 00 00 01 01 04 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 0 (Hearbeat) with 8 bytes
Info:MAIN:Time 106, idle 79564/s, free 60040, MQTT 1(1), bWifi 1, secondsWithNoPing 34, socks 4/38 POWERSAVE
Info:MAIN:Time 107, idle 83331/s, free 60040, MQTT 1(1), bWifi 1, secondsWithNoPing 35, socks 4/38 POWERSAVE
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 14 01 00 01 01 25 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 20, dataType 1-bool and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 1
Info:TuyaMCU:Color is sent as 0000000003A2
Info:MQTT:Publishing val 1 to obkE1347ADD/led_enableAll/get retain=0
Info:MQTT:Publishing val 97 to obkE1347ADD/led_dimmer/get retain=0
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 14 01 00 01 01 25 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 20, dataType 1-bool and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 1
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obkE1347ADD/led_enableAll/get
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obkE1347ADD/led_dimmer/get
Info:TuyaMCU:Color is sent as 0000000003A2
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 10 18 03 00 0C 30 30 30 30 30 30 30 30 30 33 41 32 96 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 23 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 24, dataType 3-str and 12 data bytes
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 10 18 03 00 0C 30 30 30 30 30 30 30 30 30 33 41 32 96 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 23 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 24, dataType 3-str and 12 data bytes
Info:MAIN:Time 108, idle 64202/s, free 60040, MQTT 1(1), bWifi 1, secondsWithNoPing 36, socks 4/38 POWERSAVE
Info:MAIN:Time 109, idle 80193/s, free 60040, MQTT 1(1), bWifi 1, secondsWithNoPing 37, socks 4/38 POWERSAVE
Info:TuyaMCU:TUYAMCU received: 55 AA 03 00 00 01 01 04 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 0 (Hearbeat) with 8 bytes
Info:MAIN:Time 110, idle 82530/s, free 60040, MQTT 1(1), bWifi 1, secondsWithNoPing 38, socks 4/38 POWERSAVE
Info:GEN:dhcp=0 ip=192.168.0.74 gate=192.168.0.2 mask=255.255.255.0 mac=c4:82:e1:34:7a:dd
Info:GEN:sta: 1, softap: 0, b/g/n
Info:GEN:sta:rssi=-43,ssid=acopen,bssid=50:c7:bf:8b:39:de,channel=13,cipher_type:CCMP
Info:MAIN:Time 111, idle 80360/s, free 51416, MQTT 1(1), bWifi 1, secondsWithNoPing 39, socks 5/38 POWERSAVE
Info:MAIN:Time 112, idle 88356/s, free 60040, MQTT 1(1), bWifi 1, secondsWithNoPing 40, socks 4/38 POWERSAVE
  • #75 20886122
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14631
    Help: 655
    Rate: 12647
    Can you please be more clear at how it works, because I can't seem to tell it from your message?

    What happens when you:
    1. set the CW brightness in OBK to 100%, and then from remote change it to 50% - does OBK follow the state of remote?
    2. Set the CW temperature to warm in OBK, and then change it to cold from remote - does OBK follow the state of remote?
    Helpful post? Buy me a coffee.
  • #76 20886174
    alvaroconsuegra
    Level 7  
    Posts: 12
    Help: 1
    Rate: 2
    >> 1. set the CW brightness in OBK to 100%, and then from remote change it to 50% - does OBK follow the state of remote?
    It is updated in OBK, but some times, it has a strange beavior:
    When i modify brigtness in remote, the controler fall in a loop, alternating between 2 values, as you can see in the logs:
    Code: text Expand Select all Copy to clipboard
    Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 350
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 03 CA FB 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 970
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 01 A4 D2 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 420
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 03 CA FB 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 970
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 28 55 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 40
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 03 CA FB 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 970
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 50 7D 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 80
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 03 CA FB 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 970
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 01 36 64 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 310
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 03 CA FB 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 970
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 01 5E 8C 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 350
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 03 CA FB 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 970
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 01 A4 D2 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 420
5 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 40
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 03 CA FB 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 970
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 50 7D 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 80
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 03 CA FB 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 970
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 01 36 64 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 310
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 03 CA FB 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 970
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 01 5E 8C 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 350
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 03 CA FB 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 970
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 01 A4 D2 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 420
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 03 CA FB 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 970
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 28 55 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 40
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 03 CA FB 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 970
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 00 50 7D 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 80
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 03 CA FB 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 970
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 01 36 64 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 310


    If i modify again the brightness from remote, some times it gets out of the loop.
    I have also noticed that somtimes, when brigtness is updated in OBK, the light ON/OFF is modified to red, but the led stripe is on. If push it in OBK, it gets green and if i push it again, is gets red turn lights off.

    <<2. Set the CW temperature to warm in OBK, and then change it to cold from remote - does OBK follow the state of remote?
    It is also updated, but as with luminosity, some times there is a delay of several second in the update and one time, the controler has rebooted

    So it seems that the updates are working, but some times, it gets up to 5 or 6 seconds.... In my previous post, i am just toogling on off too fast.
  • #77 20886213
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14631
    Help: 655
    Rate: 12647
    It's the ping-pong case I was worried about. That's why we test.

    Okay, so I pushed update, can you check now?

    Now, OBK will not reply to MCU, only it will update the state.

    Please open the link, and scroll down to the bottom, and get the new binaries as I explained two posts ago...
    https://github.com/openshwprojects/OpenBK7231T_App/pull/1017
    Then recheck, and tell me if it works better, just please try to be precise, I need to know how it works.
    Build should be ready in two minutes, it's building right now:
    Screenshot of a GitHub page showing an open pull request for the openshwprojects project with two incomplete checks.
    Helpful post? Buy me a coffee.
  • #78 20886322
    alvaroconsuegra
    Level 7  
    Posts: 12
    Help: 1
    Rate: 2

    I have done the same tests as before, and everything looks fine to me.
    Values are updated in OBK and Home Assistant for the CCT part and no more loops.
    The only "problems" I can find are:
    When I select RGB in the remote and modify the color, the selected color is not reported to OBK, but the stripe color is modified.
    Maybe also related, when I put it in CCT mode, cold white full bright, the stripe looks pure white.
    If I disconnect the controller from power and reconnect it, the stripe is turned on at the same temperature and brightness in the CCT part, but it also has a little bit of red.
    If I power off and back on in color mode, for a moment, the last color selected in the remote is restored until the controller connects to the network, and then it turns on R, G, and B at a low brightness. This is not the color shown in the OBK interface.
    It looks like RGB values are not reported back correctly from the MCU.

    This is not a problem for me because I mainly use it for CCT.

    I will continue testing and reporting if I find something more.
    Very nice job and very nice firmware.

    In these logs, I push RGB in the remote and select a red color in the color wheel:

    Quote:
    Info:MAIN:Time 607, idle 149715/s, free 71632, MQTT 1(1), bWifi 1, secondsWithNoPing 536, socks 3/38 POWERSAVE
    Info:MAIN:Time 608, idle 73443/s, free 71632, MQTT 1(1), bWifi 1, secondsWithNoPing 537, socks 3/38 POWERSAVE
    Info:MAIN:Time 609, idle 68418/s, free 71632, MQTT 1(1), bWifi 1, secondsWithNoPing 538, socks 3/38 POWERSAVE
    Info:TuyaMCU:TUYAMCU received: 55 AA 03 00 00 01 01 04
    Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 0 (Heartbeat) with 8 bytes
    Info:MAIN:Time 610, idle 138694/s, free 71632, MQTT 1(1), bWifi 1, secondsWithNoPing 539, socks 3/38 POWERSAVE
    Info:GEN:dhcp=0 ip=192.168.0.74 gate=192.168.0.2 mask=255.255.255.0 mac=c4:82:e1:34:7a:dd
    Info:GEN:sta: 1, softap: 0, b/g/n
    Info:GEN:sta:rssi=-42,ssid=acopen,bssid=50:c7:bf:8b:39:de,channel=13,cipher_type:CCMP
    Info:MAIN:Time 611, idle 67903/s, free 71632, MQTT 1(1), bWifi 1, secondsWithNoPing 540, socks 3/38 POWERSAVE
    Info:MAIN:Time 612, idle 68853/s, free 71632, MQTT 1(1), bWifi 1, secondsWithNoPing 541, socks 3/38 POWERSAVE
    Info:MAIN:Time 613, idle 71830/s, free 71632, MQTT 1(1), bWifi 1, secondsWithNoPing 542, socks 3/38 POWERSAVE
    Info:TuyaMCU:TUYAMCU received: 55 AA 03 00 00 01 01 04
    Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 0 (Heartbeat) with 8 bytes
    Info:MAIN:Time 614, idle 72010/s, free 71632, MQTT 1(1), bWifi 1, secondsWithNoPing 543, socks 3/38 POWERSAVE
    Info:MAIN:Time 615, idle 73913/s, free 71632, MQTT 1(1), bWifi 1, secondsWithNoPing 544, socks 3/38 POWERSAVE
    Info:MAIN:Time 616, idle 71711/s, free 71632, MQTT 1(1), bWifi 1, secondsWithNoPing 545, socks 3/38 POWERSAVE
    Info:MAIN:Time 617, idle 69574/s, free 71416, MQTT 1(1), bWifi 1, secondsWithNoPing 546, socks 4/38 POWERSAVE
    Info:TuyaMCU:TUYAMCU received: 55 AA 03 00 00 01 01 04
    Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 0 (Heartbeat) with 8 bytes
    Info:MAIN:Time 618, idle 72275/s, free 71632, MQTT 1(1), bWifi 1, secondsWithNoPing 547, socks 3/38 POWERSAVE
    Info:MAIN:Time 619, idle 74967/s, free 71632, MQTT 1(1), bWifi 1, secondsWithNoPing 548, socks 3/38 POWERSAVE
    Info:MAIN:Time 620, idle 72435/s, free 71632, MQTT 1(1), bWifi 1, secondsWithNoPing 549, socks 3/38 POWERSAVE
    Info:GEN:dhcp=0 ip=192.168.0.74 gate=192.168.0.2 mask=255.255.255.0 mac=c4:82:e1:34:7a:dd
    Info:GEN:sta: 1, softap: 0, b/g/n

  • #79 20886335
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14631
    Help: 655
    Rate: 12647
    I would love to help more, but if the situation is as you say below:
    alvaroconsuegra wrote:

    It looks like RGB values are not reported back correctly from MCU.

    Then it's not possible to get color data...

    Of course, you can double check, and maybe you can also do experiment, execute this command with Web App log open:
    Code: text Expand Select all Copy to clipboard
    
tuyaMcu_sendQueryState

    and show me the log of all data received...
    Helpful post? Buy me a coffee.
  • #80 20886395
    alvaroconsuegra
    Level 7  
    Posts: 12
    Help: 1
    Rate: 2
    This is the log when i send the command:

    Code: text Expand Select all Copy to clipboard
    Info:MAIN:Time 3649, idle 75989/s, free 71632, MQTT 1(1), bWifi 1, secondsWithNoPing 3578, socks 3/38 POWERSAVE
Info:TuyaMCU:TUYAMCU received: 55 AA 03 00 00 01 01 04 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 0 (Hearbeat) with 8 bytes
Info:MAIN:Time 3650, idle 154055/s, free 71632, MQTT 1(1), bWifi 1, secondsWithNoPing 3579, socks 3/38 POWERSAVE
Info:GEN:dhcp=0 ip=192.168.0.74 gate=192.168.0.2 mask=255.255.255.0 mac=c4:82:e1:34:7a:dd
Info:GEN:sta: 1, softap: 0, b/g/n
Info:GEN:sta:rssi=-44,ssid=acopen,bssid=50:c7:bf:8b:39:de,channel=13,cipher_type:CCMP
Info:CMD:[WebApp Cmd 'tuyaMcu_sendQueryState' Result] OK
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 14 01 00 01 00 24 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 20, dataType 1-bool and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 0
Info:MQTT:Publishing val 0 to obkE1347ADD/led_enableAll/get retain=0
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 15 04 00 01 01 29 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 21, dataType 4-enum and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 1
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 01 54 82 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 340
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 03 DE 0F 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 990
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 1A 02 00 04 00 00 00 00 31 
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obkE1347ADD/led_enableAll/get
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 26, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 0
Info:MAIN:Time 3651, idle 58770/s, free 71632, MQTT 1(1), bWifi 1, secondsWithNoPing 3580, socks 3/38 POWERSAVE
  • #81 20886579
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14631
    Help: 655
    Rate: 12647
    Can you set the strip into the RGB mode and retry sending query command?
    Helpful post? Buy me a coffee.
  • #82 20886598
    alvaroconsuegra
    Level 7  
    Posts: 12
    Help: 1
    Rate: 2
    Code: text Expand Select all Copy to clipboard
    Info:MAIN:Time 12165, idle 75632/s, free 71416, MQTT 1(1), bWifi 1, secondsWithNoPing 12094, socks 4/38 POWERSAVE
Info:TuyaMCU:TUYAMCU received: 55 AA 03 00 00 01 01 04 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 0 (Hearbeat) with 8 bytes
Info:MAIN:Time 12166, idle 73700/s, free 71328, MQTT 1(1), bWifi 1, secondsWithNoPing 12095, socks 3/38 POWERSAVE
Info:CMD:[WebApp Cmd 'tuyaMcu_sendQueryState' Result] OK
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 14 01 00 01 01 25 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 20, dataType 1-bool and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 1
Info:TuyaMCU:Color is sent as 000003C0026C
Info:MQTT:Publishing val 1 to obkE1347ADD/led_enableAll/get retain=0
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 15 04 00 01 01 29 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 21, dataType 4-enum and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 1
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obkE1347ADD/led_enableAll/get
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 02 6C 9B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 620
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 17 02 00 04 00 00 03 DE 0F 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 990
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 1A 02 00 04 00 00 00 00 31 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 26, dataType 2-val and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 0
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 10 18 03 00 0C 30 30 30 30 30 33 43 30 30 32 36 43 B1 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 23 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 24, dataType 3-str and 12 data bytes
Info:MAIN:Time 12167, idle 69349/s, free 71632, MQTT 1(1), bWifi 1, secondsWithNoPing 12096, socks 3/38 POWERSAVE
  • #83 20889438
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14631
    Help: 655
    Rate: 12647
    It looks like RGB color is indeed sent in case of your device, or at least it's sent when we query state when in RGB mode. Still, I haven't seen it being sent when you changed color via remote... this is unexpected. Maybe we have missed that? Are you really sure that dpID 24 was not being sent when you changed colors with remote?
    Helpful post? Buy me a coffee.
  • #84 20891466
    atomphil
    Level 10  
    Posts: 31
    Help: 4
    Rate: 17
    With version 1.17.391, it also works for me that CCT and brightness change in the web interface if they have been changed via RF. However, only if they are changed via the controllers. If CCT and brightness are changed via a scene on the remote, nothing changes in the web interface. RGB changes are also not changed.

    Unfortunately, the problem that the correct values of the TuyaMCU are overwritten by the WiFi module still exists.

    It would be good if the WiFi module would only send values to the TuyaMCU when the user makes active inputs via the web interface or some changes received from HA. But at least, as already stated above, the sending of values after start-up should be suppressed. (This would significantly increase the WAF of my installation ;-) )
  • #85 20891476
    alvaroconsuegra
    Level 7  
    Posts: 12
    Help: 1
    Rate: 2

    Thanks. I will test it as soon as it is installed.
  • #86 20919237
    atomphil
    Level 10  
    Posts: 31
    Help: 4
    Rate: 17
    Is there any progress yet? ;)
  • #87 21051523
    st242
    Level 2  
    Posts: 2
    Rate: 1
    Im new to openbeken, i was looking for alternate WT5 firmware and found this. im familiar with tasmota.

    have managed to flash the latest (1.17.551) version, configured wifi & mqtt ok..

    i then added the autoexec start script on the `import` page..

    --------
    Code: text Expand Select all Copy to clipboard
    startDriver TuyaMCU
startDriver SSDP
PowerSave 1

tuyaMcu_setBaudRate 115200
tuyaMcu_defWiFiState 4
tuyaMcu_setupLED 24 0

    -------
    then got it discovered in HomeAssistant and it works.. great work...

    until i power cycle the WT5 device - then it stops working.
    i have to reapply the above `import` and it starts again..
    what am i missing ?
  • #88 21052871
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14631
    Help: 655
    Rate: 12647
    The import page just executes script once and then settings are forget after reboot.

    You should rather use autoexec.bat, which executes script on every reboot.

    Please see the autoexec.bat tutorial and follow steps there to create your script:


    Helpful post? Buy me a coffee.
  • #89 21095588
    atomphil
    Level 10  
    Posts: 31
    Help: 4
    Rate: 17

    >>20873958
    Is there now a way to switch off or suppress the initial sending of settings to the TuyaMCU without user input?
    I have been using the controller without the WiFi function for half a year now (simply not loading the Tuya driver) because this initial pointless sending of OpenBeken to the Tuya MCU only disturbs the use of our bathroom lighting.
    But it would be nice if I could use WiFi again, e.g. to integrate additional smart buttons via HA.
    Whether the web interface displays the correct values after start-up is irrelevant for our application.
  • #90 21364017
    goutiu5438
    Level 1  
    Posts: 1
    Hello, I wonder where the remote control input signal goes
    And I wonder where the output signal comes from and if only the output signal can be used through the connection line
    (I want to print out D+, D-, GND)
Reply | New topic
Report a violation of the law

Topic summary

✨ The discussion centers on the WT5 Multi-Channel LED controller with RF remote support, focusing on firmware flashing, TuyaMCU protocol integration, and OpenBeken (OBK) firmware usage. The WT5 uses a WB3S Wi-Fi module and an SC95F8615 secondary MCU controlling MOSFETs, with RF communication handled by an LT8900SSK chip via SPI. Users successfully dumped the 2MB flash, confirmed TuyaMCU communication at 115200 baud, and captured UART data to analyze DPIDs for LED control functions such as on/off (DP20), mode (DP21), brightness (DP22), temperature (DP23), and color data (DP24). OpenBeken firmware supports TuyaMCU devices, allowing Wi-Fi and MQTT integration, but challenges remain in synchronizing RF remote inputs with Wi-Fi state, especially for color and brightness updates. The Wi-Fi module overwrites LED states at startup, causing desynchronization with RF inputs; a proposed workaround involves delaying or suppressing initial state transmissions from Wi-Fi to MCU. SPI slave mode is not supported on WB3S, complicating passive listening to RF-MCU SPI communication; hardware modifications or bit-banged SPI on WB3S pins are considered. The WB3S is not 5V tolerant; level shifting via resistor dividers is recommended. Users report successful flashing and configuration of WT5 and related WB5 devices with OpenBeken, including integration with Home Assistant. Issues with web panel access and Wi-Fi connectivity were resolved by restoring bootloader and RF partitions and configuring static IP addresses. The community developed and tested firmware updates to improve TuyaMCU DP handling, reduce state update loops, and enhance RF and Wi-Fi coexistence. Documentation and tools such as TuyaMCUAnalyzer and OpenBeken web app guides support ongoing development and user assistance.
Generated by the language model.
Today's popular

FAQ

TL;DR: With 115200 baud and 5 confirmed core dpIDs, the WT5 works in OpenBeken via TuyaMCU; as one maintainer put it, "It’s TuyaMCU device." This FAQ is for WT5 owners who want stable RGB+CCT control, RF coexistence, correct autoexec.bat setup, and a fix for boot-time state overwrite using tuyaMcu_enableAutoSend. [#20687286]

Why it matters: A WT5 can appear fully working after flashing, yet still break daily use if OpenBeken overwrites the TuyaMCU’s RF-restored state a few seconds after power-up.

Approach RGB+CCT control RF coexistence Boot-state behavior Effort
OpenBeken + TuyaMCU Works Yes Needs autosend control for best coexistence Low
ESPHome on WT5 Partial in-thread, later working but less documented here Unclear Not resolved in-thread Medium
Replacing secondary MCU / direct RF driver Possible in theory Custom Fully custom High

Key insight: The easiest stable WT5 setup is to keep the secondary MCU and RF path intact, run OpenBeken as the Wi-Fi side over TuyaMCU at 115200, and suppress automatic resend on boot when RF state retention matters. [#21619412]

Quick Facts

  • WT5 boards discussed in the thread use WB3S or CB3S Wi-Fi modules plus a secondary MCU, and the PCB was traced as a 5-MOSFET design where PWM outputs go to the MCU, not directly to the Wi-Fi module. [#20687084]
  • The confirmed TuyaMCU UART speed for WT5 is 115200 baud, found in flash config and later used successfully with the analyzer and OpenBeken. [#20688328]
  • Confirmed WT5 Tuya dpIDs include 20 = on/off, 21 = mode, 22 = brightness, 23 = color temperature, 24 = color string, and 26 = countdown/state-related value 0 in query output. [#20699088]
  • RF still works after flashing OpenBeken because the secondary TuyaMCU handles RF locally; this was confirmed in practice after OBK flashing. [#20699117]
  • A later OpenBeken command, tuyaMcu_enableAutoSend 0, was added specifically to stop OBK from overwriting the TuyaMCU’s saved state during boot; an example autoexec re-enables autosend after 12 seconds. [#21619412]

How do I configure a WT5 Multi-Channel LED controller with a WB3S/CB3S module in OpenBeken using TuyaMCU and autoexec.bat?

Use TuyaMCU at 115200 baud and place the commands in autoexec.bat, not the Import page. A working minimal setup is:
  1. startDriver TuyaMCU
  2. tuyaMcu_setBaudRate 115200
  3. tuyaMcu_defWiFiState 4 and tuyaMcu_setupLED 24 0 Several users confirmed this works on WT5 units with WB3S and CB3S modules. The Import page only runs once, while autoexec.bat runs on every reboot, which fixes the “works until power cycle” problem. [#21052871]

Why does the WT5 restore the correct RF-set lighting state at power-up and then get overwritten by OpenBeken a few seconds later?

Because the TuyaMCU restores its own last state first, then OpenBeken later pushes its saved LED state back to the MCU. Users observed the light power up correctly from RF memory, then switch a few seconds later to OBK’s stored value or to cold-white full brightness when the remember-state flag was off. The root cause is OBK’s automatic send path for LED synchronization during boot. That behavior remained the practical blocker for mixed RF and Wi-Fi use until autosend control was added. [#20873136]

What is TuyaMCU, and how does it communicate with the Wi-Fi module in devices like the WT5 LED controller?

"TuyaMCU is a secondary control MCU that drives the real device functions while the Wi-Fi module exchanges high-level state over a serial protocol, usually on UART at a fixed baud rate." In the WT5, the WB3S/CB3S module talks to the secondary MCU over UART, and the thread confirmed the working rate is 115200 baud. The RF remote path stays on the secondary MCU side, which is why RF can still work after flashing the Wi-Fi module. [#20686758]

What is dpID in TuyaMCU, and which dpIDs are used by the WT5 for on/off, brightness, temperature, RGB color, and mode?

A dpID is the Tuya data-point identifier for one device function. On the WT5, the thread mapped dpID 20 = on/off, 21 = mode enum, 22 = brightness, 23 = color temperature, 24 = RGB color string, 26 = countdown/state value, and discussed 28 as an additional compound control string. Those mappings came from UART captures and later tuyaMcu_sendQueryState results on flashed devices. For practical OpenBeken control, dpIDs 20, 21, 22, 23, and 24 are the important ones. [#20699088]

Which OpenBeken commands are needed for the WT5, such as tuyaMcu_setBaudRate, tuyaMcu_defWiFiState, tuyaMcu_setupLED, and tuyaMcu_enableAutoSend?

The core WT5 commands are tuyaMcu_setBaudRate 115200, tuyaMcu_defWiFiState 4, and tuyaMcu_setupLED 24 0. Later, tuyaMcu_enableAutoSend 0 was added to suppress OBK’s automatic resend during boot, and one proven example re-enabled it after 12 seconds with addRepeatingEvent 12 1 tuyaMcu_enableAutoSend 1. Use startDriver TuyaMCU first, then the baud and Wi-Fi-state commands, then LED setup. That sequence preserves RF coexistence and fixes the common startup overwrite issue. [#21619412]

How can I capture and analyze TuyaMCU UART traffic from a WT5 using a logic analyzer or TuyaMCUAnalyzer?

Capture the WB3S/CB3S serial lines at 115200 baud and log both state changes and app or RF actions. The thread workflow was: 1. verify whether TX1/RX1 connect to the secondary MCU, 2. run a logic analyzer or TuyaMCU analyzer at 115200, 3. trigger known actions such as on/off, mode, brightness, and temperature changes. That method exposed dpIDs 20, 21, 22, 23, 24, and color-string formats. One maintainer explicitly said UART captures for each app operation were “very useful” for determining color format. [#20687757]

Why do RF remote changes on the WT5 update DP20 but sometimes not fully sync RGB, brightness, or CCT back to the OpenBeken web interface?

Because the WT5 does not report every RF-originated state back to the Wi-Fi module consistently. The thread repeatedly showed DP20 on/off arriving reliably, while RGB changes often produced no dpID 24 updates, and some scene or remote buttons produced no log entries at all. Later builds improved dpID 22 and 23 feedback, but users still reported missing RGB sync and scene-based changes that never appeared in the web UI. So the RF path works, yet full mirror-back to OBK remains partial on this device family. [#20891466]

What is the purpose of tuyaMcu_enableAutoSend in OpenBeken, and how does it prevent OBK from overriding the TuyaMCU saved state during boot?

tuyaMcu_enableAutoSend turns OpenBeken’s automatic TuyaMCU sending on or off. Setting it to 0 stops OBK from pushing its stored LED values during boot, so the TuyaMCU can keep the last RF-restored state instead of being overwritten a few seconds later. A WT5 user later posted a working solution with tuyaMcu_enableAutoSend 0 and optional re-enable after 12 seconds. That command was added specifically to solve the long-running WT5 mixed RF and Wi-Fi startup problem. [#21619412]

How do I use tuyaMcu_sendQueryState to see which TuyaMCU dpIDs the WT5 reports in CCT mode versus RGB mode?

Run tuyaMcu_sendQueryState from the web console with the log open, first in CCT mode and then in RGB mode. In the thread, query results in CCT returned dpIDs 20, 21, 22, 23, and 26, while RGB-mode query also returned dpID 24 with the 12-byte color string. That makes tuyaMcu_sendQueryState the fastest way to verify what the MCU will actually report back on your unit. It also exposes cases where RGB state exists internally but is not pushed during normal RF use. [#20886598]

What differences were found between dpID 24 and dpID 28 on the WT5, and how is the Tuya ASCII color format interpreted?

dpID 24 was identified as the main RGB color string, while dpID 28 looked like a longer compound string that may include both RGB and white-channel information. For example, one captured dpID 24 string decoded to 00 73 03 e8 03 e8 for a green test, matching a known Tuya color format already seen in another OpenBeken topic. The thread’s working conclusion was that dpID 24 is the actionable RGB field, while dpID 28 remained less certain and appeared to mirror extra white-related data. [#20689271]

OpenBeken vs ESPHome for a WT5 Tuya LED controller: which approach works better for RGB+CCT control and RF coexistence?

OpenBeken worked better in this thread because it got a documented TuyaMCU setup, working RGB+CCT control, and later a boot-overwrite fix. One CB3S user reported ESPHome flashed successfully but had no RGB working at first, while another later confirmed OpenBeken handled CCT and RGB on the same hardware. OpenBeken also preserved RF because it kept the TuyaMCU path intact. If you want the most evidence-backed path from this thread alone, OpenBeken is the safer choice for WT5 RGB+CCT plus RF coexistence. [#20884069]

How can I troubleshoot a flashed CB3S/WB3S WT5 that joins Wi-Fi incorrectly, does not expose an AP, or does not open the basic web panel after flashing?

First restore the bootloader and RF partition, then verify network settings. The thread fix was: 1. enable overwrite bootloader in the flasher if you used Erase All, 2. perform Restore RF partition, 3. test AP mode or set a static IP if DHCP behaves incorrectly. One CB3S user had no AP, no web panel, and partial Wi-Fi until restoring the bootloader; later, static IP plus router reservation made the basic web panel work. Also remember the basic panel is on port 80. [#21408440]

What is the RF partition and bootloader in BK7231 flashing, and why can 'Erase All' break Wi-Fi or web access on a WT5?

The bootloader starts the BK7231 firmware, while the RF partition stores radio calibration and related wireless data. On the WT5, a maintainer warned that Erase All can wipe critical areas, leaving OBK flashed but with broken Wi-Fi, no AP, or no basic web panel. In one real case, restoring the bootloader solved missing Wi-Fi logs and network startup. Restoring the RF partition was also recommended when the device responded oddly after full erasure. So Erase All is risky unless you are ready to rebuild those partitions. [#21407847]

How safe is it to monitor the WT5 serial lines or RF chip SPI lines, and what precautions matter when the device power supply may or may not be isolated?

It is safe only when you know the power domain and voltage levels. The thread explicitly warned that if the device uses a non-isolated supply, connecting UART directly to a PC can damage both the PC and the controller. A safe case is an isolated 12 V DC powered device, where UART capture can be done without extra opto-isolation. The WT5 discussion also rejected calling WB3S “5 V tolerant”; users were advised to use a resistor divider when listening to 5 V logic. [#20873671]

How would you approach adding direct RF support in OpenBeken for the WT5's LT8900-based receiver, and when is using TuyaMCU easier than replacing the secondary MCU?

Use TuyaMCU first unless you specifically need custom RF features. The thread eventually identified the RF chip as LT8900-compatible over SPI with a fifth interrupt/status line, but OpenBeken did not support that RF path directly. The proposed direct-RF route was to capture SPI traffic, use GPIO interrupt plus software or hardware SPI, and possibly remove the secondary MCU if needed. Even then, the maintainer still said TuyaMCU control was “a much easier way” because most device behavior already existed in the shipped firmware and RF kept working after Wi-Fi reflashing. [#20688417]
Generated by the language model.
ADVERTISEMENT