Possible to un-brick a Zooz switch

🛎️ Get Help Devices
1

I very stupidly selected the wrong firmware file for an OTA update with my C7. I selected a ZEN22 firmware file and applied it using the Elevation firmware updater to a ZEN27 switch. Now, it's unresponsive. Is there any chance I can repair the switch?

2

Perhaps @agnes.zooz can help.

1 Like
3

If the device did what it was supposed to do, reject the non-matching firmware, it probably just needs to be power cycled..

3 Likes
4

Maybe I'm wrong in assuming that pulling the air-gap switch would be sufficient to power cycle it, but I did try that.

EDIT to add: I've now power cycled by cutting power to the circuit. No difference.

5

Does it work with manual/physical operation? If so, the switch has factory-reset itself and needs to be added back to Hubitat.

To do so, make sure you first exclude it and then re-include it. If you don't exclude it first, you will be left with a Ghost device that will play havoc with your z-wave mesh.

6

Sadly, it is not responsive to physical interaction.

7

If the wrong firmware is applied, a device can be bricked as we mention in our OTA instructions. @bcopeland can you send us more information what needs to be added on the device side for it to reject the firmware? I haven't seen that on Z-Wave devices in the past so we'd like to learn more and pass it on to our engineers.

2 Likes
8

The device is supposed to verify the firmware file metadata (MFG ID, Firmware ID, Target, Hardware Version) to know if it's valid for that device.. And it will send back an error if it is not valid.. Usually one of these:

        2:"The transferred image does not match the Manufacturer ID",
        3:"The transferred image does not match the Firmware ID",
        4:"The transferred image does not match the Firmware Target",
        5:"Invalid file header information",
        6:"Invalid file header format",
        7:"Insufficient memory",
        8:"The transferred image does not match the Hardware version",
2 Likes
9

The protocol side is pretty well described in SDS13782

And depending on which SDK version each device is using there is documentation on how to handle that on the firmware side..

3 Likes
10

Bryan @bcopeland, you should transfer this info to Inovelli (@Eric_Inovelli) because I bricked one of there dimmers a few weeks back when I got distracted and chose the wrong file when updating it :rage:

11

So, the final answer is No?

I'm comfortable with a command line / terminal. I'm happy to try anything.

12

I bricked an old Inovelli dimmer by applying the wrong update a year or so ago. Luckily, I was somehow able to flash it again with the correct firmware and it recovered. This was a C5 with your community based firmware updater, so maybe not exactly comparable to the others situation.

But apparently this can happen somehow...

13

Well, there has to be a way to do it because, at manufacture, the devices contain no firmware and an initial firmware build must be loaded to make the device operational. Perhaps there is some pin that needs to be shorted to get the initial boot loader going, perhaps using a manufacturing jig.

3 Likes
14

There's definitely a way to do it at the factory :slight_smile: But for OTA, you may need to be able to include/exclude the switch, depending on what state it's in.

@bcopeland thanks for the details, I'll run this by our engineers to make sure we're implementing this feature. I could see how the older models would not fully support it but will double check.

@david.home please get in touch with our support so we can troubleshoot this together and get it resolved for you.

5 Likes