Core: Inconsistent luminance unit of measurement

Created on 16 Mar 2019  路  5Comments  路  Source: home-assistant/core

Home Assistant release with the issue:
0.89.1

Component/platform:
miflora
zwave

Description of problem:
I wanted to create a min/max sensor from two sources of luminance. Unfortunately, this did not work because the two sensors did not match units. The miflora component used lx while the zwave sensor (through zwave) used lux.

Edit:
Updated to from zha to zwave

stale

Most helpful comment

The integration that uses lux should be updated to use lx - these two are just aliases for the same thing and some time ago it was decided we should use lx consistently.

However, lumen and lx describe different things @andriej. lx is a unit for illuminance (amount of light that falls on a given surface) while lumen is a unit for luminous flux (amount of light emitted in all directions).

All 5 comments

Isn't that because those sensors manufacturers use different units inside devices?
I agree it would be nice to convert them to one-chosen, but I also have Xiaomi motion sensors wich report lux while other xiaomi (zigbee) devices report lumens.

The integration that uses lux should be updated to use lx - these two are just aliases for the same thing and some time ago it was decided we should use lx consistently.

However, lumen and lx describe different things @andriej. lx is a unit for illuminance (amount of light that falls on a given surface) while lumen is a unit for luminous flux (amount of light emitted in all directions).

ZHA is already using lx as the unit of measure. Is there another issue w/ ZHA specifically here?

My mistake. After looking at my configuration, the sensor was not zigbee but rather zwave.
More specifically, aeotec zw100 multisensor 6

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 馃憤
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Was this page helpful?
0 / 5 - 0 ratings