2nd stick also bricked - UZB firmware 5.36 update failed. Device is bricked. Return to seller

Discussions about Z-Way software and Z-Wave technology in general
ypoosn
Posts: 4
Joined: 31 Jul 2019 22:53

2nd stick also bricked - UZB firmware 5.36 update failed. Device is bricked. Return to seller

Post by ypoosn »

Hi,

I tried to update the firmware of the UZB-Stick ZMEEUZBB 5.27 to the latest version
Unfortunately the update failed and the device is not recognized anymore. Neither
using Linux (Raspberry) nor Windows. The blue LED is not blinking anymore
when inserted into the USB slot.

Please find attached the logfile of this update disaster.


Is there any alternative way to reset the stick?



best,

ypoosn
Attachments
updatelog.txt.bz2
z-way logfiles of update
(235.24 KiB) Downloaded 272 times
Last edited by ypoosn on 02 Aug 2019 00:59, edited 3 times in total.
User avatar
PoltoS
Posts: 7571
Joined: 26 Jan 2011 19:36

Re: UZB firmware update failed. Device not recognized anymore

Post by PoltoS »

Hello!

Sorry to inform you, but there is a known issue in some UZB manufactured by our partners on license base that after upgrade they become bricked.

If dmesg do not show CDC-ACM device, then you should replace it with your seller or with Z-Wave Europe.

Sorry for this.

Make sure to keep files on your SD card to restore the backup
ypoosn
Posts: 4
Joined: 31 Jul 2019 22:53

Re: UZB firmware update failed. Device not recognized anymore

Post by ypoosn »

Hi,

thanks for your quick reply. Okay, device is bricked ;-(

The device has the S/N 04/19 01 and the label ZMEEUUZBB and was bought from Amazon
a few days ago.

Is there a chance to identify the devices that cannot be updated? I am not sure how
many bricked devices I can sent back to them?

An older device I have has the label ZMEEUZB1 with some "real" SN and some older FW 5.07. Is this device
updatable?

thanks in advance.

ypoosn
User avatar
PoltoS
Posts: 7571
Joined: 26 Jan 2011 19:36

Re: UZB firmware update failed. Device not recognized anymore

Post by PoltoS »

Is there a chance to identify the devices that cannot be updated? I am not sure how
many bricked devices I can sent back to them?
Unfortunatelly no ;( Even we do not know it. There was some small percentage during few years. This was found this spring only. It was a programming issue due to programmer error.
ypoosn
Posts: 4
Joined: 31 Jul 2019 22:53

2nd stick also bricked

Post by ypoosn »

Hi,

some really bad news. The replacement stick that Amazon send me also bricked.
It shows the same label with serial S/N 04.19.01 and had firmware 5.27 installed.
bf8b5d98-00b2-4a20-ad3a-a31c307b0321.jpg
bf8b5d98-00b2-4a20-ad3a-a31c307b0321.jpg (3.92 KiB) Viewed 8842 times
I will return it to Amazon and request a refund.

The good news is that I was able to update my "old" stick with some real sn to
5.36 without any problem.

Any reliable seller that is offering updateble sticks in Germany?

best,

ypoosn
Attachments
updatebrick.log.bz2
(239.05 KiB) Downloaded 255 times
User avatar
aLiEnHeAd
Posts: 136
Joined: 02 Feb 2017 15:09

Re: 2nd stick also bricked

Post by aLiEnHeAd »

ypoosn wrote:
02 Aug 2019 00:04
Any reliable seller that is offering updateble sticks in Germany?
https://www.notebooksbilliger.de/produkte/ZMEEUZBB
is currently selling the stick for 19,95€ (CODE: BWNBBZWAVE)

But I don't know if it's the right (i.e. updateable) one...
I think there is no other way but try and if it's the wrong version to send it back :?
ypoosn
Posts: 4
Joined: 31 Jul 2019 22:53

Re: 2nd stick also bricked

Post by ypoosn »

aLiEnHeAd wrote:
02 Aug 2019 12:33
https://www.notebooksbilliger.de/produkte/ZMEEUZBB
is currently selling the stick for 19,95€ (CODE: BWNBBZWAVE)

But I don't know if it's the right (i.e. updateable) one...
I think there is no other way but try and if it's the wrong version to send it back :?
Thanks for the hint I ordered the stick from notebooksbilliger. The sticks looks like the previous ones
(see photo above) that get bricked before. Firmware is also 5.27.

Any official comment from z-wave.me whether I should try again? It could become a hat trick and then I question
if "There was some small percentage during few years" is still true. Maybe a different problem with newer versions
of the stick and firmware 5.27 on the raspberry platform?

5.36 is offered as upgrade and 5.23 as downgrade when typing in the access token "all"
Shall I try to downgrade to 5.23 first and the upgrade to 5.36?

Any hint or response from official side is appreciated.

best,
ypoosn
User avatar
PoltoS
Posts: 7571
Joined: 26 Jan 2011 19:36

Re: 2nd stick also bricked - UZB firmware 5.36 update failed. Device is bricked. Return to seller

Post by PoltoS »

The upgrade bricks them due to a problem with dongle. Unfortunately we don't know exactly how many are affected. They were manufactured by our partner under license agreement and it is hard for us to estimate the real situation.

Better to buy from another one to have another batch
CharlesCY
Posts: 1
Joined: 13 May 2020 00:01

Re: 2nd stick also bricked - UZB firmware 5.36 update failed. Device is bricked. Return to seller

Post by CharlesCY »

PoltoS wrote:
05 Aug 2019 23:18
The upgrade bricks them due to a problem with dongle. Unfortunately we don't know exactly how many are affected. They were manufactured by our partner under license agreement and it is hard for us to estimate the real situation.

Better to buy from another one to have another batch
Apologies for jumping in an oldish thread. I'm a Z-Wave newbie!
I have just bricked mine after firmware update on Z-Wave server. S/N 04.19.01. No blue light, dead.

Just ordered two ZMEEUZB1, one as spare but noticed the one I bricked is ZMEEUZBB which came with a Homeseer Z-NET from Vesternet. Is there a difference between them?

Thanks
Charles
User avatar
PoltoS
Posts: 7571
Joined: 26 Jan 2011 19:36

Re: 2nd stick also bricked - UZB firmware 5.36 update failed. Device is bricked. Return to seller

Post by PoltoS »

The ZMEEUZBB was some re-labeling made by Z-Wave Europe. I expect it was a UZB with license included, but not sure.
Post Reply