Hi there,
yesterday I did an upgrade to some pimatic components and now my DHT22 sensors stopped working (via Arduino Nano) after the upgrades (see screenshot) were successfully installed (09:35pm)…
Any ideas are highly welcome 
Kind Regards,
Paule
-
DHT22 sensors stopped working after upgrading pimatic to v0.9.40
-
what says the log (/home/pi/pimatic-app/pimatic-deamon.log) ?
Is Pimatic starting without any problems? -
pimatic is starting successful inlcuding all other Homeduino functions…
the log says:
“…HomeduinoDHTSensor] error: Error getting attribute value dht22.humidity: timeout_error”
"…HomeduinoDHTSensor] error: Error getting attribute value dht22.temperature: timeout_error"
“Unhandled rejection Error: timeout_error”
“warn: Could not update variable dht22.humidity: timeout_error”
“warn: Could not update variable dht22.temperature: timeout_error”btw: what is “bluebird” indeed?
Kind Regards,
Cybolord -
@Cybolord said in DHT22 sensors stopped working after upgrading pimatic to v0.9.40:
HomeduinoDHTSensor
Can you please also check the log for other Homeduino messages appearing prior to the ones you have posted?
Bluebird is a full promise library used by pimatic as an abstraction layer for handling asynchronous functions. Promise are now part of Node.js, however, it still makes sense to use it as it provides some additional feature and claims to be faster than the native implementation as part of the runtime.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
…nothing special I guess, isn’t it?
pi@pimatic:/ $ cat /home/pi/pimatic-app/pimatic-daemon.log | grep “DHT”
21:31:02.689 [pimatic-homeduino, HomeduinoDHTSensor] error: Error getting attribute value dht23.humidity: timeout_error
21:31:02.727 [pimatic-homeduino, HomeduinoDHTSensor] error: Error getting attribute value dht23.temperature: timeout_error
21:31:11.952 [pimatic-homeduino, HomeduinoDHTSensor] error: Error getting attribute value dht22.humidity: timeout_error
21:31:11.984 [pimatic-homeduino, HomeduinoDHTSensor] error: Error getting attribute value dht22.temperature: timeout_error
21:56:02.276 [pimatic-homeduino, HomeduinoDHTSensor] error: Error getting attribute value dht22.temperature: timeout_error
21:56:02.309 [pimatic-homeduino, HomeduinoDHTSensor] error: Error getting attribute value dht22.humidity: timeout_error
21:56:02.897 [pimatic-homeduino, HomeduinoDHTSensor] error: Error getting attribute value dht23.temperature: timeout_error
21:56:02.930 [pimatic-homeduino, HomeduinoDHTSensor] error: Error getting attribute value dht23.humidity: timeout_error
22:13:20.668 [pimatic-homeduino, HomeduinoDHTSensor] error: Error getting attribute value dht22.temperature: timeout_error
22:13:20.709 [pimatic-homeduino, HomeduinoDHTSensor] error: Error getting attribute value dht22.humidity: timeout_error
22:13:22.926 [pimatic-homeduino, HomeduinoDHTSensor] error: Error getting attribute value dht23.temperature: timeout_error
22:13:22.965 [pimatic-homeduino, HomeduinoDHTSensor] error: Error getting attribute value dht23.humidity: timeout_error
01:06:38.783 [pimatic-homeduino, HomeduinoDHTSensor] error: Error getting attribute value dht22.temperature: timeout_error
01:06:38.816 [pimatic-homeduino, HomeduinoDHTSensor] error: Error getting attribute value dht22.humidity: timeout_error
01:06:40.736 [pimatic-homeduino, HomeduinoDHTSensor] error: Error getting attribute value dht23.temperature: timeout_error
01:06:40.769 [pimatic-homeduino, HomeduinoDHTSensor] error: Error getting attribute value dht23.humidity: timeout_error -
…after restarting the Raspbian OS a little bit more
19:12:59.775 [pimatic-homeduino] debug: data: "ERR timeout_error" 19:12:59.798 [pimatic-homeduino, HomeduinoDHTSensor] error: Error getting attribute value dht23.temperature: timeout_error 19:12:59.837 [pimatic-homeduino, HomeduinoDHTSensor] error: Error getting attribute value dht23.humidity: timeout_error 19:12:59.850 [pimatic] warn: Could not update variable dht23.temperature: timeout_error 19:12:59.863 [pimatic] warn: Could not update variable dht23.humidity: timeout_error Unhandled rejection Error: timeout_error at /home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/lib/board.js:294:19 at tryCatcher (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/util.js:26:23) at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/promise.js:503:31) at Promise._settlePromiseAt (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/promise.js:577:18) at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/promise.js:693:14) at Async._drainQueue (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/async.js:123:16) at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/async.js:133:10) at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/async.15:14) at processImmediate [as _immediateCallback] (timers.js:383:17) Unhandled rejection Error: timeout_error at /home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/lib/board.js:294:19 at tryCatcher (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/util.js:26:23) at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/promise.js:503:31) at Promise._settlePromiseAt (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/promise.js:577:18) at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/promise.js:693:14) at Async._drainQueue (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/async.js:123:16) at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/async.js:133:10) at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/async.15:14) at processImmediate [as _immediateCallback] (timers.js:383:17) 19:13:57.715 [pimatic-homeduino] debug: data: "ERR timeout_error" 19:13:57.737 [pimatic-homeduino] debug: got timeout_error while reading DHT sensor, retrying: 0 of 5 19:13:59.905 [pimatic-homeduino] debug: data: "ERR timeout_error" 19:13:59.926 [pimatic-homeduino] debug: got timeout_error while reading DHT sensor, retrying: 0 of 5 19:14:00.266 [pimatic-homeduino] debug: data: "ERR timeout_error" 19:14:00.287 [pimatic-homeduino] debug: got timeout_error while reading DHT sensor, retrying: 1 of 5 19:14:02.463 [pimatic-homeduino] debug: data: "ERR timeout_error" 19:14:02.487 [pimatic-homeduino] debug: got timeout_error while reading DHT sensor, retrying: 1 of 5 19:14:02.819 [pimatic-homeduino] debug: data: "ERR timeout_error" 19:14:02.840 [pimatic-homeduino] debug: got timeout_error while reading DHT sensor, retrying: 2 of 5 19:14:05.019 [pimatic-homeduino] debug: data: "ERR timeout_error" 19:14:05.040 [pimatic-homeduino] debug: got timeout_error while reading DHT sensor, retrying: 2 of 5 19:14:05.372 [pimatic-homeduino] debug: data: "ERR timeout_error" 19:14:05.396 [pimatic-homeduino] debug: got timeout_error while reading DHT sensor, retrying: 3 of 5 19:14:07.572 [pimatic-homeduino] debug: data: "ERR timeout_error" 19:14:07.593 [pimatic-homeduino] debug: got timeout_error while reading DHT sensor, retrying: 3 of 5 19:14:07.927 [pimatic-homeduino] debug: data: "ERR timeout_error" 19:14:07.952 [pimatic-homeduino] debug: got timeout_error while reading DHT sensor, retrying: 4 of 5 19:14:10.127 [pimatic-homeduino] debug: data: "ERR timeout_error" 19:14:10.147 [pimatic-homeduino] debug: got timeout_error while reading DHT sensor, retrying: 4 of 5 -
Try the following:
- Stop Pimatic
- unplug the arduino Board
- Plug in the arduino Board
- Start Pimatic
Can you Post the hole log between start and First error?
-
@schmucke said in DHT22 sensors stopped working after upgrading pimatic to v0.9.40:
Try the following:
- Stop Pimatic
- unplug the arduino Board
- Plug in the arduino Board
- Start Pimatic
Can you Post the hole log between start and First error?
in my opinion unplugging the power supply for 5min for both devices does the same, right? so the log above is “from scratch” …
19:05:43.195 [pimatic] info: Starting pimatic version 0.9.40 19:06:02.730 [pimatic, ppm] info: 2.15.12 19:06:03.077 [pimatic] info: Loading plugin: "pimatic-cron" (0.8.8) 19:06:06.511 [pimatic] info: Loading plugin: "pimatic-mobile-frontend" (0.9.11) 19:06:10.881 [pimatic] info: Loading plugin: "pimatic-ping" (0.9.5) 19:06:11.205 [pimatic] info: Loading plugin: "pimatic-sysinfo" (0.9.4) 19:06:12.345 [pimatic] info: Loading plugin: "pimatic-fritz" (0.5.6) 19:06:21.847 [pimatic] info: Loading plugin: "pimatic-orvibo" (0.0.3) 19:06:22.103 [pimatic] info: Loading plugin: "pimatic-led-light" (0.9.5) 19:06:28.390 [pimatic] info: Loading plugin: "pimatic-sunrise" (0.8.7) 19:06:28.619 [pimatic] info: Loading plugin: "pimatic-openweather" (0.9.4) 19:06:29.011 [pimatic] info: Loading plugin: "pimatic-homeduino" (0.9.11) 19:06:34.462 [pimatic] info: Loading plugin: "pimatic-iframe" (0.2.0) 19:06:34.654 [pimatic] info: Loading plugin: "pimatic-shell-execute" (0.9.11) 19:06:34.918 [pimatic] info: Loading plugin: "pimatic-wakeonlan" (0.9.4) 19:06:35.140 [pimatic] info: Loading plugin: "pimatic-pushover" (0.9.4) 19:06:35.402 [pimatic] info: Loading plugin: "pimatic-alarm" (0.2.0) 19:06:35.580 [pimatic-cron] info: the time is: Wed Jul 05 2017 19:06:35 GMT+0200 (CEST) 19:06:40.248 [pimatic-orvibo] info: Starting pimatic-orvibo plugin 19:06:40.786 [pimatic-sunrise] info: Your location is set to lat: x.9616346, long: y.7786688 19:06:46.090 [pimatic-alarm] info: Starting alarm system ... . . . 19:11:37.349 [pimatic-led-light] info: Connected to hyperion! 19:11:37.792 [pimatic-fritz] warn: Re-establishing session at http://fritz.box 19:11:39.912 [pimatic-homeduino] debug: data: "ready" 19:11:40.057 [pimatic-homeduino] info: Connected to homeduino device. 19:11:41.982 [pimatic-homeduino] debug: data: "PING" 19:11:41.999 [pimatic-homeduino] debug: data: "ACK" 19:11:42.205 [pimatic-homeduino] debug: Receiving on pin 0 19:11:43.489 [pimatic-mobile-frontend] info: packing static assets 19:11:50.554 [pimatic-mobile-frontend] info: packing static assets finished 19:11:50.616 [pimatic-mobile-frontend] info: rendering html 19:12:03.733 [pimatic-homeduino] debug: data: "ERR timeout_error" 19:12:04.464 [pimatic-homeduino] debug: got timeout_error while reading DHT sensor, retrying: 0 of 5 19:12:45.737 [pimatic-mobile-frontend] info: rendering html finished 19:12:46.011 [pimatic] info: Listening for HTTP-request on port 80... 19:12:46.166 [pimatic-homeduino] debug: data: "ERR timeout_error" -
I have the problem with my arduino nano, that the USB driver issnt load at restart the raspberry. Then i must unplug the nano (the raspberry is on) and plug it in… But, my is connected with usb…
after that i can start pimatic and it works.
-
@schmucke said in DHT22 sensors stopped working after upgrading pimatic to v0.9.40:
I have the problem with my arduino nano, that the USB driver issnt load at restart the raspberry. Then i must unplug the nano (the raspberry is on) and plug it in… But, my is connected with usb…
after that i can start pimatic and it works.
roger that and thank you - understood - BUT: all other Homeduino stuff is working flawlessly - e.g. switching my 433MHz devices and receiving open/close states from my 433MHz sensors…
did you see the log file entries like:
Unhandled rejection Error: timeout_error
at /home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/lib/board.js:294:19 -
@schmucke said in DHT22 sensors stopped working after upgrading pimatic to v0.9.40:
Try the following:
- Stop Pimatic
- unplug the arduino Board
- Plug in the arduino Board
- Start Pimatic
Can you Post the hole log between start and First error?
to make sure it could work I tried this out but with no success
…parsing the log with DEBUG active now shows:
21:14:48.107 [pimatic-homeduino] debug: data: "ERR timeout_error" Unhandled rejection (<{"error":{"code":"ECONNRESET"},"option...>, no stack trace) 21:14:48.696 [pimatic-homeduino] debug: got timeout_error while reading DHT sensor, retrying: 0 of 5 -
…coming to the point: is there kind of “downgrade path” to go back to a working constellation please?!
Thanks again.
-
@Cybolord said in DHT22 sensors stopped working after upgrading pimatic to v0.9.40:
coming to the point: is there kind of “downgrade path” to go back to a working constellation please?!
If you think pimatic v0.9.40 is causing the problem you can downgrade pimatic as follows:
sudo service pimatic stop # At this point I recommend to perform a back of config.json and the database file cd /home/pi/pimatic-app sudo npm install pimatic@0.9.39 --unsafe-perm sudo service pimatic start"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@mwittig said in DHT22 sensors stopped working after upgrading pimatic to v0.9.40:
If you think pimatic v0.9.40 is causing the problem you can downgrade pimatic as follows:
sudo service pimatic stop # At this point I recommend to perform a back of config.json and the database file cd /home/pi/pimatic-app sudo npm install pimatic@0.9.39 --unsafe-perm sudo service pimatic startThank you very much. does this also downgrade following components?
- bluebird
- pimatic-plugin-commons
-
…please let me ask again:
did you see the log file entries like - is this ‘fixable’ in board.js file:
Unhandled rejection Error: timeout_error at /home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/lib/board.js:294:19 -
Thank you very much. does this also downgrade following components?
bluebird
pimatic-plugin-commonsYes, it does.
did you see the log file entries like - is this ‘fixable’ in board.js file:
Well, I had a short look into this and I am not sure why the exception bubbles up here, but I have been looking at master which perhaps contains changes since the last release, I think the timeout is raised in the serialport board driver which appears odd to me as you said the 433 Mhz RF comms via Arduino is working fine, right?
Did you update anything else, e.g. at the OS-level?
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@mwittig said in [DHT22 sensors stopped working after upgrading pimatic
Well, I had a short look into this and I am not sure why the exception bubbles up here, but I have been looking at master which perhaps contains changes since the last release, I think the timeout is raised in the serialport board driver which appears odd to me as you said the 433 Mhz RF comms via Arduino is working fine, right?
Did you update anything else, e.g. at the OS-level?
Yes, indeed: all Homeduino 433MHz stuff is working like a charme
and Yes again: two weeks ago I compiled “unbound v1.6.2”, installed also some dependencies for that on my Pi 1 - rebooted several times and all pimatic related stuff seems to works without any issues… then a couple of days ago I decided to update pimatic to v0.9.40… restarted pimatic service/ later rebooted the Pi and straight ahead DHT22 communication was gone…
-
@mwittig said in DHT22 sensors stopped working after upgrading pimatic to v0.9.40:
followed your guide…
sudo service pimatic stop # At this point I recommend to perform a back of config.json and the database file cd /home/pi/pimatic-app sudo npm install pimatic@0.9.39 --unsafe-perm sudo service pimatic startpimatic@0.9.39 node_modules/pimatic ├── basic-auth@1.1.0 ├── cookie-parser@1.4.3 (cookie-signature@1.0.6, cookie@0.3.1) ├── cookie-session@1.2.0 (on-headers@1.0.1, debug@2.2.0, cookies@0.5.0) ├── connect-timeout@1.9.0 (ms@2.0.0, on-headers@1.0.1, on-finished@2.3.0, http-errors@1.6.1) ├── method-override@2.3.9 (methods@1.1.2, parseurl@1.3.1, vary@1.1.1, debug@2.6.8) ├── cross-spawn@5.1.0 (shebang-command@1.2.0, lru-cache@4.1.1, which@1.2.14) ├── body-parser@1.17.2 (content-type@1.0.2, bytes@2.4.0, depd@1.1.0, on-finished@2.3.0, qs@6.4.0, http-errors@1.6.1, raw-body@2.2.0, debug@2.6.7, iconv-lite@0.4.15, type-is@1.6.15) ├── logrotate-stream@0.2.5 (byt@0.1.0, log-rotate@0.2.7, optimist@0.6.1) ├── socket.io@1.7.4 (object-assign@4.1.0, socket.io-adapter@0.5.0, has-binary@0.1.7, debug@2.3.3, socket.io-parser@2.3.1, engine.io@1.8.4, socket.io-client@1.7.4) ├── jsonlint@1.6.2 (nomnom@1.8.1, JSV@4.0.2) └── request-promise@2.0.1 (bluebird@2.11.0, request@2.81.0, lodash@4.17.4) starting v0.9.39... ``09:49:41.656 2017-07-07 Friday coffee-cache: compiling coffee-script file "lib/api.coffee"...Done coffee-cache: compiling coffee-script file "lib/users.coffee"...Done coffee-cache: compiling coffee-script file "lib/devices.coffee"...Done coffee-cache: compiling coffee-script file "lib/matcher.coffee"...Done coffee-cache: compiling coffee-script file "lib/milliseconds.coffee"...Done coffee-cache: compiling coffee-script file "lib/variables.coffee"...Done coffee-cache: compiling coffee-script file "lib/variables-ast-builder.coffee"...Done coffee-cache: compiling coffee-script file "lib/actions.coffee"...Done coffee-cache: compiling coffee-script file "lib/predicates.coffee"...Done coffee-cache: compiling coffee-script file "lib/rules.coffee"...Done coffee-cache: compiling coffee-script file "lib/rules-ast-builder.coffee"...Done coffee-cache: compiling coffee-script file "lib/plugins.coffee"...Done coffee-cache: compiling coffee-script file "lib/database.coffee"...Done coffee-cache: compiling coffee-script file "lib/groups.coffee"...Done coffee-cache: compiling coffee-script file "lib/pages.coffee"...Done coffee-cache: compiling coffee-script file "lib/framework.coffee"...Done 09:52:44.333 [pimatic] info: Starting pimatic version 0.9.39 coffee-cache: compiling coffee-script file "config-schema.coffee"...Done ...and same errors :( at processImmediate [as _immediateCallback] (timers.js:383:17) 09:58:13.683 [pimatic-homeduino, HomeduinoDHTSensor] error: Error getting attribute value dht23.temperature: timeout_error 09:58:13.716 [pimatic-homeduino, HomeduinoDHTSensor] error: Error getting attribute value dht23.humidity: timeout_error 09:58:13.728 [pimatic] warn: Could not update variable dht23.temperature: timeout_error 09:58:13.739 [pimatic] warn: Could not update variable dht23.humidity: timeout_error Unhandled rejection Error: timeout_error at /home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/lib/board.js:294:19 at tryCatcher (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/util.js:26:23) at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/promise.js:503:31) at Promise._settlePromiseAt (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/promise.js:577:18) at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/promise.js:693:14) at Async._drainQueue (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/async.js:123:16) at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/async.js:133:10) at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/async.js:15:14) at processImmediate [as _immediateCallback] (timers.js:383:17) Unhandled rejection Error: timeout_error at /home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/lib/board.js:294:19 at tryCatcher (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/util.js:26:23) at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/promise.js:503:31) at Promise._settlePromiseAt (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/promise.js:577:18) at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/promise.js:693:14) at Async._drainQueue (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/async.js:123:16) at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/async.js:133:10) at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/bluebird/js/main/async.js:15:14) at processImmediate [as _immediateCallback] (timers.js:383:17) Unhandled rejection timeout -
@Cybolord That’s what I expected, basically. The error does not appear to be related to pimatic v0.9.40 upgrade.
May be it is hardware problem. Do you have a spare DHT sensor to test with? Another which can be done is to connect the Arduino to a serial console to check whether or not the messages contain the DHT message probes.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@mwittig said in DHT22 sensors stopped working after upgrading pimatic to v0.9.40:
May be it is hardware problem. Do you have a spare DHT sensor to test with?
thank you again… I’ve two more to change existing and do some tests but actually both of them stopped working at the same time… this is strange, isn’t it?!
so what about the …/homeduino plugin path - I’ve got a file system backup - does it make sense to restore to this point only?
I am sorry - no idea how to do this:
Another which can be done is to connect the Arduino to a serial console to check whether or not the messages contain the DHT message probes.
