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 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:

  1. Revert to version 2.3.7 from the Diagnostic Tool
  2. Go to the following end point: yourHubIP*/hub/zwaveDebugDisable
  3. Reboot the hub

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

If you continue to have problems after performing the above steps, then try the following:

  1. Perform a Soft Reset by following instructions in this [document]
  2. Be sure to check the "Also clear past logs" option

If all efforts fail, and you are current Hub Protect subscriber, then performing a Full Reset and restoring a cloud back would resolve the issue.

We are very sorry for the inconvenience that this may have caused to you or your family.