HTU2x supported?

24 views
Skip to first unread message

Ulf Holt

unread,
Jul 17, 2024, 1:07:01 PM (7 days ago) Jul 17
to TasmotaUsers
I have some
 HTU2x sensors, and wonder if it is possible to make them work with Tasmota. Have tried to compile the kernel using #define USE_HTU, but after uploading the binaries, nothing is displayed, and i2cscan finds nothing. I am using GPIO2 and GPIO4, which works perfekt when testing with BME280.

Best regards

Ulf H.

Philip Knowles

unread,
Jul 17, 2024, 2:16:00 PM (6 days ago) Jul 17
to Ulf Holt, TasmotaUsers
It should work without a need for compiling using sensors (or an ESP32). If you are using TLS or something requiring compiling I'd try with sensors first

8
HTU21
Temperature and Humidity sensor
xsns_08_htu21.ino
I2C
0x40
2018
Heiko Krupp,
Theo Arends

USE_HTU
-
- / x
-
x
-



From: sonof...@googlegroups.com <sonof...@googlegroups.com> on behalf of Ulf Holt <ulf....@gmail.com>
Sent: 17 July 2024 18:07
To: TasmotaUsers <sonof...@googlegroups.com>
Subject: HTU2x supported?
 
--
You received this message because you are subscribed to the Google Groups "TasmotaUsers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonoffusers...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/sonoffusers/aff58d7a-15af-4773-a866-ebad2d4d3c64n%40googlegroups.com.

Ulf Holt

unread,
Jul 17, 2024, 9:05:45 PM (6 days ago) Jul 17
to TasmotaUsers
I have been using GPIO 2 and 4, which works fine with BME280, might this be an issue? I’ll be testing with Sensors tomorrow, but I need SSL

Andrew Russell

unread,
Jul 18, 2024, 4:05:28 AM (6 days ago) Jul 18
to Ulf Holt, TasmotaUsers
i2cscan should find the device, even if it's not supported.
Test one step at a time. Remove the BME280 from a working system and replace with the HTU. If it does not show up, then I would suspect a dead HTU, or incorrect wiring.

benjam...@t-online.de

unread,
Jul 18, 2024, 4:31:14 AM (6 days ago) Jul 18
to TasmotaUsers
Could be an issue with i2c addresses. May be another supported device is using the same address and has priority. If so, it has to be disabled and the HTU2x has to be enabled. I had this with the VL53L0x

Philip Knowles

unread,
Jul 18, 2024, 4:43:09 AM (6 days ago) Jul 18
to Ulf Holt, TasmotaUsers
SSL is included in ESP32 so that might be your best bet.

Sent: 18 July 2024 02:05
To: TasmotaUsers <sonof...@googlegroups.com>
Subject: Re: HTU2x supported?
 

Justin Adie

unread,
Jul 18, 2024, 5:28:24 AM (6 days ago) Jul 18
to Ulf Holt, SonoffUsers
Generally not a good idea to use pin 2 for i2c on the esp32 as the pull-ups will prevent the chip going into flashing mode.   That said, in runtime the gpio will behave normally and this won’t be the cause of your issue.  



Justin Adie

unread,
Jul 18, 2024, 5:51:47 AM (6 days ago) Jul 18
to SonoffUsers
For future readers.  

The default i2c address for HTU2x is 0x40.  So far as I remember this is not changeable.
For BME280 it is 0x77 or 0x76 depending on whether the SDO pin is connected to VCC or GND (it must be connected to one of these, and not left floating). 





Reply all
Reply to author
Forward
0 new messages