New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wind sensor... #3418
Comments
This sensor provides two impulse per rotation. You can connect this sensor to a free GPIO and use a Counter to count the number of impulse per time - but without additonal info about your knowledge/environment and without a third-party system it will be difficult to evaluate the wind speed from the number of impulse counts. Some additonal information (from Amazon review, unfortunately only in german, use a translator if neccessary) can be found here: Summarized:
where rps = rotations per second Example:
|
Hi, Closing this issue as your questions has been addressed. Ask to reopen this issue if you need it. Thanks |
Hi, I am also interested in connecting this sensor to ESP/Tasmota. Calculation of windspeed will be done in FHEM. At the moment I can only get counts, but don't know how to get impulses per time (rps). Is it possible to do that with a rule in Tasmota and how should it look like? |
Without rules (using current dev 6.2.1.18): GPIOx 42 (Counter1)
next 30 sec. you get for example FHEM do extract of JSON (e.g. your Tasmota device called Sonoff):
now you have the readings "Time" and "COUNTER_C1" the rest you have to write by yourself (hopefully): |
Thanks for detailed suggestion, very helpful. It would be more convenient if calculations could be done in Tasmota. No need to send mqtt message every 10 to 30 seconds if wind speed is 0 (which is most of the time), faster response if wind is changing, no need checking counter overflow in FHEM... |
Thumbs up. |
Sensor is now implemented in 8.3.0 see here: |
Any idea how to connect and use a wind sensor such as:
https://www.eltako.com/fileadmin/downloads/en/_datasheets/Datasheet_WS.pdf
Thanks!
The text was updated successfully, but these errors were encountered: