Since upgrading to 2.2.4.153, I'm observing that I get the dreaded "Z-Wave Network responded with Busy message." error for some time after hub startup. Curiously, it appears to be in 20 second intervals:
sys:12020-12-02 04:16:58.906 pm warnZ-Wave Network responded with Busy message.
sys:12020-12-02 04:16:38.904 pm warnZ-Wave Network responded with Busy message.
sys:12020-12-02 04:16:18.869 pm warnZ-Wave Network responded with Busy message.
sys:12020-12-02 04:15:58.855 pm warnZ-Wave Network responded with Busy message.
sys:12020-12-02 04:15:38.837 pm warnZ-Wave Network responded with Busy message.
sys:12020-12-02 04:15:18.822 pm warnZ-Wave Network responded with Busy message.
sys:12020-12-02 04:14:58.820 pm warnZ-Wave Network responded with Busy message.
sys:12020-12-02 04:14:38.778 pm warnZ-Wave Network responded with Busy message.
sys:12020-12-02 04:14:18.767 pm warnZ-Wave Network responded with Busy message.
sys:12020-12-02 04:13:58.759 pm warnZ-Wave Network responded with Busy message.
sys:12020-12-02 04:13:38.740 pm warnZ-Wave Network responded with Busy message.
sys:12020-12-02 04:13:18.723 pm warnZ-Wave Network responded with Busy message.
sys:12020-12-02 04:12:58.704 pm warnZ-Wave Network responded with Busy message.
--- Live Log Started, waiting for events --
While this is happening, it appears the hub can receive but not send. For example, I can use a switch (Zwave) to control my lights (CoCoHue integration->Zigbee).
The last couple of shutdown/power up cycles I did it seemed to stop after roughly 5 minutes. Of course, as I type this up, it's been going for 13 minutes already. So perhaps there's something I did to break the cycle -- I am in the middle of a ton of Zwave exclude/includes.
-jd