But you will have reset the device back to defaults, and it may not have been reconfigured. Try to reinitialise the device using the binding option for this thing.
Not sure what you mean.. How to reinitialise a zigbee device? Remember, Im using the 2.5M1 binding.
Updated the binding. reinitialised the device.. Cant say it changed anything.. Still more frequent lumiance update than ever before.
Reporting/polling configuration is not available in 2.5.0M1, you need a recent snapshot. And make sure to use HABmin, not PaperUI.
One variable you may not be accounting for Kim. Hue motion sensor actually reports luminance when ever the value changes. It is one of the things I like about it for luminance sensing, the values are updated pretty much in real time. I use one pointed straight out my kitchen window to sense the outside ambient light and adjust my intior light levels accordingly. It works… literally in real time. Sun goes behind a cloud, lights come up, sun comes back out, lights dim down. That may in fact be why there is not way to sett a polling interval. As far as battery life, my Hue motion sensor uses batteries up in about 3-4 months, which isn’t great but it is only two little AAAs and a pack of twenty is $10
Just so we get what I’m saying, when the sensor was on the other stick, it may have been situated such that the light level didn’t change often. Or you didn’t notice it changing.
It wasn’t the reporting configuration I was referring to - just the initialisation option. The binding will still set the reporting even with the older versions.
I will check what the default reporting levels are - it’s always set to no faster than one update per second, but it’s the level that really matters and I think it should be 1 lux in this case.
If it conforms to ZigBee standards, then this should be configurable, and the binding does configure it - I will check what it is configuring to though. As above, it will be 1 second max rate, and probably something like 1 or 2 hour minimum rate, and then when the value changes by some amount…
mine seems to report about every 3 or 4 minutes
yeah and so Kim 5 or 6 times a minute is pretty huts
The sensor is placed exactly the same.
I usually have the tail log open all the time. I would have noticed. I´m pretty positive something have changed.
I agree with your however, it is nice that the device update evey change. However, at lumiance change from 200.xx to 200.xy is not that kind of changes I would like to receive, to be honest. Its waste of battery, even though battery isn´t a high prize, it still calls for a frequent exchange. And thats not good.
This part doesnt seem to work. I see changes when .xx changes:
2019-07-28 12:51:23.713 [vent.ItemStateChangedEvent] - HUE_illumiance changed from 246.33 to 246.43
I´m 99.9% possitive, it didn´t do this kind of frequent changes on the old system..
yeah, at that rate, it may toast the battery in a few hours
you have a battery channel hooked up to it?
anyhow, I just checked in Habmin and no way to adjust polling
In a rules is doesnt matter. My concern is the update from the device.. This device doesnt seem to sleep at all when doing that kind of frequent updates for the lumiance.
Nothing has changed, so probably it is not being configured correctly after you reset it.
What do you mean by “the old system”?
The Rpi using the Elabs coordinator.
Now I use Odroid C2 and the EM357 coordinator.
I’ve already said that the coordinator makes NO difference. None of the firmware in the coordinator works at the application layer.
I know and understood that part, Chris.. This is why I original asked the question, cause it was the only obvious change, since I havn´t changed anything else.
I´ll delete the device and re-add it to see if it makes any changes. Hopefully..
There may be a bug in the binding and reporting may be incorrectly set - that’s possible - but it won’t have changed. This is especially true if you’ve always been using the 2.5M1 version, and probably also true of older versions.
I would have noticed for sure..
Just re-added the device.. I get an error, (dont think it´s related though), which I also saw the first time I added the device.
==> /var/log/openhab2/openhab.log <==
2019-07-28 16:17:10.724 [ERROR] [verter.ZigBeeConverterBatteryPercent] - 0017880102139D00: Error 0xffff setting server binding
==> /var/log/openhab2/events.log <==
2019-07-28 16:17:14.097 [hingStatusInfoChangedEvent] - 'zigbee:philips_sml001:f42905cb:0017880102139d00' changed from UNKNOWN to ONLINE
2019-07-28 16:17:14.300 [vent.ItemStateChangedEvent] - HUE_batteryPercent changed from NULL to 58
2019-07-28 16:17:14.309 [GroupItemStateChangedEvent] - BatteriLevel changed from 100 to 58 through HUE_batteryPercent
2019-07-28 16:17:14.312 [me.event.ThingUpdatedEvent] - Thing 'zigbee:philips_sml001:f42905cb:0017880102139d00' has been updated.
2019-07-28 16:17:14.315 [vent.ItemStateChangedEvent] - HUE_Temp changed from NULL to 25.06
2019-07-28 16:17:14.317 [vent.ItemStateChangedEvent] - HUE_illumiance changed from 225.85 to 160.46
2019-07-28 16:17:14.321 [GroupItemStateChangedEvent] - gLumiance changed from 225.85 to 160.46 through HUE_illumiance
2019-07-28 16:17:23.515 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_ember:f42905cb' has been updated.
Maybe - maybe not. Everyone says that, but not everyone does 
Do you have a logfile I could look at?