Hmm - I seem to have bought an older version. The one I ordered sounds like yours (here), but the one that was delivered is plain white on one side and has a serial no, “QIVICAN ZigBee Stick” and a UK address on the other.
Just watched the Mixtile video it looks really good and I hope that it almost becomes a dumb hub which can just pass everything onto Hass. I saw them using Xiaomi/Aqura sensors in their promo video guess the cracked the Xiaomi protocol?
Has anyone had success in flashing an EZSP-capable firmware to the Qivicon/DT stick?
@Frank thanks for the guide. I’m able to do everything, except actually flash the firmware. I’ve tried doing it in Windows and Linux, but results are the same. It seems that the stick aborts the XModem upload immediately.
ATI
Telegesis ETRX357
R309C-DTAG build12S
000D6F000B30323D
OK
AT+BLOAD
ETRX357 Serial Bootloader v8001.02.01
1. upload ebl
2. run
3. ebl info
BL > 3
Telegesis AT-Commandset R309
ETRX357 Serial Bootloader v8001.02.01
1. upload ebl
2. run
3. ebl info
BL > 1
begin upload
CC
+-----------[xmodem upload - Press CTRL-C to quit]------------+
|Sending em357-ncp-uart-xon-xoff-use-with-serial-uart-bl-500.e|
|bl, 909 blocks: Give your local XMODEM receive command now. |
|Xmodem sectors/kbytes sent: 0/ 0kRetry 0: Cancelled |
| |
|Transfer incomplete |
| |
| READY: press any key to continue... |
+-------------------------------------------------------------+
I’m trying to get the same stick working in a virtualbox ubuntu installation (windows host) and I can’t add it. It doesn’t see it and the only manual thing telegenesis option is the ETRX3.
In windows it doesn’t do anything so I found out afterwards that it is clearly specified here that it only works in linux but how? and who made it work? who added it to the list?
There are at least two versions of the Qivicon stick. I bought one several month ago, and it was 10 min to flash it. I bought another stick for development later one and never made it to flash it. Same error as yours, xmodem upload failed.
Hmm, did this, and I think I bricked it.
The small red light does not come back on.
It is being detected as connected nu dmesg.
But I can’t reach it with mincom.
Same here. It all seemed to go fine and it uploaded the image. However when it finished the xmodem upload it sent garbage characters to the console. Then when I closed the connection and replugged in the stick the light would not come back on and it is not accepting a serial connection.
For anyone else think about trying this, pretty sure I bricked mine as well. FWIW it is an ETRX357USB-LRS not an ETRX357USB-LRS+8M, so that might have been the issue, but proceed with caution.
I just had to add the integration manually through the webui, as it was not auto-discovered (likely because I run HA under docker, even though I added “–device=/dev/ttyUSB0” to the “docker run”)
After your comments I ordered one from amazon.de but have no success with it what of course could be my fault because I’m totally new with Zigbee devices.
Could you please help me a little bit on it?
I wrote every aspect of my experiments here:
And for the proper communication, my device is this one:
[ 2.855187] usb 1-3: new full-speed USB device number 3 using xhci_hcd
[ 3.005948] usb 1-3: New USB device found, idVendor=10c4, idProduct=8b34, bcdDevice= 1.00
[ 3.005950] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.005951] usb 1-3: Product: BV 2010/10
[ 3.005951] usb 1-3: Manufacturer: Silicon Labs
[ 3.005952] usb 1-3: SerialNumber: 0137F05F
[ 19.445852] usb 1-3: cp210x converter now attached to ttyUSB0