I have a problem: I like to SNOOZE. I mean, it feels so good to go back to sleep after your alarm wakes you up, especially when its cold in the room, or you don’t really have to get up. I have tried many strategies to overcome this behavior: putting my alarm across the room, so I have to get up and hit snooze, giving myself a rule that I cannot wake up after 10am, jumping out of bed and yelling; but what usually happens is I don’t remember to use these tricks because I’m half asleep, or I get used to them and don’t ever remember walking across the room to hit the snooze button. I am sick of it. For my Networked Objects final project I am going to solve this one.
My plan is to make the alarm last long enough so that I actually wake up, and then hopefully make the more rational and reasonable decision to GET UP. This is how it will work: a little devise will sit next to my alarm, and three to four other devises will be placed throughout my apartment. When my alarm goes off in the morning, and I hit snnoze, the little devise sitting next to it, hears, and tells one of the other devises in the room to go off. So, I have to get up, find which one is going off, and hit it’s snooze button. Once I do that, it tells one of the other devises in the apartment to go off, so I have to find that one. This process continues until all alarms have been deactivated. Its like a like a little game. And because it is random which alarm goes off when, the game is always changing and I can’t learn it. I know it sounds drastic, but I’ve tried everything else (except having a regular sleep schedule I guess).
The great part about the system is that it is scalable. A user can add as many alarm nodes as they want, and the system automatically uses then. So if a person is really bad at waking up, they could have 10, or if a person just needs a little help, 2.
If you want to know more about the technical aspects of how the system would work, you can refer the the System Diagram.