Yeah, the very last (reading top down, or first chronologically) log entry in your second screenshot, the one at 09:49:43.307 AM, has the key: they're apparently trying to run zwaveSecureEncap() on a list of commands that has both already had this method and delayBetween() (or perhaps manually inserted delays) run on it. The zwaveSecureEncap() method is barfing on the "delay"s, but I'm not sure it would like to be run twice on the same actual Z-Wave command either (I don't know; it may or may not work -- the delays are just the problem that is apparent from the logs). They need to figure out a way to stop this from happening in their driver -- confirming my guess above.
Hopefully that's enough to help them figure something out!
