logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Treatlife DS01 Dimmer TuyaMCU dpIDs and autoexec.bat config for OpenBK

ShellDude 963 17
ADVERTISEMENT
Reply | New topic
  • #1 20760096
    ShellDude
    Level 4  
    My apologies in advance if this has been covered before.

    I have a Treatlife DS01-Dimmer wall outlet with a WB3S controller I would like to free from Tuya and use with HA directly over MQTT.

    I have been unable to locate anything here, or generally, that states whether or not I can use OpenBeken with it.

    I have the switch torn down at the moment and have been able to locate all the proper pins / etc.

    It appears this device used to use a Tuya ESP module and was swapped out for the WB3S at some point as Tasmota has a template for it with an ESP8266.

    It has visual similarities with the DS02/DS03 referenced in the Beken device database but is basically a binary on/off and tactile slider type dimmer.

    Any pointers would be greatly appreciated!
  • ADVERTISEMENT
  • #2 20760180
    p.kaczmarek2
    Moderator Smart Home  
    Hello, I think it should work, it will be most likely a TuyaMCU device like many others that we have already supported. We can give it a try. Flash a single piece for a start.

    Please provide more information if you can and we'll try to setup it together.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #3 20760191
    ShellDude
    Level 4  
    I made a ton of progress on this tonight. OpenBeken is flashed. I couldn't get the Windows Flasher to work but a 3rd party python one worked just fine. This could be for a number of reasons (Windows arm VM on a MacBook, flakey uart drivers, etc).

    I found a template for it as well in the cloudcutter repo, applied it, created an autoexec.bat, and just finished putting it all back together.

    It's getting late here so I'll pick back up in the morning by reconnecting it to my mains power and see how things go.

    This is awesome. I had originally thought it was an esp chip and was all prepped to flash tasmota but once I got a good look at the board, I had to quickly scramble -- and found OpenBeken!

    Will report back here if I find myself needing help. I've got one more of these I need to flash and a binary (non-dimmer) version to do as well.

    I'll be sure to follow the guidelines for publishing a legitimate template for them assuming everything works out
  • ADVERTISEMENT
  • #4 20760224
    p.kaczmarek2
    Moderator Smart Home  
    I am happy to hear that it worked out for you. Did you also force the WiFi state 0x04, which is required by some devices which do not want to function unless they think that they are connected to the cloud?
    You can see some examples in our docs:
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/README.md
    I will be making a generic TuyaMCU guide soon, so futher users should have the process even easier with the new guidance.
    Helpful post? Buy me a coffee.
  • #5 20760240
    ShellDude
    Level 4  
    I did find that have it in my autoexec.

    I'm pretty sure I'm going to have to configure the pin roles. While the template I used created two channels, all ports are undefined in GPIO Doctor.

    Looking at the board pwm0, and pwm3 are soldered.
  • #6 20760245
    p.kaczmarek2
    Moderator Smart Home  
    Wait, the Tuya device can be either TuyaMCU or GPIO-based. I haven't seen any device requiring both TuyaMCU driver and GPIO configuration.

    You can check if your device is TuyaMCU very easily. Just do the GPIO extraction:
    https://www.youtube.com/watch?v=WunlqIMAdgw&ab_channel=Elektrodacom
    Helpful post? Buy me a coffee.
  • #7 20760645
    ShellDude
    Level 4  
    Here's what i got back:

    Quote:
    Sorry, no meaningful pins data found. This device may be TuyaMCU or a custom one with no Tuya config data.
    No module information found.
    And the Tuya section starts at UNCOMMON POSITION 0


    I also noticed the following in the log when using the DS02S autoexec.bat

    Code: text Expand Select all Copy to clipboard
    Info:TuyaMCU:Consumed 255 unwanted non-header byte in Tuya MCU buffer
Info:TuyaMCU:Skipped data (part) 00 FE 00 FE 00 FE 00 FE 00 FE 00 00 F0 00 FE 00 FE 00 FE 00 FE 00 00 00 00 00 00 00 F0 00 FE 00 00 00 00 00 00 FE 00 00 00 00 00 00 00 00 00 00 00 FE 00 00 00 00 00 00 00 00 00 00 00 00 F0 00 00 00 00 00 00 00 F0 00 00 F0 00 00 00 00 00 00 00 F0 00 00 00


    And my autoexec:

    Code: text Expand Select all Copy to clipboard
    startDriver TuyaMCU
tuyaMcu_setBaudRate 115200
setChannelType 1 toggle
setChannelType 2 dimmer
tuyaMcu_sendState 4 4 0
tuyaMcu_sendState 3 2 10
tuyaMcu_setDimmerRange 10 1000
linkTuyaMCUOutputToChannel 1 1 1
linkTuyaMCUOutputToChannel 2 2 2
tuyaMcu_defWiFiState 4


    Added after 1 [hours] 9 [minutes]:

    Doing some basic diagostics with just the tuyaMCU driver loaded:

    Power button ON to OFF:
    Code: text Expand Select all Copy to clipboard
    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 02 02 00 04 00 00 03 49 65 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 841
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 01 01 00 01 00 11 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 1, dataType 1-DP_TYPE_BOOL and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 
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


    Power button OFF to ON:
    Code: text Expand Select all Copy to clipboard
    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 02 02 00 04 00 00 03 49 65 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 841
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 01 01 00 01 01 12 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 1, dataType 1-DP_TYPE_BOOL and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 
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


    Adjust brightness to MAX:
    Code: text Expand Select all Copy to clipboard
    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 02 02 00 04 00 00 00 96 AF 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 150
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 96 AF 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 150
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 96 AF 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 150
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 96 AF 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 150
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 96 AF 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 150
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 02 02 00 04 00 00 01 A9 C3 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 425
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 02 02 00 04 00 00 01 A9 C3 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 425
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 02 02 00 04 00 00 02 BF DA 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 703
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 02 02 00 04 00 00 02 BF DA 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 703
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 02 02 00 04 00 00 03 E8 04 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 1000
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 02 02 00 04 00 00 03 E8 04 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 1000
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


    Adjust brightness to MIN:
    Code: text Expand Select all Copy to clipboard
    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 02 02 00 04 00 00 03 E8 04 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 1000
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 02 02 00 04 00 00 03 E8 04 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 1000
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 02 02 00 04 00 00 03 E8 04 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 1000
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 02 02 00 04 00 00 03 85 A1 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 901
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 02 02 00 04 00 00 02 BF DA 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 703
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 02 02 00 04 00 00 02 3E 59 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 574
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 02 02 00 04 00 00 01 82 9C 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 386
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 96 AF 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 150
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 96 AF 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 150
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 96 AF 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 150
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 96 AF 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 150
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


    Bear with me as I'm still learning. I'll see about parsing this and figuring out how to apply it.
  • #8 20760713
    p.kaczmarek2
    Moderator Smart Home  
    At the current moment I am not sure whether it's a TuyaMCU device or not. Would you be able to provide the picture of the board? Is there a MCU connected to the WiFi module on UART1 (RX1, TX1) port?
    Helpful post? Buy me a coffee.
  • #9 20760726
    ShellDude
    Level 4  
    I am super new to this but I do think it is using tuyaMCU.

    After enabling just the tuyaMCU driver, I watched the tuya packets flowing across the bus via the web app log interface.

    From that I constructed a couple simple commands based on the values being returned (focusing right now on just the toggle):
    Code: text Expand Select all Copy to clipboard
    setChannelType 1 toggle
linkTuyaMCUOutputToChannel 1 1 1


    And complete success... I am now able to control the toggle via OpenBeken and receive updates when I physically press it!

    Moving on to the dimmer now!

    Added after 10 [minutes]:

    And similar for the dimmer...

    Code: text Expand Select all Copy to clipboard
    setChannelType 2 dimmer
tuyaMcu_setDimmerRange 14 1000
linkTuyaMCUOutputToChannel 2 2 2


    I now have full control of the switch / dimmer and am using the following autoexec.bat:

    Code: text Expand Select all Copy to clipboard
    startDriver TuyaMCU
setChannelType 1 toggle
linkTuyaMCUOutputToChannel 1 1 1
setChannelType 2 dimmer
tuyaMcu_setDimmerRange 14 1000
linkTuyaMCUOutputToChannel 2 2 2
  • #10 20760747
    p.kaczmarek2
    Moderator Smart Home  
    That's good to hear. If that's the case, then you don't need any GPIOs, right? Everything is controlled by TuyaMCU protocol on the UART line.
    Helpful post? Buy me a coffee.
  • #11 20760758
    ShellDude
    Level 4  
    Yes, everything I need to control / view / monitor is working 100% with just the tuyaMCU protocol. I'll move to the basic binary switch tonight.

    All the documentation for OpenBeken made the learning curve super fast!

    I wonder if it was the 115200 baud rate in the DS02S autoexec that messed things up. I'll see about recreating the initial issue I was having by swapping out a few of the startup commands and see which one caused me problems.

    Does not work
    Code: text Expand Select all Copy to clipboard
    startDriver TuyaMCU
tuyaMcu_setBaudRate 115200
setChannelType 1 toggle
setChannelType 2 dimmer
tuyaMcu_sendState 4 4 0
tuyaMcu_sendState 3 2 10
tuyaMcu_setDimmerRange 10 1000
linkTuyaMCUOutputToChannel 1 1 1
linkTuyaMCUOutputToChannel 2 2 2
tuyaMcu_defWiFiState 4


    Works
    Code: text Expand Select all Copy to clipboard
    startDriver TuyaMCU

setChannelType 1 toggle
linkTuyaMCUOutputToChannel 1 1 1

setChannelType 2 dimmer
tuyaMcu_setDimmerRange 14 1000
linkTuyaMCUOutputToChannel 2 2 2
  • #12 20760778
    p.kaczmarek2
    Moderator Smart Home  
    Well, now that you post two configs, it seems that it's obviously a 9600-baud device, 9600 is a default value for baud here. So, this line:
    Code: text Expand Select all Copy to clipboard
    
tuyaMcu_setBaudRate 

    breaks the communication.

    Futhermore, what is the purpose of:
    Code: text Expand Select all Copy to clipboard
    
tuyaMcu_sendState 4 4 0
tuyaMcu_sendState 3 2 10

    It seems that someone tried to send some data to the MCU on the start, but I don't think it's needed.
    Helpful post? Buy me a coffee.
  • #13 20760788
    ShellDude
    Level 4  
    Found those settings here: https://www.elektroda.com/rtvforum/topic3957849.html#20566728

    Looks like there are some additional channels on the DS02S the author was trying to accommodate.

    Added after 3 [minutes]:

    Here's my "final" autoexec.bat:

    Code: text Expand Select all Copy to clipboard
    startDriver TuyaMCU
tuyaMcu_setBaudRate 9600
setChannelType 1 toggle
linkTuyaMCUOutputToChannel 1 1 1
setChannelType 2 dimmer
tuyaMcu_setDimmerRange 14 1000
linkTuyaMCUOutputToChannel 2 2 2
tuyaMcu_defWiFiState 4
  • #14 20760828
    p.kaczmarek2
    Moderator Smart Home  
    Ah yes, it seems he has found the following dpIDs:
    Code: text Expand Select all Copy to clipboard
    

dpId 4 corresponds with the dimming mode (Valid values are 0,1,2)
dpId 3 corresponds with the minimum dimming level (Valid values range is 10 - 1000)

    It may be possible to access them from OBK if that's needed.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #15 20762194
    ShellDude
    Level 4  
    Wouldn't you know it, my Single Pole Binary switch (Treatlife ‎SS01S-1) and my second dimmer (Treatlife ‎DS01-Dimmer) are both ESP8266EX devices.

    The two dimmers were bought about a year and a half apart. The older one is an ESP8266EX bought in June of 2020 and the newer one we worked to get working here was purchased in December of 2021.

    That was quite a treat bouncing between Tasmota and OBK to get these 3 devices configured.

    Thanks again for all your assistance!

    Added after 4 [minutes]:

    I have found bouncing between both Tasmota and OBK, that OBK is much more responsive (at least via the web interface). The web interface offers more options, provides direct Home Assistant Discovery via its MQTT configuration, and overall was more pleasant to work with.

    If you ever have a port of this that runs on ESP devices, I would not hesitate to convert my ESP devices to it.
  • #16 20764751
    ShellDude
    Level 4  
    Moving on to converting other devices of mine, I have come across an IR Blaster with a Realtek WBR3 board in it. I saw reference to OBK being updated to include support for these controllers and would like to know if it is worth giving it a shot.

    IR Blaster circuit with LEDs and Realtek WBR3 component on a dark background. IR Blaster with Realtek WBR3 card on a round circuit board.
  • #17 20765233
    p.kaczmarek2
    Moderator Smart Home  
    ShellDude wrote:

    I have found bouncing between both Tasmota and OBK, that OBK is much more responsive (at least via the web interface). The web interface offers more options, provides direct Home Assistant Discovery via its MQTT configuration, and overall was more pleasant to work with.

    If you ever have a port of this that runs on ESP devices, I would not hesitate to convert my ESP devices to it.


    Thank you, those platforms are planned, I will post on forum when we'll be needing testers. Just follow the thread and wait for more info.

    Btw, I don't know if you are aware of it, but we also have an OpenBeken Windows port (with simulator).
    Helpful post? Buy me a coffee.
  • #18 21379248
    p.kaczmarek2
    Moderator Smart Home  
    New guide for those WBR3 chips:
    WBR2, WBR3, WBRU, W701-VA2-CG pinout, datasheet, flashing for Home Assistant
    Helpful post? Buy me a coffee.
Reply | New topic
Report a violation of the law

Topic summary

The discussion revolves around the Treatlife DS01-Dimmer, which utilizes a WB3S controller and aims to be freed from Tuya integration to operate directly with Home Assistant (HA) via MQTT using OpenBeken firmware. Initial challenges included flashing the device and configuring the autoexec.bat file. Users confirmed that the device operates as a TuyaMCU, allowing control of toggle and dimmer functions without needing GPIO configurations. The baud rate was identified as a critical factor, with successful communication established at 9600 baud. The conversation also highlighted the ease of transitioning between Tasmota and OpenBeken, with users noting OpenBeken's superior responsiveness and features for HA integration. Future plans include testing other devices with OpenBeken support.
Summary generated by the language model.
Popular Topics
ADVERTISEMENT