Right after I typed that my pantry sensor stopped responding. 
I went to check the device and logs and realized that that one is still on an old C7 and the C7 had locked up - an ongoing issue with that hub. I need to finish migrating off that hub.
I thought this thread had cursed me! 
no, sorry it was me.. I read your message and got up and out of the chair, banged my shin and cursed.. you were the unfortunate recipient. I wasn't aiming at you, you just happened to be in the path. 
FYI: After downgrading to firmware 2.3.8.140 yesterday, besides one hiccup, all of my v2 motion sensors have been working and pairing perfectly..
48 hrs and still working! …. As I have not posted here in quotes some time, does Hubitat support still monitor these forms and acknowledge and log these bug reports to be addressed, or do I need to email them and open a support ticket???
HE staff is active on this community but they don't monitor all threads. Email support has been disabled and you have to open a warranty case via the support website. The best way to engage them in the community is to tag them.
@mike.maxwell handles the zigbee drivers and maybe can help. Mike know this is a long thread but Iris v2 motions have stopped pairing for @sven and @csteele in recent releases. As I mentioned above I am on the latest beta and they are pairing fine for me.
Iris V3 Motion - Data point for what it's worth to the discussion.
Iris iL07_1
Zigbee Ch 20
Hubitat C-5
on 2.3.9.197
And I have at least 6 of them running fine (last I checked). If I lost their small form factor & functionality I'd be up a creek.
And with all due respect to the positives of upgrading platforms-
I have ...this comment to make ...about my highly reliable C-5s:
"From my cold, dead hands.”
@ritchierich Thank you for tagging Mike on this post for this issue:
@csteele , @danabw : I see a newer firmware has been posted, 2.3.9.200 with this in the release notes:
"Added Zigbee hub code to respond to active endpoint and match descriptor requests coming from devices."
Can you try this on your spare hub and see if it works for pairing the v2 sensors? I would hate to update mine and not be able to re-wind back if it does not address the issue...
That 2.3.9.200 platform change didn't seem to affect my results testing Iris v2 pariing recently (I'm in the beta program, and it was in one of the beta releases for the past four or five days). That change in .200 wasn't specifically related to pairing Zigbee devices, so not surprised that it didn't change things.
I have found that a lot of issues like this are YMMV situations. It should be no harm/no foul for you to try the .200 release, and you can just roll back to 2.3.8.140 if you don't see any improvement 2.3.9.200
Thank you for testing… I don’t want to risk not being able to roll back to a stable version the easy way….
Just another data point. I just paired an Iris v2 Motion sensor to my Development C-8 hub (2.3.9.200, channel 19, power 8) with no issues whatsoever. This hub is only used for development purposes, and as such had no other Zigbee devices paired to it when I ran this test.
I also recently had an issue where I let a battery completely die on an Iris v2 Contact sensor. When I swapped the battery, the sensor went back into pairing mode (blue blinking LED). I was able to simply re-pair that sensor to my C-8 Pro hub (2.3.9.199, channel 20, power 8) with no issues. This hub has ~75 zigbee devices paired to it, mostly all Iris V2 sensors (leak, motion, and contact) and Iris v2 outlets.
Note: All of my Iris v2 devices were upgraded to their latest respective firmware just before Lowes shut down the Iris platform. Not sure if that might matter in whether or not they pair successfully?
What FW version do yours show? Mine all appear to be on:
firmwareMT: C2DF-001F-1C005310
softwareBuild: 1C005310
Like @ogiewon I purchased an Iris hub before the shutdown and upgraded all of my devices. My v2 motions are all:
No problems with any of my Iris V2 motion or contact sensors either. I’m using channel 19 and power level 16. I also had to repair one of the motion sensors recently due to a dead battery, and couldn’t get it to pair in place. I had to bring it closer to the hub to pair.
FYI: I have only had issues with the v2 motion sensors (as far as I know) my firmware is:
firmwareMT: C2DF-001F-1C005310
manufacturer: CentraLite
model: 3326-L
softwareBuild: 1C005310
Yup - exactly the same FW as mine...as I noted above, these types of issues are often YMMV which makes them that much harder to root-cause/determine a specific fix (and there may not be one).
One thing you could try, @sven, is a Zigbee channel change, @ogiewon and @Ken_Fraleigh are both on 19 and having success. You could swap you Zigbee radio to that channel and see if that makes a difference...
I would; however, does that make sense as channel 20 is working fine with the older firmware?? I live in a single-family home so it’s not like I had a neighbor moved next-door in a condo introducing a new factor.
The channel change might be more about the v2 devices being "happier" on the C8 on the other channel, rather than some new interference appeared...though that does happen. Neighbors get a new router, get bad info and set their 2.4 Wi-Fi channel to 40 mhz and transmission power to max 
(because "More is always better!!").
You'd be surprised what you see from your neighbors when you do a Wi-Fi scan...depending on your lot size/number of neaby neighbors, etc.
Download the Hubitat app
