I've also tested my DHT22 sensor on the RPI4B with a simple python script and it seems to be connected and outputting correctly
Can anyone help point to me towards where I've cooked it?
In my mind it could be an issue of BCM2385 vs BCM2711 for the later rpi4b versions but honestly at this point I'm unsure
EDIT: I'm going to try and connect up my SCD30 to see if that interfaces with node-red
EDIT2: This is my flow, with the only two edits being in timestamp (regular intervals) and in debug node to make the output include the complete msg object
That should eliminate incorrect wiring (wrong GPIO and/or power)... but good to doublecheck.
The fact that it is seeing "0.00" for both reading tells me it is simply not connecting... I honestly don't know if that node would pass on the more traditional NAN error, or if "0.00" is the equivalent.
Are you running Node-Red with the correct root permissions? as indicated in the directions. However, I will admit to a lack of NR knowledge on how to confirm that ... all I know it that I must be, as my DHT sensor works fine with same node/settings, although I am using GPIO 26.
If the Dht is hooked up wrong you will get 00.00 on the output not NaN. The single hardest thing is figuring out which pin to hook up to.
I use node-red-contrib-dht-sensor and the node does work. I use the BCM GPIO pin numbering scheme. Find a good website that lists out all the different pin numbering schemes and sort out which pin you need to hook to. The chip is pretty robust I've hooked them up backwards and they survived. I suspect you have the data on the wrong pin and it may take some research to get it right but once you do it should work. There are so many pin numbering schemes it's tough to slog through them.
[EDIT]
I'm sure you realize you are way behind on Node Red version. My DHT ran fine on that version but sooner or later consider an upgrade to new version.
... all I know it that I must be, as my DHT sensor works fine with same node/settings, although I am using GPIO 26.
