Looks like for Sonoff coordinators, ncp-uart-nsw_6.7.9_115200.ota is the must
Fast battery draining is one hard/software thing that is most hitting Sonoff ZBB (EFRMG21) but also others EZSP coordinators and is because of miss tune radio that is not calibrated in the manufacturing posses. Best workaround is having god routers around so the sleeping end devices can using and not having the coordinator as parent.
Some bugs is fixed in EZSP 6.7.8.0 that can making it but for sonoff coordinators must running the EZSP 6.7.9.0 that is patched for tuning the RF or its very likely draining batteries in 48 hours.
EM35X and EFR32MG1X coordinators is not having the 48 hours problem if running on EZSP 6.7.8.0 than all chips is calibrated from Silabs factory and the EFR32MG2X is not and shall being made of the device manufacture (that Sonoff not have done).
Thanks for the info. Unfortunately I can’t find 6.7.9 anywhere. But I didn’t notice battery drain issues in my environment, but I have several bulbs and lamps that are routers, pretty solid mesh, so probably I was not affected by the problem.
I went for @tube0013 EFR32 gateway, but unfortunately the package got lost during the shipment and now I have to wait for another shipment, but components to assemble it are not available right now. I’ll go on ethernet instead of USB.
Can I please ask if upgrading uart firmware in sonoff zb bridge will need me to repair all devices?
I’m currently on ncp-uart-sw_6.5.5_115200 and I’m starting having problems.
I’d like to be sure about that, repairing is quite a long and boring task, and I’d like to do it only when replacing the coordinator (and I still hope that one day devices can be backed-up and restored through coordinators)
Thanks. Just got the ZigStar. I need some help with setting things up. So I removed my previous dongle, deleted the ZHA, restarted the Pi, and plugged in the new ZigStar stick. I added ZHA integration and I get two Serial Paths; one with USB and one with AMA. AMA one is not working correctly as it fails to connect in the final step. But the USB serial works. All the previously connected devices appear as well but they are still connected to the previous coordinator, not the new one. The new one is visible in the diagram as well. The previous coordinator (now unplugged) is shown as “unk device” “unk model”. How do I start a new integration or migrate all the devices to the new one?
Deleted the Zigbee.db and it allowed me start afresh. I started with two TRADFRI repeaters and three Xiaomi Leak detectors. It was so hard to pair them. My network looked like this yesterday night:
But all the three leak detectors have already gone offline by today morning. These leak detectors are not far from the coordinator. Less than 10 meters and two of them are around 5 meters away. What am I missing?
I also tried pairing a TRADFRI 5 button remote and after about 40 times I could not get it to pair. Sometimes a new device is found but the discovery process always times out. I am noting the paring is way harder with ZigStar than the sonoff stick. Is it because the ZigStar is shielded?
Most likely you’re missing WiFi… (vice-versa actually).
Look into 2.4 WiFi channel and your zigbee channels, the answer could be there - zigbee wifi coexistance.
P.S. I am running 18 zigbee networks on same spot simmultaniously, from 30 to 90 deviceas each, no dropped devices ever, even despite some networks use same zigbee channel, ask me how - I exterminated 2.4 gHz wi-fi…
It is directly plugged to a USB port, just like the previous unshielded sonoff zigbee stick. It is sitting in an area with some interference but I hoped it would handle that better than the unshielded stick.
Thanks. I will look into that as well even though I can’t switch off 2.4 gHz because some devices only use that channel. I’ll try first with an extension cable.