2.3.8.140 seems stuck in an update loop?

[danabw]

Under the category might help, won't hurt...

• Clear cache in your browser (depending on what you're using interweb will have instructions)
• Re-do the download of the platform version via the endpoint /hub/advanced/downloadPlatform/234
• Cross fingers

[jonnyborbs]

Yeah man, appreciate that but I’ve tried all those already. The platform download endpoint spun for a while and then timed out. It can’t be browser cache as I’ve tried 3 or 4 across multiple computers. Crossing fingers was the first act

[jtp10181]

I wonder if the soft reset with logs purge indicated here would help clear things out better to get it updated? @bobbyD thoughts on why he cannot update?

I read the post again and there are instructions in there for if you are unable to update!

Urgent Z-Wave Logging issue identified in platform version 2.3.8

Our engineers have identified an issue with Z-Wave logging that could potentially cause the hub to lock up. This issue occurs ONLY in systems that experience Z-Wave problems, and was introduced with platform version 2.3.8. A fix was released on Friday with update version 2.3.8.140. If you didn't update yet, we urge you to do so at your earliest convenience. If you are unable to update, or if your hub is already locked up, please follow below steps in your troubleshooting efforts: Revert to v…

[jonnyborbs]

Hmmmm - I will give this a shot this evening. I’m not sure if I’m seeing the symptoms of the z-wave lockup (I have had the hub hard lock a few times recently, so maybe)

Thanks for the pointer though, another thing to test! I was also kinda wondering at this point if waiting til .141 (or just .next) would fix this for me too. Either way the help is very appreciated

[bobbyD]

@jonnyborbs

Now I see it download, verify, extract, and then give this “download failed” message.

This sounds more like a network problem. Do you use any special firewalls, firewall rules? Mind sharing more about your network?

[bobbyD]

@jonnyborbs

I’m not sure if I’m seeing the symptoms of the z-wave lockup (I have had the hub hard lock a few times recently, so maybe)

It's worth a shot to eliminate that possibility. Please go to the following end point: yourHubIP*/hub/zwaveDebugDisable then reboot the hub

*yourHubIP - use your actual IP address as assigned by your router

[jonnyborbs]

This did it! I used the instructions in the link above to revert to 2.3.7, hit the zWaveDebugDisable endpoint, did a reboot with a rebuild and log purge, then it took 2.3.8.140 no problem!

@bobbyD do I need to do anything to re-enable zWaveDebug after this process or is it fine as it is?

Thanks so much to everyone who pitched in here. Appreciate that nobody just went straight to "RTFM" as I just hadn't seen this link that ended up being so helpful

[bobbyD]

@jonnyborbs

anything to re-enable zWaveDebug after this process or is it fine as it is

Glad it worked. And no, you do not need to do anything to re-enable the logging. It was turned on in our effort to get to the bottom of some edge case Z-Wave issues.

[Owen]

Just to add I had the same problem (extracting update -> download failed) and this worked for me too:
yourHubIP*/hub/zwaveDebugDisable
I was not able to update for a long time and was stuck on 2.3.8.123. I ran the above, rebooted (with DB rebuild/log purge) and it updated fine after that. Thanks.