Based on the esphome log file, I am experiencing an error “Communication failed”, “Invalid readings! Check pin number and pull-up resistor and try manually specifying the model.” on both of my recently (<3 months ago) purchased temp-humidity sensors. See pictures and documentation below. I am new to this technology, but learning fast. What am I doing incorrectly?
I followed the wiring diagram provided, but initially used too high a Zone for the DAT connection that was not compatible. I am now using Zone 1, with nothing connected to Zone 2 (in case of a conflict). I am using Alarm Panel Pro 45eb94 (project version 1.2.1.17) on ESPHome version 2025.9.1
The Alarm Panel Pro web page indicates “NA” for both “Indoor Temp-Hum Temperature” and “Indoor Temp-Hum Humidity”. The Alarm Panel Pro is providing a measured 5.04VDC at the +5V (red wire) and GND (black wire) pins. I always use “Indoor Temp-Hum” in the Zone setup and have tried variations on Update intervals and Units, but nothing works.T
It doesn’t look like you’re doing anything wrong. We’ve recently heard a couple of similar reports of temperature/humidity sensors not working reliably. I think it may be related to this ESPHome issue.
I was working with another customer who had a similar issue, but his would work for a little while, and then stop working with the same error. Is yours never getting a good reading at all? Do you have a 2nd sensor to try in case it’s a problem with the sensor itself?
Thanks for this Nate. I bought 2 DHT22 devices on the same order and neither one has provided any data. I initially tried them both when I received them (~3 months ago) - they did not work, but i had no time to follow-up. I tried them again a few days ago, still did not work, so I documented the problem and reported it. I could check the log files for sporadic evidence of valid data, but unsure how to get access to that other than what is scrolling on my Konnected device web page.
I did note the DHT22 circuit board has some “post-pin” etching to resistors? and reroutes pins to other pins? Has the manufacturer changed the pin-out design?
See attached photos of bottom and top of this circuit board.
Thanks for this Nate. I have 2 devices and neither one has provided any data. I initially tried them both when I received them (3 months ago) - they did not work. I tried them again a few days ago, still did not work, so I documented the problem and reported it.
I’ve had a few other reports of this issue. I believe that the problem is that ESPHome is not automatically detecting the type of sensor. I’m not sure when or why this changed, but there is a solution. I have an update to the Konnected app coming that will add a select box to choose the sensor type in the DHT zone configuration.
My 2 x DHT22’s are still not providing any data and have the same errors as initially documented. I updated my Konnected App to v1.6.7 this morning and noted a new drop-down menu “Model” under the Zone “Type” “Indoor Temp-Hum”. I tried new firmware using models: DHT22 (Type 2), DHT, Auto, AM2302, and DHT11. None of these models worked with either of my 2 x AM2302DHT22 sensors.
At this point I would like a replacement for these 2 x DHT22 sensors from Order #49965 as I believe they are faulty, especially after this latest Konnected app update to accommodate so many different models of DHT.
I just played with this and initially had the same issue as you. I dug into the firmware to figure out what could be wrong here, and I think I solved it. A fix is deploying to our servers now – to apply it you will need to edit and build a new firmware build for your device and apply the update.
I’m not sure if it really matters what model is selected – I had success on my Alarm Panel Pro with DHT22_TYPE2 and AM2302 selected.
The trick seems to have been a configuration of the internal pullup on the pin. Since these “red board” temperature sensors have an external pullup resistor already built-in, I think the firmware was trying to add an internal pullup which was conflicting with the external pullup that’s already on the sensor. Anyway, I disabled the internal pullup in our firmware configuration now, and the readings were accurate and reliable in my testing after doing so.
Please update your firmware and let us know how that goes.
