Any information or help would be appreciated.
Zooz support is great, just saying.
2 Likes
@Chippy111 Unlikely it would have bricked it or even uploaded in the first place because of the CRC type checks that are done when trying to push it to the device. I don't even think if you cut it off half way that will do anything as internally it has to confirm beginning and end are there before applying.
1 Like
Like @rlithgow1 says I don't think it will let you do that. I am pretty sure I did it a while back. In my case it was to my ZEN power switch. As mentioned, I believe it indicated there was a incorrect CRC and didn't do anything.
CRC checks for the file data integrity and has nothing to do with the device.
A device Strap Bits are used to make sure a correct file is loaded for the specific device.
Did it complete with a success message or did it error out? Does the switch still power up?
I think the intention is that the device should confirm it is the correct firmware before applying, but that may very well be up to the firmware itself. If they don't have any safeguards in place then yes you possibly bricked it. Probably more like a soft-brick, as in if you were to somehow connect to the chip/board and flash it directly it may be restorable.
Right but I was trying to simplify the terminology for the user and the relationship to the device. Point still stands, if the firmware isn't correct, the device shouldn't accept it.
I did this a while ago and burned the wrong firmware to an ZSE44 (with some other Zooz product firmware, don't remember which) and it finished okay. After that, I could never get it to come alive again. Wound up buying another ZSE44.
OK. But sometime simplification creates more unnecessary confusions.
1 Like
This means Zooz did not use a device protection mechanism.
The device still could be recovered with the low level programming tools.
But this process is very complicated for the end users.
1 Like
Fair enough
This is what I imagine happened to me.
It went through no issues.
Didn’t realize it until later when the color on the led was a weird greenish white.
Is it worth trying to see if their 5 year warranty covers this or am I SOL?
You can ask, they might replace just to be nice if its the first time you are asking for a warranty.
I don't understand why the firmware does not check that its for the correct device before applying, seems like a no brainer to do but maybe it is not easily achievable. There have been other stories on here of zigbee and zwave devices allowing incorrect firmware to brick devices. One of the HE devs had replied on a zigbee related thread thinking that should not even be possible, the device should block it, but here we are...
1 Like
No dice.
Update your firmware at your own risk, etc. etc.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
