logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

[BK7231N CBU] Generic Temperature and Humidity Sensor

Chasbrot 66480 359

TL;DR

  • A generic AliExpress WiFi temperature and humidity sensor based on a BK7231N CBU module was torn down and identified.
  • The teardown includes device pinout notes and references for the BK7231N uC and Sensirion SHT30 sensor, with the specific part marked SHT30 DIAS7M.
  • The WiFi version arrived from de.aliexpress.com in about 2 weeks to Austria.
  • The latest BK7231N image could be flashed via console, but OpenBK7231T still lacks an SHT30 driver, tracked in GitHub issue 574.
Generated by the language model.
ADVERTISEMENT
Report a violation of the law
Reply Cool? Ranking DIY | New topic
Notify about new articles
📢 Listen (AI):
  • #241 20860881
    Virnik0
    Level 5  
    Posts: 16
    Help: 1
    Rate: 1
    >>20699189
    Hi, this sensor comes cheap, and is ideal addition to various trinkets, like Fish feeder units, or Windows shades control units, where it makes sense to also add temperature as a measured variable.

    Sorry for answering for to an old post, I've been looking around trying to figure my issue with the same sensor for last week, before realizing the driver to use it is missing. I am using BL602 based Fish Feeder. There seems to be no TuyaMCU inside. According to specs, GPIO17 is free for use, as it is not connected. I used it to solder data (yellow) wire on it, red to VCC and black to ground. I have also put 150k resistor between data and vcc to serve as a pullup. Alas, found out OpenBeken doesn't support it yet.
  • ADVERTISEMENT
  • #242 20876355
    sirhcsat
    Level 7  
    Posts: 27
    @p.kaczmarek2 because both door sensor and temp sensor boards are the same board, can the sht sensor be added to the door sensor and have both work together ? thus giving a door sensor that can also provide temp of the are the sensor is mounted . just a wid though I had while flashing another 6 door sensors for my HA setup to monitor external doors and use with Alarmo.
  • #243 20876512
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12349
    @Virnik0 you can try enabling TuyaMCU driver for BL602 and see if it works. I don't have any BL602 TuyaMCU devices yet, so I am not able to test it. BL602 chips are very rare.
    @sirhcsat certainly! You can add any sensor to unused GPIOs, even DHT11 .Just make sure to configure it properly and redo HASS Discovery (if supported), or add it to HA manually (by writing yaml code)
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #244 20876646
    Virnik0
    Level 5  
    Posts: 16
    Help: 1
    Rate: 1
    I have tried to activate it, but OpenBeken tells me that there is no such driver.
  • #245 20876679
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12349
    @Virnik0 I apologize, we must have misunderstood each other. By saying "try enabling it", I meant enabling it in the source code and maybe checking the UART settings in code. As far as I know, BL602 has already UART code in place, but it has two UART ports, so you'd have to make sure that correct one is used. Futhermore, to enable TuyaMCU driver, open config file:
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/src/obk_config.h
    For BL602, in related section, add:
    Code: text Expand Select all Copy to clipboard
    
#define ENABLE_DRIVER_TUYAMCU   1

    Then recompile. You can compile it online. We also have automatic compilations for all platforms in pull requests, so you can just open pull request and modify it to get correct binaries.

    The following operation requires only some basic IT knowledge, you don't need to write C code yourself, but you should be able to at least read it and navigate...
    Helpful post? Buy me a coffee.
  • #246 20876760
    sirhcsat
    Level 7  
    Posts: 27
    @p.kaczmarek2

    the door sensor is configured
    Code: text Expand Select all Copy to clipboard
    "16": "DoorSnsrWSleep_nPup;0",
"17": "BAT_Relay;1",
"20": "Btn;2",
"23": "BAT_ADC;1",
"26": "LED;0"


    the temp sensor is configured
    Code: text Expand Select all Copy to clipboard
    "7": "SHT3X_SCK;0",
"8": "SHT3X_SDA;2;3",
"17": "Rel;5",
"20": "dInput_n;0",
"23": "ADC;4",
"26": "LED;1"


    so looking at both the configs they seem to be already connected board trace wise (white pcb) and ready to go, just adding an smt sht3x to the door sensor board and tweaking the config could it work or is the relay switching to do powerup readings. do you think it would take door reading every time the temp sensor took a reading and a temp reading every time the door switch was activated or maybe even confuse and muddle up each other. I have a few smt sht3 on order from china to play with but they will not be here untill mid Jan 24

    adding the config lines from the temp sensor in this thread I come up with a config below to try once the sht3s arrive.

    Code: text Expand Select all Copy to clipboard
    "7": "SHT3X_SCK;0",
"8": "SHT3X_SDA;2;3",
"16": "DoorSnsrWSleep_nPup;0",
"17": "BAT_Relay;1",
"20": "Btn;2",
"23": "BAT_ADC;1",
"26": "LED;0"
  • #247 20876906
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12349
    It will not confuse each other, it's just, if you are using deep sleep, it will report temperature every time that doors are either opened or closed. If that's acceptable, then it will work well.
    Helpful post? Buy me a coffee.
  • #248 20881105
    Xinayder
    Level 8  
    Posts: 24
    Rate: 4
    I have finally managed to setup my SHT30 sensor and I'd like to share my autoexec script:

    Code: text Expand Select all Copy to clipboard
    
startDriver SHT3X

// hold button to get into safe mode
addEventHandler OnHold 20 SafeMode

// rechargable AAA battery is 1.2V
Battery_Setup 1800 2400
Battery_Measure

SHT_cycle 15

mqtt_broadcastInterval 1
mqtt_broadcastItemsPerSec 5

// wait until wifi is connected
waitFor WiFiState 4

// go to deep sleep if mqtt can't connect
addRepeatingEventID 30 -1 1337 DeepSleep 120

// wait until mqtt is connected
waitFor MQTTState 1

cancelRepeatingEvent 1337

SHT_Measure
delay_s 10

publishChannels
delay_s 5

delay_s 60
DeepSleep 300


    One thing I've noticed is, it was either going to deep sleep too fast after connecting to wifi, or it wasn't publishing the channels properly; once it went into deep sleep, it wouldn't turn on the red LED after 2 minutes (deep sleep timer). I've setup a cancel event command so that if it manages to connect to MQTT, the repeating event is cancelled.

    EDIT: Is it possible to change the topic name for temperature/humidity? Right now my sensor publishes humidity to topic 0 and temperature to topic 2. If I use a setChannelLabel command, will it change the name of the channel for Home Assistant?

    Another thing, it seems like my sensor is becoming unavailable 1-3 minutes since the last broadcast. What can I do to prevent this from happening in HASS?

    EDIT2: Fixed the issue above by enabling flag 35 "Deactivate avty_t flag for sensor when publishing to HASS (permit to keep value)".

    EDIT3: I've flashed this sensor back in August, what is channel 8 supposed to be? I thought it could be the SHT heater, but it's not. This is my device template:

    Code: text Expand Select all Copy to clipboard
    {
  "vendor": "Tuya",
  "bDetailed": "0",
  "name": "Full Device Name Here",
  "model": "enter short model name here",
  "chip": "BK7231N",
  "board": "TODO",
  "flags": "4",
  "keywords": [
    "TODO",
    "TODO",
    "TODO"
  ],
  "pins": {
    "7": "SHT3X_SCK;0",
    "8": "SHT3X_SDA;2",
    "16": "dInput;8",
    "17": "BAT_Relay;4",
    "20": "Btn;6",
    "23": "BAT_ADC;4",
    "26": "WifiLED_n;0"
  },
  "command": "",
  "image": "https://obrazki.elektroda.pl/YOUR_IMAGE.jpg",
  "wiki": "https://www.elektroda.com/rtvforum/topic_YOUR_TOPIC.html"
}
  • #249 20882846
    Xinayder
    Level 8  
    Posts: 24
    Rate: 4
    After a day running, my sensor managed to empty the battery because it was transmitting data every 10 seconds whenever it would wake up. I tried changing the batteries to non-rechargeable AAA batteries and the sensor started making some high-pitched noise that I haven't seen before. Swapped to recharged batteries and the sensor won't boot.

    Does this mean I have to reprogram the sensor? I remember reading somewhere around the forums that some corruption happened due to low battery and I suppose that's what happened.
  • ADVERTISEMENT
  • #250 20882895
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12349
    Do you have 2MB flash backup? Can you make a 2MB dump now? It would be helpful for us to check exactly what has changed in flash so we can investigate the issue more in depth.
    Helpful post? Buy me a coffee.
  • #251 20883915
    @GUTEK@
    Level 31  
    Posts: 1560
    Help: 163
    Rate: 367
    Xinayder wrote:
    I finally managed to configure the SHT30 sensor and would like to share my autoexec script:

    Code: text Expand Select all Copy to clipboard
    
startDriver SHT3X

// hold button to get into safe mode
addEventHandler OnHold 20 SafeMode

// rechargable AAA battery is 1.2V
Battery_Setup 1800 2400
Battery_Measure

SHT_cycle 15

mqtt_broadcastInterval 1
mqtt_broadcastItemsPerSec 5

// wait until wifi is connected
waitFor WiFiState 4

// go to deep sleep if mqtt can't connect
addRepeatingEventID 30 -1 1337 DeepSleep 120

// wait until mqtt is connected
waitFor MQTTState 1

cancelRepeatingEvent 1337

SHT_Measure
delay_s 10

publishChannels
delay_s 5

delay_s 60
DeepSleep 300


    Thank you very much for sharing the script. In some free time over the holidays, I sat down to install Home Assistant in Docker and watched how it works.
    I modified this script for myself and it works for me as follows. Additionally, I also set a hard IP address and turned on flags 2 and 35.
    Code: text Expand Select all Copy to clipboard
    
PowerSave 1
startDriver SHT3X

// hold button to get into safe mode
addEventHandler OnHold 20 SafeMode

// go to deep sleep if mqtt can't connect
addRepeatingEventID 60 -1 1337 DeepSleep 600

//battery 18650 4.2V, min 2.5V
Battery_Setup 2500 4200 2.29 2400 4096
battery_measure

SHT_cycle 15

mqtt_broadcastInterval 1
mqtt_broadcastItemsPerSec 5

// wait until wifi is connected
waitFor WiFiState 4

cancelRepeatingEvent 1337

addRepeatingEventID 60 -1 1337 DeepSleep 600

// wait until mqtt is connected
waitFor MQTTState 1

cancelRepeatingEvent 1337

//SHT_Calibrate -0.8 2

SHT_Measure
delay_s 1

publishChannels
delay_s 5

//Deep Sleep ~15min
DeepSleep 875

    Since powering from AAA batteries is highly inefficient, I use a 18650 battery to power it, although its voltage is too high for this system, but it still works properly. In order to reduce power consumption, I wake up the system every 15 minutes and added "PowerSave 1". As long as my readings are correct:
    Home Assistant interface screen with device and sensor information.


    I also 3D printed an additional housing in which I placed the battery basket:
    3D model of a rectangular battery compartment. 3D printed enclosure with a sensor for a battery. Pink 18650 battery housed in a white 3D-printed enclosure.
  • #252 20886949
    Xinayder
    Level 8  
    Posts: 24
    Rate: 4
    >>20882895

    I think it wasn't the flash that changed but something corrupted the RF partition. I managed to dump the 2MB flash and it seemed okay, no CRC mismatch errors nor anything changed in the configuration (I checked it with a hex editor).

    This issue happened with both of my sensors, the temperature one with SHT30 and the door sensor, both without TuyaMCU. I had to use the Erase All button on the Windows flasher tool and even after the full formatting, the sensor wouldn't work properly. I reflashed the RF partition and it worked.

    There was a similar issue discussed earlier on this thread: https://www.elektroda.com/rtvforum/topic3945688-30.html#20406557

    EDIT: I'll attach the dumps shortly.

    Another thing I noticed, I have flag 2 enabled (Broadcast self state every N (def: 60) seconds (delay configurable by 'mqtt_broadcastInterval' and 'mqtt_broadcastItemsPerSec' commands) and set the interval to 60 seconds, broadcasting 5 items per second. I've noticed that this is not always the case, as my sensor is broadcasting twice every wake up (better than broadcasting at every second or so) even though the broadcast interval is set to 1 minute.

    As you can see in this image from Home Assistant, it broadcasted 5 times in a 2 minute interval (where the red lines are). Is this related to the broadcastItemsPerSec setting?


    Chart showing temperature changes from a sensor over time.
  • ADVERTISEMENT
  • #253 20886955
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12349
    Can someone maybe provide a sample of flash before and after corruption so we can check what exactly breaks and where?

    Maybe even break a device for a purpose, just for testing, so we can investigate...
    Helpful post? Buy me a coffee.
  • #254 20886978
    Xinayder
    Level 8  
    Posts: 24
    Rate: 4
    Here are the dumps from both of my sensors (door sensor and the SHT30 temp+humidity):
    Attachments:
    • readResult_BK7231N_QIO_sht_corrupted_2024-01-1-15-38-10.bin (2 MB) You must be logged in to download this attachment.
    • readResult_BK7231N_QIO_doorsensor_corrupted_2024-01-1-16-29-59.bin (2 MB) You must be logged in to download this attachment.
  • #255 20887108
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12349
    .. and before corruption?
    Helpful post? Buy me a coffee.
  • #256 20893481
    Virnik0
    Level 5  
    Posts: 16
    Help: 1
    Rate: 1
    >>20876679
    OK, fetched the git repo, but there is no README or in otherwords an instruction on how to build the image. I can build it and take a care of dependencies, but I need to know how to build the project. Assume generic linux environment.
  • #257 20893730
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12349
    @Virnik0 I would say the simplest way is to use our online builds, you can get them on your repo or in pull request to our repo.
    Still, if you want to learn how to build for BL602 yourself, see:
    https://www.elektroda.com/rtvforum/topic3889041.html
    Search for section:
    Code: text Expand Select all Copy to clipboard
    
For the programmer - MSys2 installation
    Helpful post? Buy me a coffee.
  • #258 20894355
    Xinayder
    Level 8  
    Posts: 24
    Rate: 4
    >>20887108

    The same issue happened again. Even with 5 minutes for deep sleep and measurement intervals of 60 seconds, a fully charged AAA battery lasted around a full day.

    I have attached 2MB dumps from the following stages:

    - after battery died (_corrupted2)
    - after flashing OpenBK again (_afterflash1)
    - after restoring RF part, right after reflashing OpenBK (_afterflash2)
    - after formatting the sensor (using erase all button, filename is _aftererase)
    - after reflashing OpenBK right after using the erase all button (_aftereraseall2)

    In all situations, the option to configure OpenBK was checked. I manually configured OpenBK this time, based on the previous configuration.

    The sensor only worked again after using erase all and reflashing OpenBK and applying the manually configured settings.

    EDIT: this was my current autoexec.bat script:

    Code: text Expand Select all Copy to clipboard
    startDriver SHT3X

mqtt_broadcastInterval 60

// hold button to get into safe mode
addEventHandler OnHold 20 SafeMode

setChannelLabel 3 humidity
setChannelLabel 2 temperature

// AAA battery: 1500 3000
// rechargable: 1800 2400
Battery_Setup 1500 3000
Battery_Measure

Battery_cycle 60
SHT_cycle 60

// wait until wifi is connected
waitFor WiFiState 4

// go to deep sleep if mqtt can't connect
addRepeatingEventID 30 -1 1337 DeepSleep 300

// wait until mqtt is connected
waitFor MQTTState 1

cancelRepeatingEvent 1337

scheduleHADiscovery

delay_s 60
DeepSleep 300


    Is there a way to disable broadcasting RSSI or specific mqtt channels?

    also, HASS shows a sharp decrease in battery voltage after almost a whole day running the script:

    Voltage chart of the obk_E2C00007B device battery over a day.

    It also shows that RSSI was being broadcast every 2-3 minutes instead of the usual 5 minutes after deep sleep, with some holes in its reading:


    Graph showing changes in RSSI signal levels throughout the day.
    Attachments:
    • readResult_BK7231N_QIO_sht30_corrupted2_2024-06-1-15-08-10.bin (2 MB) You must be logged in to download this attachment.
    • readResult_BK7231N_QIO_sht30_aftererase_2024-06-1-15-19-17.bin (2 MB) You must be logged in to download this attachment.
    • readResult_BK7231N_QIO_sht30_afterflash2_2024-06-1-15-17-23.bin (2 MB) You must be logged in to download this attachment.
    • readResult_BK7231N_QIO_sht30_afterflash1_2024-06-1-15-15-26.bin (2 MB) You must be logged in to download this attachment.
    • readResult_BK7231N_QIO_sht30_aftereraseall2_2024-06-1-15-21-20.bin (2 MB) You must be logged in to download this attachment.
  • #259 20894432
    DeDaMrAz
    Level 22  
    Posts: 596
    Help: 34
    Rate: 125
    @Xinayder

    It was mentioned several times but it is worth repeating, don't run your device below 2V you are severely impacting signal integrity below that value. FLASH inside BK chip is not designed to run (read/write) below that value.

    Technical datasheet table for EON EN25QH16B (2A) chip. Table and waveform diagram regarding AC measurement conditions for the EN25QH16B (2A) chip. Table and graphs showing the operating ranges of an integrated circuit.

    More info could be found in the datasheet here - https://www.esmt.com.tw/upload/pdf/ESMT/datasheets/EN25QH16B(2A).pdf

    Also by studying your setup it looks like you are not understanding how your device works and hence you are getting very bad results. I'll try to answer what I see in your backups a bit latter.

    Thanks for providing those!
  • #260 20894571
    Xinayder
    Level 8  
    Posts: 24
    Rate: 4
    I have read that it shouldn't run below 2V, and in this case it corrupted again because I wasn't at home to change the batteries.

    Still, if the output voltage shouldn't run below 2.3-2.4V, then these sensors aren't compatible with rechargeable AAA batteries either, since their max voltage is 1.2V instead of the usual 1.5V.

    And no, it's not a TuyaMCU variant, it doesn't have any other microcontroller in it. The burnt marks are due to my solder wire, as it's not the best.


    Close-up of an electronic board with soldered wires on a red fabric background.
  • #261 20894596
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12349
    First of all, if I may, why do you want device stay online for 60 seconds after MQTT connection? People are struggling to keep whole reporting procedure at 10 seconds (5 seconds to 8 for WiFi and 2s for report), and you impose an extra 60 seconds delay... this is very, very inefficient.
    Helpful post? Buy me a coffee.
  • #262 20894636
    Xinayder
    Level 8  
    Posts: 24
    Rate: 4
    p.kaczmarek2 wrote:
    First of all, if I may, why do you want device stay online for 60 seconds after MQTT connection? People are struggling to keep whole reporting procedure at 10 seconds (5 seconds to 8 for WiFi and 2s for report), and you impose an extra 60 seconds delay... this is very, very inefficient.


    It was my understanding that the device would need to stay up a bit longer before going to deep sleep, especially if I need to change some of its settings (thought I guess this can be achieved by holding the reset button to start the sensor in safe mode). Also, with the measuring cycle set to 1 minute, doesn't it mean that the device must be awake for at least 60 seconds before it can complete a sensor reading? Or the ideal way would be to set this cycle as high as possible and just call SHT_measure, for example, to measure the sensor and immediately broadcast it, then go to sleep?

    From my experience, the power usage is not that efficient either, as I have a door sensor with this logic, going to sleep 15 seconds after the sensor's state was changed, and the battery usage is still far from ideal, compared to TuyaMCU powered devices. Setting the temperature sensor to wake up every 5 minutes, stay awake for ~15 seconds and go to sleep again will extend its battery life but I don't think it will be able to run 6 months without requiring a battery change.

    And I'm using this sensor as an outside temperature sensor, which shortens its battery life even more since batteries lose part of their capacity the colder they are.

    EDIT: I've read this FAQ from Tuya: https://developer.tuya.com/en/docs/iot/zigbee...d-humidity-sensor-common-faq?id=K9tp1656vjg9r

    it states that the temperature sensor measures temp and humidity every 5 minutes and the battery levels are read every 4 hours. The temperature and humidity values will only be transmitted if they differ 0.6C or 6% from the previous reading, and they recommend AAA batteries for more than 100 readings per day (should be around 288 readings a day if the sensor is measuring data every 5 minutes); another important part is that they mention the sensor is not suitable for outdoor use. Is it possible to achieve something like this?
  • #263 20901966
    sirhcsat
    Level 7  
    Posts: 27
    Close-up of a temperature/humidity sensor motherboard with visible components and labels.

    I have just recieved a new temp/humidity sensor from china that seems to have NO response from the CBU. I have connected my flasher as usual to the breakout points but no connection. I have traced the breakout points to the CBU and they are all connected as they should. I have connected directly to the CBU and still no response from the chip. Could the chinese be disabling the rx1 & tx1 by ota update to stop or slow down the hacking of their devices ? could they be pre flashed to only accept ota updates ??

    There are 2 test points on the main board so I wonder if these connect to rx2 & tx2 .. More investigation is needed .. Anyone any ideas ??
  • #264 20904505
    alexkip
    Level 5  
    Posts: 5
    Rate: 1
    Hello. Me too receive same sensor. I try bk7231flasher_1.1.6 and no one can`t read/write. About test points, TP1 connected to GND and TP2 connected to pin RX2 of CBU and we can read some data.
    This my log:
    Spoiler:

    <0>

    V:BK7231N_1.0.1

    REG:cpsr spsr r13 r14

    SVC:000000D3 00401C1C 000033AC

    IRQ:000000d2 00000010 00401e0c 7a1c8bcf

    FIR:000000d1 00000010 00401ffc d6fcefcf

    SYS:000000df 0040192c 00000158

    ST:00000000

    J 0x10000

    [01-01 18:12:15 TUYA Info][lr:0xa7ab9] mqc app init ...
    [01-01 18:12:15 TUYA Info][lr:0xb0fbf] thread_create name:sys_timer,stackDepth:4096,totalstackDepth:4096,priority:5
    [01-01 18:12:15 TUYA Info][lr:0xb0fbf] thread_create name:cmmod,stackDepth:4096,totalstackDepth:8192,priority:4
    [01-01 18:12:15 TUYA Debug][lr:0xa7a67] mq_pro:5 cnt:1
    [01-01 18:12:15 TUYA Debug][lr:0xa7a67] mq_pro:31 cnt:2
    [01-01 18:12:15 TUYA Debug][lr:0xb0e4b] Thread:sys_timer Exec Start. Set to Running Stat
    [01-01 18:12:15 TUYA Debug][lr:0xa180d] read m:1 f:0 l:0
    [01-01 18:12:15 TUYA Debug][lr:0xb092f] svc online log init success
    [01-01 18:12:15 TUYA Info][lr:0xb0fbf] thread_create name:wk_th-0,stackDepth:5120,totalstackDepth:13312,priority:3
    [01-01 18:12:15 TUYA Err][lr:0x99efd] wd_protected_read fails gw_bi -1
    [01-01 18:12:15 TUYA Debug][lr:0x9a1bf] gw base read finish:-1
    [01-01 18:12:15 TUYA Debug][lr:0xa4dd1] ty bt cmmod regist ok:1
    [01-01 18:12:15 TUYA Debug][lr:0xa50cd] upd adv para, send conn_req beacon.
    [PLATFORM DEBUG]!!!!!!!!!!tuya_os_adapt_bt_port_init
    [01-01 18:12:15 TUYA Notice][lr:0xa54d3] ble sdk rtus:0x0
    [01-01 18:12:15 TUYA Notice][lr:0xa4[PLATFORM NOTICE]STACK etion:0x28,status:0x0
    INIT OK
    [PLATFORM NOTI[01-01 18:12:15 TUYA DebC TUYA Debug][lr:0x594aug][lr:0x594a3] < TUYA 3] < TUYA IOT SDK V:2.3IOT SDK V:2.3.1 BS:40.0.1 BS:40.00_PT:2.2_LAN:0_PT:2.2_LAN:3.4_CAD:1.3.4_CAD:1.0.3_CD:1.0.0 0.3_CD:1.0.0 >
    < BUILD >
    < BUILD AT:2022_04_1AT:2022_04_14_10_40_13 4_10_40_13 BY ci_manageBY ci_manage FOR ty_iot FOR ty_iot_sdk_bk7231n_sdk_bk7231nl AT BK7231l AT BK7231NL >
    IOT DENL >
    IOT DEFS < WIFI_GWFS < WIFI_GW:1 DEBUG:1 :1 DEBUG:1 KV_FILE:0 SHKV_FILE:0 SHUTDOWN_MODEUTDOWN_MODE:0 LITTLE_:0 LITTLE_[01-01 18:12:15 TUYA Debug][lr:0x594ad] TH08_CBU_7231NL:1.0.0
    [01-01 18:12:15 TUYA Notice][lr:0x594b7] firmware compiled at Oct 12 2023 21:04:59
    [PLATFO[01-01 18:12:15 TUYA DeR8:12:15 TUYA Debug][lrbug][lr:0xa50cd] upd ad:0xa50cd] upd adv para,v para, send conn_req be send conn_req beacon.
    acon.
    [PLATFORM DEBUG][01-01 18:12:15 TUYA N!UYA Notice][lr:0x594c3otice][lr:0x594c3] syst] system reset reason:[em reset reason:[(null)(null)]
    ]
    [01-01 18:12:15 TUYA Debug][lr:0x99dcd] init fs. Path: (null)
    [01-01 18:12:15 TUYA Debug][lr:0xc29e3] *****************kvs_init.
    [01-01 18:12:15 TUYA Notice][lr:0xc492f] key_addr: 0x1ee000 block_sz 4096
    [01-01 18:12:15 TUYA Notice][lr:0xa51e5] ble adv upd!
    [PLATFORM NOTICE]!!!!!!!!!!tuya_before_netcfg_cb
    [PLATFORM DEBUG]UNKN[01-01 18:12:15 TUYA NoONotice][lr:0xc4a03] gettice][lr:0xc4a03] get k key:
    [PLATFORM DEBUG]estatus:0x0
    0x79 0xe 0UNKNOW EVENT:16
    [PLxLATFORM DEBUG]UNKNOW EVENATFORM DEBUG]UNKNOW EVET:16
    0xf2 0x17 0x4b 0xNT:16
    [PLATFORM DEBUG]UaATFORM DEBUG]UNKNOW EVNKNOW EVENT:16
    ENT:16
    0x2b[PLATFORM DEBUG]UN FORM DEBUG]UNKNOW EVENKNOWT:16
    0x37 0x12 0x3 EVENT:16
    7 0x67 0x21 0x8 0xb6 0x7e
    [01-01 18:12:15 TUYA Debug][lr:0xa012d] mf_core_init success
    [01-01 18:12:15 TUYA Info][lr:0xb0fbf] thread_create name:mf_test,stackDepth:5120,totalstackDepth:18432,priority:4
    [01-01 18:12:15 TUYA Debug][lr:0xb0e4b] Thread:cmmod Exec Start. Set to Running Stat
    [01-01 18:12:15 TUYA Debug][lr:0xb0e3f] enter Thread:mf_test func call
    [01-01 18:12:15 TUYA Debug][lr:0xb0e4b] Thread:mf_test Exec Start. Set to Running Stat
    [01-01 18:12:15 TUYA Debug][01-01 18:12:15 TUYA Debug][lr:0x9f421] mf thread delete
    [01-01 18:12:15 TUYA Debug][lr:0xb104b] Del Thrd:mf_test
    [01-01 18:12:15 TUYA Notice][lr:0x582b5] mf_init succ
    [01-01 18:12:15 TUYA Debug][lr:0xb3a77] pinname:16
    [01-01 18:12:15 TUYA Debug][lr:0x582c3] gwcm_mode 5
    [01-01 18:12:15 TUYA Debug][lr:0x582d1] low_power select
    [01-01 18:12:15 TUYA Debug][lr:0x583cd] no tuya_mdev_test!
    [01-01 18:12:15 TUYA Debug][lr:0x583d3] device_init in
    [01-01 18:12:15 TUYA Debug][lr:0x595fb] ------------tuya_iot_wf_soc_dev_init_param------------------
    [01-01 18:12:15 TUYA Debug][lr:0xacf8b] tuya svc upgrade init success!
    [PLATFORM NOTICE]bk_rst:0 tuya_rst:0
    [01-01 18:12:16 TUYA Notice][lr:0x9e43f] Last reset reason: 0
    [01-01 18:12:16 TUYA Debug][lr:0xb3dcf] init watchdog, interval: 60
    [01-01 18:12:16 TUYA Debug][lr:0xb3e0d] watch_dog_interval:60, monitor_detect_interval:600
    [01-01 18:12:16 TUYA Info][lr:0xb0fbf] thread_create name:health_monitor,stackDepth:1536,totalstackDepth:19968,priority:5
    [01-01 18:12:16 TUYA Debug][lr:0xb0d89] del list not empty...deleting
    [01-01 18:12:16 TUYA Debug][lr:0xb0da1] Thread:mf_test is still running..
    [01-01 18:12:16 TUYA Debug][lr:0xb0e4b] Thread:health_monitor Exec Start. Set to Running Stat
    [01-01 18:12:16 TUYA Debug][lr:0x9a1bf] gw base read finish:0
    [01-01 18:12:16 TUYA Debug][lr:0xa88f5] tls register constant 0dc5b2fe69c5789b 90QLl7l5lHq5jIbHMc6G7gzlSK8lHNUR rJrGJwwtIeXIS8HYpa4UUdLaKWDggvWgK9jXv
    [01-01 18:12:16 TUYA Debug][lr:0xa87ff] tls_ca_cnt:0 and parse:0
    [01-01 18:12:16 TUYA Notice][lr:0x9e5af] serial_no:c482e160e846
    [01-01 18:12:16 TUYA Debug][lr:0x9a51b] gw_wsm read success
    [01-01 18:12:16 TUYA Notice][lr:0x9e5e7] gw_cntl.gw_wsm.stat:0
    [01-01 18:12:16 TUYA Debug][lr:0x9e637] <__gw_upd_nc_type> bcustom_mode:0, old_wf_start_mode: 3
    [01-01 18:12:16 TUYA Notice][lr:0x9e675] gw_cntl.gw_wsm.nc_tp:1
    [01-01 18:12:16 TUYA Notice][lr:0x9e67d] gw_cntl.gw_wsm.md:0
    [01-01 18:12:16 TUYA Debug][lr:0xb24e5] set_dns_cache_priority:0
    [01-01 18:12:16 TUYA Debug][lr:0x9aa55] gw_di read success
    [01-01 18:12:16 TUYA Debug][lr:0x9ccdf] stride from flash: 0.
    [01-01 18:12:16 TUYA Debug][lr:0x9ccf7] no actived, no upgrade:0
    [01-01 18:12:16 TUYA Notice][lr:0x9e86b] gw_cntl.gw_if.abi:0 input:0
    [01-01 18:12:16 TUYA Notice][lr:0x9e877] gw_cntl.gw_if.product_key:xflodz7oja0pndk3, input:xflodz7oja0pndk3
    [01-01 18:12:16 TUYA Notice][lr:0x9e883] gw_cntl.gw_if.tp:0, input:0
    [01-01 18:12:16 TUYA Debug][lr:0x9af91] gw_ai read success
    [01-01 18:12:16 TUYA Debug][lr:0xb2651] set_dns_region:1
    [01-01 18:12:16 TUYA Debug][lr:0xb2265] cache dns [http://a.tuyaeu.com/d.json]<->[18.193.39.40]
    [01-01 18:12:16 TUYA Debug][lr:0xb2265] cache dns [https://a3.tuyaeu.com/d.json]<->[3.121.131.36]
    [01-01 18:12:16 TUYA Debug][lr:0xb2265] cache dns [m2.tuyaeu.com:1883]<->[18.184.31.90]
    [01-01 18:12:16 TUYA Debug][lr:0xb2265] cache dns [m2.tuyaeu.com:8886]<->[18.184.31.90]
    [01-01 18:12:16 TUYA Debug][lr:0x9ec73] enter success_proc
    [01-01 18:12:16 TUYA Debug][lr:0xa7a67] mq_pro:11 cnt:3
    [01-01 18:12:16 TUYA Debug][lr:0xa7a67] mq_pro:41 cnt:4
    [01-01 18:12:16 TUYA Debug][lr:0xa7a67] mq_pro:100 cnt:5
    [01-01 18:12:16 TUYA Debug][lr:0xa7a67] mq_pro:27 cnt:6
    [01-01 18:12:16 TUYA Notice][lr:0xa4f0f] ty bt upd product:xflodz7oja0pndk3 0
    [01-01 18:12:16 TUYA Notice][lr:0xa536b] upd product_id type:0 xflodz7oja0pndk3 0dc5b2fe69c5789b 90QLl7l5lHq5jIbHMc6G7gzlSK8lHNUR
    [01-01 18:12:16 TUYA Debug][lr:0x9b8e9] nc_tp:1, md:0
    [01-01 18:12:16 TUYA Debug][lr:0x9bbb7] lowpower timeout has been set to 60000 ms.
    [01-01 18:12:16 TUYA Debug][lr:0x5961d] ------------tuya_iot_wf_soc_dev_init_param_end------------------
    [01-01 18:12:16 TUYA Notice][lr:0x59c1d] tuya_hard_soft_timer_init--------------------------
    [01-01 18:12:16 TUYA Debug][lr:0xb4cf5] register wifi network monitor. interval:1
    [01-01 18:12:16 TUYA Notice][lr:0x59649] system free heap:70704
    [01-01 18:12:16 TUYA Debug][lr:0x5964f] -----
    [01-01 18:12:16 TUYA Err][lr:0x58f91] in_create_use_task---------
    [01-01 18:12:16 TUYA Err][lr:0x5871f] -----------r_w_os_parameter-------------
    [01-01 18:12:16 TUYA Err][lr:0x586eb] -----TH02W-OK------------
    [01-01 18:12:16 TUYA Err][lr:0x587fd] -----------read_parameter-------------
    [01-01 18:12:16 TUYA Err][lr:0x588ef] ---------R-th_parameter.alarm_status_bits.alarm_8bits=0x0-----------
    [01-01 18:12:16 TUYA Notice][lr:0x59219] debug_io_initial----------
    [01-01 18:12:16 TUYA Err][lr:0x58f79] --------create cmd_queue success-----------
    [01-01 18:12:16 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-success---------
    [01-01 18:12:16 TUYA Debug][lr:0x5a3d3] -----READ_CH83X5-----
    [01-01 18:12:16 TUYA Debug][lr:0xbb097] type:0x10001,is_set:1
    [01-01 18:12:16 TUYA Err][lr:0x5a033] -----------------sensor_ok-------------------
    [01-01 18:12:16 TUYA Debug][lr:0x5a247] -----Vid=0x8215-----
    [01-01 18:12:16 TUYA Err][lr:0x5a033] -----------------sensor_ok-------------------
    [01-01 18:12:16 TUYA Debug][lr:0x5a257] -----Mid=0x5959-----
    [01-01 18:12:16 TUYA Err][lr:0x5a033] -----------------sensor_ok-------------------
    [01-01 18:12:16 TUYA Debug][lr:0x5a267] -----state=0x880-----
    [01-01 18:12:16 TUYA Err][lr:0x5a423] READ_CH8315-ok-------------------
    [01-01 18:12:16 TUYA Debug][lr:0xb0e8d] Thread:mf_test Exec Finish. Set to Del Stat
    [01-01 18:12:16 TUYA Debug][lr:0xb0d89] del list not empty...deleting
    [01-01 18:12:16 TUYA Debug][lr:0xb0db5] Final Free Thread:mf_test, is_self:1
    [01-01 18:12:16 TUYA Debug][lr:0xb0dc7] delay to delete thread self
    [01-01 18:12:16 TUYA Debug][lr:0xb0df5] finally delete thread self
    [01-01 18:12:16 TUYA Err][lr:0x5a033] -----------------sensor_ok-------------------
    [01-01 18:12:16 TUYA Err][lr:0x5a163] --------tempare_value=0x1720-------------------
    [01-01 18:12:16 TUYA Err][lr:0x5a033] -----------------sensor_ok-------------------
    [01-01 18:12:16 TUYA Debug][lr:0x5a1ed] --------humidity_value=0x40c9-------------------
    [01-01 18:12:16 TUYA Debug][lr:0x5a20f] --------humidity_value_1=0x32-------------------
    [01-01 18:12:16 TUYA Debug][lr:0x5a459] ---------------th_parameter.temperature_value=231---------------
    [01-01 18:12:16 TUYA Debug][lr:0x5a461] ---------------th_parameter.humidity_value=50----------------
    [01-01 18:12:16 TUYA Debug][lr:0x59eab] ---------read_battery_voltage-------------
    [01-01 18:12:17 TUYA Debug][lr:0x59f2d] ----------adc_value=1901-------------
    [01-01 18:12:17 TUYA Debug][lr:0x59f63] ----------battery_value=100---------
    [01-01 18:12:17 TUYA Err][lr:0x58fe1] Create update_data_to_wifi_task ok!: 0
    [01-01 18:12:17 TUYA Err][lr:0x59001] Create sleep_task ok!: 0
    [01-01 18:12:17 TUYA Err][lr:0x59021] Create key_task ok!: 0
    [01-01 18:12:17 TUYA Err][lr:0x58dbb] ------------first_power----------------
    [01-01 18:12:17 TUYA Err][lr:0x59cc1] -----upload_dp_enable-dp_battery_percentage----------
    [01-01 18:12:17 TUYA Debug][lr:0x59eab] ---------read_battery_voltage-------------
    [01-01 18:12:17 TUYA Debug][lr:0x59f2d] ----------adc_value=1893-------------
    [01-01 18:12:17 TUYA Debug][lr:0x59f63] ----------battery_value=100---------
    [01-01 18:12:17 TUYA Debug][lr:0xb3a77] pinname:16
    [01-01 18:12:17 TUYA Debug][lr:0xb3a77] pinname:16
    [01-01 18:12:18 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-success---------
    [01-01 18:12:18 TUYA Debug][lr:0xbb8ed] sta search all ap and num: 3
    [01-01 18:12:18 TUYA Debug][lr:0xbb969] channel:06 bssid:de-2c-6e-19-71-b9 rssi:-38 ssid:MikroTik_2G
    [01-01 18:12:18 TUYA Debug][lr:0xbb969] channel:06 bssid:ca-6b-bc-52-5d-13 rssi:-47 ssid:4G-CPE_8612
    [01-01 18:12:18 TUYA Debug][lr:0xbb969] channel:11 bssid:7c-8b-ca-d1-b5-ec rssi:-94 ssid:342
    [01-01 18:12:18 TUYA Debug][lr:0xbb097] type:0x10001,is_set:0
    [01-01 18:12:18 TUYA Debug][lr:0xbb097] type:0x10004,is_set:0
    [01-01 18:12:18 TUYA Debug][lr:0xbb097] type:0x10001,is_set:0
    [01-01 18:12:18 TUYA Debug][lr:0xbb097] type:0x10004,is_set:0
    [01-01 18:12:18 TUYA Debug][lr:0xbb097] type:0x10001,is_set:1
    [01-01 18:12:18 TUYA Debug][lr:0xbb245] netcfg module start type:0x10001
    [01-01 18:12:18 TUYA Debug][lr:0xbb245] netcfg module start type:0x10004
    [01-01 18:12:18 TUYA Debug][lr:0xb4bc1] wifi netstat changed to:1 -->>
    [01-01 18:12:18 TUYA Notice][lr:0x593c9] cur_wifi_stat:1
    [01-01 18:12:18 TUYA Notice][lr:0x593cf] nw_stat_cb-----------------------
    [01-01 18:12:18 TUYA Debug][lr:0x59d6f] tuya_hard_wifi_status-------------------
    [01-01 18:12:18 TUYA Debug][lr:0x59d77] cur_stat=1
    [01-01 18:12:18 TUYA Err][lr:0x59db7] -----dev_cfg_s.f_update=0-----
    [01-01 18:12:18 TUYA Err][lr:0x59dc3] -----dev_cfg_s.f_cfg_state=0-----
    [01-01 18:12:18 TUYA Debug][lr:0xb4bdb] wifi netstat changed to:1 <<--
    [01-01 18:12:18 TUYA Debug][lr:0xbc97b] smart cfg start type:65537
    [01-01 18:12:18 TUYA Debug][lr:0xbb5cf] ----netcfgType:0x10001
    [01-01 18:12:18 TUYA Debug][lr:0xbbd9b] ----register netcfgType:0x10001
    [01-01 18:12:18 TUYA Debug][lr:0xbbb9d] ----start netcfgType:0x10001
    [01-01 18:12:18 TUYA Debug][lr:0xbb405] ----start netcfgType:0x10001
    [01-01 18:12:18 TUYA Debug][lr:0xbb05f] start 0x10001 ret:0
    [01-01 18:12:18 TUYA Debug][lr:0xc6307] bt netcfg start
    [01-01 18:12:18 TUYA Notice][lr:0xa53ef] update bound stat:0
    [01-01 18:12:18 TUYA Debug][lr:0xbb05f] start 0x10004 ret:0
    [01-01 18:12:18 TUYA Debug][lr:0xa50cd] upd adv para, send conn_req beacon.
    [PLATFORM DEBUG]!!!!!!!!!!tuya_os_adapt_bt_reset_adv
    [PLATFORM DEBUG]UNKNOW EVENT:19
    [PLATFORM DEBUG]UNKNOW EVENT:16
    [PLATFORM DEBUG]UNKNOW EVENT:20
    [PLATFORM DEBUG]UNKNOW EVENT:16
    [01-01 18:12:18 TUYA Notice][lr:0xa51e5] ble adv upd!
    [01-01 18:12:19 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=100-----------
    [01-01 18:12:19 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-success---------
    [01-01 18:12:20 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=101-----------
    [01-01 18:12:20 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-fail---------
    [01-01 18:12:20 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=102-----------
    [01-01 18:12:20 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-fail---------
    [01-01 18:12:21 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=103-----------
    [01-01 18:12:21 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-fail---------
    [01-01 18:12:21 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=104-----------
    [01-01 18:12:21 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-fail---------
    [01-01 18:12:22 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=105-----------
    [01-01 18:12:22 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-fail---------
    [01-01 18:12:22 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=106-----------
    [01-01 18:12:22 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-fail---------
    [01-01 18:12:23 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=107-----------
    [01-01 18:12:23 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-fail---------
    [01-01 18:12:23 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=108-----------
    [01-01 18:12:23 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-fail---------
    [01-01 18:12:24 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=109-----------
    [01-01 18:12:24 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-fail---------
    [01-01 18:12:24 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=110-----------
    [01-01 18:12:24 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-fail---------
    [01-01 18:12:25 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=111-----------
    [01-01 18:12:25 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-fail---------
    [01-01 18:12:25 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=112-----------
    [01-01 18:12:25 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-fail---------
    [01-01 18:12:26 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=113-----------
    [01-01 18:12:26 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-fail---------
    [01-01 18:12:26 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=114-----------
    [01-01 18:12:26 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-fail---------
    [01-01 18:12:27 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=115-----------
    [01-01 18:12:27 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-fail---------
    [01-01 18:12:27 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=116-----------
    [01-01 18:12:27 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-fail---------
    [01-01 18:12:28 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=117-----------
    [01-01 18:12:28 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-fail---------
    [01-01 18:12:28 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=118-----------
    [01-01 18:12:28 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-fail---------
    [01-01 18:12:29 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=119-----------
    [01-01 18:12:29 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-fail---------
    [01-01 18:12:29 TUYA Err][lr:0x58e49] --------------net_det_overtime_count=120-----------
    [01-01 18:12:29 TUYA Err][lr:0x58d67] ---send_sensor_message--InQueue-fail---------
    [01-01 18:12:30 TUYA Debug][lr:0xb3a77] pinname:16
    [01-01 18:12:30 TUYA Err][lr:0x5871f] -----------r_w_os_parameter-------------
    [01-01 18:12:30 TUYA Err][lr:0x58a13] ---------W-th_parameter.alarm_status_bits.alarm_8bits=0x0-----------
    [01-01 18:12:30 TUYA Notice][lr:0x58a83] pframe -> 1, 60 14 1
    [01-01 18:12:30 TUYA Notice][lr:0x58b1f] enter sleep mode,sleep_timer is 3600, 4080, 4080

  • #265 20904603
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12349
    You mean TX2 on CBU?

    Have you tried desoldering the WiFi module?

    Added after 56 [seconds]:

    I'd say probably you are trying to connect to wrong GPIO, or CBU is in sleep mode (it still has some power from capacitors), or something is connected on RX/TX, for example, a button with debouncing capacitor or a LED.
    Helpful post? Buy me a coffee.
  • #266 20905285
    sirhcsat
    Level 7  
    Posts: 27
    If I get a chance today I will remove the cbu from the board and test a little more but I need to get my car ready for its anual MOT so that takes priority.. the only visual difference is this cbu has a metal shield over the beken chip whereas all the rest of my units have nothing. when shorting cen to ground the chip resets. I have tried external 3.3v power. there could be something on the board pulling tx1 or rx1 to ground but untill I free the cbu it is all guess work.
  • #267 20905309
    alexkip
    Level 5  
    Posts: 5
    Rate: 1
    I update firmware, just swap RX an TX wires
  • #268 20905587
    sirhcsat
    Level 7  
    Posts: 27
    I have swapped rx1 & tx1 and I could dump the original flash into a 2mb dump.
    here is the log from the backup.

    Code: text Expand Select all Copy to clipboard
    Backup name has not been set, so output file will only contain flash type/date.
Starting read!
Now is: 12 January 2024 14:49:58.
Flasher mode: BK7231N
Going to open port: COM7.
Serial port open!
Getting bus... (now, please do reboot by CEN or by power off/on)
Getting bus success!
Going to set baud rate setting (921600)!
Will try to read device flash MID (for unprotect N):
Flash MID loaded: 1560EB
Will now search for Flash def in out database...
Flash def found! For: 1560EB
Flash information: mid: 1560EB, icName: TH25Q_16HB, manufacturer: TH, szMem: 1000000, szSR: 2, cwUnp: 0, cwEnp: 7, cwMsk: 407C, sb: 2, lb: 5, cwdRd: 05-35-FF-FF, cwdWr: 01-FF-FF-FF
Entering SetProtectState(True)...
sr: 34
sr: 34
final sr: 34
msk: 407c
cw: 0, sb: 2, lb: 5
bfd: 0
sr: 0
sr: 0
final sr: 0
msk: 407c
cw: 0, sb: 2, lb: 5
bfd: 0
SetProtectState(True) success!
Going to start reading at offset 0x00...
Reading 0x00... Ok! Reading 0x1000... Ok! Reading 0x2000... Ok! Reading 0x3000... Ok! Reading 0x4000... Ok! Reading 0x5000... Ok! Reading 0x6000... Ok! Reading 0x7000... Ok! Reading 0x8000... Ok! Reading 0x9000... Ok! Reading 0xA000... Ok! Reading 0xB000... Ok! Reading 0xC000... Ok! Reading 0xD000... Ok! Reading 0xE000... Ok! Reading 0xF000... Ok! Reading 0x10000... Ok! Reading 0x11000... Ok! Reading 0x12000... Ok! Reading 0x13000... Ok! Reading 0x14000... Ok! Reading 0x15000... Ok! Reading 0x16000... Ok! Reading 0x17000... Ok! Reading 0x18000... Ok! Reading 0x19000... Ok! Reading 0x1A000... Ok! Reading 0x1B000... Ok! Reading 0x1C000... Ok! Reading 0x1D000... Ok! Reading 0x1E000... Ok! Reading 0x1F000... Ok! Reading 0x20000... Ok! Reading 0x21000... Ok! Reading 0x22000... Ok! Reading 0x23000... Ok! Reading 0x24000... Ok! Reading 0x25000... Ok! Reading 0x26000... Ok! Reading 0x27000... Ok! Reading 0x28000... Ok! Reading 0x29000... Ok! Reading 0x2A000... Ok! Reading 0x2B000... Ok! Reading 0x2C000... Ok! Reading 0x2D000... Ok! Reading 0x2E000... Ok! Reading 0x2F000... Ok! Reading 0x30000... Ok! Reading 0x31000... Ok! Reading 0x32000... Ok! Reading 0x33000... Ok! Reading 0x34000... Ok! Reading 0x35000... Ok! Reading 0x36000... Ok! Reading 0x37000... Ok! Reading 0x38000... Ok! Reading 0x39000... Ok! Reading 0x3A000... Ok! Reading 0x3B000... Ok! Reading 0x3C000... Ok! Reading 0x3D000... Ok! Reading 0x3E000... Ok! Reading 0x3F000... Ok! Reading 0x40000... Ok! Reading 0x41000... Ok! Reading 0x42000... Ok! Reading 0x43000... Ok! Reading 0x44000... Ok! Reading 0x45000... Ok! Reading 0x46000... Ok! Reading 0x47000... Ok! Reading 0x48000... Ok! Reading 0x49000... Ok! Reading 0x4A000... Ok! Reading 0x4B000... Ok! Reading 0x4C000... Ok! Reading 0x4D000... Ok! Reading 0x4E000... Ok! Reading 0x4F000... Ok! Reading 0x50000... Ok! Reading 0x51000... Ok! Reading 0x52000... Ok! Reading 0x53000... Ok! Reading 0x54000... Ok! Reading 0x55000... Ok! Reading 0x56000... Ok! Reading 0x57000... Ok! Reading 0x58000... Ok! Reading 0x59000... Ok! Reading 0x5A000... Ok! Reading 0x5B000... Ok! Reading 0x5C000... Ok! Reading 0x5D000... Ok! Reading 0x5E000... Ok! Reading 0x5F000... Ok! Reading 0x60000... Ok! Reading 0x61000... Ok! Reading 0x62000... Ok! Reading 0x63000... Ok! Reading 0x64000... Ok! Reading 0x65000... Ok! Reading 0x66000... Ok! Reading 0x67000... Ok! Reading 0x68000... Ok! Reading 0x69000... Ok! Reading 0x6A000... Ok! Reading 0x6B000... Ok! Reading 0x6C000... Ok! Reading 0x6D000... Ok! Reading 0x6E000... Ok! Reading 0x6F000... Ok! Reading 0x70000... Ok! Reading 0x71000... Ok! Reading 0x72000... Ok! Reading 0x73000... Ok! Reading 0x74000... Ok! Reading 0x75000... Ok! Reading 0x76000... Ok! Reading 0x77000... Ok! Reading 0x78000... Ok! Reading 0x79000... Ok! Reading 0x7A000... Ok! Reading 0x7B000... Ok! Reading 0x7C000... Ok! Reading 0x7D000... Ok! Reading 0x7E000... Ok! Reading 0x7F000... Ok! Reading 0x80000... Ok! Reading 0x81000... Ok! Reading 0x82000... Ok! Reading 0x83000... Ok! Reading 0x84000... Ok! Reading 0x85000... Ok! Reading 0x86000... Ok! Reading 0x87000... Ok! Reading 0x88000... Ok! Reading 0x89000... Ok! Reading 0x8A000... Ok! Reading 0x8B000... Ok! Reading 0x8C000... Ok! Reading 0x8D000... Ok! Reading 0x8E000... Ok! Reading 0x8F000... Ok! Reading 0x90000... Ok! Reading 0x91000... Ok! Reading 0x92000... Ok! Reading 0x93000... Ok! Reading 0x94000... Ok! Reading 0x95000... Ok! Reading 0x96000... Ok! Reading 0x97000... Ok! Reading 0x98000... Ok! Reading 0x99000... Ok! Reading 0x9A000... Ok! Reading 0x9B000... Ok! Reading 0x9C000... Ok! Reading 0x9D000... Ok! Reading 0x9E000... Ok! Reading 0x9F000... Ok! Reading 0xA0000... Ok! Reading 0xA1000... Ok! Reading 0xA2000... Ok! Reading 0xA3000... Ok! Reading 0xA4000... Ok! Reading 0xA5000... Ok! Reading 0xA6000... Ok! Reading 0xA7000... Ok! Reading 0xA8000... Ok! Reading 0xA9000... Ok! Reading 0xAA000... Ok! Reading 0xAB000... Ok! Reading 0xAC000... Ok! Reading 0xAD000... Ok! Reading 0xAE000... Ok! Reading 0xAF000... Ok! Reading 0xB0000... Ok! Reading 0xB1000... Ok! Reading 0xB2000... Ok! Reading 0xB3000... Ok! Reading 0xB4000... Ok! Reading 0xB5000... Ok! Reading 0xB6000... Ok! Reading 0xB7000... Ok! Reading 0xB8000... Ok! Reading 0xB9000... Ok! Reading 0xBA000... Ok! Reading 0xBB000... Ok! Reading 0xBC000... Ok! Reading 0xBD000... Ok! Reading 0xBE000... Ok! Reading 0xBF000... Ok! Reading 0xC0000... Ok! Reading 0xC1000... Ok! Reading 0xC2000... Ok! Reading 0xC3000... Ok! Reading 0xC4000... Ok! Reading 0xC5000... Ok! Reading 0xC6000... Ok! Reading 0xC7000... Ok! Reading 0xC8000... Ok! Reading 0xC9000... Ok! Reading 0xCA000... Ok! Reading 0xCB000... Ok! Reading 0xCC000... Ok! Reading 0xCD000... Ok! Reading 0xCE000... Ok! Reading 0xCF000... Ok! Reading 0xD0000... Ok! Reading 0xD1000... Ok! Reading 0xD2000... Ok! Reading 0xD3000... Ok! Reading 0xD4000... Ok! Reading 0xD5000... Ok! Reading 0xD6000... Ok! Reading 0xD7000... Ok! Reading 0xD8000... Ok! Reading 0xD9000... Ok! Reading 0xDA000... Ok! Reading 0xDB000... Ok! Reading 0xDC000... Ok! Reading 0xDD000... Ok! Reading 0xDE000... Ok! Reading 0xDF000... Ok! Reading 0xE0000... Ok! Reading 0xE1000... Ok! Reading 0xE2000... Ok! Reading 0xE3000... Ok! Reading 0xE4000... Ok! Reading 0xE5000... Ok! Reading 0xE6000... Ok! Reading 0xE7000... Ok! Reading 0xE8000... Ok! Reading 0xE9000... Ok! Reading 0xEA000... Ok! Reading 0xEB000... Ok! Reading 0xEC000... Ok! Reading 0xED000... Ok! Reading 0xEE000... Ok! Reading 0xEF000... Ok! Reading 0xF0000... Ok! Reading 0xF1000... Ok! Reading 0xF2000... Ok! Reading 0xF3000... Ok! Reading 0xF4000... Ok! Reading 0xF5000... Ok! Reading 0xF6000... Ok! Reading 0xF7000... Ok! Reading 0xF8000... Ok! Reading 0xF9000... Ok! Reading 0xFA000... Ok! Reading 0xFB000... Ok! Reading 0xFC000... Ok! Reading 0xFD000... Ok! Reading 0xFE000... Ok! Reading 0xFF000... Ok! Reading 0x100000... Ok! Reading 0x101000... Ok! Reading 0x102000... Ok! Reading 0x103000... Ok! Reading 0x104000... Ok! Reading 0x105000... Ok! Reading 0x106000... Ok! Reading 0x107000... Ok! Reading 0x108000... Ok! Reading 0x109000... Ok! Reading 0x10A000... Ok! Reading 0x10B000... Ok! Reading 0x10C000... Ok! Reading 0x10D000... Ok! Reading 0x10E000... Ok! Reading 0x10F000... Ok! Reading 0x110000... Ok! Reading 0x111000... Ok! Reading 0x112000... Ok! Reading 0x113000... Ok! Reading 0x114000... Ok! Reading 0x115000... Ok! Reading 0x116000... Ok! Reading 0x117000... Ok! Reading 0x118000... Ok! Reading 0x119000... Ok! Reading 0x11A000... Ok! Reading 0x11B000... Ok! Reading 0x11C000... Ok! Reading 0x11D000... Ok! Reading 0x11E000... Ok! Reading 0x11F000... Ok! Reading 0x120000... Ok! Reading 0x121000... Ok! Reading 0x122000... Ok! Reading 0x123000... Ok! Reading 0x124000... Ok! Reading 0x125000... Ok! Reading 0x126000... Ok! Reading 0x127000... Ok! Reading 0x128000... Ok! Reading 0x129000... Ok! Reading 0x12A000... Ok! Reading 0x12B000... Ok! Reading 0x12C000... Ok! Reading 0x12D000... Ok! Reading 0x12E000... Ok! Reading 0x12F000... Ok! Reading 0x130000... Ok! Reading 0x131000... Ok! Reading 0x132000... Ok! Reading 0x133000... Ok! Reading 0x134000... Ok! Reading 0x135000... Ok! Reading 0x136000... Ok! Reading 0x137000... Ok! Reading 0x138000... Ok! Reading 0x139000... Ok! Reading 0x13A000... Ok! Reading 0x13B000... Ok! Reading 0x13C000... Ok! Reading 0x13D000... Ok! Reading 0x13E000... Ok! Reading 0x13F000... Ok! Reading 0x140000... Ok! Reading 0x141000... Ok! Reading 0x142000... Ok! Reading 0x143000... Ok! Reading 0x144000... Ok! Reading 0x145000... Ok! Reading 0x146000... Ok! Reading 0x147000... Ok! Reading 0x148000... Ok! Reading 0x149000... Ok! Reading 0x14A000... Ok! Reading 0x14B000... Ok! Reading 0x14C000... Ok! Reading 0x14D000... Ok! Reading 0x14E000... Ok! Reading 0x14F000... Ok! Reading 0x150000... Ok! Reading 0x151000... Ok! Reading 0x152000... Ok! Reading 0x153000... Ok! Reading 0x154000... Ok! Reading 0x155000... Ok! Reading 0x156000... Ok! Reading 0x157000... Ok! Reading 0x158000... Ok! Reading 0x159000... Ok! Reading 0x15A000... Ok! Reading 0x15B000... Ok! Reading 0x15C000... Ok! Reading 0x15D000... Ok! Reading 0x15E000... Ok! Reading 0x15F000... Ok! Reading 0x160000... Ok! Reading 0x161000... Ok! Reading 0x162000... Ok! Reading 0x163000... Ok! Reading 0x164000... Ok! Reading 0x165000... Ok! Reading 0x166000... Ok! Reading 0x167000... Ok! Reading 0x168000... Ok! Reading 0x169000... Ok! Reading 0x16A000... Ok! Reading 0x16B000... Ok! Reading 0x16C000... Ok! Reading 0x16D000... Ok! Reading 0x16E000... Ok! Reading 0x16F000... Ok! Reading 0x170000... Ok! Reading 0x171000... Ok! Reading 0x172000... Ok! Reading 0x173000... Ok! Reading 0x174000... Ok! Reading 0x175000... Ok! Reading 0x176000... Ok! Reading 0x177000... Ok! Reading 0x178000... Ok! Reading 0x179000... Ok! Reading 0x17A000... Ok! Reading 0x17B000... Ok! Reading 0x17C000... Ok! Reading 0x17D000... Ok! Reading 0x17E000... Ok! Reading 0x17F000... Ok! Reading 0x180000... Ok! Reading 0x181000... Ok! Reading 0x182000... Ok! Reading 0x183000... Ok! Reading 0x184000... Ok! Reading 0x185000... Ok! Reading 0x186000... Ok! Reading 0x187000... Ok! Reading 0x188000... Ok! Reading 0x189000... Ok! Reading 0x18A000... Ok! Reading 0x18B000... Ok! Reading 0x18C000... Ok! Reading 0x18D000... Ok! Reading 0x18E000... Ok! Reading 0x18F000... Ok! Reading 0x190000... Ok! Reading 0x191000... Ok! Reading 0x192000... Ok! Reading 0x193000... Ok! Reading 0x194000... Ok! Reading 0x195000... Ok! Reading 0x196000... Ok! Reading 0x197000... Ok! Reading 0x198000... Ok! Reading 0x199000... Ok! Reading 0x19A000... Ok! Reading 0x19B000... Ok! Reading 0x19C000... Ok! Reading 0x19D000... Ok! Reading 0x19E000... Ok! Reading 0x19F000... Ok! Reading 0x1A0000... Ok! Reading 0x1A1000... Ok! Reading 0x1A2000... Ok! Reading 0x1A3000... Ok! Reading 0x1A4000... Ok! Reading 0x1A5000... Ok! Reading 0x1A6000... Ok! Reading 0x1A7000... Ok! Reading 0x1A8000... Ok! Reading 0x1A9000... Ok! Reading 0x1AA000... Ok! Reading 0x1AB000... Ok! Reading 0x1AC000... Ok! Reading 0x1AD000... Ok! Reading 0x1AE000... Ok! Reading 0x1AF000... Ok! Reading 0x1B0000... Ok! Reading 0x1B1000... Ok! Reading 0x1B2000... Ok! Reading 0x1B3000... Ok! Reading 0x1B4000... Ok! Reading 0x1B5000... Ok! Reading 0x1B6000... Ok! Reading 0x1B7000... Ok! Reading 0x1B8000... Ok! Reading 0x1B9000... Ok! Reading 0x1BA000... Ok! Reading 0x1BB000... Ok! Reading 0x1BC000... Ok! Reading 0x1BD000... Ok! Reading 0x1BE000... Ok! Reading 0x1BF000... Ok! Reading 0x1C0000... Ok! Reading 0x1C1000... Ok! Reading 0x1C2000... Ok! Reading 0x1C3000... Ok! Reading 0x1C4000... Ok! Reading 0x1C5000... Ok! Reading 0x1C6000... Ok! Reading 0x1C7000... Ok! Reading 0x1C8000... Ok! Reading 0x1C9000... Ok! Reading 0x1CA000... Ok! Reading 0x1CB000... Ok! Reading 0x1CC000... Ok! Reading 0x1CD000... Ok! Reading 0x1CE000... Ok! Reading 0x1CF000... Ok! Reading 0x1D0000... Ok! Reading 0x1D1000... Ok! Reading 0x1D2000... Ok! Reading 0x1D3000... Ok! Reading 0x1D4000... Ok! Reading 0x1D5000... Ok! Reading 0x1D6000... Ok! Reading 0x1D7000... Ok! Reading 0x1D8000... Ok! Reading 0x1D9000... Ok! Reading 0x1DA000... Ok! Reading 0x1DB000... Ok! Reading 0x1DC000... Ok! Reading 0x1DD000... Ok! Reading 0x1DE000... Ok! Reading 0x1DF000... Ok! Reading 0x1E0000... Ok! Reading 0x1E1000... Ok! Reading 0x1E2000... Ok! Reading 0x1E3000... Ok! Reading 0x1E4000... Ok! Reading 0x1E5000... Ok! Reading 0x1E6000... Ok! Reading 0x1E7000... Ok! Reading 0x1E8000... Ok! Reading 0x1E9000... Ok! Reading 0x1EA000... Ok! Reading 0x1EB000... Ok! Reading 0x1EC000... Ok! Reading 0x1ED000... Ok! Reading 0x1EE000... Ok! Reading 0x1EF000... Ok! Reading 0x1F0000... Ok! Reading 0x1F1000... Ok! Reading 0x1F2000... Ok! Reading 0x1F3000... Ok! Reading 0x1F4000... Ok! Reading 0x1F5000... Ok! Reading 0x1F6000... Ok! Reading 0x1F7000... Ok! Reading 0x1F8000... Ok! Reading 0x1F9000... Ok! Reading 0x1FA000... Ok! Reading 0x1FB000... Ok! Reading 0x1FC000... Ok! Reading 0x1FD000... Ok! Reading 0x1FE000... Ok! Reading 0x1FF000... Ok! 
Basic read operation finished, but now it's time to verify...
Starting CRC check for 512 sectors, starting at offset 00
CRC matches 0x8A123AA4!
All read!
Loaded total 0x200000 bytes 
Wrote 2097152 to readResult_BK7231N_QIO_2024-12-1-14-50-34.bin
Backup 2MB created, now will attempt to extract OBK config.
It's not an OBK config, header is bad
OBK config not found.
Backup 2MB created, 


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, as usual, at 2023424


    Flashing with latest update the log looked as it should but since no pins were found, setting it up could be trial and error finding them .
    I can not get it to connect to my wifi either..

    since they seemed to have reconfigured rx1 & tx1 I wonder if they have reconfigured the other gpio pins as well.
  • #269 20905650
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12349
    Why do you think they swapped physically RX1 and TX1 of CBU? Have you triple-checked, maybe the error is on your side? Are you soldering directly to CBU pads or to the port on the board?
    Helpful post? Buy me a coffee.
  • #270 20905729
    alexkip
    Level 5  
    Posts: 5
    Rate: 1
    The port on the board really have wrong marking.
    @sirhcsat
    Try insert batteries, my device start normally after flashing.
Reply Cool? Ranking DIY | New topic
Notify about new articles
📢 Listen (AI):
Report a violation of the law

Topic summary

✨ The discussion centers on a generic WiFi temperature and humidity sensor based on the BK7231N CBU module with an SHT30 DIAS7M sensor, purchased from AliExpress. Key technical challenges include implementing effective power-saving strategies, particularly deep sleep modes, to extend battery life in this battery-powered device. Contributors explored the device's pinout, I2C communication (notably software I2C on pins P7 and P8), and firmware modifications using the OpenBeken SDK. Deep sleep implementation on BK7231N shows partial success: the device enters deep sleep and reboots after a set time but may reboot unexpectedly or cause boot loops if deep sleep is triggered too early in the startup script. PowerSave commands reduce power consumption but are insufficient alone; deep sleep with wake-up via GPIO or timer is essential. Battery voltage measurement and reporting were added, with calibration and percentage calculations to monitor battery health and trigger alerts on low voltage. The SHT30 sensor driver was enhanced with commands for calibration, single and periodic measurements, heater control, and alert modes that can wake the device from pindeepsleep. Scripts for automated measurement, battery management, and deep sleep cycles were developed and refined. Issues with script execution timing, startup command behavior, and SDK differences between BK7231N (N) and BK7231T (T) platforms were discussed. GPIO wake-up works on BK7231T but was initially unavailable on BK7231N until recent SDK updates. The MOSFET on the board likely provides reverse polarity protection. Integration with Home Assistant and Tasmota Control via MQTT and JSON was addressed, including sensor data formatting and auto-discovery. Challenges remain with battery-induced firmware corruption below 2V, requiring UART reflashing. Relay-based devices using CB2S boards with BK7231N were also discussed, highlighting pin assignment constraints and I2C communication issues. Overall, the community is actively developing firmware and scripts to enable local control, power optimization, and reliable sensor data reporting for these generic BK7231N-based temperature and humidity sensors.
Generated by the language model.
Today's popular

FAQ

TL;DR: Stock firmware can empty two AAA cells in just 6 h at a 10-min refresh rate [Elektroda, dheenhasty, post #20385425] “SHT30 seems very simple to support” [Elektroda, p.kaczmarek2, post #20362193] Use DeepSleep + PowerSave to cut current by >90 %.

Why it matters: Proper scripting turns a one-week gadget into a months-long sensor.

Quick Facts

• MCU: Beken BK7231N CBU module, 3.3 V core, Wi-Fi b/g/n [Elektroda, p.kaczmarek2, post #20362193] • Temp/Humidity chips: SHT30 or CHT8310/8315, I²C @ 100 kHz [Sensirion, 2023] • Battery range: 2.0 – 3.0 V (two AAA) [Elektroda, user_param_key dump] • DeepSleep current: ≈ 6 µA; active Wi-Fi current: ≈ 70 mA [Elektroda, dheenhasty, post #20393117] • Typical script wake-time: 8–12 s, 15-min cycle ⇒ ~1 % duty-cycle power use.

How do I wire the UART for flashing?

Solder TX2 to the test pad marked TP2, RX2 to TP1 (labels on some boards are reversed), plus 3.3 V and GND. Pull CEN low during power-up to enter boot mode, then use BK7231 Flasher at 921 600 baud [Elektroda, sirhcsat, post #20905587]

My sensor shows −49 °C and 3 % RH. What’s wrong?

Those values appear when the I²C pins or driver don’t match the chip. Select CHT8305 roles if your board carries CHT8310/8315 instead of SHT30 [Elektroda, sirhcsat, post #20905846]

Why does the device sometimes brick after a flat battery?

Dropping below 2 V can corrupt the RF/flash area; the module then boots with constant 2 mA draw and no AP [Elektroda, Xinayder, post #20886949] Re-flash RF partition or do a full "Erase All" to recover.

How can I stop endless waiting for MQTT when broker is offline?

Add a guard timer: addRepeatingEventID 30 1 999 DeepSleep 900 before waitFor MQTTState 1; if MQTT is still down after 30 s the sensor sleeps for 15 min [Elektroda, erdeidominik1999, post #20792052]

What script gives longest battery life?

1 ) enable PowerSave. 2 ) measure once, publish, sleep:
startDriver SHT3X → waitFor MQTTState 1 → SHT_Measure → publishChannels → DeepSleep 900. 3 ) Use flag 37 for quick Wi-Fi connect. Users report >30 days on AAA with a 15-min cycle [Elektroda, dheenhasty, post #20456982]

Edge case: device stays awake 60 s instead of 10 s

mqtt_broadcastInterval left at 1 s sends five retained topics, stretching awake time. Set it to 60 s or disable extra broadcasts to avoid triple publishes [Elektroda, Xinayder, post #20882846]

Can I combine a door switch and temperature on one PCB?

Yes. Add an SHT30 to the unused P7/P8 lines of the door-sensor board. Door events will wake the MCU, publish temp/RH, then DeepSleep. Expect one extra MQTT burst per open/close [Elektroda, p.kaczmarek2, post #20906906]

How do I calibrate the SHT30?

Run SHT_Calibrate <TempOffset> <RHOffset> once in autoexec, e.g. SHT_Calibrate -2.4 3 lowers reported temperature by 2.4 °C and raises humidity by 3 % RH [Elektroda, dheenhasty, post #20458926]

Quick 3-step UART flashing?

  1. Hold CEN low, power the board at 3.3 V. 2. Use BK7231 Flasher, select BK7231N, click Erase All then Write OpenBK. 3. Release CEN and reboot; connect to the OBK_XXXX AP.

How to round sensor output to two decimals?

Set channel type to temperature_div10 for 0.1 °C granularity or divide in publish: publishFloat temp $CH2/10. OBK trims trailing zeros from JSON [Elektroda, p.kaczmarek2, post #20458933]

What’s the failure threshold for Safe-Mode?

Five boots shorter than 5 s mark firmware as unstable and skip autoexec.bat, letting you reconfigure via AP without UART [Elektroda, p.kaczmarek2, post #21014538]
Generated by the language model.
ADVERTISEMENT