logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

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

p.kaczmarek2 178107 1242
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
Reply Cool? Ranking DIY | New topic
Notify about new articles
  • #91 19873965
    p.kaczmarek2
    Moderator Smart Home  
    I have committed the required fix to the repository. Binaries update will come soon, as I have to check some things first (@btsimonh contributed some miscellaneous features which I'd want to review deeper).


    More generic changes, clear up and formatting is coming up soon. All device parameters will be changeable by config. Just please remember that updating might break your previous configuration (eg. device unique ID will change).


    I might also look into doing Tasmota HTTP support - so people can use Tasmota Control from Google Play without having main central server like Home Assistant.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #92 19874165
    ExploWare
    Level 10  
    As you requested, some IP addresses and MAC addresses as represented in the dhcp table of my modem

    192.168.2.17; 70:89:76:f8:23:4c; OpenBK7231_708976F8
    192.168.2.19; 70:89:76:f8:21:76; OpenBK7231_708976F8
    192.168.2.8; 84:e3:42:ca:3a:03; OpenBK7231_84E342CA
    192.168.2.14; 70:89:76:f8:2f:97; OpenBK7231_708976F8

    It indeed looks like the address made from the first part of the MACaddresses is the cause, the Unique part of these are omitted :)
    In my case the 192.168.2.8 one should unique, I'll have to verify that :)

    Dodano po 10 [minuty]:

    OK, there are two right now:
    "obk708976F8/0/get 0"
    "obk84E342CA/0/get 0"

    The MQTT settings were not complete one the last one... :)
  • ADVERTISEMENT
  • #93 19874195
    p.kaczmarek2
    Moderator Smart Home  
    ExploWare wrote:
    MACaddresses is the cause, the Unique part of these are omitted

    As I said in previous message, it's already fixed. I didn't notice it because I have each device from different batch/manufacturer, as I order them en masse per testing.

    Anyway, thank you for reporting. I don't know how could we missed that.

    Two more smart devices has just arrived - it's time to extend the range of supported devices once again!
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant

    PS: as I managed to get the main app also to build with BK7231N SDK (notice N - not T), is there anyone who's willing to help with BK7231N testing? Anyone with BK7231N device and basic soldering skills and UART converter?
    Helpful post? Buy me a coffee.
  • #94 19874445
    boozeman
    Level 11  
    Hi,

    Is there anything that I can do to debug that

    Code: text Expand Select all Copy to clipboard
    [
17:43:23.291] 
V:BK7231S_1.0.5
CPSR:000000D3
R0:ADC9AA37
R1:FD12CA35
R2:4311FA1F
R3:FEF46C99
R4:DF7B5BFD
R13:02A64A2E
R14(LR):3C4FA5CF
ST:886631A3
J 0x10000
prvHeapInit-start addr:0x41c908, size:145144
init log


    Problem after flashing?

    I even install cygwin env to rule out the possibility that it would be my Debian installation. The chip is the same BK7231TQN32. Some of us succeed in flashing this same device and then again some don’t. What should be the unifying factor in these?

    Flashing do succeed every time, but after booting it freezes.

    I included my last build. Can anyone try to see if it works?
    Attachments:
  • #95 19874513
    p.kaczmarek2
    Moderator Smart Home  
    Hey @boozeman , I'm happy to check this out for you!

    Tested on my first device:
    [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
    It seems to work, I haven't tested anything more than what's on screenshots but it boots and runs

    EDIT: is this your build date down here?
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant

    Also, please note how WB2S retains its configuration after flashing - the config sections of memory are not overwritten by BKwriter so it remembers my SSID, etc etc

    EDIT: Boozeman, I just realized something.
    Maybe you've set your UART TX pin role to something like digital IO and that resides in your config and breaks stuff?
    Give me a second, I will prepare something for you

    EDIT2:
    Can you check if this app works for you?
    https://github.com/openshwprojects/OpenBK7231T/tree/master/apps/obk_hello_world/src
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant
    Attachments:
    Helpful post? Buy me a coffee.
  • #96 19874577
    boozeman
    Level 11  
    p.kaczmarek2 wrote:


    EDIT2:
    Can you check if this app works for you?


    Yes it works! Some init at first and then steady

    Code: text Expand Select all Copy to clipboard
    19:09:15.027] Hello world - timer is 3 free mem 131824
[19:09:16.031] Hello world - timer is 4 free mem 131824
[19:09:17.025] Hello world - timer is 5 free mem 131824
[19:09:18.029] Hello world - timer is 6 free mem 131824
[19:09:19.078] Hello world - timer is 7 free mem 131824
[19:09:20.031] Hello world - timer is 8 free mem 131824
  • #97 19874584
    p.kaczmarek2
    Moderator Smart Home  
    @boozeman do you know how to checkout specific commit and compile yourself a binary?

    Would you be able to check, let's say, if the repository worked for you, before some certain changes?
    Helpful post? Buy me a coffee.
  • #98 19874603
    boozeman
    Level 11  
    p.kaczmarek2 wrote:
    @boozeman do you know how to checkout specific commit and compile yourself a binary?

    Would you be able to check, let's say, if the repository worked for you, before some certain changes?


    Hi,

    Normal Git pull at my bk7231t
    ./build.sh ./build_app.sh apps/obk_demo_openAccessPoint/ obk_demo_openAccessPoint 1.0.0
    Flashing... It starts and I now have accesspoint OpenBK2731T_WiFi_D.. on my phone! No web server, but it works!

    I think that you're after something here and soon we have working WB2S's to all :)
  • #99 19874628
    p.kaczmarek2
    Moderator Smart Home  
    So you're able to build yourself... good.

    I've added more debug printf at two sections of code:
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant
    Can you compile latest version of App (main app, pull both repos) and paste your log?
    Here is my log:
    Code: text Expand Select all Copy to clipboard
    
V:BK7231S_1.0.5
CPSR:000000D3
R0:E76F05AF
R1:A93E49E8
R2:7F6FBF7C
R3:5331FCE4
R4:DB643E15
R13:2BF7DBA3
R14(LR):B8FE65F7
ST:6EF25514
J 0x10000

prvHeapInit-start addr:0x41c908, size:145144
Entering init log...
Init log done!
[bk]tx_txdesc_flush
[rx_iq]rx_amp_err_rd: 0x009
[rx_iq]rx_phase_err_rd: 0x010
[rx_iq]rx_ty2_rd: 0x000
*********** finally result **********
gtx_dcorMod            : 0x8
gtx_dcorPA             : 0xa
gtx_pre_gain           : 0x0
gtx_i_dc_comp          : 0x1fd
gtx_q_dc_comp          : 0x20d
gtx_i_gain_comp        : 0x3f8
gtx_q_gain_comp        : 0x3ff
gtx_ifilter_corner over: 0x11
gtx_qfilter_corner over: 0x11
gtx_phase_comp         : 0x20e
gtx_phase_ty2          : 0x200
gbias_after_cal        : 0x16
gav_tssi               : 0x22
g_rx_dc_gain_tab 0 over: 0x80788078
g_rx_dc_gain_tab 1 over: 0x80788078
g_rx_dc_gain_tab 2 over: 0x84788478
g_rx_dc_gain_tab 3 over: 0x94708c74
g_rx_dc_gain_tab 4 over: 0x92729470
g_rx_dc_gain_tab 5 over: 0x92709072
g_rx_dc_gain_tab 6 over: 0x93709370
g_rx_dc_gain_tab 7 over: 0x93719371
grx_amp_err_wr         : 0x1fb
grx_phase_err_wr       : 0x008
**************************************
ble use fit!
temp in flash is:250
lpf_i & q in flash is:17, 17
xtal in flash is:21
-----pwr_gain:12, g_idx:12, shift_b:0, shift_g:0
-----[pwr_gain]12
Initializing TCP/IP stack
PIN_LoadFromFlash called - going to load pins.
UART log breaking after that means that you changed the role of [bk]tx_txdesc_flush
bssid 48-ee-0c-48-93-12
security2cipher 2 3 24 8 security=6
cipher2security 2 3 24 8
enter low level!
mac d4:a6:51:30:36:8a
leave low level!
do td cur_t:259--last:idx:13,t:250 -- new:idx:14,t:262 
--0xc:08, shift_b:0, shift_g:0, X:2
TX pin to digital IO or smth else.
PIN_LoadFromFlash pins have been set up.
Using SSID [5G_FULL_POWER]
Using Pass [P@ssw0rd]
Registered for wifi changes
Started http tcp server
Initialised pins
Initialised other callbacks
mqtt_userName homeassistant
mqtt_pass ma1oovoo0pooTie7koa8Eiwae9vohth1vool8ekaej8Voohi7beif5uMuph9Diex
mqtt_clientID obk5130368A
mqtt_host 192.168.0.113:1883
Initialised mqtt
started timer
wl_status 3
ssid:5G_FULL_POWER, 1
ht in scan
scan_start_req_handler
Channel has changed! Publishing change 1 with 100 
26 key_short_press
SM_DISCONNECTING status=1
Timer discovetrs disconnected mqtt 0
Timer is 1 free mem 111472
Timer discovetrs disconnected mqtt 1
Timer is 2 free mem 111472
Timer discovetrs disconnected mqtt 2
Timer is 3 free mem 111472
Timer discovetrs disconnected mqtt 3
Timer is 4 free mem 111472
Timer discovetrs disconnected mqtt 4
Timer is 5 free mem 111472
Timer discovetrs disconnected mqtt 5
Timer is 6 free mem 111472


    There are right now three options.
    1. you are getting crash/stuck at log init
    2. you are losing TX pin because it gets initialized to digital IO by PIN_LoadFromFlash because
    a) you've set it yourself to digital IO once and disconnected yourself that way from UART
    b) the identifier of flash section used for pins was accidentally used by Tuya as well and our code tried to interpret Tuya config as ours - unlikely?
    3. There is some other error, in which case, we'll debug more.

    Most important parts to check:
    Quote:

    Entering init log...
    Init log done!
    PIN_LoadFromFlash called - going to load pins.
    PIN_LoadFromFlash pins have been set up.

    NOTE: your old "init log" UART message is now "Entering init log..."
    Helpful post? Buy me a coffee.
  • #100 19874655
    boozeman
    Level 11  
    p.kaczmarek2 wrote:
    So you're able to build yourself... good.


    another git pull and compilation

    Code: text Expand Select all Copy to clipboard
    
src/logging/logging.c | 3 ++-
src/new_pins.c        | 6 ++++++


    Still

    Code: text Expand Select all Copy to clipboard
    19:38:07.841] 
V:BK7231S_1.0.5
CPSR:000000D3
R0:EDE9AA35
R1:FD3BEA35
R2:47B5FA8A
R3:73C46850
R4:EAF8FD7D
R13:208E6A0F
R14(LR):1AFF211B
ST:882621A3
J 0x10000
prvHeapInit-start addr:0x41c908, size:145144
Entering init log...
Init log done!



    p.kaczmarek2 wrote:

    There are right now three options.
    1. you are getting crash/stuck at log init
    2. you are losing TX pin because it gets initialized to digital IO by PIN_LoadFromFlash because
    a) you've set it yourself to digital IO once and disconnected yourself that way from UART
    b) the identifier of flash section used for pins was accidentally used by Tuya as well and our code tried to interpret Tuya config as ours - unlikely?
    3. There is some other error, in which case, we'll debug more.

    Most important parts to check:
    Entering init log...
    Init log done!
    PIN_LoadFromFlash called - going to load pins.
    PIN_LoadFromFlash pins have been set up.

    NOTE: your old "init log" UART message is now "Entering init log..."


    This problem here happen with plain module too. I can do more tests if needed. When we sort this out, I think others with same situation can finally flash their devices. With that obk wifi demo, I get similar log than yours.

    Btw, do we have some Discord bot wizard to fire up some OpenBeken Discord group? :)
  • #101 19874693
    p.kaczmarek2
    Moderator Smart Home  
    That's interesting.

    Can you check latest commit (of course build it, etc)? I want to at least remove the possibility that's the logger issue.
    NOTE: the latest commit might not be a stable version for release, please just check if you're still having the same issue as before

    As for Discord... I will think about it and I might open such a server (I know how to manage Discord server and create bots there), but I think that discussion on forum like Elektroda is more accessible to people and it's more public and widespread, Google indexes our forum well, while when talking on Discord, we're pretty closing ourselves to external world. Not exactly within my goals, I want to open Bekken for as many people as possible, even non-english speakers.
    Helpful post? Buy me a coffee.
  • #102 19874702
    boozeman
    Level 11  
    p.kaczmarek2 wrote:
    That's interesting.

    Can you check latest commit (of course build it, etc)? I want to at least remove the possibility that's the logger issue.
    NOTE: the latest commit might not be a stable version for release, please just check if you're still having the same issue as before


    The output.

    Code: text Expand Select all Copy to clipboard
    [20:06:59.330] 
V:BK7231S_1.0.5
CPSR:000000D3
R0:00000000
R1:00DFFEFC
R2:00802000
R3:F1CCFFFF
R4:00420208
R13:0043F6A0
R14(LR):0000BCBC
ST:BEDEAD11
J 0x10000
prvHeapInit-start addr:0x41b3e8, size:150552
PIN_LoadFromFlash called - going to load pins.
UART log breaking after that means that you changed the role of TX pin to digital IO or smth else.
PIN_LoadFromFlash pins have been set up.
Using SSID []
Using Pass []
Started http tcp server
Initialised pins
Initialised other callbacks


    p.kaczmarek2 wrote:

    As for Discord... I will think about it and I might open such a server (I know how to manage Discord server and create bots there), but I think that discussion on forum like Elektroda is more accessible to people and it's more public and widespread, Google indexes our forum well, while when talking on Discord, we're pretty closing ourselves to external world. Not exactly within my goals, I want to open Bekken for as many people as possible, even non-english speakers.


    You're right about Discord those servers are Isolated silos of stuff. And you're right about that tx pin. No AP on the phone. But howto I change it and where?
  • #103 19874723
    kuba2k2
    Level 13  
    Discord servers can also be publicly available, for everyone to join. That being a realtime form of communication would improve collaboration, make fixing bugs easier, thus accelerate the development of the project. Yes, forum pages are good for asking single questions to a wide group of knowledged people, or for sharing articles, like How-Tos, guides, etc. But for more dynamic discussions like this one, checking the thread every 15 minutes is not actually the best option. IMO opening a public, though properly moderated, Discord server about the project, and Beken devices in general, would be a great idea, so I totally +1 @boozeman.
  • #104 19874732
    p.kaczmarek2
    Moderator Smart Home  
    boozeman wrote:


    Code: text Expand Select all Copy to clipboard
    
prvHeapInit-start addr:0x41b3e8, size:150552
PIN_LoadFromFlash called - going to load pins.
UART log breaking after that means that you changed the role of TX pin to digital IO or smth else.
PIN_LoadFromFlash pins have been set up.
Using SSID []
Using Pass []
Started http tcp server
Initialised pins
Initialised other callbacks

    Actually it means it's not a pins config issue. I'd rather say it's a threading problem. Is it really now crashing for you after that, no timer prints?

    It's on normal WB2S?

    @kuba2k2 by "publicly" I meant they don't show up in google and content is not indexed in any way by web browsers
    Helpful post? Buy me a coffee.
  • #105 19874757
    kuba2k2
    Level 13  
    p.kaczmarek2 wrote:
    @kuba2k2 by "publicly" I meant they don't show up in google and content is not indexed in any way by web browsers

    They don't need to - an average user/developer who wants to enjoy the project on their device just needs the very first post - an installation guide.
    They will find the thread in Google, but don't actually need to read all the steps that were taken to debug a specific problem, which (by the time they're reading it) is probably fixed long time ago. Nearly 40 last posts are only referring to this particular issue.
    If they encounter bugs, they can check GitHub issues to find a solution or submit their issue. If they want to fix a bug, they open a PR.
    If they want to contribute something bigger, or collaborate on the project, they join the Discord server, which may be linked to in the repo or here, and discuss whatever they need.
    I'm not trying to force you all to build that server, only trying to explain the reasons behind this being IMO a good idea.
  • ADVERTISEMENT
  • #106 19874780
    boozeman
    Level 11  
    p.kaczmarek2 wrote:

    Actually it means it's not a pins config issue. I'd rather say it's a threading problem. Is it really now crashing for you after that, no timer prints?

    It's on normal WB2S?


    This one is inside of Denver SHP-100 WiFi Smart Plug. Anotther one is from Nedis Smart Plug. One bricked reveals the chip BK7231TQN32

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

    Edit: I am not yet checked this board schematics. Transistor right of the WB2S is the relay coil driver and one of it's legs are connected to rx1
  • #107 19875484
    p.kaczmarek2
    Moderator Smart Home  
    @boozeman check the latest commit of our main app.
    If it doesn't work, go to logging.c, enable #define DEBUG_USE_SIMPLE_LOGGER and try again

    PS: I also added a separate wifi scan demo, but it's just for reference/development testing purposes only
    Helpful post? Buy me a coffee.
  • #108 19875507
    boozeman
    Level 11  
    p.kaczmarek2 wrote:
    @boozeman check the latest commit of our main app.
    If it doesn't work, go to logging.c, enable #define DEBUG_USE_SIMPLE_LOGGER and try again

    PS: I also added a separate wifi scan demo, but it's just for reference/development testing purposes only


    Good morning! Git pull for sdk and app > compilation > flash > test = No go.

    There's a results After uncommenting that #define DEBUG_USE_SIMPLE_LOGGER and repeat the "working chain" above

    Code: text Expand Select all Copy to clipboard
    [07:28:01.419] 
V:BK7231S_1.0.5
CPSR:000000D3
R0:00000000
R1:00DFFEFC
R2:00802000
R3:F1CCFFFF
R4:00420208
R13:0043F6A0
R14(LR):0000BCBC
ST:BEDEAD11
J 0x10000
prvHeapInit-start addr:0x41b7f0, size:149520
PIN_LoadFromFlash called - going to load pins.
UART log breaking after that means that you changed the role of TX pin to digital IO or smth else.
PIN_LoadFromFlash pins have been set up.
Using SSID []
Using Pass []
Started http tcp server
Initialised pins
Initialised other callbacks


    No AP on the Phone. obk_wifi_scan works as expected
  • #109 19875622
    btsimonh
    Level 11  
    try setting the #define which removes MQTT startup. I had some problems with initial boot when no MQTT config existed - I thought they were fixed, but maybe not...
  • #110 19875919
    boozeman
    Level 11  
    btsimonh wrote:
    try setting the #define which removes MQTT startup. I had some problems with initial boot when no MQTT config existed - I thought they were fixed, but maybe not...


    @p.kaczmarek2 I commented out in user_main.c line 369 (#define START_MQTT )and I have now accesspoint on the phone and beautifully running log via rx2/tx2

    It was DNS.. hmm MQTT :-)
  • #111 19875933
    btsimonh
    Level 11  
    boozeman wrote:
    It was DNS

    If you find a way to fix it, that would be great!
    The problem may be now that you may not be able to reproduce... that's why I thought I had fixed it?

    p.s. gethostbyname in MQTT connect was a new recent addition.
    On my second device, I had to add the delay before starting station mode. - seemingly the Beken code had not finished initialising everything.
    It's probable that we should delay ALL startup (or find the correct 'started' trigger) - I have the impression that the Beken code does quite a bit in the background during/after calling user_main().
  • #112 19875968
    p.kaczmarek2
    Moderator Smart Home  
    btsimonh wrote:
    try setting the #define which removes MQTT startup. I had some problems with initial boot when no MQTT config existed - I thought they were fixed, but maybe not...


    I don't think it's related to missing MQTT config at startup. IT was related to MQTT in general. I have just right now experienced same error as boozeman (execution of code hangs after few minutes) and realized that's caused by calling MQTT connect from multiple threads. I have commited a fix and it works for me right now well.
    See:
    https://github.com/openshwprojects/OpenBK7231...mmit/fac54bd376695981d9447f37f5e1ad834b517a89
    The only place where MQTT connect is now the Timer.
    I will leave it running for few hours and see.

    PS: the most interesting thing is that this crash happens pretty much at random - it didn't happen to me with @btsimonh logging enabled, only when I added my minimal logging stub (see #define DEBUG_USE_SIMPLE_LOGGER). And it happened for the first time ever on my old trusted WB2S device which I used for many tests before.

    btsimonh wrote:

    The problem may be now that you may not be able to reproduce...

    If you want to reproduce the error, get this commit:
    https://github.com/openshwprojects/OpenBK7231...mmit/c21596d3147ce505ff5c7b8f04b95c3d0240a64e
    Do not run MQTT server. After few minutes, the execution will hang. And by "hang" I mean device dies totally - no UART, no response to HTTP, no response to ping, button....
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #113 19876034
    boozeman
    Level 11  
    With #define DEBUG_USE_SIMPLE_LOGGER uncommented and user_main.c line 369 define START_MQTT commented, my accesspoint is running now at 1000 ticks barrier.

    I can configure wifi and other settings, but not want to do so because I want to keep this device as "vanilla" settings and use this to debug the init hang problem.

    I am here in the hands of skilled coders :)
  • #114 19876067
    p.kaczmarek2
    Moderator Smart Home  
    Right now I'd say it should work with both DEBUG_USE_SIMPLE_LOGGER enabled and disabled, but I still have a whole day of testing ahead of me, so take everything I said with a grain of salt, I am often wrong.

    I also dedicated some time to make few mini examples of BK7231T apps (independent from our main app) and put them here: https://github.com/openshwprojects/OpenBK7231T/tree/master/apps

    I must admit that some of tuya functions which we have (with source code) are really useful, for example this:
    Code: C / C++
    Log in, to see the code


    I am going to add WiFi networks scan to main app today (like in Tasmota), also add something like uptime counter, etc
    Helpful post? Buy me a coffee.
  • #115 19876072
    btsimonh
    Level 11  
    I had an abortive look into sntp, or getting time from a website.
    Where it fell down is I didn't want to add full day/date handling - all we need is a UTC time in unix time - the browser can do everything else....
  • #116 19876091
    p.kaczmarek2
    Moderator Smart Home  
    One more MQTT crash fix pushed to repo now. I am testing in both open access point and client modes.

    btsimonh wrote:
    I had an abortive look into sntp, or getting time from a website.
    Where it fell down is I didn't want to add full day/date handling - all we need is a UTC time in unix time - the browser can do everything else....

    I did a NTP time tutorial on Elektroda once. It was for my Ethernet Arduino Shield project.
    Please consult here (use Google Translate, it's good enough):
    https://www.elektroda.pl/rtvforum/topic3712112.html
    In a free time, you can also read about my Arduino VGA shield:
    https://www.elektroda.pl/rtvforum/topic3664456.html
    We have a nice knowledge base here at Elektroda.
    Helpful post? Buy me a coffee.
  • #117 19876145
    boozeman
    Level 11  
    p.kaczmarek2 wrote:
    One more MQTT crash fix pushed to repo now. I am testing in both open access point and client modes.


    Hi,

    Normal git pull > compilate > flash > It works now and keeps running with AP on phone. I’ll go next to see what changes you made.
  • #118 19876160
    p.kaczmarek2
    Moderator Smart Home  
    Access points scan (I will make them clickable soon)
    [BK7231T] My HTTP server, configurator, MQTT support from Home Assistant

    Network scan button commited - anyone willing to check if it works?
    Helpful post? Buy me a coffee.
  • #119 19876417
    boozeman
    Level 11  
    p.kaczmarek2 wrote:


    Network scan button commited - anyone willing to check if it works?


    I can confirm. It works as expected. The changes you made to the user_main.c also helped for my crash problem. Feature Request, Possibility to save another backup wifi if main connection fails [like in Tasmota]
  • #120 19876425
    MustangMatt
    Level 8  
    p.kaczmarek2 wrote:
    One more MQTT crash fix pushed to repo now. I am testing in both open access point and client modes.

    Would you mind posting a link to the commit? I'm trying to follow along but I'm not seeing it.

    Thanks!
Reply Cool? Ranking DIY | New topic
Notify about new articles
Report a violation of the law

Topic summary

The discussion revolves around the development and implementation of custom firmware for devices using the BK7231T and BK7231N chips, particularly focusing on creating a mini HTTP server, MQTT support, and integration with Home Assistant. Users share their experiences flashing various smart devices, troubleshooting issues related to UART connections, and configuring GPIO pins for different functionalities. The conversation also touches on the challenges of maintaining WiFi connectivity, the importance of proper pin configuration, and the potential for using I2C for additional device control. Several users report successful firmware updates and the addition of new features, including support for various sensors and devices.
Summary generated by the language model.
Popular Topics
ADVERTISEMENT