I found and fixed a couple of fairly severe bugs. Details in top issues on github.
One is that in response to a refreshed value, it was sending out another refresh request! So, infinite loop swamping the network. I can't figure why this hasn't bit everyone by now...
The other is that bits are dropped from a value's index, which is catastrophic if your app uses cc/inst/index tuples to identify values (those are persistent between invocations and versions unlike openzwave value ids!). Again, surprised others haven't hit this.
How do I get them incorporated? They're both no-brainers (pretty sure they're just straight up bugs, and don't impact the API at all).
-Brandyn