My motivation? I just think a Java solution is a lot more desirable. For those who prefer to run ZUI, that’s perfectly fine with me, but I don’t like to patch together a lot of different solutions using “glue and tape”. To me, it’s inefficient and fragile (not talking about this particular solution, just setting up different systems in that way generally).
In addition, this is JS, depending on JS libraries (aka NPM or similar). That in itself is a world I really want to avoid, with constant updates and deprecations that break stuff for no good reason. It can be a full-time job to run such systems without actually achieving anything, just to “keep it working”. The more interdependencies and complications, the less desirable. On top of that, JS is extremely low performance, not to mention single-threaded. I generally avoid software written in Python and JS if at all possible.
So, to start with I’m “stacked against” using ZUI I guess you could say. In addition, I got the impression that integrating it with openHABian was quite out of the question. If it were maintained that way, and interoperability with JS library versions etc. were handled by somebody else, I might be more inclined to reluctantly use such a solution. But, that’s far from the case, as far as I can understand:
So, my thinking is that for those that want the extra ZUI can offer, or that don’t mind running and maintaining separate systems, the “ZUI binding” is fine - for the rest, I think it would be good if the Z-Wave binding could serve them well.