The Browser-Based Software Control Center
The controller's home page has a very clean look.
More functionality on the first page would be nice, but you could end up with a cluttered interface were you to build extensively on the HA deployment. The General Settings screen is where time and day are set, where you key in the controller's network settings, and where you can program controls for older X-10 devices.
An individual room page, again, has a nice clean look and simple interface.
You add devices to a room from the room settings page.
You can also choose which controls to show in case the device itself is not capable of dimming. I also found a feature here that I didn't know was available with this controller. I could program automatic on and off times for given days of the week. An example of the way you'd use that would be as follows: set your bedroom lights to come on in the morning, during the work week of course, when your alarm clock is set to go off, or a few minutes later in my case.
(a) it's fragmented
(b) most applications can be accomplished in most homes with less expensive, individual systems than with any integrated system - even if one existed.
HVAC: Unless you have a large home requiring multiple HVAC zones/thermostats, and unless parts of the home are unoccupied for varying amounts of time, a programmable thermostat is an adequate solution. Setbacks (eg while you are at work) don't seem to save much money with modern HVAC systems in most US climates.
Lighting: If "security" means cycling lights so the house looks occupied, again simple timers are adequate. Unless you have a large, multi-source lighted home, few need automated lighting and "scenes".
Irrigation: If you have any sprinkler system, once again timers and rain sensors do the job well enough.
And so on.
FYI, I have a large primary residence with a networked security system that also controls multiple thermostats. A dedicated PC has replaced a stand-alone DVR to monitor security cameras. A low-voltage, microprocessor controlled system controls lighting.
If these 8-year old systems talked to each other well, maybe I could use the motion detectors to automatically turn lights on and off. And maybe I wouldn't be better off using standard internet cameras to monitor security as I travel between homes.
Its all cool technology, but as a substantial user and tech-lover, I just don't see significant, practical application in most homes.
I use a lot of 130V bulbs in the fixtures controlled by microprocessor controlled lighting system. Most of these bulbs are also oversized for their purpose, and are therefore set to run at, eg, 60% or 75% of maximum voltage when turned on.
I don't know whether I've saved any electricity or not - I doubt it lol - but I have saved a tremendous amount of money on bulbs. EG, there are 11 such bulbs in my kitchen ceiling and they run a minimum of 12 hours per day. I have not replaced a bulb in that set since they were installed over 8 years ago.
Sure it costs money but so does liquid nitrogen cooled overclocked gaming rigs.
Lamp life is very sensitive to operating voltage - for 120 volts Ge quotes 125 volts as shortening the lamp life to 1/2 and 130 volts to 1/3. The inverse is true - if you put a 130 volt lamp in a 120 volt circuit you can expect over double the lamp life, and if you have a dimmer to soft start then it can last a way lot longer.