[REQUEST] em3587 Bitronvideo BV 2010/10

[gromgsxr]

are you able to add support for em3587 Bitronvideo BV 2010/10. https://github.com/grobasoz/zigbee-firmware/issues/15 links to the correct firmware and i was able to get it flashed by your code if i edited the pid vid and serial speed to match my stick

originally when i ran the scan i got "vid": "10C4", "pid": "8B34", "deviceType": "unknown"}]} stock speed is 56700 made the edit to ncp.py and i got the current version reported and was able to flash the correct firmware

[Hedda]

I managed to upgrade my BV AV2010/10 USB-Stick with the above linked f/w today i used the walthowd docker image and a bit of editing the npc.py

Maybe best if you also submit pull request for review? -> https://github.com/walthowd/husbzb-firmware/blob/master/ncp.py

[Hedda]

are you able to add support for em3587 Bitronvideo BV 2010/10. grobasoz/zigbee-firmware#15 links to the correct firmware

FYI, "Bitron Video AV2010/10 USB-stick" is also sold as "SMaBiT AV2010/10 USB-stick", more discussion here -> https://github.com/zigpy/bellows/issues/348

Note that this requires defining a baud rate of 115200 instead of 57600 which I believe is the baud rate on the default firmware.

See https://github.com/walthowd/husbzb-firmware/pull/34

[jogethome]

@gromgsxr , could you please explain, what you've changed in npc.py to get the scan successfully working with the BV 2010/10? I tried also to add the obvious lines but stuck when reading the version info. There's an exception right after

EZSP Configuration Frame: getValue ID: 0xAA

...

ser.write(b'\x7D\x31\x43\x21\x02\x45\x85\xB2\x7E')

EZSP Response Frame: getValue ID: 0xAA

...

versioninfo = trans(ser.read(16)[1:])[5:]

These are the exceptions I get: Exception: <class 'NameError'> /dev/ttyUSB0 Exception: <class 'IndexError'> /dev/ttyAMA0

and the type is empty. Thanks for helping

[gromgsxr]

i edited the sonoff section to match the correct pid and vid for the binnatron stick after that it was able to read the firmware version on the stick and also flash the file

ITEAD/SONOFF EFR32 USB Stick

SONOFF_VID = '10C4' SONOFF_PID = '8B34' SONOFF_BAUD = 57600 SONOFF_XON_XOFF = True SONOFF_RTS_CTS = False

i had to edit the baud rate to 115200 after to confirm the firmware had updated as the version i used changes the speed

[jogethome]

Wow, that's a fast answere, thanks :-) I added a couple of more lines with extra handling of BITRON .. but this is of course faster. I'll try this. What firmeware did you use, might the NCP_USW_EM3587_6710-LR.ebl from grobasoz the right one (quite new, 3 weeks) ?

[gromgsxr]

there is a link in my first post ta a thread where i found the file. its NCP_USW_EM3587-LR_678-115k2.ebl

[jogethome]

ok, it would have been a surprise to me.... the same error. There must be something else wrong with the Response. I have got the Firmeware 5.8.0.0 on the stick, that's what is shown in compination of vendor id 4292.0 and produkt id 35636.0 by Openhab 3.2 Do you till have the information what was on yours before the flash? Maybe that would explain the difference.

[gromgsxr]

stock was 5.8.0.0 and upgraded to 6.7.8-373

[gromgsxr]

vendor id 4292 is 10C4 in hex and 35636 is 8B34 in hex so same pid and vid. i attempted to make a pull request adding support for the stick

[jogethome]

ouh yes, than there must be different environmental source of the problem, like version of python, xmodem and/or other imports. Probably also the fact that it is currently already bound/linked in Openhab (successfully but not really working with ZIGBEE 3.0 items). I will try to flash the firmware you mention and if I brick the device I will buy another model :-) If it will work I will give a note here. Thanks for helping out

[gromgsxr]

The only thing that may cause problems if you update is the new baud rate as stock it 57600 and the firmware I used was 115200 I don't use openhab so can't comment there. In homeassistant I had to edit the baud to match the new file though

[jogethome]

That would be possible in Openhab too I guess. But I guess I'll give the other one a try, the one I mentioned

[gromgsxr]

the version you mentioned flashes to my stick ok i didn't test if it actually works though, and i was able to flash it back the the one i had mentioned

[jogethome]

the version I was trying was successfully flashed to the stick, even the version came back now with the scan option. However in Openhab this was not working somehow. Before starting with all the configuraton combinations I tried your first proposal with the 115k ebl file. The flashing worked too and this time the operation inside openhab is still making problems but not as much as the other version before. I guess this is related to openhab. During scan of the network for new "things" to bind it seems that the coordinator is somehow falling back to 56k and this on the other side does a knock out of the flashed firmware and it goes offline. However switching manually back to 115k brings it back. The scanning does not work but for now at least a couple of "things" (not all but some) just came back by its own into the openhab "inbox". Strange behaviour.... I'll keep on testing, however this is quite nerving

[jogethome]

ok, my problem seems to be experienced already by others. https://community.openhab.org/t/firmware-upgrade-the-bitronvideo-bv-2010-10-zigbee-usb-dongle/128879/7 Chris Jackson has obviously implemented a fix in the Openhab Zigbee binding ... so I have to find out how to update this

[Elix-g]

I'm using some Zigbee dongle "BitronVideo AV2010/10", which reports "(Silicon Labs) BV 2010/10" as USB device name and its ID is 10c4:8b34. The stick is sold by German Telekom as accessory for their QIVICON 1 Home Base. Besides, the stick is sold under BitronVideos new company name "SmaBit".

I was finally able to update the stock firmware 5.8.0-134 using update-firmware.sh successfully to 6.7.10. Thanks a lot for your great work! I've also edited ncp.py slightly in order to detect the stick and read out the stack version properly. After that, I took the risk and updated directly to version 6.7.10 which has been made available by grobasoz:

https://github.com/grobasoz/zigbee-firmware/blob/master/EM3587/NCP_USW_EM3587_6710-LR.ebl

The dongle so far works smoothly with both bellows and OpenHab. It's indeed just required to define a baud rate of 115200 instead of 57600. In OpenHab, I've got similar issues like jogethome described above but that seems to be an issue in OpenHab indeed. It's not that the coordinator drops to 57600. It's the "Thing" configuration in OpenHab which changes when scanning for devices. As a result, OpenHab cannot communicate with the stick anymore. No hardware issue!

[NilsOF]

openHAB 3.2.0 stable should have the baud rate bug fix. This bug existed in snapshots a week or something before it was fixed just before 3.2 RC1. Fyi: openHAB has a built in coordinator firmware updater in the "openhab-console".

[gromgsxr]

Don't use openhab I submitted a pull requests to add support for this device on this repo

[cz6ace]

@gromgsxr , I used the latest snapshot of OpenHab 3.3 and I missed your note to not use that. I did use, it said upgrade started and then nothing happened for fewminutes. After that I restarted OH, changed to 115200 and it started working. So it works. I can also confirm that it solved issue with IKEA Tradfri E14 407lm bulb in compare to stock FW of BitronVideo. I tried only the IKEA bulb, the rest of house still running with other stock BV USB stick.

[cz6ace]

after two weeks I can say the used FW works with my other ZigBee devices OSRAM+ sockets, bulbs, Tuya PIR, IKEA bulbs, Mueller Licht bulbs.

[Hedda]

FYI, more users confirm EmberZNet 6.7.10 firmware working good on EM3587 here -> https://github.com/grobasoz/zigbee-firmware/issues/15