Zigbee devices (bulbs, sensors, switches, outlets) randomly failing beginning March 2016

I wonder that too, if only because we know they were making some changes to the zigbee platform in March. It’s not just the join issue because then we wouldn’t be getting temperature reports from the motion sensors while the motion was getting ignored. So it could be a fault in the implementation of the rejoin, or could be some other unintended consequence. Or it could just be a coincidence. :stuck_out_tongue_winking_eye:

1 Like

You know me, I generally prefer zigbee devices except for fixed location Devices like light switches and door locks and window covering controls where I worry about Wi-Fi interference. If nothing else, I like having more hops to work with. :wink: But that’s just me.

Zigbee is a good protocol. Zwave is a good protocol. Bluetooth is a good protocol. They all have their uses.

There are some SmartThings – related issues that only affect zwave, like the strange Sonos problem where adding two or three Sonos devices can crash Your zwave network.

So it’s not that one protocol is safe and another is not. Weird stuff happens. :sunglasses:

1 Like

Do we think this issue is primarily constrained to Hub V2?

Hub V1 firmware (and hardware) is quite different and, frankly, I haven’t had any new ZigBee specific problems.

Good question!

I don’t know, I only have v2.


Are you on a v1 or v2 hub?

Does this sound familiar? This is from the day the Poltergeist started messing with my v2 hub.

1 Like

I haven’t had any dropped devices since last October (see above thread). Occasionally I am running into ‘stuck’ devices when I reboot my hub. However, I noticed that they get stuck and require power cycling when the device changes state while the hub is rebooting so I only reboot the hub when I am alone in the house and I am not walking around for 30 minutes. This practice has reduced (if not eliminated) the stuck state. Maybe is pure superstition, but it has worked for me for 6 months.

@JDRoberts the absence of issue with my devices doesn’t negate your problems. I’ve been there. Could it be that the issues people have is regional only on specific servers?

1 Like

I continue to have zigbee devices freeze every day. Different ones, some farther from the hub, some quite close. These are primarily motion sensors, but also contact sensors. They will freeze in either state, active or inactive. Popping the battery, sometimes twice, brings them back to life.

I never saw this with V1 hub, and unfortunately I migrated to V2 right before everything went really bad.

1 Like

That’s an interesting observation. I could certainly see that happening.

That’s not what I’m seeing with these new problems, however. This just happens randomly at any time, nothing to do with the hub going on or off power.

As for regions being an issue, it certainly could be, it has been with some cloud problems in the past.

I understand. I shared my observation for @johnconstantelo maybe he can avoid some of his problems.

1 Like

This has gotten so bad, all around, so many failures every day, that it is certainly starting to look like pulling the plug is the way to go. It would be nice if this system worked, but the inability of this team to put out any new software without totally breaking it has worn really old. Every single day…


I’m on V2.

I’ve had problems with two particular motion sensors. They’ve been doing this same thing. Normally popping the battery for a couple of minutes brings them back.

I’ve written it off to their location. They are the farthest away from my hub with a lot in between them. All of my zigbee devices are battery operated, therefore no repeaters.

I’m thinking about getting a zigbee repeater too see if it improves, but after reading all of if this I doubt it will help.

I’ve been having more trouble with two that are the furthest from the hub. I just added a repeater; will see if it helps or not.

Let me know. What’s weird is these two are iris motion sensors. They are two of three motion sensors I have in my master bathroom. I have never had a problem with the third one, and it’s in the shower.

I wonder if a zigbee mesh rebuild would help with this? It would at least help remove the devices from the list of suspects.

1 Like

The only lights-coming-on experience we had is when we hit Disarm in SHM. This week it started turning on six of our Philips Hue lights, regardless of whether the disarm came from a routine, or manually. No, there was no routine or trigger for this…they just started doing it.

I finally gave up and followed advice and disabled all SHM stuff.

But at the same time, we also ran into issues with Cree bulbs, two in particular that are close to each other. These have been very reliable.

Amazon’s Echo would see one as offline, but ST showed it online and controllable. But it wouldn’t control the light. I followed the “rename the device” work around, and it worked I can access the light. But the renaming actually dropped the device from all of its SmartApps, which isn’t supposed to happen.

All of this makes me think the issue is the App. I harp on this, but it just reminds me of older applications and transaction support, lack of rollback, and data left in an incomplete state. I don’t know, but the one thing I had before all this is my lights worked. Now, that’s going wonky.

I don’t remember if it was confirmed or not, but based on my personal experience, v2 is weaker than v1. I didn’t have any repeaters with v1 and things worked well. Since v2 I had to put repeaters everywhere.

1 Like

What repeaters are you using?

I really love the Iris outlets. They repeat both zigbee and zwave