All of the sensors in the Zooz 4-in-1 Multi-sensor (ZSE40 700) show data via makerAPI.
All of the sensors except for the illuminance sensor report updated information in HomeKit.
After some tests, I determined that the illuminance level showing in HomeKit is whatever the illuminance was when the device is initially picked up in HomeKit.
This is repeatable by removing the sensor from the makerAPI list, waiting a while for it to drop from HomeKit, and then adding it again. Whatever illuminance was being reported in Hubitat, will transfer to HomeKit, but the value will never change in HomeKit after that point.
Interesting note (although not reporting as a bug, but rather an interesting behavior). When I first experienced the issue with the illuminance level, I updated the driver on Hubitat to the enhanced driver, link above, but made no other changes - device name, device label, preferences, etc.).
I found that when trying to make an automation in HomeKit, I would choose the motion sensor, and it would show me lux settings. I tried choosing the illumination option, but would still see lux settings (I thought they might be swapped, but that was not the case).
I found that the issue was likely due to me changing the driver in Hubitat, but not removing it from makerAPI first, letting it drop out of HomeKit, and then re-adding it.
Since then, if I change a driver in Hubitat, I make sure to remove it from makerAPI, ensure that it has dropped from HomeKit, then re-add it to Hubitat. Probably common sense, but it caught me unawares.
All of the sensors in the Zooz 4-in-1 Multi-sensor (ZSE40 700) show data via makerAPI.
All of the sensors except for the illuminance sensor report updated information in HomeKit.
After some tests, I determined that the illuminance level showing in HomeKit is whatever the illuminance was when the device is initially picked up in HomeKit.
This is repeatable by removing the sensor from the makerAPI list, waiting a while for it to drop from HomeKit, and then adding it again. Whatever illuminance was being reported in Hubitat, will transfer to HomeKit, but the value will never change in HomeKit after that point.
I am using the Zooz enhanced driver (https://raw.githubusercontent.com/jtp10181/Hubitat/main/Drivers/zooz/zooz-zse40-multisensor.groovy), but experienced the same behavior with the Hubitat built-in driver.
Interesting note (although not reporting as a bug, but rather an interesting behavior). When I first experienced the issue with the illuminance level, I updated the driver on Hubitat to the enhanced driver, link above, but made no other changes - device name, device label, preferences, etc.).
I found that when trying to make an automation in HomeKit, I would choose the motion sensor, and it would show me lux settings. I tried choosing the illumination option, but would still see lux settings (I thought they might be swapped, but that was not the case).
I found that the issue was likely due to me changing the driver in Hubitat, but not removing it from makerAPI first, letting it drop out of HomeKit, and then re-adding it.
Since then, if I change a driver in Hubitat, I make sure to remove it from makerAPI, ensure that it has dropped from HomeKit, then re-add it to Hubitat. Probably common sense, but it caught me unawares.