This tries to illustrate the differences between the two approaches (sorry for the poor artwork :) ). 
Both approaches are fundamentally the same code - I could take my internal.config package and make it another binding, and we could define an extra interface between the two bindings. Alternatively, we compile the package into the binding - code wise it's almost the same - interface wise, there would be more interfaces we'd need to define - future refactoring wise, I don't think it makes too much difference since the code is reasonably self contained anyway.

I think this is more of a conceptual issue here so we probably need Kai/Thomas to input. I am however concerned that the zwave binding does need something to support configuration, so I think it's a good binding to use to develop this system (if everyone thinks that an admin interface along the lines of this concept is needed).

![image](https://f.cloud.github.com/assets/1041475/1624821/a7361324-56c8-11e3-99b2-0eeecc985fcb.png)