Open mmccool opened 8 months ago
To be honest this does not annoy me as much as another zigbee "illuminance" sensor I have that actually just returns an uncalibrated brightness (as a percentage) - but was advertised as an "illuminance" sensor. But the Tempest at least makes an attempt at calibration, so...
Also for the record, here is the sensor Weatherflow is currently using. It combines ambient and UV measurements. However, they also calibrate it against other data measured nearby (to account for age, drift, etc) so it's semi-accurate (they claim with calibration, about 2%).
https://optoelectronics.liteon.com/upload/download/DS86-2015-0004/LTR-390UV_Final_%20DS_V1%201.pdf
This integration is no longer been maintained as the domain name conflicts with a new Core Integration that uses UDP to get pure local data - but is then missing a lot of the sensors you can get from the REST API. I have made a new and more up-to-date integration that replaces this one. The new integration names the sensor illuminance. Get it from here
This may seem minor and pedantic but… when the Tempest entities were renamed to Weatherflow entities for unknown reasons “illuminance” was renamed to “brightness”.
Illuminance is the technical term for light falling on a surface, which is what is being measured by the sensor, in units of lux.
Brightness is the term for a light source, and is informal, typically being a percentage. Luminance is the technical term, with units of lumens.
So brightness is the wrong name. Illuminance was correct.