logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda
Give yourself a gift! »
Give yourself a gift! » Print 3D • Smart Home • Flipper
ADVERTISEMENT
Dostępna jest polska wersja

Czy wolisz polską wersję strony elektroda?

Nie, dziękuję Przekieruj mnie tam

[BK7231T] My HTTP server, configurator, MQTT support from Home Assistant

p.kaczmarek2 205629 1308

TL;DR

  • OpenBK7231T adds a cross-platform C HTTP mini-server, web pin configurator, and MQTT integration for BK7231T-based WB2S/WB3S modules with Home Assistant control.
  • The design splits Windows-specific networking from reusable HTTP and pin code, so the same configurator and packet parser can run on Windows and on the BK7231T firmware.
  • The server listens on port 80, uses one int as a channel bitmask, and therefore supports up to 32 channels on a 32-bit platform.
  • MQTT callbacks propagate relay/button changes to Home Assistant and accept commands back, and a 4-relay setup uses wildcard topics like wb2s/1/get through wb2s/4/set.
  • The current pin configurator does not save settings to Flash yet, so configuration is still coded and compiled into the firmware.
Generated by the language model.
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
Report a violation of the law
Reply Cool? Ranking DIY | New topic
Notify about new articles
📢 Listen (AI):
  • #511 19998229
    p.kaczmarek2
    Moderator Smart Home  
    @kuba2k2 I am sure that it stopped working just after I tried flashing image to different sector of memory by accident. I checked several times. Are you saying that should not happen?

    I have added a HTTP GET send command. It's now possible to simple script one device to trigger other device. More to come soon.

    XR809 water sensor demo is also on the way.

    Also, have you seen that? Almost a week uptime!
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #512 19998323
    kuba2k2
    Level 13  
    p.kaczmarek2 wrote:
    Are you saying that should not happen?

    I think that the basic UART uploader should still work. After all, its code is not even stored in the SPI flash.
  • #513 19998475
    sebastian48
    Level 9  
    p.kaczmarek2 wrote:

    Still, I am unable to test all possible scenarios and I suspect that the "crash" (or should you rather say, the disconnection from WiFI, because button is still working) is related to some WiFi bugs, maybe caused by overlapped WiFI channels, so I have decided to add extra failsafe just for you.

    This is always DISABLED by default, you have to enable it per device.

    It's called "ping watchdog", it pings a certain IP (preferrably your router IP) and if it fails to ping it for a given number of seconds, it forces a reconnect.


    Nice workaround. I too suspect a lower level issue. Since rebooting the "crashed" device it "took over" and the first one started to become unresponsive instead. Initially it seemed like same hardware MAC could have been the same but that would not render the "take over" scenario (or my router has serious security issues). My router shows different MAC nevertheless. The quest will go on.

    Excuse my ignorance but I can't seem to find the OTA instructions? Having WB2S I understand I should go for the UA version?
  • #514 19998506
    p.kaczmarek2
    Moderator Smart Home  
    For OTA, you use always RBL file, as said on javascript panel, which is easier for OTA because you can just drag and drop the file.

    I have already added a notice about RBL file to both OTA mechanisms (the old one with pasting URL for HTTP GET and the new one for drag and drop).

    but your issue is very strange @sebastian48 . How often it happens, what kind of router?
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant
    almost 7 days uptime here
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #515 19998535
    sebastian48
    Level 9  
    p.kaczmarek2 wrote:
    For OTA, you use always RBL file, as said on javascript panel, which is easier for OTA because you can just drag and drop the file.

    I have already added a notice about RBL file to both OTA mechanisms (the old one with pasting URL for HTTP GET and the new one for drag and drop).

    but your issue is very strange @sebastian48 . How often it happens, what kind of router?
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant
    almost 7 days uptime here


    The one that is running is pretty much rock solid. Router is Asus RT-AX92U which is a mesh router. Both devices are on the same access point.

    Both my devices are running the very first release so this will be my first update in that sense. However I'm afraid I don't follow. RBL file/javascript panel? Is this something added to a later firmware? Could you point me in the right direction with a link for instructions or a quick breakdown of what I need to do. I remember reading somewhere about OTA and setting up a web server but I can't seem to find it any more.
  • #516 19998579
    p.kaczmarek2
    Moderator Smart Home  
    sebastian48 wrote:

    Both my devices are running the very first release so this will be my first update in that sense. However I'm afraid I don't follow. RBL file/javascript panel?

    Oh no,so you don't have:
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant
    if so, then you really have to use the old method with link to HTTP server (still, link to RBL file).
    Remember that in old version for BK7321N OTA might not work. For T, it should be OK.
    Helpful post? Buy me a coffee.
  • #517 19998611
    sebastian48
    Level 9  
    I don't have that. I guess old OTA is the way then. I'm on T so that should be fine. However, I'm uncertain of the steps for this and I can't seem to find the information any more. Can you provide a short tutorial on necessary steps?
  • #518 19998622
    p.kaczmarek2
    Moderator Smart Home  
    Well, in theory it should work if you paste the link to correct RBL file from Github:
    Code: text Expand Select all Copy to clipboard
    
http://github.com/openshwprojects/OpenBK7231T_App/releases/download/1.0.19/OpenBK7231T_1.0.19.rbl

    but the old version has 64 bytes buffer so that URL is too long.

    RBL file can be hosted anywhere, just need HTTP get link and for older version link must be shorter than 64 chars

    Maybe download a xampp server for Windows, put the rbl file to htdocs and use 192.168.0.25 style link for update?
    Helpful post? Buy me a coffee.
  • #519 19998656
    sebastian48
    Level 9  
    OK thats fine but I don't understand how to get the device to connect to the HTTP server once the file is hosted. BTW, what exactly is the RBL file? Does it point to the BIN-file? Should both be hosted side by side or is JUST the RBL-file sufficient in itself?
  • #520 19998681
    p.kaczmarek2
    Moderator Smart Home  
    There is really nothing more in this procedure. RBL file is everything that device needs and device can download any RBL from any HTTP server just by a simple URL. There is no need for extra pointing.

    Just make sure that your HTTP server (the free one you will create on your machine) is accessible from your local area network, so the device can access it as well by IP.

    Or maybe... I can even help you more, if you 're not sure how to host http file on your computer with Xampp (but really, it's 5 minutes of installing), then I can send you a short update URL that you will just paste here and push the button and that's it. Check your PM.


    PS: I know it really would be easier if the old version was able to process URL longer than 64 characters, but @btsimonh added the HTTP get code himself and I didn't catch that so-very-small buffer in time.
    Helpful post? Buy me a coffee.
  • #521 19998781
    Dark Man
    Level 13  
    Hi
    Some time ago I bought a few bulbs from the Action promotion from the LSC Smart brand, more precisely the model (out of the box) 970 715.1 v1.1 (806 lumens E27 CCW)
    Unfortunately, but the ESP chip is not there either, and the WB2L is there (according to the BK7231T documentation)
    I knew that something was going on in the subject of alternative chips, so I did not regret the money spent :)
    - I mixed an adapter in the form of a clip for it [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant
    - I desoldered this WB2L chip (stuck with some silicone glue)
    - I powered it from USB => AMS1117 3.3V => WB2L
    - connected to USB CP2102: RX to U1_TXD, TX to U1_RXD
    - I tried to download the firmware by BKwriter in ways that first connected the UART, then the power supply or the UART connected with the power supply and the RST field to ground per second
    No response from BKwriter.
    I also tried the same by connecting to the U2_TXD, U2_RXD pads - it did not do anything, except that I read the COM port monitor at startup:


    Code: text Expand Select all Copy to clipboard
    V:BK7231S_1.0.5

CPSR:000000D3

R0:7EDFAC3E

R1:9FA37FB7

R2:1B29765D

R3:E9459D5B

R4:8F32AB96

R13:A191D14A

R14(LR):BEFDF1FE

ST:032E0A49

J 0x10000

prvHeapInit-start addr:0x41f1d8, size:134696
[01-01 18:12:15 TUYA Debug][uni_thread.c:215] Thread:sys_timer Exec Start. Set to Running Status
[01-01 18:12:15 TUYA Err][online_log_serv.c:280] log stats ufread fail.
[01-01 18:12:15 TUYA Debug][online_log_serv.c:540] log serv init success
[01-01 18:12:15 TUYA Notice][light_system.c:1425] go to pre device!
bk_rst:0 tuya_rst:0[01-01 18:12:15 TUYA Notice][light_system.c:1436] goto first bright up!
bk_rst:0 tuya_rst:00xcb 0x4e 0x3e 0xa4 0x0 0x30 0x9d 0xab 0x65 0x6d 0x8d 0xbf 0xe4 0xb9 0x3f 0x35 
[01-01 18:12:15 TUYA Notice][tuya_main.c:203] **********[oem_bk7231s_light_ty] [1.1.2] compiled at May 30 2020 16:23:50**********
[rx_iq]rx_amp_err_rd: 0x030
[rx_iq]rx_phase_err_rd: 0xffffffe8
[rx_iq]rx_ty2_rd: 0x000
*********** finally result **********
gbias_after_cal: 0x17
gav_tssi: 0x2a
gtx_q_dc_comp:0x1f6
gtx_i_dc_comp:0x1fc
gtx_i_gain_comp:1023
gtx_q_gain_comp:1023
gtx_phase_comp:512
gtx_phase_ty2:512
gtx_ifilter_corner over: 0x10
gtx_qfilter_corner over: 0x10
gtx_dcorMod:0x8, gtx_dcorPA:0xa
gtx_pre_gain:0x8
g_rx_dc_gain_tab 0 over: 0x80788078
g_rx_dc_gain_tab 1 over: 0x86708070
g_rx_dc_gain_tab 2 over: 0x88608860
g_rx_dc_gain_tab 3 over: 0x982c9440
g_rx_dc_gain_tab 4 over: 0x982a982a
g_rx_dc_gain_tab 5 over: 0x98269828
g_rx_dc_gain_tab 6 over: 0x9a269926
g_rx_dc_gain_tab 7 over: 0x9a279a26
grx_amp_err_wr:0x1e9
grx_phase_err_wr:0x3f4
**************************************
temp in flash is:265
lpf_i & q in flash is:16, 16
xtal in flash is:32
-----pwr_gain:12, g_idx:12, shift_b:0, shift_g:0
-----[pwr_gain]12
Initializing TCP/IP stack
[01-01 18:12:16 TUYA Notice][tuya_main.c:229] mf_init succ
[01-01 18:12:16 TUYA Notice][tuya_ble_api.c:292] ble sdk inited
device id key : 16
d4 1d 8c d9 8f 00 b2 04 e9 80 09 98 ec f8 42 7e 
!!!!!!!!!!tuya_bt_port_init
[01-01 18:12:16 TUYA Notice][tuya_ble_api.c:328] ble sdk re_inited
[01-01 18:12:16 TUYA Notice][tuya_bt_sdk.c:319] ty bt sdk init success finish
[01-01 18:12:16 TUYA Notice][light_system.c:1484] < TUYA IOT SDK V:2.0.0 BS:30.06_PT:2.2_LAN:3.3_CAD:1.0.2_CD:1.0.0 >
< tuya_iot_lib BUILD AT:2018_12_05_17_03_30 BY tuya_iot_team AT 8710_2M >
IOT DEFS < WIFI_GW:1 DEBUG:1 KV_FILE:0 SHUTDOWN_MODE:0 LITTL[01-01 18:12:16 TUYA Notice][light_system.c:1485] oem_bk7231s_light_ty:1.1.2
[01-01 18:12:16 TUYA Notice][device_config_load.c:310] device config data already load! Don't load again!!
[01-01 18:12:16 TUYA Notice][light_set_color.c:94] Drive init already init ok
[01-01 18:12:16 TUYA Notice][tuya_main.c:128] current product ssid name:tuya_mdev_test2
ht in scan
scan_start_req_handler
gapm_cmp_evt_handler operation = 0x1, status = 0x0 
gapm_cmp_evt_handler operation = 0x3, status = 0x0 
STACK INIT OK
ble_env->start_hdl = 0x7gapm_cmp_evt_handler operation = 0x1b, status = 0x0 
CREATE DB SUCCESS
[01-01 18:12:16 TUYA Notice][tuya_ble_api.c:256] rev ble event 3
device id key : 16
d4 1d 8c d9 8f 00 b2 04 e9 80 09 98 ec f8 42 7e 
!!!!!!!!!!tuya_bt_reset_adv
[01-01 18:12:16 TUYA Notice][tuya_ble_api.c:120] ble adv && resp changed
do td cur_t:293--last:idx:13,t:265 -- new:idx:15,t:289 
--0xc:08, shift_b:0, shift_g:0, X:1
do td cur_t:298--last:idx:15,t:289 -- new:idx:16,t:301 
--0xc:08, shift_b:0, shift_g:0, X:0
[01-01 18:12:18 TUYA Notice][gw_intf.c:3166] serial_no:70897628444b
[01-01 18:12:18 TUYA Notice][gw_intf.c:3197] gw_cntl.gw_wsm.stat:0
[01-01 18:12:18 TUYA Notice][gw_intf.c:3200] gw_cntl.gw_wsm.nc_tp:1
[01-01 18:12:18 TUYA Notice][gw_intf.c:3201] gw_cntl.gw_wsm.md:0
[01-01 18:12:18 TUYA Notice][gw_intf.c:3238] gw_cntl.gw_if.abi:0 input:0
[01-01 18:12:18 TUYA Notice][gw_intf.c:3239] gw_cntl.gw_if.product_key:keytg5kq8gvkv9dh, input:keytg5kq8gvkv9dh
[01-01 18:12:18 TUYA Notice][gw_intf.c:3240] gw_cntl.gw_if.tp:0, input:0
[01-01 18:12:18 TUYA Notice][gw_intf.c:3242] gw_cntl.gw_if.firmware_key:keytg5kq8gvkv9dh, input:keytg5kq8gvkv9dh
[01-01 18:12:18 TUYA Notice][tuya_bt_sdk.c:337] ty bt update product:keytg5kq8gvkv9dh 1
[01-01 18:12:18 TUYA Notice][tuya_ble_api.c:137] update product_id type:1 keytg5kq8gvkv9dh 9c766472a409945f HOXk4mLqNDChr4wUY5VpBH5HyF4A4BjP
[01-01 18:12:18 TUYA Notice][gw_intf.c:2981] start tmm long timer,cfg_lp_timeout:180000ms
[01-01 18:12:18 TUYA Notice][light_system.c:1395] frame init ok!
ht in scan
scan_start_req_handler
[01-01 18:12:19 TUYA Err][uf_flash_file_app.c:339] uf_get_size err,filepath:3,ret:13
[01-01 18:12:19 TUYA Err][uf_flash_file_app.c:339] uf_get_size err,filepath:5,ret:13
[01-01 18:12:19 TUYA Err][uf_flash_file_app.c:339] uf_get_size err,filepath:4,ret:13
[01-01 18:12:19 TUYA Notice][light_system.c:594] start ez config auto blink
me_set_ps_disable:840 0 0 0 462557 952021
------beacon_int_set:100 TU
set_active param 0
[msg]APM_STOP_CFM
update_ongoing_1_bcn_update
mm-next-timer_null
hal_machw_enter_monitor_mode
[01-01 18:12:21 TUYA Notice][tuya_bt_sdk.c:345] ty bt start network cfg..
[01-01 18:12:21 TUYA Notice][tuya_ble_api.c:161] update bound state 0
device id key : 16
6b 51 d4 fd 36 e5 b3 aa 4b 3a 9a b5 df 6e 0b cc 
!!!!!!!!!!tuya_bt_reset_adv
[01-01 18:12:21 TUYA Notice][tuya_ble_api.c:120] ble adv && resp changed
!!!!!!!!!!tuya_before_netcfg_cb
appm start advertising
do td cur_t:309--last:idx:16,t:301 -- new:idx:17,t:313 
--0xc:08, shift_b:0, shift_g:0, X:0


    It is not going to rip or upload the new firmware.

    Any advice?
  • #522 19998828
    p.kaczmarek2
    Moderator Smart Home  
    Dark Man wrote:

    Some time ago I bought a few bulbs from the Action promotion from the LSC Smart brand, more precisely the model (out of the box) 970 715.1 v1.1 (806 lumens E27 CCW)
    Unfortunately, but the ESP chip is not there either, and the WB2L is there (according to the BK7231T documentation)

    How many and how many pieces?

    Maybe try to do this:
    1. USB converter in 3.3V mode, ground to ground, RX to TX and TX to RX
    2. Power supply from LDO 3.3V from a separate, proven power supply
    3. in bkwriter, turn on read (we need the original batch for tuya-cloudcutter to be able to remotely program such products without opening the case - on the tuya-cloudcutter github you have to send them this batch and information from which specific product they would prepare an OTA hack)
    4. disconnect the power and reconnect for a while
    5. It should read
    If not, change the baud to the smaller or the second of the smallest (it never works on the slowest)

    An external power supply (or powerbank) because perhaps disconnecting and connecting the power supply results in too high current consumption (through the capacitors on the board), which resets the USB port at the moment when it should work.
    Helpful post? Buy me a coffee.
  • #523 19999378
    kuba2k2
    Level 13  
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant
    This is super useful. When I come back to working with Bekens, I will definitely add an exception decoder. Who knows, maybe even realtime debugging?
    Speaking of, @p.kaczmarek2 do you have a Raspberry Pi? Any model would do. If yes, you could use it for debugging these chips (Realtek for sure) and programming SPI flash memories (even in the Beken).
  • #524 19999633
    Dark Man
    Level 13  
    I bought bulbs, probably PLN 12 5 pcs.
    their regular price is PLN 18

    Regarding what to do:
    Ad.1 this converter only works in 3.3V logic. I have programmed all ESPs with it so far.
    As I wrote earlier, I connected CP2102 RX to U1_TXD, CP2102 TX to U1_RXD
    Ad.2 WB2L module as I wrote earlier - I power it from a separate USB port, also the voltage stabilizer AMS1117 3.3V with a capacity of 1A and then to the WB2L module
    Ad.3 and Ad.4 I tried to do Read - the time is 15s, at this time I tried to connect the power supply from the stabilizer again, as well as I tried to short the RST contact from the WB2L module to ground - BKwriter still ends with the FAILED message when it reaches 15s
    Ad.5 I tried to do at each of the three available speeds - with no results
    Now I also tried to power it from the powerbank => AMS1117 3.3V => WB2L
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant [/ img]
    Just in case, I gave up the clip and soldered everything to rule out no contact with the fields on WB2L.

    WB2L module
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant
  • #525 19999812
    p.kaczmarek2
    Moderator Smart Home  
    @ darkman1 can be powered from a separate power supply [although how do you write that the power bank is the same ...]? Maybe another USB to UART converter? Why not try a Python programming tool? But I always have bkWriter 1.60 working and I program a lot of these modules

    It's hard for me to believe that you are definitely doing everything correctly. Take a look:
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant
    FCmila smart spotlight. WB2L, the same module as you have. TC1264 LDO 3.3V powered from USB charger and USB to UART in 3.3V mode. BKwriter 1.60. Zero fun with CEN / RST, only by unplugging the power supply I do a reboot. It went without problems, for the 1st time.
    We even managed to rip the batch and send the men from tuya-cloudcutter, here:
    https://github.com/tuya-cloudcutter/tuya-cloudcutter/issues/76

    I think I will go to this Action and I will also try to buy something there for a trial ... then I would have a tuya-cloudcutter profile and you would already program remotely (i.e. I would send the input to people from tuya-cloudcutter).
    Helpful post? Buy me a coffee.
  • #526 19999988
    gamerayers
    Level 5  
    Sorry, I have been very busy. I may try to get to the external power supply version today to see if that will work. The SOIC-8s are both BP5778 so they are PWM.

    p.kaczmarek2 wrote:
    First of all, you haven't replied what is written on the SOIC-8 chips that are alongside the LEDs. It would be good to know, because @kuba2k2 could be wrong and if that's a I2C driver, then it still needs to be implemented. I would do I2C driver for those chips quickly, but I don't have such bulb at hand.

    For programming, you should follow one of the guides from the Teardowns sections.

    Never connect 5V directly to WB modules. I used to connect 5V to AMS1117-3.3V input (this LDO is often present alongside WB/Beken chips on boards), but in case of your bulb, I can't see where is the source of 3.3V so maybe it makes sense to use external 3.3V LDO to get external 3.3V. As for external LDO, I use TC1264-3.3V, but there many many low dropout regulators with 3.3V output. You could even take 3.3V from Arduino and it would work.
    If you are worried about big capacitor resetting USB, you can either get 3.3V from other port or source than the one used for programming, or use CEN method for resetting instead of repowering the chip.


    As per bullseye pattern... I haven't tested this module yet so I don't know. Still, there are only two possible options. None of the other chips had such a strange pad pattern for RX and TX. WB8P is unique in that manner.
  • ADVERTISEMENT
  • #527 20000005
    Dark Man
    Level 13  
    Managed to :)
    There were 2 problems.
    - my USB to CP2102 adapter did not work
    - I found the same one you have, i.e. on the CH340 chip
    - my powerbank disconnected the power supply because it detected too little power consumption
    THX

    Now it's time to re-solder the chip and reconfigure it.

    Enclosed is my dump - WB2L chip never paired with any network or application
    Attachments:
    • bk7231s_dump-2022- 4-29-14-26-25.bin (956 KB) You must be logged in to download this attachment.
  • ADVERTISEMENT
  • #528 20000011
    p.kaczmarek2
    Moderator Smart Home  
    Congratulations and thanks for the info on CP2102 - I'll give a note about it on the repo.

    Can you give me some pictures of the packaging or the model name of the bulb with the charge?
    The point is that in tuya-cloudcutter you choose what to flash and depending on this you need a different key or something (pulled from the batch), so the authors need to know what the batch is from.
    Helpful post? Buy me a coffee.
  • #530 20000081
    p.kaczmarek2
    Moderator Smart Home  
    Will you check tuya-cloudcutter's profile as they prepare it? Thanks to this, you can program other bulbs without opening the housing.

    I sent them:
    https://github.com/tuya-cloudcutter/tuya-cloudcutter/issues/80


    EDIT: @ darkman1 See the answer from the link above, they ask if you can check the existing LSC profiles for light bulbs that have them, if they fit, and if not, they will prepare a new one.

    Quote:

    specifically, i see he mentioned it has 970715.1 on it, so the 3000272-970715 profile probably works. https://github.com/tuya-cloudcutter/tuya-clou.../tree/main/device-profiles/LSC/3000272-970715
    Helpful post? Buy me a coffee.
  • #531 20000719
    wesleyceraso
    Level 2  
    Hi @p.kaczmarek2, I was able to flash the Feit Smart Dimmer with both template_demo and scanNetworks apps (template_demo won't build with the latest commit due to CFG_GetDeviceName, so I moved to cbdb2fb).

    I saw you posted that dimmers are working now, but I don't understand if you have made the code available somewhere or not, can you clarify how do I get from building and flashing examples to a get this dimmer working like a tasmota device?

    Thanks in advance.
  • #532 20000723
    p.kaczmarek2
    Moderator Smart Home  
    @gamerayers so it really may work, good luck, try and report back here.

    @wesleyceraso why are you flashing development examples for programmers and not the real app? Are you a C developer willing to help or are you unable to find where the release binaries are?

    By dimmers, do you mean TuyaMCU dimmers?
    If so, see this pull request:
    https://github.com/openshwprojects/OpenBK7231T_App/pull/75
    It was verified by me as well that it works great, I have the same TuyaMCU dimmer.

    @kuba2k2 I can help you testing that debugging stuff if you tell me how. I have Banana Pi and Raspberry Pi Zero (the tiny one with only WiFi and no Ethernet port).


    PS: I am working on TuyaMCU version 0 (not 3), the one that is used for low-power devices:
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant
    https://developer.tuya.com/en/docs/iot/tuyacl...niversalserialaccessprotocol?id=K95afs9h4tjjh
    Helpful post? Buy me a coffee.
  • #533 20000736
    wesleyceraso
    Level 2  
    @p.kaczmarek2 Thanks, I was looking for releases in the wrong project indeed.

    Unfortunately I can't post links yet, however, if you follow the installation instructions in the SDK project, it takes you to a comment of yours where you point to the wrong release page, and that's what got me confused and I thought I had to rebuilt it by myself.

    Thanks for the help and kudos on the great project.
  • #534 20000753
    p.kaczmarek2
    Moderator Smart Home  
    @wesleyceraso uh it seems that you are correct, there is indeed an older version of description in the first post, I will update it today.
    Helpful post? Buy me a coffee.
  • #535 20000792
    Dark Man
    Level 13  
    I will check the freshly programmed system and the cloudcutter on my raspberry 3b on which I use the tuya-converter, but this is only at the end of next week because I have all the equipment (workshop) at work, and now a long weekend.
    By the way, yesterday I was in the Action store and it turns out that they have already changed the same bulbs again.
    Now there are new models on the front (same price), although I managed to get the model from the end of the shelf that I have :)
    Attached is a photo of both models - boxes from the front and the bottom.

    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant

    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant
  • #536 20000859
    kuba2k2
    Level 13  
    p.kaczmarek2 wrote:
    I have Banana Pi and Raspberry Pi Zero (the tiny one with only WiFi and no Ethernet port).

    Pi Zero should do. I posted debugging instructions in my docs here:
    https://kuba2k2.github.io/libretuya/docs/platform/realtek/debugging/
    So with this, you should be able to connect to your Realtek chip (even if it's bricked and appears dead) and force the uart download mode. If not, that can mean it's hardware bricked i.e. fried.
  • #538 20001314
    p.kaczmarek2
    Moderator Smart Home  
    Yes, I have and support that kind of device. In fact, I have already almost ready tutorial/article for this device which I am going to publish in about 3 days on Polish section on the forum, and several days later in the english section.
    Some photos:
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant

    Please wait a week and you will get a step by step tutorial for that.


    and if you mean some other kind of switch that is not supported, just tell me where to buy one, and I will add support for it, if that's needed


    PS: TuyaMCU moes dimmer works as well
    Helpful post? Buy me a coffee.
  • #539 20001559
    kuba2k2
    Level 13  
    Do you have SSL support in OpenBeken? If so, how do you handle root certificates? A whole CA bundle is over 130 KiB in size, so embedding this in the binary (like ESP32 does, I believe) is really not my favorite idea. yes I'm too lazy to check myself

    Btw. My RTL8710 is currently running both Station and AP mode, with 3 HTTP servers at once, and it works great 😎
  • #540 20002961
    leecher1337
    Level 6  
    I hope that's the correct thread to ask for, if not, please excuse me.
    It seems that I cannot post links, so I can just write a textual description.
    I successfully installed OpenBK on DS-102-2 Wi-Fi 2gang Light Switch (aliexpress item 1005001698977140)
    CPU: WB3S
    Firmware dump available, if needed (check issue at tuya-cloudcutter).

    I'd like to ask if there is support for this, as in how to configure GPIO pins. There is a description for Tasmota regarding GPIOs, but after reading WB3S documentation, I guess it is useless for OpenBK integration.
    Can I somehow help to find out the correct GPIOs or is there already a template for it?
    Thanks in advance.
Reply Cool? Ranking DIY | New topic
Notify about new articles
📢 Listen (AI):
Report a violation of the law

Topic summary

✨ The discussion centers on the development and testing of an open-source firmware project for the BK7231T microcontroller, focusing on creating a cross-platform mini HTTP server, web-based pin configuration, MQTT integration, and Home Assistant compatibility. The project includes a Visual Studio project for Windows and firmware flashing tools like Beken Writer and a Python-based uartprogram. Users report challenges with flashing devices, including issues with firmware size limits (956KB), UART converter compatibility, and power supply stability during flashing. Solutions include using specific UART adapters (e.g., FT232R, CP2102), resetting devices via the CEN pin instead of power cycling, and trimming firmware binaries. The firmware supports devices with BK7231T and BK7231N chips, with ongoing work to add PWM dimmer support, BLE, TuyaMCU protocol integration, and OTA updates. Various smart devices such as WB2S/WB3S modules, smart plugs, LED bulbs, and switches from brands like MOES, Nedis, Hama, and Calex are tested. Users share detailed hardware teardowns, pinouts, and flashing procedures. MQTT topic naming issues related to MAC address usage were identified and fixed. The project emphasizes community collaboration, with suggestions for a Discord server to enhance real-time communication. Additional tools and SDK improvements, including CMake support and BLE integration, are under development to facilitate firmware building and device support expansion.
Generated by the language model.
Today's popular

FAQ

TL;DR: 100 % flash-success reported on BK7231 T/N modules [Elektroda, p.kaczmarek2, post #19906676]; “OpenBK7231T now boots on three chip families” [Elektroda, p.kaczmarek2, post #19883071] Use QIO image for BK7231N, UA for BK7231T; erase only 0×11000-0×1EF000. Why it matters: a single workflow now replaces vendor firmware on 60 + low-cost IoT boards.

Quick Facts

• Supported MCUs: BK7231T, BK7231N, XR809 (Wi-Fi + BLE) [Elektroda, 19883071] • Recommended UART speed: 921 600 bps for write, 115 200 bps for read [Elektroda, 19857664] • Flash sizes: Typical 2 MB on-chip; config area starts @ 0×1EF000 [Elektroda, post #19893493] • OTA format: .rbl (gzip + AES, served by HTTP) [Elektroda, btsimonh, post #19880525] • Typical power: 5 V @ 500 mA to AMS1117 input for safe programming [Elektroda, ExploWare, post #19853546]

3. Writer stops at “Erasing 0×11000” – why?

The chip is protected. For BK7231N add --unprotect when using uartprogram, or choose BK7231N mode in BKWriter; baud 921 600 often succeeds after 115 200 fails [Elektroda, boozeman, post #19857804]

4. Relay clicks during flashing – safe fix?

A pull-up on RX1 ties the push-button to 3 V3, driving the relay. Remove jumper R33 on Nedis WIFIPO120FWT, flash, then solder it back [Elektroda, boozeman, post #19882233]

5. How can I back-up the Tuya stock firmware?

Run python bk7231tools.py read_flash -d COMx --no-verify-checksum -s 0 -c 512 dump.bin for T/N chips (2 MB, 512 × 4 KB) [GitHub bk7231tools].

6. My BK7231N loses settings after power-cycle.

Disable FAST_CONNECT (RL_SUPPORT_FAST_CONNECT) or use latest OpenBK build ≥ f6c3c8f6 that stores config outside NET_PARAM table [Elektroda, p.kaczmarek2, post #19893493]

7. Does OTA work and how do I host updates?

Yes. Serve *.rbl over HTTP (http-here --host 0.0.0.0 8000). In WebApp → OTA tab → enter http://<IP>:8000/firmware.rbl; device backs up filesystem, flashes, restores settings [Elektroda, btsimonh, post #19880525]

9. What are the default GPIO roles for common plugs?

• Nedis WIFIPO120FWT – P6 LED, P10 Button, P26 Relay [Elektroda, 19883937] • QiaChip Smart Switch (WB2S,T) – P24 Relay, P26 Button [Elektroda, 19906692]

10. How do I compile on Linux or Windows?

Clone SDK OpenBK7231T, then OpenBK7231T_App into /apps. Build: ./build_app.sh apps/OpenBK7231T_App OpenBK7231T_App git (Linux) or Cygwin on Windows; ensure build-essential and gcc-arm-none-eabi installed [Elektroda, boozeman, post #19885620]

11. Is there a no-solder exploit?

Yes. CloudCutter abuses 2019 Tuya SDK bug to OTA-flash BK7231 lights wirelessly; code published February 2022 [khalednassar/tuya-cloudcutter]. "It works on every test bulb so far" [Tom Clement, #19890768].
Generated by the language model.
ADVERTISEMENT