500: Internal Server Error. How to fix it? (March 2019)

[Brad_ST (Brad)]

I removed the “ghost node” though it wasn’t likely causing an issue.

Neither of the errors from 0C in the network repair are inherently bad - “Could not assign new route” and “Could not delete old routes”. JD expands on it here:

FAQ: Zwave repair not working (how to fix error messages)

When you run a zwave repair, The hub goes through its device table and attempts to contact each device and ask them who their current neighbors are. The hub then takes all of this information together and calculate some optimal routes in advance. It sends this routing information back to each individual device, just The part that applies to that specific device. So each device ends up with a partial routing table. All of this should make routing faster and more efficient. So in a sense the hub asks a question, the node answers, and then the hub sends out a New map for the node to use. The two common error messages that you will see are “Failed to update mesh information.” This means the node didn’t answer the first question. It didn’t send back the list of its neighbors. That might …

The offline devices don’t look like they are reporting all of the states they should be. I would exclude and re-add them.