Z-Wave firmware on C7. ERROR: This firmware target is not upgradable

This makes a lot of sense...nice brain work. :slight_smile:

If by endpoint, you are referring to the firmware download location, I'm thinking not. Yesterday when I tried the firmware update, before it failed, it downloaded the file, completed the CRC check, attempted to start the update then failed. I just tried it again and got the same result. Any further attempts just fail immediately - I’m guessing because the file is already downloaded.

1 Like

In that post "endpoint" means the URL the hub is hitting to try to do the Z-Wave FW update...not the FW download location.

Not clear, did you try above? That should resolve your issue, based on feedback from HE staff that @jtp10181 sought out.

Bit the bullet and tried it... no go even after restoring old firmware

i have hub protect.. maybe i can get it replaced. but unfort. we will not be at that location till the beginning of april?

1 Like

That's after falling back to 2.3.6, right? Bummer, that looked like a good path.

unfort. also that is why i didnt want to do this.. i now lost control of the 1 remaining zwave device the door lock.. nothing works and i am not there to re-pair it.. sigh.

1 Like

Not sure why you would need re pair a zwave device just because the firmware updated refused to go? I thought you had a way to power cycle the hub remotely?

So after the Z-Wave update attempt the lock became uncontrollable? Bummer. I assume you've tried the off/remove power/wait/restart remotely? Or do you not have that hub on a wi-fi plug yet?

Yes i can power remotely. I did try shutdown wait reboot device still shows no route. And no zwave messages and re-pair fails

1 Like

Came back this morn. When the renter must have manually opened the.lock. weird.i can get responses from the lock but not.send to.it. literally 15 ft from hub. Will research more when back at the condo. Hopefully fw update issue resolved b4 then.

A couple of notes:

  1. I too am apprehensive about downgrading firmware.
  2. If I understand what I’ve read correctly, @kahn-hubitat, if you have hub protect, you should be able to restore your z wave chip to a known good backup - if you have one. Am I mistaken here?
  3. I’ve been trying to wrap my head around installing a separately and reliably controlled device to power cycle the C7. The concept of a WIFI plug makes sense… but since I was out of available outlets on my rack mounted UPS’s and my rack mount PDU, I just temporarily powered the C7 off one of my RPIs’ usb ports - which has outside SSH access. Just wrote a quick script to shutdown the USB ports on the RPI and bring them up 90 seconds later so I may keep it that way for a while. Thanks for the inspiration!
  4. Since I did a clean repair followed by a power cycle two nights ago, my z wave table hasn’t emptied. I hope I didn’t just jinx myself!!! OFC, today I disrupted my runtime as I came up with a power cycle approach.
  5. QUESTION - does the C8 Pro have to be power cycled if the z wave table goes empty or the z wave chip wigs out? Or does it have the ability to reset power to the chip through a restart or through the UI/Software? I’m thinking about upgrading/migrating for the extended range, but was curious.

Again, just a noob here, so I apologize for any ignorance as I try to catch up. New to HE, but been into Zwave Automation for 15+ years - since the early days of Vera.

It seems that the downgrade does not solve the issue anyway so probably not worth trying any further.

This has nothing to do with the z-wave firmware update? The Update will not fix this I do not think.

Yes, same as a C7

I read a suggestion on another thread about empty zwave tables on here - I believe by an “ambassador” - that upgrading the firmware may fix the empty table. That’s why I ended up here in the first place.

That said, is an empty zwave table a usual occurrence? Or should I just chock that up to the heavy resource loads I was probably applying as I quickly built my network?

HE staff is actively working on an update to resolve this issue - I think the best approach at the moment is to sit tight. I know, hard to do... :wink:

1 Like

No, usually happens if zwave crashes. If it happens regularly there is a problem somewhere on the mesh.

I think you may be right though now that I think about it, that getting it updated may help. With the old zwave firmware it does not take much to overload the mesh due to some underlying issues that got fixed in newer versions.

2 Likes

A post was split to a new topic: ZEN34 Firmware update stuck

I assume nothing in the new hub firmware update to address this issue?

I tried the new 122 update this morning which per the release notes should fix this issue. Unfortunately, I got the same results/error.

@kahn-hubitat , have you tried the update, and if so, was it successful for you?

contact @bobbyD for instructions.. the update just enables it but there are specific steps to download certain files to get it to update.

1 Like