My system is seeing extreme sluggish behavior often accompanied by numerous device time out/Z-Wave power cycle events. They occur randomly, but cluster around times when multiple devices are being controlled. In the hub event log devices will show as timing out, however they will respond quickly following the reboot and work fine when controlled the next time.

Z-Wave association mode isn’t reliably working either. I have to reboot the hub after each device is added in order to be able to add another one.

This is just from turning on a hall light and unlocking the front door. Both devices work fine when controlled on their own.

I am sorry you are experiencing issues. I am going to look at hub logs, and be in touch with you. I am seeing some network repair failures currently happening, but would like to know what has led to power cycle issues (we power cycle the Z-Wave chip if the Z-Wave chip becomes unresponsive to commands).

After looking at the hub logs (only a limited amount of logs available and for a given period), it seems about 7 Hours ago, a network repair was initiated, and it was just finished. When network repair is in progress, it restricts lots of functionality such as sending packets to the nodes on the network.

I suggest re-cycling your hub (thus causing a reset on the z-wave chip) and reporting if similar issues occur.

I will be watching your hub closely for any sign of issues in the meantime.

Now that the repair has finished I am still seeing numerous Z-wave power resets, often without any device co troll activity occurring. Would you like me to reboot the hub now or will that wipe any logs?

As of right now, I am not sure if resetting the chip through a power cycle will help with this issue you are experiencing.

Hopefully once i get to the office tomorrow, I can try to reproduce this issue and find a work around. I am not too worried about the resets if the chip is hung up, the only thing i’d like to avoid is having to drop messages as a result of reset.

I found what is causing this issue, we fixed an issue in 18.22, but that fix exposes an issue that is documented by the Z-Wave Firmware (rarely ran into it because of another issue, interesting how that works, right?). Should have a fix for that pretty much soon, and we will keep you updated when the fix will go out

19.13 appears to almost have solved the problem. It is much better than it was as the frequency has been reduced. However looking at the event log since the update pushed through I’m still seeing random power cycle events without any explanation.

I rebooted your z-wave just now, turned on some extra logging to capture the traffic with the Z-Wave chip.

The issue in 19.12 was that a particular message in a z-wave message transmission was not being sent from the z-wave chip to the application layer in the hub firmware. After digging more, we learned that the message could occasionally be dropped by the z-wave chip (not in our control to change). So we are now accounting for that in 19.13.

However, it looks to me that a subset of those missing messages is followed by the Z-wave chip not responding back, so I am investigating this now.

I am sorry this is frustrating, one because we are not in charge of what the z-wave chip does, we only interface with it, and also some of these issues are almost impossible to reproduce when during development just because different network configuration results in different timing parameters which leads to different behaviors.

Thanks for your help! I’m sure one way or another this will get resolved even if it takes cooperation with the chip manufacturer. For what its worth I’ve been experiencing some level of Z-Wave problems since I got into SmartThings 18 months ago. Please feel free to capture whatever data is necessary and let me know if there is any specific testing that you’d like me to perform.