Navigate to the top level page for more information about all the components of this system.

The Home Automation Hub (HAH) Project transforms the Livebox into one of the most capable and affordable Home Automation systems that you might imagine.

The following features were proven to make this project a winner:

• Browser based user interface
• Pre-programmed automation scheduling via Google Calendar
• Instant control via Twitter
• Data logging to pachube
• Power use monitoring/graphing from a Current Cost unit
• Easy to control remote RF mains sockets (Bye Bye Standby & HomeEasy)
• Seamlessly integrated with JeeNodes
• Open control protocol (xAP)
• Input sensing (upto 4 switch inputs) as well as output driving (upto 4 relays)
• Free, Open Sourced, HAH firmware
• User scripting language for customisation of operation
• Cheap to run. Only uses 6 Watts of power
• Solid operation - not prone to hangups
• Gets its IP address via DHCP or STATIC
• Remote firmware 'auto-updates'
• Configuration not lost on 'hard' reset
• Makes a great solar PV controller

HAH components can be bought from the shop or drop by the forums if you have any questions about the HAH project.

Note that your Livebox needs to be like the one pictured above. The newer Livebox 'mini' version won't do the job.

You might want to read about the experience of a HAH user. Karl has a writeup here.

Now with a xAPFlash interface!

Monitor
Control

Also, control from Andriod devices

Mobile App

The 20,000ft view of how the HAH controller fits into a network and the devices that it is able to control with the custom hardware.

Focusing on the software that controls the HAH additional Hardware

• Using the open protocol xAP gives us the flexibility that our project requires
• For the webserver component we use klone. It's a webserver where you build all the web pages using normal HTML but the embedded scripting language is C. Then it compiles all the pages into a BINARY executable which you ship. One binary and that IS your application. No CGI. No interfacing issues, and best of all no possibility that the scripting language can't do it!

A block diagram of how the daemons interact with one another on the livebox.

• xap-HUB - allows multiple xAP devices to be controlled from a server. In this case, the Livebox.
• xap-adapter - convert the AVR menu interface into an xAP protocol and interfaces with the RS232 port.
• xap-currentcost - USB/Serial interface to the CURRENT COST electricity monitor.
• xap-sms - USB/Serial interface via a DLR-3 cable to a Nokia 7110 mobile phone.
• xap-pachube - Feed xAP BSC data to the PACHUBE data aggregation service.
• xap-googlecal - Trigger xAP events from Google calendar.
• xap-twitter - Remote control with Twitter.
• xap-plugboard - Lua based scripting engine.
• iserver - xAP/TCP gateway for running a Wi-Fi based touch screen for remote control.

All components use the file /etc/xap-livebox.ini as the universal registry for their settings. This is in “windows ini” file format using minini the INI file parser.

~~DISCUSSION:off~~