TH01 BK7231N CHT8310 Showing 0.00 Temperature and Humidity After Flashing

Question

TH01 BK7231N CHT8310 No temperature or humidity readout. Flashed OK without cutting any lines. I can access the IP address. I have tried several templates and Autoexec.bat files. The temp and humidity always say 0.00. I don't know where to go from here. AI: Which firmware (name, version, and...

divadiow · Accepted Answer

your device is the same as this here firmware key: keycx5ftedppgup7 product key: x3o8epevyeo3z3oa schema: fz4og8 Added after 1 [minutes]:what's in your autoexec.bat?

p.kaczmarek2 · Answer

Hey, can you provide some more information about your device? Some photos? Is it using TuyaMCU, or is sensor connected directly? Did you try to extract Tuya config?

johnnyh · Answer

It's from AliExpress, I think Tuya MCU. This is my first temp sensor, more complicated than Wi‑Fi plugs!

divadiow · Answer

that 4mb dump looks to be from a Quectel Matter device. Code: TextLog in, to see the code Code: TextLog in, to see the code

johnnyh · Answer

>>21829432 *Sorry, try this one.

johnnyh · Answer

>>21829432 How do I read these dumps? When I open the last one I uploaded, I just get unrecognisable signs.

divadiow · Answer

Tuya KV extraction is performed in this tab in Easy Flasher If it's a TuyaMCU device only the baud needed will be shown as there are no GPIO assignments

johnnyh · Answer

>>21829798 Ah, I think it's too late then, as the original was deleted and written with the OBK firmware over the top. I must have extracted the original with the wrong baud rate (if that's possible); it just shows as bizarre characters.Any idea why I get no temp readings?

johnnyh · Answer

>>21829809 I don't know why I didn't find that thread, I've searched a dozen times with TH01 etc. Anyway, thanks, I will follow through that one this evening. Added after 1 [minutes]: >>21829809 Autoexec.bat: Just this at the moment: startDriver tuyaMCU startDriver tmSensor linkTuyaMCUOutputToChannel 1 val 1 setChannelType 1 Temperature_Div10 linkTuyaMCUOutputToChannel 2 val 2 setChannelType 2 Humidity

divadiow · Answer

yes, there are quite a few TH01 variations, some with TuyaMCU, some without. Could do with a TH0x library with pics and known-good autoexec.bat, if theyre TuyaMCU.

johnnyh · Answer

Just going through that thread now, and looks like a different board layout, and mine's 2 years newer (or at least bought 2 years later), so might be quite a bit different. I said it was CHT3810 only because that's what's printed on the board and TH01 as that's what's printed on the box, but having said that, whilst checking the board with a magnifier, I see that the model is actually ZY-TH02-CB3S_V.1.0 So do people normally just keep trying different configs and files until they hit something that works, or is there a process to home in on the right files and configs? I'm pretty new to this so if there is a methodical process that would save time, I'm all ears, as they say. I'll do a search for the TH02 model. Added after 1 [hours]: I haven't got what it takes to photograph tiny components but this sensor has S M L and EBPT on it.

johnnyh · Answer

I've been trying different templates and now got temp of 125 and humidity of 119%... Is it just a case of trying anything and everything, or are there some rules to help find the right pins?

divadiow · Answer

try with tuyaMcu_defWiFiState 4 after startdriver tmsensor

johnnyh · Answer

Still got the same numbers showing. My autoexec is now: startDriver TuyaMCU startDriver tmSensor tuyaMcu_defWiFiState 4 setChannelType 1 temperature_div10 linkTuyaMCUOutputToChannel 1 val 1 setChannelType 2 Humidity linkTuyaMCUOutputToChannel 2 val 2

divadiow · Answer

try Code: TextLog in, to see the code

johnnyh · Answer

Thanks, I tried it, but still got 120% and 119%; however, for a moment the temp looked normal around 25 °C, but when I refreshed after a bit of faffing it was back to the usual.

p.kaczmarek2 · Answer

If you have valid dpIDs, but they have different multiplier than ones supported by OBK, you can specify extra multipler/divider while linking channels. Code: text Expand Select all Copy to clipboard linkTuyaMCUOutputToChannel [dpId][varType][channelID][obkFlags-Optional][mult-optional] [delta-Optional][delta2][delta3] Added after 32 :The main queston now is, do you have valid dpIDs, and you just want to scale their values, or is something wrong going on?

johnnyh · Answer

I don't think it can be corrected by multiplying/dividing, at least not by 10.The sensor is in a heated room, so we could be expecting 200 or even 250, but not 120.

p.kaczmarek2 · Answer

With linkTuyaMCUOutputToChannel , you can specify any divider, also 2 (I saw this in few devices), and also an offset.

divadiow · Answer

well these are the dpIDs from Tuya after pairing your backup file and using product key x3o8epevyeo3z3oa Code: JSONLog in, to see the code dpIDs 27, 46 and 101 are where the test autoexec.bat came from

johnnyh · Answer

Also the reading doesn't change, so I'm guessing it's not an actual temperature reading. Divadiow, are those definitely the correct channels then? What else could be wrong?

divadiow · Answer

I *think* they are. I did what I usually do with a backup to get them. I can't recall if tuyaMcu_defWiFiState 4 is always required, so maybe add that, as in previous autoexec.bat

johnnyh · Answer

After playing about with the thing, holding my finger on the sensor and on the chip, I often get plausible readings. It seems to be working at least for now, although if anything it may be a faulty product. However, in the screenshot the top part shows the correct readings, but below that CHT8305 TEMPERATURE stays at 120.00, and Humidity also stays wrong at 119%.

divadiow · Answer

oh. you have start-up commands too? only TuyaMCU and tmsensor should be running. The other drivers are for non-TuyaMCU devices. Clear startup command and use autoexec.bat only?

johnnyh · Answer

Deleted startup commands. Things have changed, but still got some weirdness going on.

p.kaczmarek2 · Answer

CH83XX driver should not be run. It may overwrite your channels with bogus data.

johnnyh · Answer

I don't think I've got that. I've got no startup commands now and the Autoexec.bat doesn't mention CHT83XX driver — only TuyaMCU and tmSensor drivers. Edit: No, but yeah! There it is: 4 drivers active... CHT83XX... Where is the thing that makes that happen? The template? I can't see where it's activated, and I have other issues with wifi etc. so maybe this will be the fix. Otherwise, it's working at least for temperature and I don't care about humidity. So how do I turn this driver off ? Much appreciated, all your help, by the way.

johnnyh · Answer

I did a hard reset from the Tools menu and I no longer have the CHT83XX driver running. Autoexec is: Code: text Expand Select all Copy to clipboardstartDriver TuyaMCU startDriver tmSensor // DPID 27: temperature setChannelType 1 temperature_div10 setChannelLabel 1 Temperature linkTuyaMCUOutputToChannel 27 val 1 // DPID 46: humidity setChannelType 2 Humidity setChannelLabel 2 Humidity linkTuyaMCUOutputToChannel 46 val 2 // DPID 101: battery_state enum: low(0), middle(1), high(2) setChannelType 3 ReadOnlyLowMidHigh setChannelLabel 3 Battery linkTuyaMCUOutputToChannel 101 enum 3 Please advise which template to upload? What's weird is that the config_pins page is blank, as in no pins are selected or assigned, yet it publishes temp and humidity data.

TH01 BK7231N CHT8310 Showing 0.00 Temperature and Humidity After Flashing

Post #1

Post #2

Post #3

Post #4

Post #5

Post #6

Post #7

Post #8

Post #9

Post #10

Post #11

Post #12

Post #13

Post #14

Post #15

Post #16

Post #17

Post #18

Post #19

Post #20

Post #21

Post #22

Post #23

Post #24

Post #25

Post #26

Post #27

Post #28

Post #29

Topic summary