Problems with Temp/Humidity

[mihalski]

Hi,

I got my new Sonoff, configured the user_config file including uncommenting #define SEND_TELEMETRY_DHT, and programmed the Sonoff.

I then plugged in the temp/humidity sensor (all the way until you hear the click and it's securely plugged in) and waited for temp/humidity telemetry data.. Nada. All I get is this:

2:17:53 MQTT: sonoff/UPTIME = 0
12:17:53 MQTT: sonoff/RSSI = 100
12:17:53 MQTT: sonoff/LIGHT = On
12:17:53 MQTT: sonoff/TIME = 2016-10-11T12:17:53

I notice the time is wrong also (I assumed 10 would be correct as I'm in Brisbane/Australia).

Any ideas as to what might be wrong?

EDIT: I've since found, set, recompiled and uploaded new firmware with the following setting:

#define DHT_TYPE             AM2301

Still Nada.

Regards,
Michal

[arendst]

Many could be wrong...

1. If you have a sonoff TH10/16 then forget about using GPIO04 as in my case this is not available on the Sonoff TH10/16 connector; they just did not install the parts needed as I noticed and measured on mine. Only GPIO14 is available on the tip of the connector, the second ring from the tip should have been GPIO04 but is not connected to the ESP8266. The third ring is ground and the last ring, closest to the cable is +3V3.

So in order to use your DHT just swap the defines for GPIO04 and GPIO14 in user_config.h and recompile and upload. That should solve it (unless itead decided to use the second ring of the connector for the DHT sensor in which case you'll have to contact itead for a solution).

BTW I would not be surprised; my received ds18b20 didn't work either as they swapped both power connections of the sensor...

Also remember that itead insists to plug in the sensor first before power on the sonoff TH10/16 as you may most probably short Gnd and +3V3 otherwise.

2. If I change the timezone to 10 it adds ten hours to UTC as expected. What is your result compared to UTC if you execute command timezone 10 and then perform command status using the serial interface or the console in the webinterface?

Another option is to update both TIME_DST and TIME_STD in user_config.h for your location and execute command timezone 99 in which case it also supports daylight savings.

[arendst]

Also do not forget to change define DHT_TYPE into DHT22

[mihalski]

Thank you for the quick reply.

The timezone issue seems to have resolved itself but still no luck with temp/humidity readings.. There is SOME progress though. At least it acknowledges the existence of TEMP.

With GPIO pins reversed:

00:00:00 APP: Project sonoff (Topic sonoff1, Fallback DVES_07C2BA, GroupTopic sonoffs) Version 2.0.4
00:00:04 HTTP: Webserver active on sonoff1-0698 with IP address 192.168.1.3
00:00:04 MQTT: Attempting connection...
00:00:04 MQTT: Connected
00:00:04 MQTT: sonoff1/INFO = Sonoff module version 2.0.4, Fallback DVES_07C2BA, GroupTopic sonoffs
00:00:04 MQTT: sonoff1/INFO = Webserver active for Admin on sonoff1-0698 with IP address 192.168.1.3
10:00:40 MQTT: sonoff1/UPTIME = 0
10:00:40 MQTT: sonoff1/RSSI = 88
10:00:40 MQTT: sonoff1/TEMP = 0.0
10:00:40 MQTT: sonoff1/POWER = Off
10:00:40 MQTT: sonoff1/TIME = 2016-10-12T10:00:40
10:02:10 MQTT: sonoff1/STATUS = 2.0.4, 1, sonoff1, 0, POWER, 0, 10, 1, 1, 1, 0

With GPIO pins as default:

00:00:00 APP: Project sonoff (Topic sonoff1, Fallback DVES_07C2BA, GroupTopic sonoffs) Version 2.0.4
00:00:04 HTTP: Webserver active on sonoff1-0698 with IP address 192.168.1.3
00:00:04 MQTT: Attempting connection...
00:00:04 MQTT: Connected
00:00:04 MQTT: sonoff1/INFO = Sonoff module version 2.0.4, Fallback DVES_07C2BA, GroupTopic sonoffs
00:00:04 MQTT: sonoff1/INFO = Webserver active for Admin on sonoff1-0698 with IP address 192.168.1.3
10:10:41 MQTT: sonoff1/UPTIME = 0
10:10:41 MQTT: sonoff1/RSSI = 92
10:10:41 MQTT: sonoff1/TEMP = -0.1
10:10:41 MQTT: sonoff1/POWER = Off
10:10:41 MQTT: sonoff1/TIME = 2016-10-12T10:10:41

I'll keep fiddling with settings while I await any other suggestions.. I'd even settle for a precompiled firmware that you KNOW works (or even a user config) in case I am making some sort of stupid mistake.

EDIT: To make matters more confusing the erroneous TEMP readings only appear when I define the incorrect temperature sensor. If I have it configured for the DHT I get NOTHING. Are the below settings correct?

// MQTT - Telemetry
#define TELE_PERIOD            300          // Telemetry (0 = disable, 2 - 3600 seconds)
#define SEND_TELEMETRY_UPTIME               // Enable sending uptime telemetry (if disabled will still send hourly message)
#define SEND_TELEMETRY_RSSI                 // Enable sending wifi RSSI telemetry
//#define SEND_TELEMETRY_DS18B20              // Enable sending DS18B20 temperature telemetry
#define SEND_TELEMETRY_DHT                  // Enable sending DHT11, DHT21, DHT22, AM2301, AM2302 or AM2321 temperature and humidity telemetry
#define SEND_TELEMETRY_POWER                // Enable sending power telemetry

#if MODULE == SONOFF                        // programming header 1:3.3V 2:rx 3:tx 4:gnd
  #define APP_NAME             "Sonoff module"
  #define LED_PIN              13           // GPIO 13 = Green/Blue Led (0 = On, 1 = Off) - Sonoff
  #define LED_INVERTED         1            // 0 = (1 = On, 0 = Off), 1 = (0 = On, 1 = Off)
  #define REL_PIN              12           // GPIO 12 = Red Led and Relay (0 = Off, 1 = On)
  #define KEY_PIN              0            // GPIO 00 = Button
  #define DSB_PIN              4           // GPIO 14 = TEM1 - DS18B20 (Sonoff_TH10A(16A), Sonoff SV)
  #define DHT_PIN              14            // GPIO 04 = TEM2 - DHT22 (Sonoff_TH10A(16A), Sonoff SV)
  #define DHT_TYPE             DHT22        // DHT module type (DHT11, DHT21, DHT22, AM2301, AM2302 or AM2321)

As I mentioned before, I've tried GPIO pins 4 and 14 both ways around.

EDIT2: I've also tried with:

#define DHT_TYPE AM2301

Regards,
Michal

[arendst]

First, after investigating the Sonoff TH10/16 website it seems the DHT sensor is an AM2301 (=DHT22 compatible) so the AM2301 should work.

Second, from your first two screen shots I suspect why you only see sonoff1/TEMP without sonoff1/HUM that you must have selected SEND_TELEMETRY_DS18B20 instead of SEND_TELEMETRY_DHT. The code for SEND_TELEMETRY_DHT will ALWAYS output nothing or both TEMP and HUM and not TEMP only. This confirms your first EDIT.

You might execute command seriallog 3 to see some logging regarding the DHT sensor but I'm afraid it will only show the message "DHT: Timeout waiting for start signal low pulse" in which case it cannot find the sensor.

In my setup both DHT11 and DHT22 perform as expected. You might have a sensor wiring issue as I had with the DS18B20 (swapped power lines) or the signal cable is connected to the wrong ring on the sensor plug. I only have both DHT11 and DH22 as breadboard items.

When I measure the resistance between Gnd and Uv I measure 300 ohm with meter Gnd connected to sensor Gnd and high resistance between Gnd and Uv with meter Gnd connected to sensor Uv.

When I measure the resistance between Gnd and signal I measure 400 ohm with meter Gnd connected to sensor Gnd and high resistance between Gnd and signal with meter Gnd connected to signal.

This might give some info about possible cable miswire.

The below user_config.h part works for me:

// MQTT - Telemetry
#define TELE_PERIOD            300          // Telemetry (0 = disable, 2 - 3600 seconds)
#define SEND_TELEMETRY_UPTIME               // Enable sending uptime telemetry (if disabled will still send hourly message)
#define SEND_TELEMETRY_RSSI                 // Enable sending wifi RSSI telemetry
//#define SEND_TELEMETRY_DS18B20              // Enable sending DS18B20 temperature telemetry
#define SEND_TELEMETRY_DHT                  // Enable sending DHT11, DHT21, DHT22, AM2301, AM2302 or AM2321 temperature and humidity telemetry
#define SEND_TELEMETRY_POWER                // Enable sending power telemetry

#if MODULE == SONOFF                        // programming header 1:3.3V 2:rx 3:tx 4:gnd
  #define APP_NAME             "Sonoff module"
  #define LED_PIN              13           // GPIO 13 = Green/Blue Led (0 = On, 1 = Off) - Sonoff
  #define LED_INVERTED         1            // 0 = (1 = On, 0 = Off), 1 = (0 = On, 1 = Off)
  #define REL_PIN              12           // GPIO 12 = Red Led and Relay (0 = Off, 1 = On)
  #define KEY_PIN              0            // GPIO 00 = Button
  #define DSB_PIN              14           // GPIO 14 = TEM1 - DS18B20 (Sonoff_TH10A(16A), Sonoff SV)
  #define DHT_PIN              14           // GPIO 14 = TEM1 - DHT22 (Sonoff_TH10A(16A), Sonoff SV)
  #define DHT_TYPE             AM2301       // DHT module type (DHT11, DHT21, DHT22, AM2301, AM2302 or AM2321)

[mihalski]

I don't think I quite grasp the measurements you made. I was able to test contoinuity from the sensor to the socket (but not the ESP as the contacts on that are far too small).

I've attached an image. Not sure if it's of any help at all but I thought I'd try.

http://prnt.sc/ctqub2

I actually purchased 2 basic Sonoff's and 2 Sonoffs with temp/humidity sensor just in case. Going to see if I can use the original firmware to figure anything out. I wish it was easier to trace from the socket to the ESP :/

I also have some queries with regards to the MQTT commands, but I'll start a new thread for that.

EDIT: Interestingly (in an incredibly depressing way) the original Sonoff firmware seems to read ZERO for the sensors as well. I've tried with 2 of the sensors I have. Wish I had tested that first. Doesn't really explain anything :/ Tomorrow I'll try testing the sensors themselves.

EDIT2: It took a while but finally sensor data has updated with what look to be correct values! Mpre confused than ever.

Regards,
Michal

[arendst]

Ah, nice picture. In my case the red and black connections were swapped in the sensor assy. That's what I tried to explain.

Why does the sensor update now? Does it also happen with the sonoff software?

[mihalski]

Only the unmodified sensor updates the temp/humidity. The one with the Sonoff-MQTT-OTA-Arduino firmware does not.

Physically they are both identical so I don't know what's wrong. Is there a way to dump the Sonoff firmware from the unmodified device?

According to the iOS app it's running firmware 2.0.1 which is the latest version.

Here's an image from the EWeLink app.

http://prnt.sc/ctxl5a

Regards,
Michal

[arendst]

Michal, I did a rewrite of the DHT sensor code. Could you be so kind to try it out and let me know if this works? You can download it from my Experimental repository as sonoff-dht.

Thnx in advance, Theo.

[mihalski]

Thank you for making the effort to try and get this working.

Unfortunately no luck:

00:00:00 APP: Project sonoff (Topic sonoff1, Fallback DVES_07C2BA, GroupTopic sonoffs) Version 2.0.4b
00:00:04 HTTP: Webserver active on sonoff1-0698 with IP address 192.168.1.3
00:00:04 MQTT: Attempting connection...
00:00:04 MQTT: Connected
00:00:04 MQTT: sonoff1/INFO = Sonoff module version 2.0.4b, Fallback DVES_07C2BA, GroupTopic sonoffs
00:00:04 MQTT: sonoff1/INFO = Webserver active for Admin on sonoff1-0698 with IP address 192.168.1.3
19:20:03 MQTT: sonoff1/1/POWER = On
19:20:05 MQTT: sonoff1/1/POWER = Off
19:24:38 MQTT: sonoff1/UPTIME = 0
19:24:38 MQTT: sonoff1/POWER = Off
19:24:38 MQTT: sonoff1/TIME = 2016-10-16T19:24:38
19:29:38 MQTT: sonoff1/UPTIME = 0
19:29:38 MQTT: sonoff1/POWER = Off
19:29:38 MQTT: sonoff1/TIME = 2016-10-16T19:29:38

Is there some sort of debugging/probing that could be done? ie send some sort of signal TO the sensor so that I can at least identify if the correct GPIO is being used? Might see if I can capture what's happening on the signal line of the temperature sensor on both the modified firmware and original firmware modules.

[arendst]

You could enable some more info with seriallog 3. It needs to use GPIO14 anyway as that is the only one available on the sonoff TH

[mihalski]

Giving it a go now.

00:00:00 APP: Project sonoff (Topic sonoff1, Fallback DVES_07C2BA, GroupTopic sonoffs) Version 2.0.4b
00:00:04 HTTP: Webserver active on sonoff1-0698 with IP address 192.168.1.3
00:00:04 MQTT: Attempting connection...
00:00:04 MQTT: Connected
00:00:04 MQTT: sonoff1/INFO = Sonoff module version 2.0.4b, Fallback DVES_07C2BA, GroupTopic sonoffs
00:00:04 MQTT: sonoff1/INFO = Webserver active for Admin on sonoff1-0698 with IP address 192.168.1.3
20:10:43 MQTT: sonoff1/1/POWER = On
20:11:06 MQTT: sonoff1/SERIALLOG = 3
20:14:00 MQTT: sonoff1/UPTIME = 0
20:14:00 MQTT: sonoff1/POWER = On
20:14:00 MQTT: sonoff1/TIME = 2016-10-16T20:14:00

Seriallog 3 doesn't appear to add anything to the console.

I also tried to snoop on the signal of the unmodified module with an ancient Saleae Logic but I wasn't able to figure out the data even with the datasheet (http://webmeteobox.ru/docs/AM2301.pdf). It's over my head for now but maybe I'll eventually decipher it.

[arendst]

For the console you use commando weblog 3

[mihalski]

I feel a little more stupid than usual.

Here's the output I get now:

21:06:34 MQTT: sonoff1/WEBLOG = 3
21:06:35 Config: Saved configuration to flash at F9 and count 90
21:09:50 MQTT: sonoff1/UPTIME = 1
21:09:50 DHT: Timeout waiting for start signal low pulse
21:09:50 MQTT: sonoff1/POWER = On
21:09:50 MQTT: sonoff1/TIME = 2016-10-16T21:09:50

I guess that's progress of sorts.

[arendst]

Michal,

I think I know what's wrong. It seems the AM2301 is not a DHT22 but based on SH1x. My driver won't work with the AM2301. I have to insert a driver for SH1x what will take a few days.

Sorry for the inconvenience.... ;-)

[mihalski]

Thank you for taking the time to look into this. I'm just glad I wasn't doing something stupid that was preventing things from working :)

If you need me to test anything let me know.

Oh, and sorry for the VERY late response!