The firmwares are for test. Follow here: Z-Stack_3.x.0 coordinator 20240315 feedback · Koenkk/Z-Stack-firmware · Discussion #496 · GitHub
Make sure you read the description and flash right one
1 Like
UZG-01 starting from Hardware Version 0.2 and up,is using only P7
LAN Gateways are still using P2
1 Like
I’m having some issues with Z2M not connecting to my UZG01 P7 now, think an attempt to flash the firmware failed, it’s showing unknown. Z2M times out connecting to it, and I can see in the status that it shows one socket connection for about 10-20 seconds, then 0.
Any tips on getting it alive again? I’ve tried the built in tool without any success (stops at 79%), the ZigStar TI CC2652P7 FW Flasher addon just says
Failed to get add-on logs, Failed to fetch and the Multi tool does not support the P7 I think?
Weird, disabling and enabling password authentication on the web interface made it come back alive. Still stumped on how I can flash newer firmware on it though 
Happened to me a few times as well. Heart in my mouth moments lol
The multi tool does work for P7. I tried it a few times as well. Just need to make sure you got python installed.
1 Like
Thanks a bunch, for some reason I’ve managed to download an old version of the multi tool, found a newer one and flashing went smooth Now I’m hoping the new firmware fixes my devices randomly dropping out.
Multitool work perfect with P7,check last version(last release), and is flashing over network very fast now.
For last P7 firmware please check here: Z-Stack_3.x.0 coordinator 20240315 feedback · Koenkk/Z-Stack-firmware · Discussion #496 · GitHub
and to make life easier,i want to make a teaser. Flashing over web interface is already working,with options like:
- Zigbee Coordinator
- Zigbee Router
- Matter over Thread
- Bluetooth Proxy
that will be available very soon.
Will move soon to new firmware,we are checking now bugs.
3 Likes
So far so good, no device dropped off which they tended to do within 18 hours, so looking good!
Hi @mercenaruss,
I have a question, I had my whole network crash, I had the following Errors in Z2M
[2024-05-07 10:59:59] error: zh:controller:device: Handling of poll check-in from 0x0015bc001a022738 failed
[2024-05-09 03:49:11] error: zh:controller:device: Handling of poll check-in from 0xbc33acfffe207b56 failed
[2024-05-09 04:48:00] error: zh:controller:device: Default response to 0xa4c138fd77ded024 failed
I suppose this is the known issue with the P7 chipset? I had to reset the dongle by power cycle to get my network back.
Is there some workaround for this? Can I use the restart zigbee service call with UZG-01 to have the same result until we have a fix?
1 Like
Which firmware are you on?
20240316
Its been fine for over a week 
so this has been the first real issue. Power cycle of the coordinator brought most of the devices back online, I had to repair 3 routers.
I have a fairly large network around 150 devices.
Yes,go to Web Interface of your UZG-01 and go to MQTT section,from there you will connect to your MQTT server and will get all options for restart zigbee,restart ESP and so on.
and check last version of P7 firmware: Z-Stack_3.x.0 coordinator 20240315 feedback · Koenkk/Z-Stack-firmware · Discussion #496 · GitHub
OK perfect thanks @mercenaruss, I have that setup already, will try it.
Unless there is a newer test firmware, I am already on 20240316, the problem is still there unfortunately, other than this bug everything else seems good.
1 Like
Hi @mercenaruss,
This is what I have that is from Tuya
TS011F_plug_1 = 1 [Power Socket]
TS0503B = 1 [RGB LED Controller]
ZMS-102 = 2 [Motion Sensors]
BSD29_1 = 6 [Power Socket]
TS011F_plug_3 = 2 [Power Socket]
TS0044 = 2 [4 Button Battery Switch]
TS110E_2gang_2 = 1 [2 Gang Dimmer with Neutral]
I have a UZG-01 (hw version: CC2652P7) running CC2652P fw rev: 20230507 and connected to HA via Z2M. It is connected via WiFi.
I would like to move to the newer firmware of 20240316 mentioned above, which is done by flashing file CC1352P7_coordinator_20240316.hex I assume.
What is best/preferred method for doing this fw upgrade.:
- Upload/flash via the UZG-01 own web UI “Zigbee update (in develop)”?
- Via the ZigStar GW Multi tool?
- Via the HA Add -On “ZigStar TI CC2652P7 FW Flasher” ?
I am very new to this and I am pretty nervous in case I brick it. There will probably be follow up questions when I know which route to take. Help appreciated.
Use the Multi tool, worked great here, see a couple of posts up.
1 Like
So just before I start can I confirm that the IP port is 6638 and file I use is CC1352P7_coordinator_20240316.hex and that I tick options Erase, Write, Verify and Auto BSL and then just click the Start button.
Thanks again
You can confirm or want it confirmed? I used this file znp_LP_CC1352P7_4_tirtos_ticlang_20240321.hex - this is a test firmware.
the options are correct, how ever I skipped the Auto BSL and enabled it through the GUI on the UZG.
So I went with the settings I wrote above and after a couple of false starts it now has updated to 20240316. Thanks for assistance.
FYI I have gone back to 20230507 as I found 20240316 to be unreliable. Slow responses, devices just not responding, time outs etc. This was one such error in the MQTT log:
[2024-05-10 20:30:30] error: z2m: Publish 'set' 'state' to 'ZSS12 Mains Socket' failed: 'Error: ZCL command 0xa4c13828c1e7fd25/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 57699 - 1 - 22 - 6 - 11 after 10000ms)'