And I do think you are coming to a wrong conclusion that update 150 or whatever is causing your issue
Hi @neonturbo, if you refer to me about my Zigbee network problem, it is importan to clarify that I never implied this. My problem has been appearing since maybe two or three upgrades ago.
And yes, I assumed that my problem was somehow common, therefore I also assumed it was already taken care of. Something that now I understand is not the case.
Usually the errors are meaningful and tell you why the device is failing to pair, and what next steps you may need to take. That is true for both Z-Wave and Zigbee. If you are having hard time deciphering the error message, I would share those here is the community as others may be able to help. Also, sharing the hub model up front is essential too, as different Hubitat models may have specific issues. For example older models like C4 and C5 are less capable to deal with increased load.
I never used that word, and I am Hubitat staff member 
Avoiding protocols may not be the best thing to do. It hampers your ability to automate your home. All protocols can have virtually the same problems without minimal maintenance effort. The best approach is to stick to reputable devices and to avoid those with known reliability issues. The community is a great resource to identify those devices to enjoy the best smart home experience where Zigbee, Z-Wave, Matter and network connected devices work together with no problems. You'd be surprised how many users enjoy the experience of mixing protocols without any problems at all.
There was a time... when I was adding a couple of devices in the same session, and one of them was a certain power reporting outlet....and I WAS having problems pairing...and after some investigation I DID find the Zigbee mesh offline. I did suspect the power reporting outlet, maybe naively due to verbosity in reporting until I changed the setting.
I had to ponder all the reasons these pairings were failing and go LOOK at the Zigbee mesh status...(Edit: wait a second, did I really think to go look or was there a little red warning notice that popped up like where the Update notices post??) and was shocked to see it offline cause I had NEVER seen that before or thought it could happen w/o overt selection. Granted there MAY have been some issues in HE that got fixed around this time...
But the point is, I "get" the OPs suggestion that having the Zigbee Status on the same page where you are pairing MIGHT be a useful thing to allow immediately seeing that some device you are trying to pair is raining hell on your mesh. IF indeed that is a reasonable suggestion that anything COULD. I believe I saw it could...but I could be wrong (please God, not again today)
OP is definitely correct that allowing pairing to happen at all if there's a catastrophic Zigbee problem is not a good idea.
My post was not directed at you. It was for someone else in this thread who repeatedly insists Hubitat has made a change that broke something, when that is not the case.
Underlining that, and totally discounting the effort to build it,
it would be great to see a Hubitat Seal-of-Approval labeling despite the alienation it might cause certain vendors that persist in creating junk devices.
Or, at least "a master list" somewhere that we all maintain some scoring on.
Given my recent batting average, this thread is sure to get closed now. 
Isn't the supported device list a de-facto list of devices that are endorsed by staff?
Look at the Schlage locks, they removed those from the supported device list due to many reported issues. They also have not added Aqara devices, which were shown to cause issues when tested by staff. I am sure there are others as well that haven't made that list as well. (Tuya devices?)
Fair enough. I honestly do forget to go look at that and I do think there is a gap between devices that are supported and devices the community is so pleased to have available that they're forgiving of minor misgivings
That’s a sure-fire way to get something done.
Nothing wrong with zigbee on my C7 running recent hub firmwares.
I believe one issue is; To have a reliable seal of approval Hubitat would have to have the mfg's buy in. Else the mfg could change something in the firmware and unintentionally cause issues, making such a list useless.
Hi there.
I'm not trying to be controversial here but I'm wondering about this.
I'm using CH20 and not seeing any issues.
This is on a C8 with 80 zigbee devices.
Is there something I'm missing or is it specific devices.
Like I say, I'm just wondering.
It's nothing concrete, but it has helped a lot of people lately. It's possible I guess 20 is getting more saturated. Could also be an issue with the 3.0 radio and channel 20. Either way a lot of people solved the issue by going to 25... (I simply switched my hue bridge from 25 to 20). Some believe it's caused by mars being in retrograde..
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
