IMPORTANT NOTE: If you want to update de coordinator please make sure you use the proper firmware download link, not the one that is indicated/used in the video (router). Thank you .beardedtinker for your excellent work.
hi flashed wrong one now getting failed to inialize device, tried new linked zip file but getting following in logs .... INFO: cc2652-flasher-up script exited with code 1 s6-rc: warning: unable to start service cc2652-flasher: command exited 1@@BeardedTinker
It is incredible that I have found this video. It worked perfectly. Now I just have to observe whether anything stops working in the network with the new firmware. But the instructions worked perfectly for me. Thank you!
Wow, I'm glad I stumbled upon this video. I just started with HA and I'm building a new Zigbee network from the ground up. I wanted to make sure my adapter was up to date on firmware and after I read through the firmware update PDF on the Z2M site I was pretty exasperated. It was going to take me at least an hour to update with that method. Instead I was done in about 10 minutes and all my devices reconnected without issue when I fired up Z2M again. Thanks!
Thank you! Now I managed to update my Slaeh´s CC2652RB stick 2021 firmware to the latest in 2023. I am new to Home Assistant and using ZHA with Coordinator Firmware. I have 102 Zigbee devices and 30 Z Wave migrated from Homey and Ikea Tradfri Router to my HA running on RPi 4.
Thank you very much! Best and easier method to update firmware. I was trying other ways and nothing worked for me other than this. Zigbee network is more reliable and works better now. Thanks again!
Found this great tutorial because of losing zigbee devices in my network. Haven;t upgraded my stick in years because i didn't want to lose my zigbee stick. With this tutorial i was able to upgrade to the latest firmware. Hopefully the problem is fixed now. A big thank you!
Man, you saved so many hours and trouble for me, this is amazing, I bought some aqara switches which needed the new firmware on my sonoff stick and the official solution to open the stick and flashing firmware seemed too daring for a novice beginner like me. But this method was so simple and easy to follow. Thanks again for making this video!
I used this add-on to successfully update the firmware on my sonoff dongle 3.0 plus. I used the latest koenkk firmware, cc1352p2_cc2652p_launchpad , as indicated in the add-on for sonoff dongles and so far it has seemed to fix all of the problems I have been having in ZHA over the past month or so. Thank you for this tutorial, I will be sure to check in from time to time to see if there will be newer firmware to keep my dongle updated.
Thank you sir for such a detailed video , I was hesistant on upgrading firmware due to the complexity but your video made it simple. I followed it word for word and everything went great. Again thankyou.
You’ve done it again another really useful find. Also had a couple of odd dropouts recently after some years, was thinking it’s Ikea beta firmware on some bulbs but might update stick firmware first as this will be easier now 👍 This is so much better
Thanks bro! Thought I should give my 2-3 years old SONOFF Zigbee USB P dongle a firmware upgrade. Been following your guide since I got my Pi4 for my HA, very helpful buddy! Today I just did this FW upgrade smooth like butter! This method was the easiest to follow and perform. No need to re-pair any Zigbee devices. Thanks a lot!
Many thanks for all this. You saved my day yesterday. Thanks to your channel I could finally update my sonoff dongle P. I always got an error until I saw your video and you indicated to fill in 127.0.0.1. Now the dongle is working just fine and retrieving more data from my devices. Please continue the good work, and many thanks again.
Thanks for the overview. I only watched 4 min, tried ZigStar and the update finally worked. I worked on this for 2 days. After the video, it took me only a few min. I have the SONOFF ZigBee 3.0 USB Dongle Plus. To start the bootloader, you need to disassemble, insert the stick, hold the boot button for a good 20 seconds before you update the firmware.
Thank you BeardedTinker! Excellent video. Works flawlessly on SONOFF Zigbee 3.0 USB Dongle Plus, TI CC2652P + CP2102N Zigbee USB Stick. No custom URL required with this hardware as coordinator. On the configuration screen I just choose my Device, Turn-on Checks for USB, Sonoff USB and "Last Koenkk Firmware - CC1352P2_CC2652P_launchpad_*.zip" Stop your Zigbee2Mqtt server then start the zigstar add-on.
Very nice video. Much better method then the TI instruments way, as it did not work with my Sonoff Dongle P... It seams to be working better now with higher link quality. Ohh, I did not have to hold the Hardware boot button...
Great Video. Will be giving this a go over christmas break. Do you need to re-pair anything afterwards or does it just pick up where it left off once upgraded?
It shouldn't break the network. But as with everything, things can go wrong. You could do stick backup (in both ZHA and Zigbee2MQTT) to be safe. So far I haven't had any issues, but you know Murphy's law - if things can go sideways, they'll go.
Great find! Im still preparing to update mine but i have a doubt. What do you mean by local loop? What IP address should i put in Network Device? Thank you and keep up with these fantastic tutorials! ;)
@@BeardedTinker Many devices seem to drop randomly, both routers and end devices. Didn't have that issue with my Sonoff Zigbee Plus. It uses the new CC2652P7. I think it's too new and the fireware needs tweaking.
Yeah, that could be firmware thing with new HW - it takes a long time to get stability to ones that are already on market for long time. Also, more people use it, more people will report bugs and quicker it will get fixed.
Hey i still use an CC2531, no need so far to change it. i live in an apartment and i don't have that many devices. So far so good, i didn't look much at the details ca CC2531 be updated? Yes this add-on will make my life much easier, i remember now using a programmer to flash the firmware. Thanks for the video.
I think for cc2531 (I still have it too) it's stuck on some 1.x version. Mine is on 20190608 firmware version. And latest is 20211115 - github.com/Koenkk/Z-Stack-firmware/blob/master/coordinator/Z-Stack_Home_1.2/CHANGELOG.md Need to try to update it, but not sure if it would work this way as this one required debugger for programming.
@@BeardedTinker i see. thanks for the message. probably i should live it alone if it works don mess wit it and then create more problems to myself. I may need to upgrade in the future, until then cc2531 works like a charm.
Bonus points if you'll show how to do it with ZHA this is awesome video! Thank you! As I need to update my firmware on mine is it a way to show within home assistant to see which actual sign-off zigbee stick I have it was confusing when I ordered it and I'm not sure which one
Thank you!!! To verify what stick you have, go to Settings, System and Hardware. There click on All hardware and look for ttyACM0 (or ttyUSB0). There you should see something like: /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20220622105009-if00 - for Dongle-E or /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_528891f7dfc9eb1191928f4f1d69213e-if00-port0 - for Dongle-P. Dongle E is as you see Plus_V2, dongle P is jsut Plus without V2 at the end in name. ;)
Maybe stupid question, but what's the difference between Silicon labs flasher from this repository and the official Silicon Labs Flashers (seen on the list at 3:34 in your video)?
In functionality, not a big difference - but one requires you to unplug device, plug into PC, flash the firmware and return to HA instance, other can do it on same machine that runs HA from within UI.
Thanks for this great video ! _But why are you using the "router" and not the "coordinator" firmware ? Edit: OK, it looks like you have more than one Stick in one zigbee network... (?)
I wish this was better communicated in the video. I flashed my Dongle P with the router url as I hoped I can just follow you along and now its not working anymore. Hope it's not broken now@@BeardedTinker
Link in video description is for coordinator. You can flash any of them (if they match the model) and than reflash the other one over it. Sorry for not making it more clear.
You are jumping too far :) That part was only to show what you can tick, not what firmware to use :) I talk about that few seconds later. Link to both Dongle P and E firmware is in video description.
You usually need coordinator - they can than be used with both ZHA and Zigbee2MQTT - router is needed only if you buy multiple sticks and want to use others to extend your network.
Didn't work for me at first got crazy errors like: ERROR: bytearray index out of range turns out that somehow the port allocation was not right, forcing the stick to another ttyUSB? did the trick
Didn't try TBH - I know that HA should be able to handle that internally. Will first check with devs. BUT as far as support, SkyConnect (or internal Yellow chip) are supported by the tool.
I've been experiencing intermittent issues with my 'SONOFF Zigbee 3.0 USB Dongle Plus-P'. Devices would occasionally become unresponsive but still show connected via Z2M. After updating coordinator FW version 20210708 to 20230507, devices seem to respond/update more "snappy". Time will tell if my intermittent issues have been resolved.
Hi, I updated coordinator firmware to my SONOFF Zigbee 3.0 USB Dongle Plus ZBDongle-P as your video and work smootly. But how do update my SONOFF Zigbee 3.0 USB Dongle Plus ZBDongle-P router? my router SONOFF Zigbee 3.0 USB Dongle Plus ZBDongle-P not connect via USB with Home Assistant. How do i update router in Zigbe2MQTT network? Thanks
For routers that are not connected to HA directly (via USB or network cable) - you can use standard method of upgrade. Did video on that about a year ago. Or you can temporarily connect to your HA and use this to update with router firmware
I have a Sonoff P dongle with original firmware on it as I haven’t got round to flashing it yet. Would this method work or would I need to flash it using an alternative method first?
You should be able to flash it this way. One note - SOME devices (99% sure this is not case with Dongle-P first flash) may require to unplug them ,press boot button and hold it while reconnecting.
Any stick that is listed on Zigbee2mqtt site for 3.x.0 or 3.x firmware should be ok. Plus firmware for Silicon Labs chipseta. I've shown the list in video
Using HAOS, ZigStar TI CC2652P/P7 PW Flasher and the SonoffUSB Dongle PLus and have disabled the USB/ZHA and still get the below error, can't figure it out. s6-rc: info: service banner successfully started s6-rc: info: service cc2652-flasher: starting unzip: short read [20:04:57] INFO: cc2652-flasher-up script exited with code 1 s6-rc: warning: unable to start service cc2652-flasher: command exited 1 s6-rc: info: service banner: stopping /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. /run/s6/basedir/scripts/rc.init: fatal: stopping the container. s6-rc: info: service banner successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service banner: starting
Any idea what this error is about? Where is that /run/ folder? ERROR: Timeout waiting for ACK/NACK after 'Synch (0x55 0x55)' [10:55:23] INFO: cc2652-flasher-up script exited with code 1 s6-rc: warning: unable to start service cc2652-flasher: command exited 1 s6-rc: info: service banner: stopping /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. /run/s6/basedir/scripts/rc.init: fatal: stopping the container.
There could be few things. Best bet is to open issue with author. But it could be that whatever you are using(ZHA or Zigbee2MQTT) is not allowing access to the device. Or that device can't via software enter bootloader mode.
I had this error multiple times because I had incorrectly thought I stopped my MQTT addon, found it still running and stopped it and re-ran the update successfully
@@YogeshPatel-io2sz that depends on coordinator - most modern ones, don't need or have BSL button. But as OP wrote, it was issue with device that was still in use.
In Zigbee2MQTT it's visible under Settings - About. As for ZHA - can't remember where you could see that - maybe it was in download diagnostics and then it will be in that file.
Not out of box. Even though AddOns are Docker images, this would not work. HA provides UI for configuration and maintenance, so even if ported, someone would need to create frontend for it. But that's way above my head...
In ZHA check device Zigbee coordinator. It should list it on the device page. If it doesn't show, you can on same page download diagnostics information and look there.
It should. If you can install AddOn - it should be able to work. Of course if USB stick is mapped in Proxmox, but probably is as you are already using it in HA?
It should be as it's same chip (2652) - not sure if you need to manually set bootloader mode or not, but you can try first without manually pressing the button.
While Conbee II is still working and a lot of people are using it, with newer chipsets that also support thread, you may consider in long term to replace it for something else. But on the other hand, if it's working, you're good to go.
Error: Using Sonoff-P, followed exactly, used 127.0.0.1 received this error: s6-rc: info: service banner successfully started s6-rc: info: service cc2652-flasher: starting [16:00:20] INFO: Triggering Bootloader mode on 10. [16:00:24] INFO: cc2652-flasher-up script exited with code 6 s6-rc: warning: unable to start service cc2652-flasher: command exited 6 /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. /run/s6/basedir/scripts/rc.init: fatal: stopping the container.
You better ask author on GitHub - he will gladly try and help - here is the link: github.com/mercenaruss/zigstar_addons/issues My only question that pops on my mind is - did you stop ZHA/Zigbee2MQTT? It says that not all services could be started. Maybe that's the reason. Other one could be that you are using firmware for P on E dongle or other way around. Nothing else pops in my mind.
Are you using the dongle as a router or coordinator? if coordinator, make sure you use the correct firmware (not the one indicated in the video which is "router") and turn Bootloader mode for network device to "off"
Great video by the way! I ran into a very weird problem. I have the Slaesh's CC2652RB stick and I used the latest "../Koenkk/Z-Stack-firmware/raw/Z-Stack_3.x.0_coordinator_20230507/coordinator/Z-Stack_3.x.0/bin/CC2652RB_coordinator_20230507.zip". Although Zigbee2MQTT works after the update, I cannot add any new devices to the zigbee network. Also I tried removing an already paired device and re add it but no success. Have you experienced such issue?
Thank you Anton! No, I haven't seen this. That's really strange one. You can try (if you already haven't) to remove the stick and insert it again. Also, you can try to reflash the same firmware on the device. How many devices do you have on your network?
Thanks for the reply! Yeah I've already tried plugging and unplugging the stick. Tried to reflash it twice. Also at some point I tried flashing it with a previous firmware version but it seems there's some kind of check and you can only flash newer firmware versions. I do think though that it's somehow connected with the Zigbee2MQTT addon for HA. I just reinstalled the addon - as you can guess it didn't help. I noticed that everytime I try to delete a paired device - there's an exception thrown and I need to check the "force remove button". I really can't think of anything else I can do..
Can you stil control other devices (turn them on/off)? BTW - one thing does pop on my mind - can you verify (redownload) firmware - maybe you flashed router firmware instead of coordinator? Not sure how this would actually work. Just to be on the safe side. github.com/Koenkk/Z-Stack-firmware/blob/master/coordinator/Z-Stack_3.x.0/bin/CC2652RB_coordinator_20230507.zip
About the firmware - yes I double checked that I've installed the coordinator firmware. The weird thing is that I only receive data from paired devices. I have an Aqara FP1 presence sensor and when I try to "reset" it's state through ZigbeetoMQTT's UI it's throwing and exception that the action failed. So any interaction with the devices fails but the paired devices report their state.
I Got this error with Dongle P s6-rc: info: service banner successfully started s6-rc: info: service cc2652-flasher: starting [19:05:26] INFO: cc2652-flasher-up script exited with code 6 s6-rc: warning: unable to start service cc2652-flasher: command exited 6 s6-rc: info: service banner: stopping /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. /run/s6/basedir/scripts/rc.init: fatal: stopping the container. s6-rc: info: service banner successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped
@@BeardedTinker Hey. I figured it out. Had to do a restore. Disable first THEN delete ZHA and it worked. Previously I just disabled ZHA. Apparently that was the issue.
"(Coordinator must be in bootloader mode before addon is started, hold BSL button while plugging into USB) " Written in Documentation of ADD ON. BNT1 button on dongle.
for me the only wich worked with switching also on Last Koenkk Firmware - CC1352P2_CC2652P_other_*.zip how can i know the next time wich version i got from usb sonof so for now it is this. yours at custom firmware link i thought there is only one version zigbee plus sonof and that did not work for me zigbee2mqtt would not start any more. so when i orderd it said SONOFF ZigBee 3.0 USB Dongle Plus, TI CC2652P Coördinator, Universele USB ZigBee Hub so did i choose in the end good or did i make mistake and need to choose another one. after swictching also Last Koenkk Firmware - CC1352P2_CC2652P_other_*.zip now it works is this ok ?.
Did you check the table on GitHub - P dongle needs CC1352P2_CC2652P_launchpad_*.zip - _other_ version is different but if it works for you, go with it. I don't know what's the difference . Botb version - launchpad and other are for CC2652P chipset.
@@BeardedTinker no did not i to be honest i thought sonof there is only the plus and the other and so in the box CC2652P followed your screen and saw it was exact same naming but in the end there are difference inside usb stick and are not the same
If you try to use Dongle P with firmware for E it would fail, same if you would use Dongle E with firmware for P - so if everything is working for you, it's ok :)
IMPORTANT NOTE: If you want to update de coordinator please make sure you use the proper firmware download link, not the one that is indicated/used in the video (router).
Thank you .beardedtinker for your excellent work.
it's a mistake i did! I flashed back to the coordinator
In video description, I've linked Coordinator firmware. My bad for cutting that part out of video...
hi flashed wrong one now getting failed to inialize device, tried new linked zip file but getting following in logs .... INFO: cc2652-flasher-up script exited with code 1
s6-rc: warning: unable to start service cc2652-flasher: command exited 1@@BeardedTinker
thank you!
too late. For 5 minutes my heart has stopped. flashing coordinator fixed it. Adrenaline slowly going down.
It is incredible that I have found this video. It worked perfectly. Now I just have to observe whether anything stops working in the network with the new firmware. But the instructions worked perfectly for me. Thank you!
Glad it helped and thanks for the comment!!!
You helped me make my Sonoff USB usable again with the Home Assistant, thanks for sharing your knowledge .
Great to hear! Good luck with it!!!
Wow, I'm glad I stumbled upon this video. I just started with HA and I'm building a new Zigbee network from the ground up. I wanted to make sure my adapter was up to date on firmware and after I read through the firmware update PDF on the Z2M site I was pretty exasperated. It was going to take me at least an hour to update with that method. Instead I was done in about 10 minutes and all my devices reconnected without issue when I fired up Z2M again. Thanks!
Awesome, glad to hear it !
Thank you! Now I managed to update my Slaeh´s CC2652RB stick 2021 firmware to the latest in 2023. I am new to Home Assistant and using ZHA with Coordinator Firmware. I have 102 Zigbee devices and 30 Z Wave migrated from Homey and Ikea Tradfri Router to my HA running on RPi 4.
Nice! This makes it really to upgrade if and when needed!
What controller do you have for ZWave?
@@BeardedTinker I use the AEOTEC Z-Stick 7 for ZWave, not the best but it works for my devices.
Thank you very much! Best and easier method to update firmware. I was trying other ways and nothing worked for me other than this. Zigbee network is more reliable and works better now. Thanks again!
Very glad to hear it!!!
Found this great tutorial because of losing zigbee devices in my network. Haven;t upgraded my stick in years because i didn't want to lose my zigbee stick. With this tutorial i was able to upgrade to the latest firmware. Hopefully the problem is fixed now. A big thank you!
Great to hear it and hope it will help!!
Excellent video, I have never seen anyone to cover this. Really useful for the whole community!
Thanks for covering this!
Glad you enjoyed it! I was really happy to find this - it can make whole process easier!
Thanks for the comment!!!
Man, you saved so many hours and trouble for me, this is amazing, I bought some aqara switches which needed the new firmware on my sonoff stick and the official solution to open the stick and flashing firmware seemed too daring for a novice beginner like me. But this method was so simple and easy to follow. Thanks again for making this video!
Really great to hear that it helped! Enjoy your Aqara switches!!
I used this add-on to successfully update the firmware on my sonoff dongle 3.0 plus. I used the latest koenkk firmware, cc1352p2_cc2652p_launchpad , as indicated in the add-on for sonoff dongles and so far it has seemed to fix all of the problems I have been having in ZHA over the past month or so. Thank you for this tutorial, I will be sure to check in from time to time to see if there will be newer firmware to keep my dongle updated.
Glad it helped!!!
Thank you sir for such a detailed video , I was hesistant on upgrading firmware due to the complexity but your video made it simple. I followed it word for word and everything went great. Again thankyou.
Glad to hear that!!!
You’ve done it again another really useful find. Also had a couple of odd dropouts recently after some years, was thinking it’s Ikea beta firmware on some bulbs but might update stick firmware first as this will be easier now 👍 This is so much better
Yeah, one way of eliminating problems - get newer firmware. For me, currently, everything is again working as it should.
Great video. Saved a lot of time and was done within 2 minutes. Thanks again and keep on the good work.
Glad it helped!!
Thanks bro! Thought I should give my 2-3 years old SONOFF Zigbee USB P dongle a firmware upgrade. Been following your guide since I got my Pi4 for my HA, very helpful buddy! Today I just did this FW upgrade smooth like butter! This method was the easiest to follow and perform. No need to re-pair any Zigbee devices. Thanks a lot!
Great to hear that! Enjoy your "new" old stick!! Sonoff P is really great device.
Many thanks for all this. You saved my day yesterday. Thanks to your channel I could finally update my sonoff dongle P. I always got an error until I saw your video and you indicated to fill in 127.0.0.1. Now the dongle is working just fine and retrieving more data from my devices. Please continue the good work, and many thanks again.
Glad I could help!!!
Thanks for the overview. I only watched 4 min, tried ZigStar and the update finally worked. I worked on this for 2 days. After the video, it took me only a few min. I have the SONOFF ZigBee 3.0 USB Dongle Plus. To start the bootloader, you need to disassemble, insert the stick, hold the boot button for a good 20 seconds before you update the firmware.
Glad it helped!
Finally upgraded my Dongle-E, never got to it because of all the hassle involved! Thnx!
I know the feeling - my Dongle-E was stock as every time I wanted to upgrade I've simply given up :)
@@BeardedTinker @RolandGoudriaan Which version did you use? the latest? thanks!
Thank you BeardedTinker! Excellent video. Works flawlessly on SONOFF Zigbee 3.0 USB Dongle Plus, TI CC2652P + CP2102N Zigbee USB Stick. No custom URL required with this hardware as coordinator. On the configuration screen I just choose my Device, Turn-on Checks for USB, Sonoff USB and "Last Koenkk Firmware - CC1352P2_CC2652P_launchpad_*.zip" Stop your Zigbee2Mqtt server then start the zigstar add-on.
Great to hear! And yeah, it's so easy compared to doing it by hand...
Thanks! I have been putting off flashing my Slaesh's CC2652RB stick for far too long! So helpful and clear! Thank you.🖥🖥🖥
Great to hear it - I know the feeling of putting it off. And thank you for SuperThanks!!!!!
Great video and thank you for the step by step instructions. Just upgraded my Sonoff P version.
Glad it helped you!!! Thank you for the comment!!!
Hero! That was well explained. Made it so easy for me.
Glad it was useful! Thank you for the comment!!!
Thnx for this extremely useful instructional video. I was able to successfully procceed with the flashing.
Glad it helped Thanks for the comment!!!
Excellent..... AGAIN....I have been dreading this upgrade process.
Thank you!!! Me too.
thank you! very informative, got to update my sonoff dongle 🙂
Glad it helped!
worked perfectly, thx a lot.. greetings from HK
Glad it helped - thank you!
Awesome Andrej! Thanks.
Glad you liked it Ed! This was such a discovery!
@@BeardedTinker Indeed. I was not aware of this. Thank you!
Very nice video. Much better method then the TI instruments way, as it did not work with my Sonoff Dongle P... It seams to be working better now with higher link quality. Ohh, I did not have to hold the Hardware boot button...
Glad it helped! Yes, for P it should be able to set boot on device without needing to hold the button.
Thanks for nice guide, this one I had missed.
Any time!
Thank you for saving my sanity
Glad it was useful!!!
Thank you! This saved me a lot of time!
Glad it helped!
Great Video. Will be giving this a go over christmas break. Do you need to re-pair anything afterwards or does it just pick up where it left off once upgraded?
It shouldn't break the network. But as with everything, things can go wrong. You could do stick backup (in both ZHA and Zigbee2MQTT) to be safe. So far I haven't had any issues, but you know Murphy's law - if things can go sideways, they'll go.
This is great! Thanks for sharing!
Glad you enjoyed it! Thank you!
That's pretty cool, thanks for posting, I'll have to buy you a cup of coffee now 😎
You're welcome! Glad you liked it!!
thank you bro, super nice video (as usual) just upgraded mine coordinator and router
P.S. enable should NOT sound like "unable" at 6:41 ;-)
enable or unable - almost the same thing 😂 (noted, thanks!)
Great find! Im still preparing to update mine but i have a doubt. What do you mean by local loop? What IP address should i put in Network Device? Thank you and keep up with these fantastic tutorials! ;)
Any IP address is OK - 127.0.0.1 is local address, so you can use that one - it is internal PC address.
Great video! The addon works great, well, at least for the ZigStar UZG-01 (haven't tried any other). Still struggling with the UZG-01 itself though. 😅
I haven't tried it with SkyConnect, but also have no reason to do that as HA handles it internally. What's the problem with your stick?
@@BeardedTinker Many devices seem to drop randomly, both routers and end devices. Didn't have that issue with my Sonoff Zigbee Plus. It uses the new CC2652P7. I think it's too new and the fireware needs tweaking.
Yeah, that could be firmware thing with new HW - it takes a long time to get stability to ones that are already on market for long time. Also, more people use it, more people will report bugs and quicker it will get fixed.
@@TommyBrenner hi ,can you open a ticket by sending an email , will discuss there and see what can be done.
@@BeardedTinker Apparently Koenkk is already working on a new firmware version. I guess time will tell how this might improve.
Great video - thanks for sharing !
Much appreciated! Thanks for the comment!!!
Hey i still use an CC2531, no need so far to change it. i live in an apartment and i don't have that many devices. So far so good, i didn't look much at the details ca CC2531 be updated? Yes this add-on will make my life much easier, i remember now using a programmer to flash the firmware. Thanks for the video.
I think for cc2531 (I still have it too) it's stuck on some 1.x version. Mine is on 20190608 firmware version. And latest is 20211115 - github.com/Koenkk/Z-Stack-firmware/blob/master/coordinator/Z-Stack_Home_1.2/CHANGELOG.md
Need to try to update it, but not sure if it would work this way as this one required debugger for programming.
@@BeardedTinker i see. thanks for the message. probably i should live it alone if it works don mess wit it and then create more problems to myself. I may need to upgrade in the future, until then cc2531 works like a charm.
Yeah, for those sticks . if they work, don't touch them :)
Bonus points if you'll show how to do it with ZHA this is awesome video! Thank you! As I need to update my firmware on mine is it a way to show within home assistant to see which actual sign-off zigbee stick I have it was confusing when I ordered it and I'm not sure which one
just stop ZHA and run the add-on. main thing is to stop the app from using the coordinator while it's being flashed. it's the same for zha or z2m.
Thank you!!!
To verify what stick you have, go to Settings, System and Hardware. There click on All hardware and look for ttyACM0 (or ttyUSB0). There you should see something like:
/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20220622105009-if00 - for Dongle-E or
/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_528891f7dfc9eb1191928f4f1d69213e-if00-port0 - for Dongle-P.
Dongle E is as you see Plus_V2, dongle P is jsut Plus without V2 at the end in name. ;)
Thank you so much
]@@BeardedTinker
You're welcome!!!
Thank you you rock,this excellent
You're very welcome - thanks for watching!!!
Maybe stupid question, but what's the difference between Silicon labs flasher from this repository and the official Silicon Labs Flashers (seen on the list at 3:34 in your video)?
Is no big diffrence,i forket to be able to adjust to my own made devices what are coming out.
In functionality, not a big difference - but one requires you to unplug device, plug into PC, flash the firmware and return to HA instance, other can do it on same machine that runs HA from within UI.
I'm assuming the 'Silicon Labs Multiprotocol' addon does he same thing for multi-pan firmwares?
Can't tell you for sure. Didn't test. While it should work, I haven't seen an example or tested myself!
Thanks for this great video ! _But why are you using the "router" and not the "coordinator" firmware ?
Edit: OK, it looks like you have more than one Stick in one zigbee network... (?)
I have currently 3 just for testing - plus 2 I use as coordinators (and also Yellow with ZB support) :)
I wish this was better communicated in the video. I flashed my Dongle P with the router url as I hoped I can just follow you along and now its not working anymore. Hope it's not broken now@@BeardedTinker
@@halfdave503I did too just refresh it with the coordinator firmware
Link in video description is for coordinator. You can flash any of them (if they match the model) and than reflash the other one over it. Sorry for not making it more clear.
@@BeardedTinker yes that worked :) thanks!
6:55 I think it is the same firmware like your custom link.
You are jumping too far :) That part was only to show what you can tick, not what firmware to use :) I talk about that few seconds later.
Link to both Dongle P and E firmware is in video description.
@@BeardedTinker 🙂Okay right .
I also have the Sonoff P stick and now it will always update automatic.
Thanks
is it right if I select the coordinator firmware if I use ZHA (not ZHA2mqtt) with my sonoff *-P? or should I choose Router?
You usually need coordinator - they can than be used with both ZHA and Zigbee2MQTT - router is needed only if you buy multiple sticks and want to use others to extend your network.
Didn't work for me at first got crazy errors like:
ERROR: bytearray index out of range
turns out that somehow the port allocation was not right, forcing the stick to another ttyUSB? did the trick
Thank you for this information. Is it possible to update the Integrated Zigbee chip inside the Home Assistant Yellow?
Didn't try TBH - I know that HA should be able to handle that internally. Will first check with devs. BUT as far as support, SkyConnect (or internal Yellow chip) are supported by the tool.
Brilliant! Thankyou
Glad you liked it!
Thank you for review.
No, thank you for all of the awesome gateways, sticks, hat's,... :)
@@BeardedTinker I need some more help with addon :) is not perfect.
Can be improved, but i dont have knowledge.
I do get you - I have so many ideas, but my capabilities don't agree with me :)
Still it really improves and simplifies whole process.
Danke!
Thank you VERY much!!!!
I've been experiencing intermittent issues with my 'SONOFF Zigbee 3.0 USB Dongle Plus-P'. Devices would occasionally become unresponsive but still show connected via Z2M. After updating coordinator FW version 20210708 to 20230507, devices seem to respond/update more "snappy". Time will tell if my intermittent issues have been resolved.
Hopefully, new FW will fix it. For Dongle-P, original firmware (2021) was really bad.
Can I stop ZigStar Flasher once the update is successfully done?
Sure!
Hi, I updated coordinator firmware to my SONOFF Zigbee 3.0 USB Dongle Plus ZBDongle-P as your video and work smootly. But how do update my SONOFF Zigbee 3.0 USB Dongle Plus ZBDongle-P router? my router SONOFF Zigbee 3.0 USB Dongle Plus ZBDongle-P not connect via USB with Home Assistant. How do i update router in Zigbe2MQTT network? Thanks
For routers that are not connected to HA directly (via USB or network cable) - you can use standard method of upgrade. Did video on that about a year ago. Or you can temporarily connect to your HA and use this to update with router firmware
You can plug it temporarily to you HA system and flash with router firmware then install in required location
Thanks, @@BeardedTinker
I will try it. Thanks @@zigstar4you
I have a Sonoff P dongle with original firmware on it as I haven’t got round to flashing it yet. Would this method work or would I need to flash it using an alternative method first?
You should be able to flash it this way. One note - SOME devices (99% sure this is not case with Dongle-P first flash) may require to unplug them ,press boot button and hold it while reconnecting.
Thanks!
Thank you very very much 😀
Does this work for the CC2652RB or is it only for the CC2652P, it isn't clear from the video as you start with one stick and then flash another one
Any stick that is listed on Zigbee2mqtt site for 3.x.0 or 3.x firmware should be ok. Plus firmware for Silicon Labs chipseta.
I've shown the list in video
Using HAOS, ZigStar TI CC2652P/P7 PW Flasher and the SonoffUSB Dongle PLus and have disabled the USB/ZHA and still get the below error, can't figure it out.
s6-rc: info: service banner successfully started
s6-rc: info: service cc2652-flasher: starting
unzip: short read
[20:04:57] INFO: cc2652-flasher-up script exited with code 1
s6-rc: warning: unable to start service cc2652-flasher: command exited 1
s6-rc: info: service banner: stopping
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service banner successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service banner: starting
Thank you.
You're welcome, and thanks for the comment Ron!
thank you
Thanks Ian!!!!
Bookmarked! 👍
Fantastic! Thank you for comment!
Any idea what this error is about? Where is that /run/ folder?
ERROR: Timeout waiting for ACK/NACK after 'Synch (0x55 0x55)'
[10:55:23] INFO: cc2652-flasher-up script exited with code 1
s6-rc: warning: unable to start service cc2652-flasher: command exited 1
s6-rc: info: service banner: stopping
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
There could be few things. Best bet is to open issue with author. But it could be that whatever you are using(ZHA or Zigbee2MQTT) is not allowing access to the device. Or that device can't via software enter bootloader mode.
I had this error multiple times because I had incorrectly thought I stopped my MQTT addon, found it still running and stopped it and re-ran the update successfully
"(Coordinator must be in bootloader mode before addon is started, hold BSL button while plugging into USB) " Written in Documentation of ADD ON.
@@YogeshPatel-io2sz that depends on coordinator - most modern ones, don't need or have BSL button. But as OP wrote, it was issue with device that was still in use.
Is there a way to find out, what firmware is currently installed on my Zigbee Stick? (Sonoff E)
In Zigbee2MQTT it's visible under Settings - About. As for ZHA - can't remember where you could see that - maybe it was in download diagnostics and then it will be in that file.
This is correct. I found it in the downloaded file. Thanks so much. @@BeardedTinker
@@blubbermax25 great! Good luck 👍
Is it possible to use this method to setup and flash a new dongle to use it as a router ?
Sure, just use router firmware on it. While I talk about coordinator I do flash router fw in this video actually.
@@BeardedTinker great. Thank you so much for this video.
Can one add this if one has a docker install and not HAS OS or no addon store?
Not out of box. Even though AddOns are Docker images, this would not work. HA provides UI for configuration and maintenance, so even if ported, someone would need to create frontend for it. But that's way above my head...
same here. Created an issue for that. Will see
How to know which firmware our dongle has (ZHA, Sonoff dongle E) ? Thx
Just checked and I Guess I have 6.10.3.0 version 297. Is it the latest stable one ?
In ZHA check device Zigbee coordinator. It should list it on the device page. If it doesn't show, you can on same page download diagnostics information and look there.
@@BeardedTinker Thank you, it indeed shows this : 6.10.3.0 build 297. Is it the latest of shoul I upgrade ?
That0s latest official firmware from Sonoff (there are some from community that are newer)
@@BeardedTinker Ok, Thank you very much !!!
Would this also work when running HAOS as a VM in Proxmox? (I think not?)
It should. If you can install AddOn - it should be able to work. Of course if USB stick is mapped in Proxmox, but probably is as you are already using it in HA?
It does - just upgraded my firmware. As a side note, make sure you stop the Zigbee2MQTT (in my case) add-on first or update will not work
@@blakrjThanks for letting me know. Will give it a try soon!
is this add-on compatible with zzh (CC2652R Stick)?
It should be as it's same chip (2652) - not sure if you need to manually set bootloader mode or not, but you can try first without manually pressing the button.
thanks
without the manual setting it does not work i will try the other way when i can
Updated to the last available firmware
Thanks again
@@francescoatria1086 awesome!!!
@@francescoatria1086 you mean toggle on "Enable Bootgloader mode for network device"?
Not sure I understood: would that work for a Conbee II with Deconz? Thank you
Unfortunately. Conbee II falls into "Almost any" category. Chipset it is using is very old and from what I know it's not supported.
That's what I was afraid of after checking the repo. Thank you for the confirmation!
While Conbee II is still working and a lot of people are using it, with newer chipsets that also support thread, you may consider in long term to replace it for something else. But on the other hand, if it's working, you're good to go.
Well that was easy 🤔
Yeah, this wasn't even supposed to be video for today, but when I've seen it, had to do it :)
Error: Using Sonoff-P, followed exactly, used 127.0.0.1 received this error: s6-rc: info: service banner successfully started
s6-rc: info: service cc2652-flasher: starting
[16:00:20] INFO: Triggering Bootloader mode on 10.
[16:00:24] INFO: cc2652-flasher-up script exited with code 6
s6-rc: warning: unable to start service cc2652-flasher: command exited 6
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
You better ask author on GitHub - he will gladly try and help - here is the link: github.com/mercenaruss/zigstar_addons/issues
My only question that pops on my mind is - did you stop ZHA/Zigbee2MQTT? It says that not all services could be started. Maybe that's the reason. Other one could be that you are using firmware for P on E dongle or other way around. Nothing else pops in my mind.
There is similar issue as yours (second post here: github.com/mercenaruss/zigstar_addons/issues/13)
Are you using the dongle as a router or coordinator? if coordinator, make sure you use the correct firmware (not the one indicated in the video which is "router") and turn Bootloader mode for network device to "off"
Great video by the way! I ran into a very weird problem. I have the Slaesh's CC2652RB stick and I used the latest "../Koenkk/Z-Stack-firmware/raw/Z-Stack_3.x.0_coordinator_20230507/coordinator/Z-Stack_3.x.0/bin/CC2652RB_coordinator_20230507.zip". Although Zigbee2MQTT works after the update, I cannot add any new devices to the zigbee network. Also I tried removing an already paired device and re add it but no success. Have you experienced such issue?
Thank you Anton!
No, I haven't seen this. That's really strange one. You can try (if you already haven't) to remove the stick and insert it again. Also, you can try to reflash the same firmware on the device.
How many devices do you have on your network?
Thanks for the reply! Yeah I've already tried plugging and unplugging the stick. Tried to reflash it twice. Also at some point I tried flashing it with a previous firmware version but it seems there's some kind of check and you can only flash newer firmware versions. I do think though that it's somehow connected with the Zigbee2MQTT addon for HA. I just reinstalled the addon - as you can guess it didn't help. I noticed that everytime I try to delete a paired device - there's an exception thrown and I need to check the "force remove button". I really can't think of anything else I can do..
Can you stil control other devices (turn them on/off)? BTW - one thing does pop on my mind - can you verify (redownload) firmware - maybe you flashed router firmware instead of coordinator? Not sure how this would actually work. Just to be on the safe side. github.com/Koenkk/Z-Stack-firmware/blob/master/coordinator/Z-Stack_3.x.0/bin/CC2652RB_coordinator_20230507.zip
Also, what version of Zigbee2MQTT are you on?
About the firmware - yes I double checked that I've installed the coordinator firmware. The weird thing is that I only receive data from paired devices. I have an Aqara FP1 presence sensor and when I try to "reset" it's state through ZigbeetoMQTT's UI it's throwing and exception that the action failed. So any interaction with the devices fails but the paired devices report their state.
I Got this error with Dongle P
s6-rc: info: service banner successfully started
s6-rc: info: service cc2652-flasher: starting
[19:05:26] INFO: cc2652-flasher-up script exited with code 6
s6-rc: warning: unable to start service cc2652-flasher: command exited 6
s6-rc: info: service banner: stopping
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service banner successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Is ZHA disabled (or Zigbee2MQTT) - this looks like problem with access to the stick.
@@BeardedTinker Hey. I figured it out. Had to do a restore. Disable first THEN delete ZHA and it worked. Previously I just disabled ZHA. Apparently that was the issue.
"(Coordinator must be in bootloader mode before addon is started, hold BSL button while plugging into USB) " Written in Documentation of ADD ON. BNT1 button on dongle.
for me the only wich worked with switching also on Last Koenkk Firmware - CC1352P2_CC2652P_other_*.zip
how can i know the next time wich version i got from usb sonof so for now it is this.
yours at custom firmware link i thought there is only one version zigbee plus sonof and that did not work for me zigbee2mqtt would not start any more. so
when i orderd it said SONOFF ZigBee 3.0 USB Dongle Plus, TI CC2652P Coördinator, Universele USB ZigBee Hub so did i choose in the end good
or did i make mistake and need to choose another one.
after swictching also Last Koenkk Firmware - CC1352P2_CC2652P_other_*.zip
now it works is this ok ?.
Did you check the table on GitHub - P dongle needs CC1352P2_CC2652P_launchpad_*.zip - _other_ version is different but if it works for you, go with it. I don't know what's the difference . Botb version - launchpad and other are for CC2652P chipset.
@@BeardedTinker no did not i to be honest i thought sonof there is only the plus and the other and so in the box CC2652P followed your screen and saw it was exact same naming
but in the end there are difference inside usb stick and are not the same
If you try to use Dongle P with firmware for E it would fail, same if you would use Dongle E with firmware for P - so if everything is working for you, it's ok :)