Fortunately, for me the downgrade was super easy. I just followed the instructions given here: ZigStar - ZigBee Coordinators and Routers - #427 by mercenaruss .
And even though ModeMCU Flasher states that it doesn’t work on M1 chips - it did work for me (though with M3). it took me like 15 minutes.
As far as I can see the issue with these controllers, and Zigbee in general, is that there are so many variables. # of devices, makes of devices, Zigbee network congestion, interference and signal strength, and many others.
With all that we have precious few diagnostic tools available as end users - just a central log and signal strength info generally.
So when it’s good it’s good, and when it’s bad it’s a nightmare.
I am certainly not gloating (it was very unreliable for me about a month ago), and I wish you all well.
1 Like
I have installed UZG-01 in my new house because I wanted a really good and stable controller.
I have just added one zigbee device and it worked for a few days, but this morning it did not, and it looked like the UZG-01 was not working properly, it did respond to ping, but Zigbee2MQTT was not able to connect.
[07:57:51] INFO: Preparing to start...
[07:57:51] INFO: Socat not enabled
[07:57:52] INFO: Starting Zigbee2MQTT...
[2024-06-26 07:57:55] info: z2m: Logging to console, file (filename: log.log)
[2024-06-26 07:57:56] info: z2m: Starting Zigbee2MQTT version 1.38.0 (commit #unknown)
[2024-06-26 07:57:56] info: z2m: Starting zigbee-herdsman (0.49.2)
[2024-06-26 07:57:56] info: zh:zstack:znp: Opening TCP socket with 10.0.24.4:6638
[2024-06-26 07:57:56] info: zh:zstack:znp: Socket connected
[2024-06-26 07:57:56] info: zh:zstack:znp: Socket ready
[2024-06-26 07:57:56] info: zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2024-06-26 07:57:57] info: zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2024-06-26 07:58:15] error: z2m: Error while starting zigbee-herdsman
[2024-06-26 07:58:15] error: z2m: Failed to start zigbee
[2024-06-26 07:58:15] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-06-26 07:58:15] error: z2m: Exiting...
[2024-06-26 07:58:15] error: z2m: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:101:27)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:127:29)
at Zigbee.start (/app/lib/zigbee.ts:62:27)
at Controller.start (/app/lib/controller.ts:109:27)
at start (/app/index.js:107:5)
When I tried to go to the UI, it was first nothing but after a few minutes I got some web-elements, two tries showed here:
Checked my UniFi Poe switch, looked good there also.
After a PoE powercycle it worked again, but I don’t want this to happen again, I need it to be stable af.
Any suggestions?
Zigbee
Mode Zigbee-Network
Socket 1 clients
Role Coordinator
Firmware 20240316
Hardware CC2652P7
IEEE 00:12:4B:00:2E:0E:1B:6A
Flash size 704 KiB
Device
Model UZG-01
Firmware 20240612
Hardware ESP32-D0WDQ6
yes, this - ZigStar - ZigBee Coordinators and Routers - #443 by margielm . I.e. - downgrade to UZG 0.2.6 .
It is running stable for me for the last 8 days.
On my UZG-01 (p7 chip) which is now running reliably I have:
- ESP Hardware: ESP32-D0WD-V3
- ESP firmware: 20240612
- Zigbee Hardware: CC2652P7
- Zigbee firmware: 20230507 (I found 20240316 to be unstable)
- Changed from WiFi to Ethernet
I got double the uptime with zigbee 20230507, but still after around 1,5 days my devices stopped responding
A little update.
I downgraded to UZG as recommended, with the P7 chip I am now running 100% stable for 3+ days. So I will stay on this platform until the newer FW is stable.
ZigBee 270752630 Rev: 20230507
ESP32 fw ver:0.2.6 (prod-solo)
ESP32 hw version: ESP32-D0WDQ6
CC2652P hw version: CC2652P7
CC2652P fw rev: 20230507
for me fw ver:0.2.6 is running stable for the last 17 days. i can just repeat what i said in my previous posts - if you have issues with XZG - downgrade to 0.2.6
1 Like
you are on 0.2.0, last one is 0.2.6
Please dont forget for proper test you can use also ESPHome firmware for Zigbee,what is long time available: BTProxy - ZigStar UZG
I’m brand new to zigbee and just got the UZG-01. Blindly went through setup and upgraded firmware without paying too much attention. UI changed to XZG branding which let me super confused as I didn’t know there was a new separate firmware.
Worse was I can’t connect to MQTT broker for some reason and I have been tearing my hair out trying to fix it. I thought for the last day that there was something weird in my firewall rules that were preventing the traffic even when the device is on the same vlan as my MQTT broker.
I discovered this post and reading through all the instability comments and a few mentions of MQTT issues as well. Makes me feel better. I’m gonna downgrade my firmware to 0.2.6 and start again.
It’s your network issue for sure.
Negative. As soon as I restored firmware to 0.2.6, exact same settings worked to connect to the MQTT broker. I even then moved the UGZ-01 back to a different vlan and it still works.
Nothing else changed to get this to work other than me downgrading the FW
I successfully flashed the coordinator firmware to the main dongle by following this tutorial
But I’m having issues trying to flash the router firmware onto secondary Sonoff Dongle P. Kept getting an error. Any tips? Followed this youtube tutorial.
Hello! Today I have got my ZigStar LilyZig PoE, and as usual decided to do first things first. I have connected it to LAN with PoE, opened WebUI and set up login and password generated previously to secure this device. It was successfully saved. And unfortunately, now I cannot login using that creds.
So, I started to search the way to reset device, and I have found that the only known way to do that is the flashing with full.bin file. So, first I have tried zig-star.com web flasher, then xzg.xyzroe.cc/install flasher and xyzroe.cc/ZigStarGW-FW. Last one just does nothing when I press install, 1st and 2nd are failing to initialize.
So, I went to Telegram: Contact @XZG_FW chat and discussed this topic. My luch, admin was very kind and tried to help me giving a lot of instructions and tips. We have discussed DIP switches positions, USB cables, COM port issues, browsers, etc. But nothing helps.
So, for now my setup is Win10 and I have tried Brave, Edge, Chrome browsers, different cables, driver was downloaded by the link from xzgroe website. I have also tried Chrome on my Debian machine.
Regarding DIP switches - when device was delivered from supplier 5 and 6 was on, and I was told to turn them off and try with 1-4 turned on. For a pitty, this didn’t worked. I’m connecting USB to the port on the upper board (ZigBee one). I have also tried NodeMCU package but it also cannot establish connection.
Maybe, someone can help me with this stuff here…
@mercenaruss, maybe you know how can I solve this issue?
Thanks in advance!
1 Like
UPD: When I was trying following all the tips and tricks to reset this device on the internet, seems like pushing/powering on while pushing some of the buttons did reset. Finally. The whole damn day to solve this little issue caused by not setting clear password rules and checks.
P.S. I still do not know which login and password allowed to be set to avoid this problem. And I don’t know exactly which button or whatever did reset.
I have a UZG-01 and noticed that the “IP whitelist for Zigbee socket connection” under “Security” doesn’t do anything. If I select that option, enter an IP address and hit save nothing happens/the changes aren’t saved. ESP f/w is 20240914 (also had the issue with 20240707).
In 2024 still the same problem with Zigstar UZG01 on ZHA (I don’t know for Z2M).
LQI values are not correct and RSSI is unknown.
Hmmm this thread was extremely active, and suddenly there’s not much more going on.
Does that mean that 20240710 is ready for prime time?
I have an UZG-1 in the mail and would like to have a stable network when I start unpacking it. Did I buy it prematurely?