Agree, but then again understanding this is way easier for you as it requires in-depth ZigBee and implementation knowledge (you to know the binding’s behavior which we do not) we do not have to the extent it takes to understand what’s going on.
As you probably see in my posts I’m not keen on shooting at the dark either, of course I am looking to systematically test things, systematic to the extent possible but that is limited by my understanding of ZigBee and knowledge of the binding’s behavior. And hard enough as we also need to take all the non-binding factors such as RF hardware effects and controller firmware into the equation.
My reasoning there also is that more flexibility will also help people with educating themselves on ZigBee by just trying out things (something I myself keep telling end users on about every other aspect of OH, too).
I’m convinced enabling them and us to ‘play’ more will help pacing speed of Zigbee adoption and even OH reputation.
Ok, back to work 
Testing the illuminance sensor. There’s three channel detail settings (four when ‘advanced’)
Upfront, when I change any of it, the thing drops into unknown state and takes quite long to recover.
While in ‘unknown’, channel details disappear completely from UI but reappear when back online (irritating but ok).
I’ve set the first channel detail parameter ‘minimum reporting period’ to 20 but I see messages coming in every 5 secs. So does that mean the sensor ignores the setting ?
At least it’s a regular 5 secs report interval now, before it seems to have reported any change.
The last parameter is ‘report on charge The minimum change of the attribute value needed to trigger a device state update’ it has a default of 5000 (5000 what ? lux?) and does not allow to set less than 10. At the same time the sensor reports even minor lux changes less than 10. Does not make sense, does it.
Next irritating thing is, everything(?) seems to be duplicated. All channel details are listed twice in UI.
When I change one parameter, the other changes, too so it might also be a UI problem only, then again a typical message like below indeicates double processing, too. Apparently one active and another not-so-active channel ? Maybe that started happening when I changed channel details, maybe only when I disabled+reenabled the thing.
It is something I saw with other sensors, too. Will restart and try to reproduce and identify what’s triggering the duplicates to appear.
2021-04-23 14:23:42.790 [DEBUG] [converter.ZigBeeConverterIlluminance] - 04CF8CDF3C78B536: ZigBee attribute reports ZclAttribute [cluster=Illuminance Measurement, id=0, name=Measured Value, dataType=UNSIGNED_16_BIT_INTEGER, lastValue=20970, lastReportTime=Fri Apr 23 14:23:42 CEST 2021, implemented=false]
2021-04-23 14:23:42.790 [DEBUG] [converter.ZigBeeConverterIlluminance] - 04CF8CDF3C78B536: ZigBee attribute reports ZclAttribute [cluster=Illuminance Measurement, id=0, name=Measured Value, dataType=UNSIGNED_16_BIT_INTEGER, lastValue=20970, lastReportTime=Fri Apr 23 14:23:42 CEST 2021, implemented=false]
2021-04-23 14:23:42.792 [DEBUG] [converter.ZigBeeBaseChannelConverter] - 04CF8CDF3C78B536: Channel zigbee:device:sonoff:04cf8cdf3c78b536:04CF8CDF3C78B536_1_illuminance updated to 124.02590302177201
2021-04-23 14:23:42.792 [DEBUG] [converter.ZigBeeBaseChannelConverter] - 04CF8CDF3C78B536: Channel zigbee:device:sonoff:04cf8cdf3c78b536:04CF8CDF3C78B536_1_illuminance updated to 124.02590302177201
2021-04-23 14:23:42.793 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - null: Updating ZigBee channel state zigbee:device:sonoff:04cf8cdf3c78b536:04CF8CDF3C78B536_1_illuminance to 124.02590302177201
2021-04-23 14:23:42.794 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 04CF8CDF3C78B536: Updating ZigBee channel state zigbee:device:sonoff:04cf8cdf3c78b536:04CF8CDF3C78B536_1_illuminance to 124.02590302177201
2021-04-23 14:23:42.795 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler ZigBeeThingHandler of thing zigbee:device:sonoff:04cf8cdf3c78b536 tried updating channel 04CF8CDF3C78B536_1_illuminance although the handler was already disposed.
2021-04-23 14:23:42.796 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker reset for handler with thingUID=zigbee:device:sonoff:04cf8cdf3c78b536
2021-04-23 14:23:42.796 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler ZigBeeThingHandler tried updating the thing status although the handler was already disposed.
2021-04-23 14:23:42.797 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker cancelled task for thingUID=zigbee:device:sonoff:04cf8cdf3c78b536
2021-04-23 14:23:42.799 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker scheduled task for thingUID=zigbee:device:sonoff:04cf8cdf3c78b536 in 7230 seconds
2021-04-23 14:23:42.800 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker reset for handler with thingUID=zigbee:device:sonoff:04cf8cdf3c78b536
2021-04-23 14:23:42.802 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker cancelled task for thingUID=zigbee:device:sonoff:04cf8cdf3c78b536
2021-04-23 14:23:42.804 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker scheduled task for thingUID=zigbee:device:sonoff:04cf8cdf3c78b536 in 7230 seconds
EDIT: restart made duplicates go away. Dis+Enable did not make them reappear.
‘Report on change’ was set to 5 after restart but clicking into the frame made the display jump to 5000
Then there is a constraint that you have to enter values from 10-20000, it seems to be an UI constraint.
According to several web sources, the luminance value of that sensor can be 0-100000.
Why is it there ? Can I change it ? (another example of things I’d like to modify/“mess” with).