I think that you don't have to choose - you can use both of them - I also plan to do the same. Misterhouse is really nice backend, quite easy to learn and customize... LMCE is great GUI, with probably crippled backend functionality, so I guess using both of them would make a nice combination...
I can help, if you decide to go that route...
Can you flesh out the wiki page a bit more if you have some experience? It would be good to see how to:
1. Add misterhouse to LMCE as a parent (this already seems to be covered)
2. Add a light to a room, controlled by MH parent
3. Configure MH to listen for the right commands and control light
4. Finally be able to turn light on/off and dim from the floorplan on LMCE
I can add my MH configuration which shows how to do motion detection firing lights in MH, as this is currently not something I can do in LME (which is why I am still running MH).
Sorry really busy at the moment, but you do a lot by yourself. I'd recomend follwing way :
1. get more familiar with DCE messages :http://wiki.linuxmce.org/index.php/Sensorshttp://wiki.linuxmce.org/index.php/MessageSend
There you can see how to send messages to control various devices or to report change in state via events... Start Orbiter, send events, commands and see how it reacts... You can also send message to each device over web-admin (and it even prints what is command line syntax for sending that message - it's nice to see and learn)...
2. How to connect to LMCE :http://wiki.linuxmce.org/index.php/Plain_Text_DCE_Messages
I guess text interface would be easy for a start... Try that basic code, register with LMCE and see what messages you'll get. You add Misterhouse as device, and add some child devices (thermostat,thermometer, light, etc...) - be sure they don't have "Implements DCE" ticked. In this case all messages for those devices will be routed to their parent -so your code will receive them...
3. Description of DCE commands, events...
Go into Web-Admin -> Advanced -> DCE and you can get more info on commands, events, etc...
So basically LMCE-MH integration should do this :
- MH registers as parent device for all devices it controls
- MH registers as message interceptor for other LMCE not being children devices...
- then do endless loop :
1. child devices:
1a. receive commands from LMCE and control them accordingly
1.b if anything under MH changes state of some device, send proper event to LMCE, so it will change its state in its own data and on Floorplan
2. other LMCE devices :
2a. intercept events for those devices and update MH data accordingly (if LMCE changed their state)
2b. send proper commands to them if something under MH wants to change their state.
?? not sure, maybe something else is also needed here...
In this way we could have wrapper code to integrate beside automation devices even mp3player under MH as media player to LMCE and vice versa. But as previously said, I'd like to have an helping hand on MH side - it would be nice if MH could automatically expose all its devices to LMCE and also take all other LMCE devices for it self - so integration could be done in fully transparent way...
MH is really nice as backend machine, generating all sorts of reminders, speech announcements etc.. LMCE is particularly strong in giving nice GUI and convenient control of devices into user's hand... Using both of them would enhance system dramatically...I've tried several times posting to MH's mailing lists, but it seems that LMCE is not so popular in this community to give a hand on integration..