search

arendst / Tasmota

Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full documentation at
https://tasmota.github.io/docs
GNU General Public License v3.0
22.26k stars 4.81k forks source link

Sensor MHZ19B after deep sleep does not have time to initialize #7290

Closed dejavy closed 4 years ago

dejavy commented 4 years ago

This CO2 sensor "MHZ19B" needs some time after switching on, so that it correctly measures the readings.

13:22:40 MQT: tele/MHZ19B/INFO3 = {"RestartReason":"Power on"} 13:22:44 MQT: tele/MHZ19B/SENSOR = {"Time":"2019-12-22T13:22:44","ANALOG":{"A0":929},"BH1750":{"Illuminance":167},"MHZ19B":{"Model":"","CarbonDioxide":0,"Temperature":0.0},"TempUnit":"C"}

It can be seen that the sensor "BH1750" immediately has the correct reading, and "MHZ19B" takes time (about 1-2 minutes)

13:23:04 MQT: tele/MHZ19B/SENSOR = {"Time":"2019-12-22T13:23:04","ANALOG":{"A0":929},"BH1750":{"Illuminance":168},"MHZ19B":{"Model":"B","CarbonDioxide":410,"Temperature":22.0},"TempUnit":"C"}

13:23:54 MQT: tele/MHZ19B/SENSOR = {"Time":"2019-12-22T13:23:54","ANALOG":{"A0":929},"BH1750":{"Illuminance":159},"MHZ19B":{"Model":"B","CarbonDioxide":2184,"Temperature":23.0},"TempUnit":"C"}

The problem is that when using the "deep sleep" mode, after waking up, he takes only one measurement and it has a zero value. All sensors have time to turn on, and have the correct readings, but this "MHZ19B" is not. Changes in the parameter "teleperiod" does not change the situation.

13:19:32 MQT: tele/MHZ19B/INFO1 = {"Module":"Generic","Version":"7.1.2(tasmota)","FallbackTopic":"cmnd/DVES_249567_fb/","GroupTopic":"cmnd/tasmotas/"} 13:19:32 MQT: tele/MHZ19B/INFO2 = {"WebServerMode":"Admin","Hostname":"MHZ19B-5479"} 13:19:32 MQT: tele/MHZ19B/INFO3 = {"RestartReason":"Power on"} 13:19:37 MQT: tele/MHZ19B/SENSOR = {"Time":"2019-12-22T13:19:37","ANALOG":{"A0":930},"BH1750":{"Illuminance":4},"MHZ19B":{"Model":"","CarbonDioxide":0,"Temperature":0.0},"TempUnit":"C"} 13:19:37 DSL: Reset wrong settings wakeup: 0, slip 0 13:19:37 MQT: stat/MHZ19B/RESULT = {"DeepSleep":{"Time":"2019-12-22T13:20:00","Epoch":1577017200}}

I understand that this can be solved somehow by the "Rules". To postpone the survey for a while, wait until the sensor wakes up. But I am at a loss for understanding the "rules"

close-issue-app[bot] commented 4 years ago

This issue has been automatically closed because the issue template is missing or incomplete. Filling the template is required so standard questions don't need to be asked again each time. Our ability to provide assistance is greatly hampered if few minutes are not taken to complete the issue template with the requested information. The details requested potentially affect which options to pursue. The small amount of time you will spend completing the template will also help the volunteers, providing assistance to you, to reduce the time required to help you. Please, could you be so kind on completing the issue template in order to have more information so as to properly help you? Thank you for taking the time to report, hopefully it can be resolved soon. Support Information Wiki for more information. Chat for more user experience. Community for forum. Code of Conduct Contributing Guideline and Policy