I’ve just bought a new Hue Motion Sensor (without the Hue Hub), and have finally managed to pair it with Z2M (my coordinator is an SMSLight SLZB06). It is reporting battery, illuminance and temperature, but reports Occupancy as “Unknown”, and does not respond to movement immediately in front of it.
Any idea why this might be?
It’s the SML003
My previous image showed an SML001 indoor motion sensor. I’ve not gone near Z2M, not looking to complicate what works well enough for me already with ZHA [g].
I have a SML003 device, but that offers Occupancy AND Opening entities for motion detection (why not “motion”, beats me [shrug] ). I don’t know why yours under Z2M doesn’t offer “Opening” like ZHA here does. 
hello,
I have the same issue on ZHA. I think the latest Home Assistant update is the cause. We’ll see if a future update fixes it.
my topic :
In the end I managed to work around it by moving the sensor right next to my coordinator and re-pairing it, before moving it back to its final resting place. It now reports all attributes correctly.
This approach is not recommended by Zigbee experts - they advise that devices should be paired while at their intended location - but in this case I didn’t have much choice. So far it is working OK (after a couple of days)…
1 Like
I tried the same, but re-pairing didn’t solve it for me. But instead running Reconfigure on the device page did it. I can confirm that for three Philips SML001 sensors! 
3 Likes
The “Permit Join” button has an arrow next to it where you can select closer devices through which you can pair your sensor. If you simply clicked Permit Join without selecting a closer router device, your sensor will try to pair directly with the coordinator which might be too far to reliably perform the handshake.
Selecting a closer router device from the dropdown will ensure that you won’t need to move your sensor at all when pairing.
hi, thanks for the tips, it’s works for me.
That’s a great tip - thanks, I will try that next time
1 Like