[Feature] Reporting TS0601 illumination the same way as TS0222 illumination
Avamander opened this issue · 5 comments
Problem description
I have two devices, TS0601 (motion sensor with illumination sensor) and TS0222 (temperature, illumination and humidity sensor with display). Unfortunately only the TS0222 lux reading appears in HomeKit.
The TS0601 reports illuminance (Raw measured illuminance) and it's displayed in lux, but not illuminance_lux. As opposed to the TS0222 which reports both (but illuminance is actually a raw value without an unit).
Suggested solution
That illuminance would be considered illuminance_lux in the case of sensors that just have a single illuminance value.
Alternative solutions
No response
Additional context / information
No response
You can provide a custom exposes information for this device in the plugin configuration as a workaround.
On the other hand, if it really reports the value in lux then the exposes information in koenkk/zigbee-herdsman-converters should probably be corrected.
On the other hand, if it really reports the value in lux then the exposes information in koenkk/zigbee-herdsman-converters should probably be corrected.
I did consider that approach at first, but maybe it's easier to consider unit-ful illuminance equivalent to the illuminance_lux one. Z2M itself shows the unit, so it's known not "raw" as it is in the second case with two values.
If it really should expose illuminance_lux instead of illuminance in luxes, I can open an issue there.
It appears that this issue did not have an update in quite some time. Please check if you can provide any additional information to help resolve this issue. If there isn't any activity in the next two weeks, this issue will be closed automatically. Thank you for your contributions!
I have the same issue. How would I implement the workaround of custom exposes? Is this in the homebridge-z2m config? Thanks
It appears that this issue did not have an update in quite some time. Please check if you can provide any additional information to help resolve this issue. If there isn't any activity in the next two weeks, this issue will be closed automatically. Thank you for your contributions!