Indeed! Thank you very much!
Has anyone tried modifying the device handler to see if the lux readings get reported ?
I have a few of the 1st Gen ones but will buy these of it reports lux.
Looking again at what clusters the new vs old sensor report supporting:
New: inputs 0000 - basic 0001 - power config 0003 - identify 0009 - alarms 0020 - poll control 1000 - touchlink FC7C - ???? outputs 0003 - identify 0004 - groups 0006 - on/off 0008 - level control 0019 - ota bootload 1000 - touchlink Old: inputs: 0000 - basic 0001 - power config 0003 - identify 0009 - alarms 0B05 - diagnostics 1000 - touchlink outputs: 0004 - groups 0006 - on/off 0019 - ota bootload 1000 - touchlink
Looks like I was referencing a cluster list that had the endianness of the bytes flipped and mistook the
0004 groups cluster as the
0400 illum measurement cluster
We can see though that the new sensor does support the level control cluster as an output. This is most certainly used to support the new feature added by the new motion sensor to turn lights on to a specific level when motion is detected.
They must be supporting some luminance measurement, as you can define by the button when to control the lights, always (day/night) or just night.
In that case the sensor would support measurements and utilize it internally but not expose this information through any (standard) Zigbee means.
Not able to see consistent reliable behaviour with the new model, multiple resets, tried covering the lux sensor, maybe I have a dud?
What do you mean consistent? What is your problem?
I only get motion alerts, and only sometimes if I completely cover the sensor, I’ve tried using both day and night settings.
They have a sleep period of 3 minutes after they detected motion. The DH was written that way, that it will clear the motion detection after that time.
You can test them with a Tradfri bulb if you pair it directly to the bulb.
I paired my new model motion detector with ST. After this I have not been able at all to pair it with any lightbulbs, so did a scene where certain lights go on after activity has been found. This works fine, however I think the reaction time before lights go on is a little to long. Is it only made to pair with one device?
The motion sensor in the IKEA environment controls lights directly paired to it. (I think up to 10 bulbs.)
In Smartthings it goes around the world as it is cloud connected. Motion triggered, command sent to cloud, cloud processing and SmartApp use, action trigger back to Smartthings connected lights, each turns on one-by-one (popcorn effect). So you might going to feel a delay, but it shouldn’t be too long. If you see multiple seconds, then your internet connection might be too slow/overloaded for it. Might be…
Well, the delay is about 4 seconds maybe, but I wish it was faster. Ill try again later on to pair the sensor directly with the bulbs. But for some strange reason, I have not been able to so far. Before pairing it to ST, i could pair it to bulbs though. However the pairing is never as easy as it should be. Tried many times before succeding.
You shouldn’t have that long a delay
I use one in my hall that triggers a morning routine and three lights come on nearly instantly.
Maybe I have many “jumps” between several zigbee units. I´ll continue trying different ways and see if I can improve it somehow.
Is there a chance the motion sensor has the same incompatibility as the Tradfri 5 button remote with V1 hubs?
Yes. It is incompatible with the v1 Hub too. Sorry for the bad news.
Hello, 3 minutes is too many time for me, there are some way to change it for example to 30 seconds to clear the presence+
It is a device hard coded value to keep batteries last long. If you need something more instant buy a SmartSence/Smartthings motion sensor.