This is good, 
Now I can be your Xbee padawan when mine arrives. Get to work, dude, and go through all the pain so I can cruise through it w/your sage advice. 
1 Like
I think you may has perceived the ripples in the force incorrectly oh Jedi Master.
It is I that come seeking enlightenment in the ways of the Xbee and it’s mysterious Midi-chlorians.
1 Like
I just went through the exercise of setting up XCTU and my Xstick on another Windows machine since I haven't done it in years.. I got it working and made some notes I can share (probably best done on another thread).
Since it had already been set up once before (and likely some of the internal configuration of the stick was not repeated in this latest exercise) it may not be a 100% complete set up guide, but it might help, since the XCTU interface is a tad eccentric.
4 Likes
You're the best, thanks, Tony!! Since my stick isn't supposed to arrive until around May 5th, I'm still in holding pattern. @Mayhem does have his, so up to you guys if you want to take a shot at it w/his stick and see if anything explodes. 
2 Likes
Ok Gents. I’ll set me self up for a busy bank holiday Monday of tweaking and twiddling. 
1 Like
Not fun.
They are working hard on it, been slipping out beta releases over the weekend working on addressing it.
Wish I could say "Twins" but mine won't be here until late this week, if things go well.
It is coming via the Royal Mail, so at least I'll finally get to meet a knight in shining armor.
Her Majesties Royal Mail or Rather HIs Majesty as of next weekend. Yep another day off used to be the gold standard of mail delivery but like so many other businesses they now hide a crap service behind the aftermath of Covid.
Hope it makes it.... If not let me know I'll UPS mine over as I expect you will make more use of it than me
1 Like
I agree. I’m trouble shooting a neighbors setup which is have a multitude of issues and I think it corresponds go this. I’m going to check. I have a similar house and set up and am not having these issues. Poor guy, I talked him into this platform and now he probably lost trust in me. .
And the saga continues...
At what point do we call this a failed product rollout? I've been very loyal to this platform since the C5 was released, but this ■■■■ is working on my last nerve. Home automation should not require me to keep daily tabs on its operation. I might as well replace all of this with X10 and analog motion-sensing lights at this point. It would be more reliable.
3 Likes
Mine shows the online/offline messages too 3 to 5x a day but doesn't seem to ever had any effect at any on my devices thus far. Is it actually effecting your devices?
It would be a very big stretch to call it a failed product when most people aren't having any issues.
Yes. I have to reset a lot of my battery powered zigbee devices near daily. My alarm keypad stops reporting and several of my smart zigbee switches will no longer report their status to the hub even though they do accept commands. You can imagine that if the device does not report its status, my automation based on their status no longer work. It's incredibly frustrating.
You might have something else going on.
Several 8 second zigbee outages a day mostly don't affect me.
Once, though I think one of them coincided with a gate function and it stuck open.
Usually, I would agree with the "something else going on," but none of this happened until the C8 upgrade. So it is clearly tied to the Zigbee radio in the C8. There are also a bunch of other people reporting that the Zigbee radio resets are causing them issues. It's not just me.
Of course it is. You wonder what's causing it though. They're probably scrambling around try to fix the zigbee stuff in the C8. Maybe the 8 second resets are an attempt to fix something else. Who knows.
This possibly will not be helpfull, but who knows. I will share my recent "fight" with C-8 and MOES light switches. I sold a lot of previous hardware, including C-4 gateway, aqara stuff, and other touch-switches, and started to build system from scratch, based on C-8, and new, newly tested devices, including mentioned above light switches from MOES.
I successfully tested mentioned switches (with specific LED bulb), and after tests I started to "plant" them in final locations. Then I started them to use and... WTF? I was loosing zigbee communication after 15 minutes with every device. Zigbee channel switching did not helped, rebuild network was helping for next 15 minutes. And no erorrs in logs, no "zigbee radio is off" messages, just zigbee network was going to be total dead, without any traces.
So I downloaded almost empty backup, and then noticed problem with joining devices. Then I reminded, that I changed hub orientation to normal / horizontal, so I reverted orientation of hub from horizontal to vertical again, and that helped for range issue (devices located on floor below hub did not want to pair at all). But the network was still unstable. So I attempted to include device one by one, and observe network. In meanwhile, I planted test BlitzWolf BW-SS7 as range extender one floor below C-8, and after that I got perfect range, no more issues with "freezing" end devices (I will use more powered switches to stabilize mesh later).
Additional note: I have water underfloor heating insulated with styrofoam and aluminum foil screen. That foil screen could be the reason of bad coverage on floor below hub location. And that could explain why hub orientation change and addition of BlitzWolf BW-SS7 as range extender stabilized the network in that strong way in my case.
After some time, I noticed, that joined specific switch was causing issues (previously tested, and previously working fine). Only difference was... different LED bulbs. So I replaced almost no-name LED bulbs (Chinese made, marketed by local custom brand) by OSRAM made LED bulbs and... all issues related with that switch gone. Including issues with light flickering when two gangs were enabled (no flickering with one gang active) or slight glow of the bulb connected to gang1, when gang2 was turned on without any devices connected. All of the above problems, including network ones disappeared after changing of bulbs.
In summary: I suspect, that in current state code of zigbee 3.0 is not mature enough to handle noise caused by broken device, or device which is behaving badly due to interferences caused by things connected to them (in my base "bad" bulbs).
4 Likes
Hard to say the extent of this particular issue. How many people are actually having ZigBee On/Off events and don't even know it because they haven't checked their event logs? Maybe they have been lucky that it didn't happen at a precise time when rules were firing or maybe they have just had a few random unexplained trigger failures.
That being said, I have actually gone quite a while (since 04/17/23) without it happening, except once right after a reboot on 04/22/23. I had been seeing these events pretty much daily before then.
