logo elektroda
logo elektroda
X
logo elektroda

Moes Wi-Fi 2 Gang Dimmer Module: OpenBK7231T WebGUI and CB2S Chip Configuration

rfulton981 1812 7
ADVERTISEMENT
  • #1 20345260
    rfulton981
    Level 2  
    Hi,

    I've got a MOES Smart 2-Gang dimmer from Amazon.

    It's got a CB2S chip on it which is a BK7231N.

    I've managed to flash this with OpenBK7231T and can now connect to the WebGUI, I'm struggling to get the device to work though.

    I've managed to construct the following autoexec.bat:

    startDriver TuyaMCU
    setChannelType 1 toggle
    setChannelType 2 dimmer
    setChannelType 3 toggle
    setChannelType 4 dimmer
    tuyaMcu_setDimmerRange 0 1000
    linkTuyaMCUOutputToChannel 1 1 1
    linkTuyaMCUOutputToChannel 2 2 2
    linkTuyaMCUOutputToChannel 7 1 3
    linkTuyaMCUOutputToChannel 8 2 4

    Based on the following output:

    Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 1, dataType 1-DP_TYPE_BOOL and 1 data bytes
    Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 7, dataType 1-DP_TYPE_BOOL and 1 data bytes
    Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 2-DP_TYPE_VALUE and 4 data bytes
    Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 8, dataType 2-DP_TYPE_VALUE and 4 data bytes

    If I run this, the device starts beeping constantly and I can't seem to stop it.

    I assume the fact that I can send and receive data from the TuyaMCU means all the soldering must be good, any ideas?
  • ADVERTISEMENT
  • #2 20345667
    p.kaczmarek2
    Moderator Smart Home
    I can't see any obvious mistakes in the config. What do you mean by "beeping"? Have you tried to first only configure one toggle and one dimmer and see if it works that way?

    I remember we had reports that double-dimmer devices are working correctly. Later we might also consider checking earlier build.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #3 20346454
    rfulton981
    Level 2  
    Beeping, as in making a high pitched beeping noise.

    With a blank autoexec, I can turn the device on and access everything through the web console

    When I run :

    startDriver TuyaMCU

    about 3 seconds later it starts to beep and never stops.

    I did test the device before I flashed it, I got the same beeping until I configured working Wifi credentials. It feels like the TuyaMCU knows it's not configured properly so warns me.

    I've not actually managed to test the dimming yet as the noise is really loud and annoying :)

    Logs from enabling TuyaMCU are :

    Info:MAIN:Time 84, idle 188771/s, free 78440, MQTT 0(5), bWifi 1, secondsWithNoPing 1, socks 3/38
    Info:MAIN:Started TuyaMCU.
    Info:MAIN:Time 85, idle 191219/s, free 77616, MQTT 0(5), bWifi 1, secondsWithNoPing 1, socks 2/38
    Info:TuyaMCU:TUYAMCU received: 55 AA 00 00 00 01 00 00
    Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 0 (Hearbeat) with 8 bytes
    Info:MAIN:Time 86, idle 190973/s, free 77616, MQTT 0(5), bWifi 1, secondsWithNoPing 1, socks 2/38
    Info:TuyaMCU:TUYAMCU received: 55 AA 00 01 00 15 6B 71 6D 30 6D 71 7A 62 35 7A 61 7A 65 77 73 62 32 2E 30 2E 32 73
    Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 1 (QueryProductInformation) with 28 bytes
    Info:TuyaMCU:TuyaMCU_ParseQueryProductInformation: received kqm0mqzb5zazewsb2.0.2
    Info:MAIN:Time 87, idle 188486/s, free 77400, MQTT 0(5), bWifi 1, secondsWithNoPing 1, socks 3/38
    Info:TuyaMCU:TUYAMCU received: 55 AA 00 02 00 00 01
    Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 2 (MCUconf) with 7 bytes
    Info:TuyaMCU:TuyaMCU_ProcessIncoming: TUYA_CMD_MCU_CONF, TODO!
    Info:MAIN:Time 88, idle 183147/s, free 77616, MQTT 0(5), bWifi 1, secondsWithNoPing 1, socks 2/38
    Info:TuyaMCU:TUYAMCU received: 55 AA 00 07 00 05 01 01 00 01 00 0E
    Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: 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 00 07 00 08 06 02 00 04 00 00 00 00 1A
    Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 7 (State) with 15 bytes
    Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 6, dataType 2-DP_TYPE_VALUE and 4 data bytes
    Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 0
    Info:TuyaMCU:TUYAMCU received: 55 AA 00 07 00 08 0C 02 00 04 00 00 00 00 20
    Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 7 (State) with 15 bytes
    Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 12, dataType 2-DP_TYPE_VALUE and 4 data bytes
    Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 0
    Info:TuyaMCU:TUYAMCU received: 55 AA 00 07 00 05 07 01 00 01 00 14
    Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 7 (State) with 12 bytes
    Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 7, dataType 1-DP_TYPE_BOOL and 1 data bytes
    Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte:
    Info:TuyaMCU:TUYAMCU received: 55 AA 00 07 00 08 02 02 00 04 00 00 03 9F B8
    Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: 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: 927
    Info:TuyaMCU:TUYAMCU received: 55 AA 00 07 00 08 08 02 00 04 00 00 02 F3 11
    Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 7 (State) with 15 bytes
    Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 8, dataType 2-DP_TYPE_VALUE and 4 data bytes
    Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 755
    Info:MAIN:Time 89, idle 183417/s, free 77616, MQTT 0(5), bWifi 1, secondsWithNoPing 1, socks 2/38
    Info:TuyaMCU:TUYAMCU received: 55 AA 00 00 00 01 01 01
    Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 0 (Hearbeat) with 8 bytes
    Info:MAIN:Time 90, idle 152379/s, free 77616, MQTT 0(5), bWifi 1, secondsWithNoPing 2, socks 2/38
    Info:GEN:dhcp=0 ip=192.168.2.79 gate=192.168.2.1 mask=255.255.255.0 mac=d8:1f:12:e7:ad:72
    Info:GEN:sta: 1, softap: 0, b/g/n
    Info:GEN:sta:rssi=-63,ssid=ha,bssid=86:2a:a8:97:1a:fc ,channel=11,cipher_type:CCMP
    Info:TuyaMCU:TUYAMCU received: 55 AA 00 03 00 00 02
    Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 3 (WiFiState) with 7 bytes
    Info:MAIN:Time 91, idle 186577/s, free 77400, MQTT 0(5), bWifi 1, secondsWithNoPing 1, socks 3/38
    Info:MAIN:Time 92, idle 185540/s, free 77616, MQTT 0(5), bWifi 1, secondsWithNoPing 1, socks 2/38
    Info:MQTT:mqtt_host empty, not starting mqtt
    Info:MAIN:Time 93, idle 193373/s, free 77616, MQTT 0(6), bWifi 1, secondsWithNoPing 1, socks 2/38
    Info:TuyaMCU:TUYAMCU received: 55 AA 00 00 00 01 01 01
    Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 0 (Hearbeat) with 8 bytes
  • #4 20347241
    p.kaczmarek2
    Moderator Smart Home
    Would you be able to provide a packet dump (capture) for original software so we can determine what's the difference between OBK's implementation of TuyaMCU and the Tuya one?

    Also, how does your device beep, why does it even have a buzzer? None of my TuyaMCU devices had a buzzer. Maybe you could just desolder one lead of a buzzer and it will work?
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #5 20348838
    rfulton981
    Level 2  
    I can certainly try, I didn't create a backup of the old firmware which I guess might create a problem?

    How would I connect this up? What software would be able to capture the various serial commands?

    Certainly de-soldering the buzzer might be the best option, it's easy to find, a small black plastic cylinder.

    I'd prefer to help you fix the software though :)
  • #6 20348851
    p.kaczmarek2
    Moderator Smart Home
    Backup of original firmware could help, but now the main question is - apart from the buzzer, is the TuyaMCU functional?

    Another question would be, what is the role of the buzzer in that device in the first place?

    Maybe it just needs some kind of extra packet to silence the buzzer.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #7 20349775
    rfulton981
    Level 2  
    So, despite the very annoying beep, I can confirm the device does work as expected to dim both sets of lights so it does appear to be fully functional

    Good question, it's incredibly annoying. The docs talk about it buzzing if Wi-Fi is not configured, nothing else

    In the logs I see :

    Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 0 (Heartbeat) with 8 bytes

    Is it expecting some kind of response to that?

    Added after 5 [minutes]:

    Ok, so I've just configured MQTT and that stopped it beeping :)
  • #8 20349869
    p.kaczmarek2
    Moderator Smart Home
    So you had no MQTT for whole time?

    Is it functional now?

    It might mean that... it beeps while WiFi state is 0, and stops when it's 4:
    Moes Wi-Fi 2 Gang Dimmer Module: OpenBK7231T WebGUI and CB2S Chip Configuration
    The only problem is I am not sure what to do with that. Maybe I should send something else than 0 in case that MQTT is off...
    Helpful post? Buy me a coffee.

Topic summary

The discussion revolves around configuring the MOES Smart 2-Gang dimmer module, which features a CB2S chip (BK7231N) and has been flashed with OpenBK7231T firmware. The user is experiencing persistent beeping when attempting to use the TuyaMCU driver, indicating potential misconfiguration. Initial troubleshooting steps included simplifying the autoexec.bat file and confirming that the device functions correctly for dimming lights despite the beeping. The beeping was linked to the absence of MQTT configuration, which, once set up, resolved the issue. The conversation also touches on the buzzer's role in the device and the possibility of capturing original firmware for further analysis.
Summary generated by the language model.
ADVERTISEMENT