why the hell are you guys doing this? especially when pluto does what misterhouse does, better?
1. Can I do this level of scripting in LMCE?
X10 motion detector triggered --> is it between dusk and dawn? --> is the light already on? --> switch the light on
Switch A5 pressed --> dim lamp A3 to 50% and switch lamp A4 off
2. Misterhouse is the only stable part of my system. It sits on a separate low-end PC which is never touched. If the lights were as reliable as the TV my girlfriend would leave me!
3. When I tried controlling X10 lights using LMCE directly there was such a huge lag that the system was useless.
4. There is no support for receiving X10 commands in LMCE (I actually receive RF commands via an MR26 and powerline commands via a CM11 in Misterhouse)
5. LMCE cannot talk to my iButton temp sensors using the simple homebrew passive serial adapter
I am aware that these things could be solved with some development, but I don't have the skills and modifying a little bit of perl to bridge MH and LMCE was very simple and very convenient.
1. Yes, dig into the criteria section of the Events on the Web Admin
2. the appliance control is the oldest and most reliable part of LMCE.
3. X10 is by its very nature, very slow, so yes, inherent lags in the messaging system will exacabate this. I can tell you that there is a lot of debugging code being executed right now that if disabled would vastly speed up this part of the system by orders of magnitude, with that said, even on my Z-Wave installation, selecting and triggering a single light only takes about 40ms, with other lights happening roughly half a second after the message is sent to each in a queue, this can be improved.
4. we need to implement this, again, not hard if you actually dig in a little. The system already can deal with it, the commands and events just need to be implemented.
5. write a driver. I use a DS9490R and it works just fine.
You're telling me you can deal with the mess that is Perl, and you don't want to even look at Ruby? I would suggest looking at a GSD template before making such a determination.. which leads me back to my original point, actually look at the system before slapping on duct tape to other things.