Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not getting any Temp data from Tasmota #34

Closed
citrusfizz opened this issue Feb 6, 2017 · 4 comments
Closed

Not getting any Temp data from Tasmota #34

citrusfizz opened this issue Feb 6, 2017 · 4 comments
Labels
help needed Action - Asking for help from the community

Comments

@citrusfizz
Copy link

citrusfizz commented Feb 6, 2017

Updated to Tasmota (first version and now todays version)
and i can't get any data for my Temp/Humidity sensor.
I turned on 4 debug logging and i don't see anything that says its even trying to get the data.
it is a dht22 sensor
i have configured gpio 14 for dht22 in the web interface and tried to set the other two GPIO options the same. tried am2301 as the device in the web configuration.
tried setting the module as a Sonoff TH instead of basic.
nothing give me any temp data.

not sure what else to do to get data like i did in the previous git hub project.
here is my user_config.h minus the irrelevant parts.
http://pastebin.com/xfdVWN29

thanks

here is my console output

00:00:00 Config: Loaded configuration from flash at 3F8 and count 13
00:00:00 APP: Bootcount 5
00:00:00 APP: Project sonoff Sonofftemp (Topic sonoff, Fallback DVES_1C9FD0, GroupTopic sonoffs) Version 3.9.11
00:00:00 Config: Saved configuration (1196 bytes) to flash at 3F7 and count 14
00:00:00 Wifi: Checking connection...
00:00:00 Wifi: Attempting connection...
00:00:00 Wifi: Patch issue 2186
00:00:00 Wifi: Connecting to AP1 CitrusNet in mode 11N as sonoff-8144...
00:00:01 Wifi: Checking connection...
00:00:01 Wifi: Attempting connection...
00:00:02 Wifi: Checking connection...
00:00:02 Wifi: Attempting connection...
00:00:03 Wifi: Checking connection...
00:00:03 Wifi: Attempting connection...
00:00:04 Wifi: Checking connection...
00:00:04 Wifi: Attempting connection...
00:00:05 Wifi: Checking connection...
00:00:05 Wifi: Attempting connection...
00:00:06 Wifi: Checking connection...
00:00:06 Wifi: Connected
00:00:06 mDNS: Initialized
00:00:06 HTTP: Webserver active on sonoff-8144.local with IP address 192.168.1.116
00:00:06 UPnP: Multicast (re)joined
00:00:08 UPnP: Multicast disabled
00:00:08 MQTT: Attempting connection...
00:00:09 mDNS: Query done with 0 mqtt services found
00:00:09 MQTT: Connected
00:00:09 MQTT: tele/sonoff/LWT = Online (retained)
00:00:09 MQTT: cmnd/sonoff/POWER =
00:00:09 MQTT: tele/sonoff/INFO1 = {"Module":"Sonoff Basic", "Version":"3.9.11", "FallbackTopic":"DVES_1C9FD0", "GroupTopic":"sonoffs"}
00:00:09 MQTT: tele/sonoff/INFO2 = {"WebserverMode":"Admin", "Hostname":"sonoff-8144", "IPaddress":"192.168.1.116"}
00:00:09 UPnP: Multicast (re)joined
00:00:09 RTC: (UTC) Mon Feb 06 19:58:22 2017
00:00:09 RTC: (DST) Sun Mar 26 02:00:00 2017
00:00:09 RTC: (STD) Sun Oct 29 03:00:00 2017
20:58:23 MQTT: stat/sonoff/RESULT = {"POWER":"ON"}
20:58:23 MQTT: stat/sonoff/POWER = ON
20:58:30 MQTT: tele/sonoff/STATE = {"Time":"2017-02-06T20:58:30", "Uptime":0, "POWER":"ON", "Wifi":{"AP":1, "SSID":"CitrusNet", "RSSI":60}}
20:58:36 HTTP: Handle root
20:58:37 HTTP: Handle console
20:58:41 Wifi: Checking connection...
20:58:41 Wifi: Connected
20:59:01 Wifi: Checking connection...
20:59:01 Wifi: Connected

@arendst
Copy link
Owner

arendst commented Feb 6, 2017

Only one gpio may be configured for DHT/AMxxx so that should be gpio14. Set the others to none.

See wiki > first steps regarding sensor config.

A power cycle after configuration might help.

Also try without DHT2 and use the inbuilt DHT driver (add slashes again before USE_DHT2).

@arendst arendst added the help needed Action - Asking for help from the community label Feb 6, 2017
@citrusfizz
Copy link
Author

I guess i wasn't to clear, i know that gpio14 is the one that needs to be set, i just set the others in hopes something might trigger it to work. i tried every combination with no luck. I read the wiki however there is nothing in the hardware modification. Power cycled many times, each while making a change, unlike the older firmware, this one does not even output that its trying to get data. the older firmware would say something like CRC error, or No data available. this one doesn't appear to have anything. thats why i posted my config.h and the console output.

@arendst
Copy link
Owner

arendst commented Feb 8, 2017

OK let's start off from the beginning.

sh_016

Without any sensor connected but with weblog set to 3 you should see at least the following lines after a restart:

00:00:00 Config: Loaded configuration from flash at F8 and count 117
00:00:00 APP: Bootcount 53
00:00:00 DHT: Max clock cycles 80000
00:00:00 APP: Project sonoff th1 (Topic th1, Fallback DVES_07C8FF, GroupTopic sonoffs) Version 3.9.12

The third line is from the DHT code calibrating it's timer. I do not see it in your log so apparently you did non configure any GPIO for a DHT sensor.

Look in the wiki > Sensor Configuration and retry.

Once connected OK you should see:

14:19:04 DHT: Received 01, A7, 00, D6, 7E =? 7E
14:19:04 MQTT: tele/th1/SENSOR = {"Time":"2017-02-08T14:19:04", "DHT":{"Temperature":"21.4", "Humidity":"42.3"}}

@citrusfizz
Copy link
Author

@arendst I flashed the latest 3.9.13 and sensor is working fine again. No other changes were made.
Greatful for everything you have done with this project. Cheers.

@arendst arendst closed this as completed Feb 13, 2017
ascillato added a commit that referenced this issue Jun 5, 2018
the-real-orca pushed a commit to the-real-orca/Sonoff-Tasmota that referenced this issue Jun 17, 2018
curzon01 pushed a commit to curzon01/Tasmota that referenced this issue Sep 7, 2018
arendst added a commit that referenced this issue May 2, 2020
* Prep for core 2.7

* Test release core 2.6.3...

if it appears in build

* Release zip as source for core?

* Release Core 2.7.0

removed comment behind definition since it generates on some platforms errors

* Update platformio_override_sample.ini

* Update (#34)

* Fix pin handling part 1

* Change pin handling part 2

* Change pin handling part 3

* Change pin handling part 4/4

* Fix pin handling part 4/4

* Change pin handling part 5

* Change pin handling part 6

* Update xsns_02_analog.ino

* Only advance to next palette color when fade is down

* Rework DGR channel update

* Update Changelog and Release notes

* Switch from GPIO array to Pin array

* Change ESP32 pin allocation part 1

* Change pin array names

Change pin array names to block unwanted use of direct access

* Fix ESP32 settings size

Fix ESP32 settings size as regression from yesterday

* Change ESP32 pin allocation part 2

* Fix http message time

* Create CI_github.yml

* CI on Push and Pull

* Change ESP32 pin allocation part 3

* Fix ESP32 pin allocation part 3 regression

* Rename .travis.yml to .travis.yml.off

* Update CI_github.yml

* Update README.md

* Update PULL_REQUEST_TEMPLATE.md

* Fix CI badge

Co-authored-by: Theo Arends <11044339+arendst@users.noreply.github.com>
Co-authored-by: kugelkopf123 <45996965+kugelkopf123@users.noreply.github.com>
Co-authored-by: Paul C Diem <PCDiem@FoxValley.net>
Co-authored-by: device111 <48546979+device111@users.noreply.github.com>

Co-authored-by: Theo Arends <11044339+arendst@users.noreply.github.com>
Co-authored-by: kugelkopf123 <45996965+kugelkopf123@users.noreply.github.com>
Co-authored-by: Paul C Diem <PCDiem@FoxValley.net>
Co-authored-by: device111 <48546979+device111@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help needed Action - Asking for help from the community
Projects
None yet
Development

No branches or pull requests

2 participants