DHT22 sensors stopped working after upgrading pimatic to v0.9.40

---

meanwhile checked position 294:19 in board.js - what is this function exactly for please:

Board.prototype._waitForAcknowledge = function() {
    return this._onAcknowledge().then((function(_this) {
      return function(_arg) {
        var args, cmd;
        cmd = _arg.cmd, args = _arg.args;
        switch (cmd) {
          case 'ERR':
 FAIL -->  throw new Error(args[0]);
            break;
          case 'ACK':
            switch (args.length) {
              case 0:
                break;
              case 1:
                return args[0];
              default:
                return args;
            }
            break;
          default:
            return assert(false);
        }
      };
    })(this));
  };

@Cybolord said in DHT22 sensors stopped working after upgrading pimatic to v0.9.40:

what is this function exactly for please

This function analyses the repsonse messages sent by Arduino (ACK and ERR messages, basically). The error is thrown as the message “ERR timeout_error\r\n” has been received from Arduino (this can traced from the stack trace posted earlier). The message is sent at https://github.com/pimatic/homeduino/blob/master/dht_command.h#L39-L41 if the DHT read command has timed out. Please double-check your homeduino device configuration, i.e. make sure the pin assignments match up with actual wiring. Check contacts between DHT sensors and the Arduino board.

@mwittig said in DHT22 sensors stopped working after upgrading pimatic to v0.9.40:

@Cybolord said in DHT22 sensors stopped working after upgrading pimatic to v0.9.40:

what is this function exactly for please

This function analyses the repsonse messages sent by Arduino (ACK and ERR messages, basically). The error is thrown as the message “ERR timeout_error\r\n” has been received from Arduino (this can traced from the stack trace posted earlier). The message is sent at https://github.com/pimatic/homeduino/blob/master/dht_command.h#L39-L41 if the DHT read command has timed out. Please double-check your homeduino device configuration, i.e. make sure the pin assignments match up with actual wiring. Check contacts between DHT sensors and the Arduino board.

thank you for the explanation!

• double checked wiring (that didn’t change btw) from Arduino board to wiring splitter box to both DHT22 sensors

conclusion and next steps:

• maybe DHT22 are both died / will change them with spare parts a.s.a.p.
• maybe Arduino Nano serial ports (PIN 11, PIN12) also died but other PINs are fully functional (433MHz stuff)?!

… otherwise I’ll have to unsolder the Arduino Nano cause its on a circuit board in a wall mounted electric cabinet… will take a while

Homeduino was updatet at my system at the same time as pimatic.
And when I understand it right your DHTs are wired with the arduino with the homeduino sketch.
Maybee there is a problem with the new homeduino version!?

My DHTs are wired direktly with the PI and works fine after the update to V0.9.40.

@V1per said in DHT22 sensors stopped working after upgrading pimatic to v0.9.40:

Homeduino was updatet at my system at the same time as pimatic.

Do you recap about which updates had been installed, specifically?

• pimatic-homeduino@0.9.11 had been released 10 months ago (!)
• pimatic-homeduino@0.9.11 is tied to homeduino@0.0.63 (that is homeduinojs) - so nothing will be update as part of package dependencies
• note beyond, homeduino@0.0.64 had been released 6 months ago, but it had not been led to a new pimatic-homeduino release due to some stability issues with the new serialport version

Considering that a timeout occurs when reading the DHT sensors on the Arduino, I think, it is more likely a software issue with the Arduino sketch if it is a software issue at all. @Cybolord did you change/update sketch on the Arduino recently, e.g. did you install the experimental sketch @TheOtherMarcus posted recently - https://forum.pimatic.org/topic/3065/homeduino-doesn-t-detect-first-single-transfer

@mwittig said in DHT22 sensors stopped working after upgrading pimatic to v0.9.40:

@Cybolord did you change/update sketch on the Arduino recently, e.g. did you install the experimental sketch

nope - it is running for round about 10-14 month with that sketch - but I have to say it again: nothing touched at all - no wiring with DHTs, no other sketch for Arduino Nano, no changes to OS (Raspbian Jessie on Pi1)… BUT: installed “unbound DNSSEC” and a few weeks later upgraded to pimatic v.0.9.40 and the DHTs are gone… I have no ideas left

so: do you recommend to upload and use a ‘more stable’ sketch to Arduino?!

once again re-building the sketch… same DHT behavior as described before but 433MHz stuff working fine

Arduino.mk Configuration:
- [AUTODETECTED]       CURRENT_OS = LINUX
- [USER]               ARDMK_DIR = /home/pi/pimatic-app/homeduino/arduino-mk
- [AUTODETECTED]       ARDUINO_DIR = /usr/share/arduino
- [AUTODETECTED]       ARDUINO_VERSION = 105
- [DEFAULT]            ARCHITECTURE =
- [DEFAULT]            VENDOR = arduino
- [DEFAULT]            ARDUINO_SKETCHBOOK = /root/sketchbook
- [BUNDLED]            AVR_TOOLS_DIR = /usr/share/arduino/hardware/tools/avr (in Arduino distribution)
- [COMPUTED]           ARDUINO_LIB_PATH = /usr/share/arduino/libraries (from ARDUINO_DIR)
- [DEFAULT]            ARDUINO_CORE_PATH = /usr/share/arduino/hardware/arduino//cores/arduino
- [COMPUTED]           ARDUINO_VAR_PATH = /usr/share/arduino/hardware/arduino//variants (from ARDUINO_DIR)
- [COMPUTED]           BOARDS_TXT = /usr/share/arduino/hardware/arduino//boards.txt (from ARDUINO_DIR)
- [USER]               USER_LIB_PATH = /home/pi/pimatic-app/homeduino/libraries
- [DEFAULT]            PRE_BUILD_HOOK = pre-build-hook.sh
- [USER]               BOARD_TAG = nano328
- [COMPUTED]           OBJDIR = build-nano328 (from BOARD_TAG)
- [DETECTED]           MONITOR_BAUDRATE = 115200  (in sketch)
- [DEFAULT]            OPTIMIZATION_LEVEL = s
- [DEFAULT]            MCU_FLAG_NAME = mmcu
- [DEFAULT]            CFLAGS_STD =
- [DEFAULT]            CXXFLAGS_STD =
- [COMPUTED]           DEVICE_PATH = /dev/ttyUSB0 (from MONITOR_PORT)
- [AUTODETECTED]       Size utility: AVR-aware for enhanced output
-
-                      ARDUINO_LIBS =
- [USER]                 SerialCommand
- [USER]                 RFControl
- [USER]                 Keypad
- [USER]                 DHTlib
- [USER]                 Keypad/utility
- [COMPUTED]           BOOTLOADER_PARENT = /usr/share/arduino/hardware/arduino//bootloaders (from ARDUINO_DIR)
- [COMPUTED]           ARDMK_VERSION = 1.3.4
- [COMPUTED]           CC_VERSION = 4.8.1 (avr-gcc)
-------------------------

Device: atmega328p

Program:   11816 bytes (36.1% Full)
(.text + .data + .bootloader)

Data:       1545 bytes (75.4% Full)
(.data + .bss + .noinit)


make reset
make[1]: Entering directory '/home/pi/pimatic-app/homeduino'
/home/pi/pimatic-app/homeduino/arduino-mk/bin/ard-reset-arduino  /dev/ttyUSB0
make[1]: Leaving directory '/home/pi/pimatic-app/homeduino'
make do_upload
make[1]: Entering directory '/home/pi/pimatic-app/homeduino'
/usr/share/arduino/hardware/tools/avr/../avrdude -q -V -D -p atmega328p -C /usr/share/arduino/hardware/tools/avr/../avrdude.conf -c arduino -b 57600 -P /dev/ttyUSB0 \
                -U flash:w:build-nano328/homeduino.hex:i

avrdude: AVR device initialized and ready to accept instructions
avrdude: Device signature = 0x1e950f
avrdude: reading input file "build-nano328/homeduino.hex"
avrdude: writing flash (11816 bytes):
avrdude: 11816 bytes of flash written

avrdude: safemode: Fuses OK (E:00, H:00, L:00)

avrdude done.  Thank you.

---- Apologies For The Confusion ----

both (!) DHT22 died at the same time indeed - unbelievable IMO and no idea why

…the new DHT22 type is working flawlessly for 96 hours now!

Thank you very much for your support!!

Kind Regards,
Paule