[BK7231N / CB3S] TH11 Temperature and humidity sensor (IP65/WiFi)

tplewa 1296 7

Treść została przetłumaczona

Zobacz oryginalną wersję tematu

Report a violation of the law

Reply Cool? Ranking DIY | New topic

Notify about new articles

📢 Listen (AI):

Post #1

21819906 26 Jan 2026 07:37

This is another WiFi temperature sensor that works with the Tuya/Smart Life system as standard. It is an IP65-rated version for outdoor placement. The sensor is powered by two AAA batteries and is based on the CB3S module and the TuyaMCU microcontroller - here, as usual, the sensor was purchased to convert to OpenBK, i.e. to work with Home Assistant bypassing the Tuya cloud.

What we get in the box

Here, without much surprise, a short instruction manual, the sensor itself + pendant and the mounting tape and magnetic tape.

Interior sensor

Here, as expected, there is not much

That is, what was mentioned the module CB3S with BK7231N chip, TuyaMCU that is an unknown microcontroller, transistor Q1 controlled by TuyaMCU chip (U3) whose task is to cut the ground from the CB3S module. As a temperature/humidity sensor, a chip Sensylink CHT8310 communicating with TuyaMCU via I2C bus was used. Plus one button, an LED and some RC passive components....

TuyaMCU connection to CB3S module

TuyaMCU (U3)

TuyaMCU (U3)	CB3S (M1)
GPIO (Pin 7)	RST (Pin 1)
UART TX (Pin 9)	RXD1 (Pin 15)
UART RX (Pin 10)	TXD1 (Pin 16)

In order to upload OpenBK, all I had to do was lift/disconnect the RX and TX legs of the TuyaMCU and power the CB3S module directly....

Image in the Tuya app and data from the Tuya Developer Platform service

Basically, like most temperature/humidity sensors there is not much in the app i.e. data visualisation and simple settings.

Data from the Tuya Developer Platform looks as follows.

Standard Instruction Set


temp_unit_convert	Enum	

{
  "range": [
    "c",
    "f"
  ]
}

Standard Instruction Set


temp_unit_convert	Enum	

{
  "range": [
    "c",
    "f"
  ]
}

Standard Status Set


va_temperature	Integer	

{
  "unit": "℃",
  "min": -200,
  "max": 600,
  "scale": 1,
  "step": 1
}

va_humidity	Integer	

{
  "unit": "%",
  "min": 0,
  "max": 100,
  "scale": 0,
  "step": 1
}

battery_state	Enum	

{
  "range": [
    "low",
    "middle",
    "high"
  ]
}

temp_unit_convert	Enum	

{
  "range": [
    "c",
    "f"
  ]
}

Standard Status Set


va_temperature	Integer	

{
  "unit": "℃",
  "min": -200,
  "max": 600,
  "scale": 1,
  "step": 1
}

va_humidity	Integer	

{
  "unit": "%",
  "min": 0,
  "max": 100,
  "scale": 0,
  "step": 1
}

battery_state	Enum	

{
  "range": [
    "low",
    "middle",
    "high"
  ]
}

temp_unit_convert	Enum	

{
  "range": [
    "c",
    "f"
  ]
}

Additional JSON extracted from original firmware

Logs of TuyaMCU communication with CB3S module

Sensor added to Tuya cloud


Sent by WiFi module:
55 AA	00	01		00 00		00	
HEADER	VER=00	Product		LEN		CHK	

Received by WiFi module:
55 AA	00	01		00 24	7B2270223A226A33666A616A66327830617073716770222C2276223A22312E302E30227D	A3	
HEADER	VER=00	Product		LEN	{"p":"j3fjajf2x0apsqgp","v":"1.0.0"}	CHK	

[inContentAd]

Received by WiFi module:
55 AA	00	02		00 00		01	
HEADER	VER=00	McuConf		LEN		CHK	

Sent by WiFi module:
55 AA	00	02		00 01	04	06	
HEADER	VER=00	McuConf		LEN	04	CHK	

Received by WiFi module:
55 AA	00	10		00 04	03091718	4E	
HEADER	VER=00	ObtainDPcache		LEN			CHK	

Received by WiFi module:
55 AA	00	0B		00 00		0A	
HEADER	VER=00	Unk		LEN		CHK	

Sent by WiFi module:
55 AA	00	10		00 02	0100	12	
HEADER	VER=00	ObtainDPcache		LEN			CHK	

Sent by WiFi module:
55 AA	00	0B		00 02	013C	49	
HEADER	VER=00	Unk		LEN	013C	CHK	

Received by WiFi module:
55 AA	00	05		00 15	090400010017020004000000001802000400000000	62	
HEADER	VER=00	Unk		LEN	dpId=9 Enum V=0,dpId=23 Val V=0,dpId=24 Val V=0		CHK	

Sent by WiFi module:
55 AA	00	05		00 01	00	05	
HEADER	VER=00	Unk		LEN			CHK	

Received by WiFi module:
55 AA	00	05		00 15	010200040000013402020004000000170304000102	7E	
HEADER	VER=00	Unk		LEN	dpId=1 Val V=308,dpId=2 Val V=23,dpId=3 Enum V=2		CHK	

Sent by WiFi module:
55 AA	00	05		00 01	00	05	
HEADER	VER=00	Unk		LEN			CHK

Sensor not connected to the Tuya cloud


Received by WiFi module:
55 AA	00	01		00 24	7B2270223A226A33666A616A66327830617073716770222C2276223A22312E302E30227D	A3	
HEADER	VER=00	Product		LEN	{"p":"j3fjajf2x0apsqgp","v":"1.0.0"}	CHK	

Sent by WiFi module:
55 AA	00	01		00 00		00	
HEADER	VER=00	Product		LEN		CHK	

Sent by WiFi module:
55 AA	00	02		00 01	03	05	
HEADER	VER=00	McuConf		LEN	03	CHK	

Received by WiFi module:
55 AA	00	02		00 00		01	
HEADER	VER=00	McuConf		LEN		CHK

OpenBK configuration

Here looking in the logs there is not much

Set flags: 2 10 19 37 51

autoexec.bat


startDriver TuyaMCU
startDriver tmSensor

setChannelType 1 temperature_div10
linkTuyaMCUOutputToChannel 1 val 1

setChannelType 2 Humidity
linkTuyaMCUOutputToChannel 2 val 2

setChannelLabel 3 Battery
setChannelType 3 ReadOnlyLowMidHigh
linkTuyaMCUOutputToChannel 3 val 3

Log of TuyaMCU communication with CB3S module with OpenBK firmware


Sent by WiFi module:
55 AA	00	01		00 00		00	
HEADER	VER=00	Product		LEN		CHK	

Received by WiFi module:
55 AA	00	01		00 24	7B2270223A226A33666A616A66327830617073716770222C2276223A22312E302E30227D	A3	
HEADER	VER=00	Product		LEN	{"p":"j3fjajf2x0apsqgp","v":"1.0.0"}	CHK	

Received by WiFi module:
55 AA	00	02		00 00		01	
HEADER	VER=00	McuConf		LEN		CHK	

Sent by WiFi module:
55 AA	00	02		00 01	03	05	
HEADER	VER=00	McuConf		LEN	03	CHK	

Received by WiFi module:
55 AA	00	02		00 00		01	
HEADER	VER=00	McuConf		LEN		CHK	

Sent by WiFi module:
55 AA	00	02		00 01	04	06	
HEADER	VER=00	McuConf		LEN	04	CHK	

Received by WiFi module:
55 AA	00	10		00 04	03091718	4E	
HEADER	VER=00	ObtainDPcache		LEN			CHK	

Sent by WiFi module:
55 AA	00	10		00 02	0100	12	
HEADER	VER=00	ObtainDPcache		LEN			CHK	

Received by WiFi module:
55 AA	00	0B		00 00		0A	
HEADER	VER=00	Unk		LEN		CHK	

Sent by WiFi module:
55 AA	00	0B		00 02	0150	5D	
HEADER	VER=00	Unk		LEN	0150	CHK	

Received by WiFi module:
55 AA	00	05		00 15	090400010017020004000000001802000400000000	62	
HEADER	VER=00	Unk		LEN	dpId=9 Enum V=0,dpId=23 Val V=0,dpId=24 Val V=0		CHK	

Sent by WiFi module:
55 AA	00	05		00 01	00	05	
HEADER	VER=00	Unk		LEN			CHK	

Received by WiFi module:
55 AA	00	05		00 15	010200040000012D02020004000000190304000102	79	
HEADER	VER=00	Unk		LEN	dpId=1 Val V=301,dpId=2 Val V=25,dpId=3 Enum V=2		CHK	

Sent by WiFi module:
55 AA	00	05		00 01	00	05	
HEADER	VER=00	Unk		LEN			CHK

Well, that's pretty much it - you can still future-proof the handling of id 9, 23, 24 - i.e. the sensor settings....

Additional moisture protection

Theoretically the sensor is IP65 rated but after uploading the firmware I decided to additionally protect the electronics with a silicone coating (MG Chemicals 422C)

Here, care must be taken that the preparation does not get into the "window" in the temperature/humidity sensor. Likewise, I do not recommend coating the antenna circuit on the CB3S module with silicone....

Cool? Ranking DIY

From Display to Complete System: How the Solution Team Creates Value at Unisystem [ad]

About Author

tplewa tplewa

Level 39

Offline

tplewa wrote 6715 posts with rating 974, helped 222 times. Live in city Warszawa. Been with us since 2003 year.

ADVERTISEMENT
#2 21819998 26 Jan 2026 09:47

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Helpful post? (0)

Post #2
21819998 26 Jan 2026 09:47

You hit on a slightly better model, not everyone has the settings (ObtainDPcache). From what I remember, we presented with @DeDaMrAz their setting here:
[CB3S/BK7231N] Temperature/humidity sensor with TuyaMCU - Schematic, reverse engineering
You can try if it works for you.

Although I would still prefer to convert to a version without TuyaMCU - there is DeepSleep in the obk.

Does your sensor report every fixed interval or when something changes? CHT has an alert function.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
ADVERTISEMENT
#3 21820206 26 Jan 2026 12:58

tplewa tplewa

Level 39

» | Topic author Helpful post? (0)

Post #3
21820206 26 Jan 2026 12:58

@p.kaczmarek2 Yes this functionality depends on the functionality of the IoT device and I guess all temperature sensors have this (they have some kind of setting whether correction or otherwise). In the case of the door opening sensor, there is actually rather nothing to configure there.

I actually fell down in a previous topic about sensors with a display i.e. (TH08 and TH08C) on a similar command i.e. 0x90 )Get cached D) and had to do a somewhat primitive and not the best working workaround. I have no idea why when startDriver tmSensor is enabled this command is not supported. When it was disabled OpenBK from what I remember responded to it.
I actually described this in post #8 - Final OpenBK firmware settings of that topic. Maybe it would be possible to improve this so that I don't do such a carnage as I did in autoexec.bat he he I looked a bit quickly in the TuyaMCU driver code on github if it could be improved quickly but here as well I would have to sit longer to understand how the data flow in the software is....

As for the use of OBK on the other hand, I will think about that in the future. At the moment I'm still too thin in these blocks - ot I've only been playing with it for a few days.

As regards the use of ObtainDPcache, I do not know how to integrate it into the HA so that parameters can be set there....

Here, the aforementioned microwave presence sensor is probably going to be quite a workaround. Unfortunately it is only supported by Tuya (it doesn't work with any HA add-on be it Tuya, Tuya Local, Local Tuya).... Likewise I looked in Debug on the Tuya Developer Platform and there is no data there i.e. no Standard Instruction Set and no Standard Status Set.... ...So it will probably be quite an exercise to get better acquainted with OBK what to do

However, going back to the topic of using OBK, I haven't checked this, but I suspect that the TuyaMCU chip polls the sensor more frequently and updates the data if the temperature changes by a certain set range. At first glance, you can see that it does not send data every certain time, but more in the moment when the temperature changes.by a certain threshold.The question is how the power consumption will look like in the case of BK systems - I have not looked at the documentation and I do not know what kind of saving modes they have - here it would be best to do such a query of the temperature/humidity sensor via I2C without waking up the WiFi etc.

When I get to grips with the burrs I have to convert - I'll probably order something inexpensive for such an experiment i.e. sprucing up the TuyaMCU and firing up the functionality on the OBK....
ADVERTISEMENT
#4 21820252 26 Jan 2026 13:44

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Helpful post? (0)

Post #4
21820252 26 Jan 2026 13:44

tplewa wrote:

I actually fell down in a previous topic about sensors with a display i.e. (TH08 and TH08C) on a similar command i.e. 0x90 )Get cached D) and had to do a somewhat primitive and not the best working workaround. I have no idea why when startDriver tmSensor is enabled this command is not supported. When it was disabled OpenBK from what I remember responded to it.
I actually described this in post #8 - Final OpenBK firmware settings of that topic. Maybe it would be possible to improve this so that I don't do such a carnage as I did in autoexec.bat he he I looked a bit in the TuyaMCU driver code on github to see if it could be improved quickly but here as well I would have to sit longer to understand how the data flow is in the software...

Thanks for your interest. I'd be happy to help figure it out, but I have quite limited time (huge number of projects - you can see for yourself on the forum), so it has to be done cleverly. On Windows and through testing.
Automatic testing of OpenBeken on Windows and on target platforms
Could you give me a 1:1 breakdown (in one block) of what the OBK should send first, what the MCU responds to? In hex. I'll put that into hardcoded tests on Windows and try to get OBK to behave according to those expectations. These tests are already on GitHub, and will make sure that future versions work as expected.

tplewa wrote:

However, returning to the topic of OBK use, I have not checked this, but I suspect that the TuyaMCU system is polling the sensor more frequently and if the temperature changes by a certain set range, it updates the data. At first glance you can see that it doesn't send data every certain time, but more in the moment when the temperature changes.by a certain threshold.The question is how the power consumption will look like in the case of BK chips - I haven't looked through the documentation and I don't know what kind of power saving modes they have - here it would be best to do such a temperature/humidity sensor query via I2C without waking up WiFi etc.

The CHT8310 can be programmed to pin alert to wake up the MCU (or WiFI module) when a certain change occurs. There is no need to do polling (manual polling).

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#5 21820891 26 Jan 2026 23:35

tplewa tplewa

Level 39
» | Topic author Helpful post? (0)

Post #5
21820891 26 Jan 2026 23:35

@p.kaczmarek2 Well with this timing I think it's always the case. Likewise with me, just as many hobby and commercial projects.... hard to reconcile it all he he

p.kaczmarek2 wrote:

Could you give me a 1:1 breakdown (in one block) of what the OBK should send first, which corresponds to the MCU? In hex. I'll put that into hardcoded tests on Windows and try to get OBK to behave according to those expectations. These tests are already on GitHub, and will make sure that future versions work as expected.

As far as I can see this is a command that works similarly to the DPCache you described.

TuyaMCU sends the command 0x90 (Get cached DP):
55 AA 03 90 00 04 03 09 17 18 D1

OBK when no data is available responds:
55 AA 00 90 00 02 01 00 92

Description from documentation:

For the moment, I made a primitive workaround in autoexec....

Code: text Expand Select all Copy to clipboard
delay_s 1 uartSendHex 55AA00900002010092

...but it's not the best approach because there's no guarantee that I'll get the answer right if there's any major delay in response.

p.kaczmarek2 wrote:

The CHT8310 can be programmed to pin alert to wake up the MCU (or WiFI module) when a certain change occurs. There is no need to do polling (manual polling).

All in all, it can be done either way - hmm looks like a good idea to practice this.

Looking at it this way, Pin3 of the CHT8310 (ALERT) is not routed out, but it should be possible to solder the kynar etc. On the other hand it's only one of many connections to make anyway

I have another sensor with the usual one not IP65 - I'll see maybe I'll dedicate it to such an experiment. I've put this IP65 out of the window and it's being tested - well, to bad the temperatures are now positive.... ...and I wanted to check how long the batteries would last in sub-zero temperatures...

By the way, as I've already ripped the card from the microscope camera, I'm pasting some pics of the TH11 sensor PCB.

I didn't paste before because the quality of my microscope camera leaves a lot to be desired, so I let it go
ADVERTISEMENT
#6 21820895 26 Jan 2026 23:41

ACCel ACCel

Level 22

» | Helpful post? (0)

Post #6
21820895 26 Jan 2026 23:41

The most important thing about these sensors is whether they report negative temperatures, many do not. I don't know if this is a limitation of Tuya or the electronics.
#7 21822982 29 Jan 2026 09:33

tplewa tplewa

Level 39

» | Topic author Helpful post? (0)

Post #7
21822982 29 Jan 2026 09:33

ACCel wrote:
The most important thing about these sensors is whether they report negative temperatures, many do not. I don't know if this is a limitation of Tuya or the electronics.

Good I can answer. This one at least finally showed a negative temperature

However, as far as the limitations are concerned, I see that all these sensors, at least from what is written on the Tuya api website, are limited to -20C even though, for example, the sensor used here, according to the data, allows measurements down to -40C....

Although, as I mentioned, I am more interested in the life of the cells in such a sensor at negative temperatures - that is, rather such which the batteries or accumulators do not like very much Especially that WiFi is a bit power hungry and here, as has been said many times, e.g. sensors with ZigBee should be better suited for such purposes.

Although as I mentioned with me it's more a game of curiosity than a desire to build a smart home - so I use what I happen to have which is WiFi....
#8 21828771 04 Feb 2026 12:23

puchalak puchalak

Level 18

» | Helpful post? (0)

Post #8
21828771 04 Feb 2026 12:23

Unfortunately wifi based battery sensors don't make sense. I have (more had, as I don't use it anymore) probably exactly this one and the battery life is about 14 days. Poor. I also noticed its strange reluctance when going below zero - the sensor showed zero for a long time, only after quite a long time minus, and even so I think it overestimates negative temperatures a bit. Without a constant power supply, it's worth opting for zigbee, or some working on another system though perhaps identical to zigbee, but not on the tuya platform, such as x-sense.
Create an account, log in here. You will receive points by participating in discussions.
Join this discussion.

Install Elektroda application

Didn't find an answer? Ask Artificial Intelligence

*I agree to send the question to OpenAI, Anthropic PBC, Perplexity AI, Inc., Kagi Inc., Google LLC - owners of language models in order to prepare the best response. The companies may monitor and log information entered into the form.

*I agree to publicly display my question and answer. The question and answer will be publicly available to everyone. The process may take a few minutes. Upon completion, you will be redirected to the page with the answer.

Wait...(2min)

Reply Cool? Ranking DIY | New topic

Notify about new articles

📢 Listen (AI):

Report a violation of the law

Home page
/
Forum
/
Smart Home
/
Smart Home IoT
/
Smart Home Devices
/
[BK7231N / CB3S] TH11 Temperature and humidity sensor (IP65/WiFi)

FAQ

TL;DR: TH11 (CB3S/BK7231N) reports temperature on a −20.0 to 60.0°C scale and humidity 0–100%; “The sensor is powered by two AAA batteries and is based on the CB3S module.” [Elektroda, tplewa, post #21819906]

Why it matters: This FAQ helps DIY users flash OpenBeken, integrate with Home Assistant, and tune TuyaMCU settings without cloud lock‑in.

Quick Facts

IP65-rated outdoor Wi‑Fi temperature/humidity sensor using CB3S (BK7231N) + TuyaMCU and CHT8310 sensor. [Elektroda, tplewa, post #21819906]
Data points: temperature DP range −200…600 with scale 1 (−20.0…60.0°C); humidity 0…100 with scale 0. [Elektroda, tplewa, post #21819906]
Battery status exposes three levels: low, middle, high (DP id 3). [Elektroda, tplewa, post #21819906]
OpenBeken sample config maps DPs: temp→channel 1 (temperature_div10), humidity→channel 2, battery→channel 3. [Elektroda, tplewa, post #21819906]
CHT8310 supports an ALERT pin to wake the MCU for threshold changes (no polling). [Elektroda, p.kaczmarek2, post #21820252]

What is the TH11 sensor and what’s inside?

TH11 is an IP65 Wi‑Fi temperature/humidity probe for Tuya/Smart Life. Inside: CB3S module with BK7231N, a TuyaMCU coprocessor, and a Sensylink CHT8310 temp/RH sensor. It runs on two AAA batteries and includes a button, LED, and basic passives. [Elektroda, tplewa, post #21819906]

Does TH11 support negative temperatures?

Yes. The firmware exposes va_temperature with min −200 and scale 1, meaning −20.0°C. Max is 60.0°C (600/10). Negative readings within this range are valid. Example telemetry shows values like 301, which equals 30.1°C after scale. [Elektroda, tplewa, post #21819906]

How often does it report—fixed interval or on change?

Behavior suggests event‑driven reporting when thresholds change rather than a fixed interval. The CHT8310 can assert its ALERT pin to wake the MCU/Wi‑Fi module for updates. "There is no need to do polling." [Elektroda, p.kaczmarek2, post #21820252]

How do I flash OpenBeken (OpenBK) onto the CB3S in TH11?

How‑To (hardware):

Lift or disconnect TuyaMCU RX/TX legs and power CB3S directly.
Flash OpenBK to CB3S via UART.
Reconnect and configure TuyaMCU↔channel links in autoexec. This avoids TuyaMCU interference during flashing. [Elektroda, tplewa, post #21819906]

What OpenBeken autoexec settings work for TH11?

Example: startDriver TuyaMCU and tmSensor, set channel types, and link DPs:

ch1 temperature_div10 ↔ DP1
ch2 Humidity ↔ DP2
ch3 ReadOnlyLowMidHigh (Battery) ↔ DP3 Flags: 2 10 19 37 51. This yields temperature, humidity, and battery status in HA. [Elektroda, tplewa, post #21819906]

What do the Tuya DPs mean (units and offsets)?

DP1 temperature uses scale 1 (tenths °C). DP2 humidity uses scale 0 (percent). DP3 is battery enum: low/middle/high. DP9 switches °C/°F. DP23 is temperature correction −2.0…+2.0 (scale 1). DP24 is humidity correction −10…+10. [Elektroda, tplewa, post #21819906]

How do I handle the 0x90 “Get cached DP” / ObtainDPcache behavior with OBK?

TuyaMCU issues 0x90; OBK should reply 55 AA 00 90 00 02 01 00 92 when no data. A temporary workaround sends that hex via uartSendHex after a short delay, though it’s timing‑sensitive. Logs and exact frames are provided. [Elektroda, tplewa, post #21820891]

What is TuyaMCU and why disconnect its RX/TX for flashing?

TuyaMCU is a microcontroller that mediates sensors and the Wi‑Fi module. It can hold the CB3S UART busy. Lifting/disconnecting its RX/TX isolates CB3S for clean flashing and direct power. Reconnect after flashing. [Elektroda, tplewa, post #21819906]

What is OpenBeken (OpenBK) and why use it with Home Assistant?

OpenBeken is alternative firmware for BK7231 devices. It enables local control and Home Assistant integration without Tuya cloud. Developers note OpenBK also supports DeepSleep on non‑TuyaMCU builds for better battery life. [Elektroda, p.kaczmarek2, post #21819998]

Can the CHT8310 ALERT pin reduce power usage?

Yes. Configure CHT8310’s ALERT to trigger on threshold changes and wake the MCU for reporting. This avoids constant polling. "There is no need to do polling." This suits battery‑powered outdoor nodes. [Elektroda, p.kaczmarek2, post #21820252]

How should I protect the PCB against moisture?

Apply a silicone conformal coating (e.g., MG Chemicals 422C) to the PCB. Do not coat the CHT8310 sensing window. Avoid the CB3S antenna area to preserve RF performance. The unit is IP65, but extra protection helps outdoors. [Elektroda, tplewa, post #21819906]

What do the battery levels actually indicate?

Battery is an enum from the device: low, middle, high (DP id 3). It is not a voltage reading. Use it as a coarse indicator for battery replacement planning. Surface it as a read‑only channel in OpenBK. [Elektroda, tplewa, post #21819906]

Do some Tuya sensors fail to show negative temperatures?

Yes, community reports note some models do not expose negatives. TH11’s DP range includes negatives (−20.0°C), but other Tuya devices may limit firmware. Check your DP schema. [Elektroda, ACCel, post #21820895]

How can I surface ObtainDPcache-based settings in Home Assistant?

The device exposes ObtainDPcache and extra DPs (e.g., DP9, 23, 24). OpenBK maps DPs to channels, but HA UI binding for these settings may need custom integration until OBK improves DP cache handling. [Elektroda, tplewa, post #21820206]

What do the example hex logs tell me about scaling and units?

Frames like dpId=1 Val V=301 mean 30.1°C after applying scale 1. Humidity uses integers (e.g., 25 → 25%). Battery reports as enum 0–2 for low/middle/high. These map cleanly in OpenBK channels. [Elektroda, tplewa, post #21819906]

Is there a non‑TuyaMCU OpenBK path with better sleep support?

Yes. Contributors prefer converting to a build without TuyaMCU for native DeepSleep in OpenBK. This can extend battery life compared with a TuyaMCU‑mediated design. [Elektroda, p.kaczmarek2, post #21819998]

[BK7231N / CB3S] TH11 Temperature and humidity sensor (IP65/WiFi)

Didn't find an answer? Ask Artificial Intelligence