I agree - a lot of various features seem to be important for each of us. But we have one strong common point - we need to implement generic support for possibility of showing state of any device on floorplans and that would solve all those problems. This is basic framework - on top of that, alot of new features can be added - but we need to solve basic problems (in my view "generic state changed" event or something similar can solve this)... Also a lot of stuff is currently hardcoded in plugins, so in majority it's not enough if you add certain device to certain category that it will be shown on floorplan... Behaviour is currently not consistent.
I have talked to Chris and Eugene some time ago, and we agreed that such support will be experimentally added for lighting and climate plugin, but currently I'm not sure if this has happened.... Will check that with Chris tomorrow.
Regarding energy consumption :
1. I agree, energy metering is important, but when you'll see numbers with your core and MDs running + other amplifiers, devices etc... :-( ...
I currently have this already implemented in home automation level, and I can see current consumption. And I'm a bit sad, we need to do a lot of work to bring such consumption down - one of the most important features of smart home platforms is also lowering energy consumption, but with system like LMCE it currently rises too much....
2. regarding measuring power consumption: I have implemented it in pretty simple way. In our country (Slovenia), we must buy household electric meters that already have pulsing output (in my case I get 500 pulses per 1kWh). My electricity provider has let me connect to that output (it's described in one of IEC standards) and I just measure time between pulses and estimate current consumption. So I'm measuring exactly same thing as I'm paying for... Nice feature, I bet a lot of you have same or similar possibility... I also had some smaller meters in consideration, but this was by far cheapest and really exact solution...