X10 Interface for Car Detection
When I get home in my car, I would like the outside lights to come on and also the hall lights. I only want this to happen when dark, and for the hall and outside lights to turn off after a set period of time. I also want a solution that could be used to open a garrage door at a later date.
I could install a movement sensor, but then that would also turn on for my neighbours, and well, they need to figure things out for themselves. Also, a movement sensor is way to easy and does not leverage the use of my Car PC.
Therefore, the solution I propose is to make use of my CarPC, wireless LAN and automated home (X10).
When my car pulls into the drive way, it automatically connects to my wireless LAN. An app (which I shall write) which will reside on my home PC, will detect the CarPC on the network.
Using the SDK for a piece of software called Home Control Assistant (HCA, check out http://www.hcatech.com), I can control X10 devices in my home (with asstiance of an X10 USB power adapter, check http://www.hnausa.com or http://www.smarthome.com).
On detecting the car, the software will use the SDK to run a script in HCA. This script will turn on the outside lights and hall lights, weight for a specified time and then turn them off.
So how does that sound? Anyone else interested? Anyone have any further thoughts?
A version is available now...
So I wrote the software yesterday... Yes, it's a BETA but it works..
So I tried initially to provide a server piece of software that ran on your HOME PC. The idea was that the utility would detect the CAR PC when it arrived home. It checks at a configurable interval, default to 1000 mssecs.
Problem was that my CAR PC using DHCP client, thus the host name could not be derrived and I could not guarantee what the IP address would be. D'oh, so I left PING as an option for those that may have a static IP in their car...
I think implemented a second detection mechanism which is a client / server method. When configured to, the server listens on a configured port. The THIN client then attempts to connect to the server at a configurable interval (default 1000 msecs). The port in which the client / server use is configurable. The Server (your home PC) needs to have a static IP though, or at least it can be dynamic but not change too often. Obviously the IP that you configure in the client can't be a public IP as when you are driving around and get online on a hotspot you'll have your lights comming on at home (or what ever you have configured it to do).
So, once the car is detected, the software runs a Home Control Assitant program (part of HCA, see http://www.hcatech.com). I did this first as it met my requirements. I guess I could add more stuff to the server app to do other things when the car is detected.
Let me know what you think, and remember it's a BETA... comments or thoughts....
I've created a website to put these updates on: