I am suddenly having issues with one my Iris V2 Zigbee motion sensors that activates my closet light. It continues to drop off my network and requires a battery pull to sometimes get it back and then it may work for a few hours before Hubitat stops seeing it.. I then though it must just be a bad sensor so I tried pairing two others I had in the drawer.. After attempting to pair each one of them with the hub, they will ONLY initialize but then fail to complete the process. I have tried the other pairing options (keys) , rebooted Hubitat, reset the sensors and even shut it down for 30 minutes and plugged it back in. All of these Motion sensors are within 15 feet of the hub and I have not added anything to or modified my Hubitat in over 6 months... Zigbee channel is 20... strangely my other closet controlled light with another one of the same sensors is been working fine..
I am not sure if something in an update may be causing this or if i might have a failing hub? Is anyone else having issues with these devices recently?
Yea, I did BUT it seemed that one of the releases leading upto 2.3.9.197 made it better because I was able to get two back, which were failing before. Unfortunately, I haven't tried any with the current to verify the 'fix hasn't been broken.'
Bottom line, I did have trouble with those Iris a month ago and then I didn't. The only differences were upgrades and time.
Channel 20 has slowly acquired a reputation of being a problem. I was on channel 20 for years and then I had to move to channel 23, three or four months ago. I believe that Channel 20, when used by the C-8 and C-8PRO, has been an issue for some. C-7 and earlier didn't seem to be affected. That makes it seem like the upgraded Zigbee 3.0 chip is a central player in the effect.
This is interesting, this problem did appear a few updates ago, and I had though it was just a low battery issue so i replaced the battery and it would work for a few days then the problem appeared again.. I now became much more concerned as I am unable to pair any of the motion sensors I have in my drawer.. I probably will try and move to Chanel 23 as you suggested tonight or tomorrow and give it a day.. These devices have been rock solid for years....
23 or 25 may help, but the channel issue has been, as @csteele noted, more associated w/the C8 hubs w/the new 3.0 Zigbee radio. 25 should get you furthest away from potential Wi-Fi (2.4ghz) intereference w/Zigbee.
You could also shut down your hub, pull power 30s, plug in again, and let it boot up - that will clear the Zibee and Z-Wave radios, can help when adding devices.
I have a ton of Iris v2 motion sensors and they are solid on my C7, in the past had issues w/them on my C8 but those have subsided. I haven't had to add an Iris v2 in a while so no results there.
I have noticed that a few of my V2s would sometimes not reset normally. By that I mean that I would do the reset process (pull battery, wait 10s, hold button/insert battery and wait 2s) and the red LED is supposed light up. That wasn't working normally, it would go straight into a blue blinking LED. I've been wondering if they are just getting old...
Thank you.. Yes, I have tried shutting down and unplugging for up to 30 minutes and that has not helped…. I also have 2 unused sensors in my drawer that I tried pairing.. I will get one long red and two short green flashes then they will either flash blue or not flash at all…. That said, it is not very likely that i have one existing sensor dead and the two in my drawer are also defective…. It appears likely something in the latest releases broke these…
@csteele@danabw Passing on what I have learned so far in case you have more troubles or anyone else does:
2.3.9.197 will not pair these v2 motion sensors… I tried for hours with all ways mentioned and more. I would have to imagine there are other zigbee devices that are also affected..
I Downgrading to the oldest firmware on my cloud backup 2.3.8.140 and the first of three of these sensors paired immediately, the other two took a reboot in between pairings.
After pairing my third device I noticed problems with the first of the three that I had just paired, it would only report inactive.. Then the second device I paired which triggered my closet device would work and appear in the hubitat live log would not trigger the rule to turn on the light?? No errors were seen.. a reboot of my hub seemed to make the motion lighting rule work again. The first one paired remains in-operative. But at least the sensors are working..
So I can pretty confidently say that this is not a channel issue that appeared all of the sudden, it is something the developers messed up in the firmware…. I have 30 of these sensors so it is not as simple as me buying all new ones..
I would like to identify the update that started this problem over the last month or two and roll back to that version however, I do not know where to find the files so I need to do my research on how to find them… Any pointers are appreciated!
I have had trouble with them getting stuck on an ON state and not resetting. I would have to pull the battery, and then they would work for a while before they'd randomly do it again. I wound up replacing most of them with Third Reality ones. I haven't had that issue with the Third Reality ones, and a bonus is they take AAA batts. They are usually really cheap on black friday. After having things not work properly with the Iris ones, I found it not worth the hassel.
I think the problems you are still having are orange problems vs the blue problems you started with Meaning although different symptoms, they are problems still. If you had a spare C-7, for example, I bet the latest Platform release would pair these just fine. That would point back to the upgraded Zigbee chip, once again.
I have a spare C-7 but 6-8 weeks ago I packed up this room and nearly everything is in boxes still. My spare Iris V2 & V3 motion sensors are in a box.. which box?
EDIT:
OK, I found the box. one V2 and one V3. I'll try them on a C-8 then a C-7.
@sven I have 7 Iris v2 motions in production paired to a C8 Pro on Zigbee channel 20 and power level 8. I am running the latest Beta version 2.3.9.199. Worth mentioning I am using an L-com antenna that I had purchased when I did the antenna mod on my old C7 vs stock antennas but that shouldn't make a difference. I have had zero issues with these Iris motions or any of my Iris smart plugs.
I have a spare v2 motion and it paired immediately to my C8 Pro and motion and temp are updating.
My expectations were met. The Iris V2 timed out during pairing on my C-8 (running latest) and paired near instantly on the C-7 (running latest).
This topic started with "Anyone having issues... " and while I do, I've been in the "Not me" camp so much, it's rather interesting being on this side for a change
(The Iris V3 is completely dead apparently. Installing a fresh new battery, no LED at all. Couldn't even try pairing it.)
You mentioned you had a sensor that was just dead.. Not sure if this is worth mentioning, but the original v2 that i was having issues with still would not factory reset or re-pair with the hub, then I removed it as a device from the hub and all of the sudden the factory reset process (remove battery, hold side button) worked and it paired using the older versio0n of firmware on my c-8.. So for me it seems to be a firmware issue which got progressively more broke each update. Now I can't go back to a firmware version from say 6 months ago. I still have not researched that process.
There's an endpoint that will allow you to download the final image of a Platform release. In other words, you can download to your hub, the final 2.3.8.[157] ?? but not to any other in the 2.3.8 train. The final released image of 2.3.6 or 2.3.7 are all available. Once downloaded to your Hub, t's just in the list of images you can boot to. In other words, downloading it does not cause it to boot. And because the hub's DB and configuration are all different from years back, the correct process is to soft reset to get rid of the modern enhancements of and in the DB. Then boot to the older Platform, then restore a saved backup from that era.
There weren't any changes to the HW in the C8 during production, same 3.0 chip at the start as it has now. So I don't see any connection w/getting an early vs. later unit, unless something changed w/manuf process and we have no info/evidence of that.
I had problems in general w/Zigbee on the C8 and ended up moving almost half my Zigbee devices back to my C7, and have a bunch of Iris v2 that are roughly split between the C8 and C7, and all are running happily now on both devices. Devices either would not pair to the C8, or paired, fell off, and would not pair again.
Many report zero Zigbee issues on the C8, some have had problems, and as @csteele noted, most likely are related to the upgraded Zigbee 3.0 chip in the C8. Most people appear to be just fine w/the C8, but a subset of us have definitely had issues.
My issues started from the initial release of the C8, have been intermittent, and have continued across many hub platform versions, so I don't see evidence that a particular version of the hub platform is the problem.
I'm on the latest beta, tried to pair an Iris v2 to my C8 just now, and it did not pair, never got to the "Device found" step...
I do not have access to the beta, so I went to look for release notes, but cannot find them. I should create a support ticket on this issue unless any of the developers are monitoring the feed..
It's easy to join, and you can choose to install or not install beta releases after your join, so very flexible.
Overall, I don't see anything new/different in your experience that has not been seen/reported previously on the C8. Folows a known pattern that a subset of us have experienced.
Thank You for your help! Do you know if there is or will be a resolution to this issue as it had been working fine before they broke it, or does the c-8 pro have the same issue? Or are my only options to get an older version of the firmware or replacing all of my motion sensors??
C8-Pro is the same other than memory/CPU upgrades, so can have the same issue.
Since the issue is inconsistent (some have, most don't) it is more likely differences combinations of devices/repeaters/layout that cause the problem, but the C8 definitely has more Zigbee issues (than experienced on the C7, C5) for some of us.
To add another data point. I have not had any issues with my C8p. Currently there are about a dozen v2 sensors in daily use and they get quite a bit of action. They trigger my lighting as I move about the house.
C8 Pro
2.3.9.193
Channel: 25
Power: 12
I also have a C8 that runs my Zigbee lights (mix of Sylvania and Singled). It is running on channel 20 and I was having some issues with lights dropping off. I realized one of my old hubs had the Zigbee radio disabled in Hubitat but this does not actually turn off the radio. I enabled it and moved it to channel 15 before again disabling it. Since then the lights have been OK but it hasn't been long enough to call it fixed.
Currently my 2.4 GHz WiFi APs are on channels 1 and 6.
Meaning although different symptoms, they are problems still. If you had a spare C-7, for example, I bet the latest Platform release would pair these just fine. That would point back to the upgraded Zigbee chip, once again.
