-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
not a bug, but calibration on SI1145 #2966
Comments
Hi, Interesting. It should be zero? See this link |
Hi, @gnkarn Any news about this? |
?? Don’t know what you mean. My intention was just a watch out . I willl also report the visible and ir values, but it has been totally cloudy these days , so no new data so far . |
Hi, I was just asking if the value of 0.23 UV Index by night need to be zero or not. In the first link, they said that by night you will have few UV due to reflection from the atmosphere, so a little UV measurement could be ok ? I'm asking. So, that is my question. 0.23 UV Index by night is not Ok ? I don't know, that's why I'm asking you. |
understand , not sure about that will need more research, but my guess is that with the sensor totally covered , the reading should be zero . on the other hand , the visible and ir light sensors are working fine , but i have no way to verify the absolute readings ( calibration) this chart shows , the visible light evolution during the whole day against solar angle, during sunrise, and sunset , so both lines represent this difference . |
Hi, Thanks for the info. Nice graphs. About the calibration. Up to now Tasmota does not have any calibration routine for general sensors. Mainly, the calibration is meant to be done in your home automation system, but if you need to do some value adaptation, you can use the code of the PR #2955, that adds to Tasmota Arithmetic Commands for rules. In that case, you should read the value of the sensor on the teleperiod, scale it, and publish to mqtt. (I don't have the sensor to test, but you should check the Sensor JSON message sent on teleperiod, so as to correct the following example) Using that PR, a example can be:
Hope this helps. |
Hi. Any news on this? Or we just close this issue? Thanks. |
You can close it , I’m not able to compare the values against a “calibrated source”, as said in my opinion the values have an offset , that can be removed on the user side , probably is something that could be mentioned on the docs. Thanks |
Describe the bug
UV index calculation is offset by 0.23 points
tested on node mcu 1.0 ,
To Reproduce
using SY1145 , wait until sun down , and the remaining uv indication is still non zero .
Expected behavior
![screen shot 2018-06-10 at 19 37 01](https://user-images.githubusercontent.com/3314004/41207077-b2fbde86-6ce5-11e8-8162-9f4d487f3a56.png)
indicate zero , on total darkness when sun is down .
Screenshots
Additional context
i will check the IR, and visible tomorrow .
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: