Here is what I think I should be able to do:
I want to be able to control things around me using the date. I think about watering my lawn. That particular task is based on a couple of things. For one, time, and the other, because I live where lawn-watering is restricted, a date. So a calendar is perfect as a user interface for setting up my lawn watering schedule. However, when it is overly windy or raining, I probably should be able to cancel that operation.
Another problem: energy usage. I want to control when my heat should come on and go off. Same with lights. Now, before you get all up in my grill about the fact that programmable devices already exist for this purpose, I will remind you that you set those based on parameters that, in reality, change and therefore render the program useless. When I am gone from my office to a job site or meeting, technically, my heat could be turned down upon leaving. When I return, it could come back on. But, if I am here, I want the temperature more constant. See where I am going with this? It is tied to my schedule. I don’t want a house full of sensor technology that is monitoring my movements and logins. I live in an old house.
The photo above shows a simple, color-coded interface to a central calendar application (which, preferably, should be open source and allow API interfacing). The “buttons” are events. Each color and/or shape indicates when a device is activated or stopped. This calendar, in turn, could interface with a synchronized control system that uses this calendar data to send signals through a web-enabled controller. The controller ultimately passes the calendar command through the home wiring system to a connected device. Instead of setting up a complex plan on a central computer or home automation panel, I could control my home using my changing schedule (via a mobile phone even!) that more accurately maps to the reality of my lifestyle.
Just a thought.