So which zigbee repeaters are working for you guys? I’ve about determined it’s the Iris 3210s that are causing the issues. I’ve taken both of mine out to test.
All nine of mine have been working perfectly even with the updates and reboots. I actually had better luck with keeping them connected since I did a soft reset once all of them were working. The Samsung plugs are my favorites, followed by Sylvania plugs which are nicer looking and half the price, but don’t appear to be able to repeat for as many devices.
What do you consider updates, reboots and soft resets? Hubitat updates?
Yes, the HE updates.
I did a backup of the database and then a soft reset followed by a restore from the backup. It cleans up the database from what I understand. The switches have been solid since.
Edit: i almost forgot that I also moved my Samsung plugs to more central locations, and put the peanuts on the outer areas so they would have less traffic to route.
Just an update. All 9 of these are working reliably since prior to the release of 2.1.5. I didn’t think they would ever be stable. The last thing I did was make sure that all of them were connected and working on first press, then I backed up my hub, did a soft reset, and restored my backup. Don’t know if that’s what helped, but I haven’t had any issues since.
I’m still on 2.1.4. My issues were solved when I removed my two 3210-L zigbee devices (just left the Zwave repeater function). The only zigbee repeater I have now is one of these Hubitat with Homemade Temperature, Humidity, Pressure and Light sensor
Guess I should update to 2.1.5 and try adding the 3210’s back.
Any changes in this driver for 2.1.6.118 @mike.maxwell?
Both of these were single press events. Light came on then right off. Living room one was holding and releasing once and it called my routine twice.
No changes.
I have nine of these and they are all behaving normally.
I have a number of these devices, and I noticed that at least of few of these have terrible battery life. Have you run into this?
No. All on original batteries. I have previously noticed when I was on SmartThings that a weak mesh would kill the batteries. I believe that end devices cut back their output when the RSSI is strong. Probably why you have only noticed with a few.
I talk about the magic reboot sequence (34, 14, 23) in a post on my blogspot, rickalm
All of your conversation got me to this combination. It solved my issues, thanks
It’s not correct. 3&4 is for zll pairing. It turns red because it fails to pair, otherwise it would turn green. 1&4 resets and 2&3 pairs. The info for this I found on the European site, where they also advertise availability of zigbee 3.0 bulbs that are compatible with the Hue bridge 
2 Likes
Thanks Ken, I updated my blog post to reflect that.
1 Like
Feel free to link, I was blocked from doing so
These connect with no issues to new empty Hub. I’m connecting all of my end devices to the new hub and will update with my results, but so far it looks promising.
One day in with 9 of the Lightify 4-button paired, 10 Sylvania 2-Button dimmers, 4 Hue dimmers, 2 Iris contact, 3 Sylvania motion sensors, and 3 Samsung plugs. All switches working perfectly on first press, no drops.
2 days in and still not a single dropped button press.
1 Like
Taking my Iris 3210-L out of zigbee repeater modes solved my issues. I assume their implementation is flawed or something between the lightify switch and hubitat or lightify switch and Iris.
2 Likes
I can't seem to get these things to work right. They pair but they don't work on button presses. I can spam a button then it will show up in the log or I can hold which seems to be more responsive. I've tried over a dozen resets and configures. I tried deleting from the system in re-adding multiple times and still the same end result.
dev:10252019-12-16 04:55:36.615 pm infoBed Button button 1 was pushed
dev:10252019-12-16 04:55:35.274 pm infoskipped cluster:0003, descMap:[raw:catchall: 0104 0003 01 01 0040 00 21F6 01 00 0000 40 00 0200, profileId:0104, clusterId:0003, clusterInt:3, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:21F6, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:40, direction:00, data:[02, 00]]
dev:10252019-12-16 04:55:34.516 pm infoskipped cluster:0000, descMap:[raw:catchall: 0104 0000 01 01 0040 00 21F6 00 00 0000 00 00 0000, profileId:0104, clusterId:0000, clusterInt:0, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:21F6, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 00]]
dev:10252019-12-16 04:55:32.695 pm infoBed Button button 4 was held
dev:10252019-12-16 04:55:31.370 pm infoBed Button button 3 was held
dev:10252019-12-16 04:55:28.710 pm infoBed Button button 2 was held
dev:10252019-12-16 04:55:27.223 pm infoBed Button button 1 was held
What else am I missing?
