I must have missed the change of repo for the add-on! Thanks seems to be working now.
Hopefully the new dongle wont still keep losing connection every couple days!
1 Like
FYI, not confirmed but someone now claims Auto-BSL is also working in the ZigStar GW Multi tool too:
1 Like
I bought one of these dongles as my first foray into Zigbee having only started with HA about 9 months ago and only used WiFi devices before now. My HA runs as a VirtualBox VM on a Windows host and I’ve been able to pass through USB to connect the dongle to the HA VM and ZHA detects it OK from within HA. All good so far, this it where it all unravels though.
I have 3 Sonoff Zigbee devices, two motion sensors and a door sensor, all battery powered. When I put them in pairing mode ZHA seems extremely hit and miss whether it detects the device or not despite only being 1 plasterboard wall and about 3m from the dongle. Having added all 3 again last night after reinstalling the integration from scratch just in case, by this morning 2 of the devices reported as “unavailable”. I then moved the sensors so they sat within 20cm of the dongle and although one sensor then reconnected the other stays “unavailable”. What’s more the door sensor that is back online continually reports 2% battery despite the battery having 3.2v tested and having swapped it for another new battery just in case.
My host PC is fairly close to my main Asus WiFi router so could be a source of interference but I’ve connected it to a 2m USB extension lead to get it as far away as practical, surely connectivity shouldn’t be this flaky should it? Is there a chance I’ve got a faulty aerial on the dongle perhaps?
I have a similar setup except I’m using ESXi that also sits next to my ASUS router. My first suggestion is to upgrade the firmware to the latest. I’m running the latest dev version. The firmware that is pre-flashed may not be that great. There is a YouTube vid a few post up that shows the process if you are not familiar. After that try increasing the tx. I was getting a big delay with the default tx. Changing mine to tx 10 helped a great deal. Instructions for that is posted before the YouTube vid about the firmware update. Another thing to check is the make sure your wifi and zigbee network are not using the same channel. I use Zigbee2mqtt and that defaults to channel 11. I assume zha does as well. Hope that helps.
2 Likes
If only using Xiaomi/Aqara and Tuya sensors without any Zigbee Router devices then yes they can be unreliable, especially during pairing. Suggest update coordinator firmware first then follow all these tips:
https://github.com/home-assistant/home-assistant.io/pull/18864 → https://github.com/home-assistant/home-assistant.io/pull/18864/commits/b21c49589d898d60a1a235afa7b9c148d013cfee
and
If you are still having problems after following all that (preferably including adding at a few known good mains-powered Zigbee devices) then I too would assume that your problem is faulty antenna or dongle.
The tx_power in the latest firmware is already set to +9 dBm as default so that should best for most scenarios. Increasing tx_power to more than that you might actually get a worse result because it will only make the coordinator “shout louder” and not “listen better” so it can get issues receiving instead.
Note! Recommendation is to change channel on Wi-Fi routers/APs, and not changing Zigbee channel. Reason for that is that some Zigbee devices will not pair and/or communicate on all Zigbee channels.
1 Like
Complete Idiot that I am I inadvertently flash the wrong firmware to my Sonoff USB Plus stick, im getting the following on checking dmesg, but when i try and flash using llama or ccbsl i get the 55 error. (I’ve tried the boot button aswell)
I assume the device is dead unless i can reflash using the special TI cjtag debugger? I have a CCdebugger for my old stick but i assume thats no good?
cp210x 1-4:1.0: device disconnected
usb 1-4: new full-speed USB device number 14 using xhci_hcd
usb 1-4: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-4: Product: Sonoff Zigbee 3.0 USB Dongle Plus
usb 1-4: Manufacturer: ITead
usb 1-4: SerialNumber: 1ea97fabbf19ec118dc37fe5f01c6278
cp210x 1-4:1.0: cp210x converter detected
usb 1-4: cp210x converter now attached to ttyUSB3
Yes and yes, you will need another type of debugger probe to unbrick CC2652 and CC1352 chips, see:
and
FYI, FCC leak show CC2652P and ESP32 based Sonoff ZBBridge-P v1.1 Zigbee Bridge coming soon.
Many thanks @billyjoebob999 @Hedda
I’ve updated the firmware this evening using the video guide (via Windows) to CC1352P2_CC2652P_launchpad_coordinator_20211217. I’ve also checked my 2.4ghz Wifi channel which is on channel 1 and there’s no other detectable WiFi from neighbours etc on any other channel when using a wifi scanner app on my phone. Despite all that there’s no improvement unfortunately. I’ve tried re-pairing one of the sensors whilst sitting it right next to the dongle and it’s still not being detected and with the one device I do still have connected if I move it more than a couple of metres away it becomes unavailable. I’ve also tried an alternative wireless screw on aerial just in case there’s a fault with the one supplied but that didn’t improve things either so I’m becoming more and more convinced there’s some kind of hardware issue going on here.
Is there an easy way I can test the dongle and connectivity to a sensor from my Windows laptop so I can be in a completely different part of the house, just in case it is something to do with it’s current location?
You can install Zigbee2mqtt on Windows:
https://www.zigbee2mqtt.io/guide/installation/04_windows.html#installing
2 Likes
Has anyone had success with changing the IEEE address on this adaptor? I get a good message when trying, but when I plug in my adaptor it fails to work with my existing devices.
aneisch@Weasel cc2538-bsl % ./cc2538-bsl.py --bootloader-sonoff-usb -ewv --ieee-address 00:12:4b:00:18:e3:1f:3c ~/Desktop/CC1352P2_CC2652P_launchpad_coordinator_20211217.hex
sonoff
Opening port /dev/tty.SLAB_USBtoUART, baud 500000
Reading data from /Users/aneisch/Desktop/CC1352P2_CC2652P_launchpad_coordinator_20211217.hex
Your firmware looks like an Intel Hex file
Connecting to target...
CC1350 PG2.0 (7x7mm): 352KB Flash, 20KB SRAM, CCFG.BL_CONFIG at 0x00057FD8
Primary IEEE Address: 00:12:4B:00:24:C0:86:83
Performing mass erase
Erasing all main bank flash sectors
Erase done
Writing 360448 bytes starting at address 0x00000000
Write 104 bytes at 0x00057F980
Write done
Verifying by comparing CRC32 calculations.
Verified (match: 0xba5c19c5)
Setting IEEE address to 00:12:4b:00:18:e3:1f:3c
Writing 8 bytes starting at address 0x00057FC8
Write 8 bytes at 0x00057FC8
Set address done
Never needed to change the IEEE address 
Did you have to re-pair?
No, I’m using z2m
are you using zigbee2mqtt?
No, ZHA (unfortunately it seems)
1 Like
Not sure if it matters but maybe need to use all upper-case capital letters when entering IEEE address?
I have not tried to change IEEE address myself either but see in the respons that at least the letters your old IEEE address was written in all upper-case capital letters (and not in lower-case letters).
Yet it looks like you are trying setting the new IEEE address with lower-case letters.
Hello
I think I have a problem with the stick → I want to switch from Conbee to the Sonoff stick but unfortunately the reception is now much worse
LQI with Conbee +200
LQI with Sonoff 50
Fimware is the current and the transmit power is 9
Do you have a solution for me?
1 Like
I received my new Sonoff stick and upgraded the firmware. I will be migrating from a HUSBZB-1 and I am hoping that someone can help guide me with the process. I have about 50 devices that I do not mind repairing as the backup and restore procedures that I have seen on these forums is a bit too much for me.
I know that I can do it the long way:
- remove all of my entities and devices
- remove the ZHA integration
- unplug the HUSBZB old stick
- plug in the new Sonoff stick, let it auto discover the USB path or define it manually
- re-add the ZHA integration
- pair each device and then rename all of the entities to their previous names.
Is there a shortcut? Can I remove the ZHA integration without removing all of the device and entities and then when I add the new stick and re-pair the devices will the device and entity names be retained?
thanks for any help!
The shortcut is the backup and restore method that you do not want to do, though it is really not hard as basically you perform backup to a file with a “bellows” CLI-command then restore from that file with “zigpy-znp” CLI-command before changing to ZNP config to use other dongle seral-port and zigpy-znp:
https://github.com/zigpy/zigpy/wiki/Coordinator-Backup-and-Migration