I was working with support to solve a problem where my sensors were not reporting the temperature. They had me remove them and re-add them, but now it does not seem to be adding them. It will say initializing, and the countdown will expire, and about 1 min later it will discover the device. It is not completely discovered as it does not fill in all the information. I have clicked save, but when I go look at the device - the current state is blank no entries at all. The data section has only endpoint and manufacture filled in, rest are blank. _ It is an Iris V1 sensor - 3320-L - and I have removed and added it several times. When I first added the sensors they started before the clock ended, now they go beyond the 60sec. Support seems to be very busy now, they don't reply for a couple of days and then send a note to close the ticket. Any thouoghts?
The Iris 3320L is a v2 Iris sensor and should be paired with the "normal" Zigbee pairing method, not Iris v1. That will probably solve your "initializing" problem. If it doesn't, I'd start to take a look at your Zigbee network, like how many total devices you have, how many are repeaters (you'll need them for more than 32 devices but should probably have them regardless), the presence of smart bulbs, or other factors that may cause problems. Good luck!
Thanks, for pointing out my mistake. I did use the normal Zigbee adding process, not the V1. As for the number of devices, I have 6 so I am under the limit. I am using this one device because it was working perfectly, and support said that the others were not setup correctly. I think that something happened to my configuration and that is why this device was the only one working. It was the first device added. All the ones afterwards, did not report battery or temp changes. They appeared to be "stuck" but would report doors open and close. So they kinda worked.
Hmm. If you aren't very close to the hub, I'd still recommend a repeater, even with 6 devices, but I can't say that it would solve this particular problem (it's just a good idea regardless). What exactly did Support say about the others "not [being] set up correctly"? As long as they were paired properly, I don't know what else could go wrong from a device perspective (certainly, an app using the device could be not doing what you want, but that's a separate issue from whether the device itself accurately communicates to/from the hub).
If you haven't tried already, maybe do a shutdown of the hub: Settings > Shutdown. Then wait at least 15 seconds or so, and unplug and plug back in either end of the power adapter to reboot it. Power cycling the Zigbee radio this way might help. If you have any not-correctly-paired devices in your "Devices" list, I'd probably remove them before this step. Then, see if you have better luck.
If you don't care to keep any Zigbee devices, you could also try resetting your Zigbee radio from Settings > Zigbee Details. I'd shutdown and restart as above after this just to be extra cautious. You can remove any Zigbee devices before (or after) doing this, but a reset won't erase them from your "Devices" list automatically. If you keep them, it should match up a newly paired Zigbee device as the old one it recognized, which may help if you have them involved in a lot of automations, but with only 6 devices, setting everything up again may not be a big deal (and would probably be a better way to ensure you aren't carrying over old problems).
So...I'm not sure, but maybe one of these ideas will help. And of course, there's also a soft or full hub reset if you feel like using a nuclear option. 
