One of the issues I noticed as well with the current Z-wave lighting system is that device state changes made outside of LMCE do not feed back to LMCE. So if I turn a light off via LMCE and then press a button on a switch to turn it on, LMCE would still think it's off and show it as such on the floorplan. I've seen other Z-wave software controllers use polling. While there are some new devices that can support state change notification, polling is the simplest solution, I believe. I plan to implement that functionality with the Insteon driver I'm writing.
I worked around that problem. Since I wrote driver by myself for my home automation system (Cybrotech.uk), I could afford that. So I monitor automation level (poll 20 times per second) and if anything changes, then I send proper event to DCERouter so floorplan devices are properly updated...
The problem is that light is like switch device and not real device (see no good point for that other than being easier to implement), so it will go into desired state in few seconds regardless of true state of device. But if you send proper events it will also act accordingly...
I'd also vote for proper implementation of lights (where low level should report curren state back) instead of switches..
Any other opinions ?
I'm also curious how to contribute in current state of LMCE. Is there SVN? Are there any maintainers to work with and approve changes ?
Thanks in advance,