We’re setting up a special forum for Luup developers. Our programmers will be responding to those forum posts daily. We will also be expanding the API and fixing bugs based on Luup developer feedback and posting new firmware upgrades every couple days with the changes. So if you’re a developer and you’re stuck because you need a new feature or a bug fix, chances are you’ll have it within a few days.
Good intentions… I hope MCV guys realize that leaving issues unanswered, or just partially answered, for weeks doesn’t help to building the right motivation for developers…
Sorry. We launched Luup after Zensys/Sigma released service pack 3 for the z-wave controllers; hence the dongle recall. We had anticipated that all Z-Wave problems were resolved, and we’d focus exclusively on Luup and our code. Unfortunately there’s another problem with the SP3 dongles, and that diverted resources unexpectedly. It takes an enormous amount of time to debug a lockup in a hardware chip since you have no logs to view after the fact. That’s not meant to be an excuse, just an explanation…
That’s absolutely understandable, but I believe there should be better communication between us and you guys.
It would be good for us, devs, to be notified that we shouldn’t expect you to answer the question for some time due to circumstances, so we would be able to plan things accordingly (some of us are busy too ).
I realize that you might not want to expose this kind of difficulties on public forums, so I would suggest to setup a limited email distribution list for “internal” notifications, development news and pre-release updates, etc. I personally wouldn’t even mind to sign NDA if it can help establish better communication.
Best Home Automation shopping experience. Shop at Ezlo!
).