Trigger a motion event using your Snapino and IFTTT.
Project showcase by Daniel Porrey
Demonstrates the Arduino capacitance meter and RC time constants project.
Did you know that a standard three-wire PC Fan can be used as a sensor?
by Daniel Porrey
Using Arduino to do a communication between sensors and Windows for IOT
Project tutorial by Christiano Faig
Yes, it's overkill, but if walking up motion-activated light-up stairs is wrong, well then I don't want to be right.
Project tutorial by Dante Roumega
The classic whack-a-mole game using LED lights and a joystick.
Project tutorial by courtlandjensen
Multi-purpose display: 4 Digits with 7 segments each. Each segment has 2 NeoPixels.
Project showcase by Nicole Jesse
Based on your description, everything seems right. Some ideas...
Take a look at the pin diagram here to double-check your wiring:
The web page for your Kuman DHT11 states it has a built in pull-up resistor. It doesn't give the size but from the photo looks to be 1K. This may be too small a value so you could try adding a 4.7K resistor between the data pin and 3.3V, just to be sure. If this does not make a difference, be sure to remove it before trying anything else.
You could also try using another GPIO such as 5 (pin 29). On GPIO 5 your code could be either (try both)
_dht = new Dht11(_pin, GpioPinDriveMode.Input);
_dht = new Dht11(_pin, GpioPinDriveMode.InputPullUp);
One last thing to try, if you have any type of Arduino such as an Uno, connect the DHT11 to this board and test it with a DHT library. This is pretty straightforward. This optional test helps to determine if the sensor is working or not. There is information in this article on using this sensor with the Uno. Here is another Hackster article showing how to do this:
I'm not exactly sure what the issue is, but you can check your VS 2017 install. Make sure you have all of the latest updates installed. In addition, using the installer, select the Individual Components tab and make sure the Windows 10 SDK's are installed for both C# and C++.
I apologize but I missed this comment. There is a new package on NuGet that corrects this issue.
Or connect with your social account:
New here? Create an account