Step 1: installation of RabbitMQ (and Erlang)

RabbitMQ is the message broker required by HouseAgent, you can download it from here.
You need the server with Windows installer:

After you have started the RabbitMQ setup, it will alert you that you also need Erlang:

Go ahead and download and install the latest Erlang version, choose the Windows binary form:

Now complete the installation of both Erlang and RabbitMQ, the default settings will suffice.

Step 2: Installation of HouseAgent

Download the latest beta release from the HouseAgent forum. And start the HouseAgent installation.
It’s an easy next->next->finish installation.

Step 3: Enjoy HouseAgent

Congratulations! You should now be ready to use HouseAgent!
There’s a HouseAgent start menu group in the start menu to get you going.

That was the short introduction of something I have been working on for quite some months already. HouseAgent has been running as my own home automation software for some time.
I hear you asking, why not use one of the standard software products available? There are a couple of reasons for that:

• Most software is expensive, for a full set-up €500,- is no exception;
• I wanted to learn from my home automation hobby, by writing my own software I got and still get a lot of insight on new frameworks/protocols/techniques etc;
• Really, I wanted free home automation software to be available to others out there as well!
• Most software out there is not designed to run on a low power/low profile systems. HouseAgent can be run on low power system without hassle.
• Also most software only runs on one platform i.e. Windows or Linux. I believe in a truly open platform where all kinds of developers can contribute.

Let’s look at some core components used in HouseAgent:

AMQP/RabbitMQ
One of the core components used in HouseAgent is AMQP. The Advanced Message Queuing Protocol (AMQP) is an open standard application layer protocol for message-oriented middleware. The defining features of AMQP are message orientation, queuing, routing (including point-to-point and publish-and-subscribe), reliability and security.
AMQP is used within HouseAgent for plugin communication. Here is a picture, which hopefully explains all the bits and pieces a bit better:

As you can see all plug-ins are separate isolated components, in fact the plug-ins don’t even know about the coordinator or each other. The coordinator is the main HouseAgent application which runs important features such as the event handler and the web-based GUI. A plug-in communicates with the broker, and the message protocol used for this is AMQP.
Certain types of messages are “published” on the broker, for example a device_value_update message might be send to the broker by a plug-in. The coordinator is “subscribed” to such messages and handles them appropriately (i.e. run a certain action based upon an event or save history to a history file)
The coordinator on it’s turn can publish messages to the broker as well, commanding the plug-ins to do certain action. One example would be the power_on message. This message commands a certain plug-in to turn on a device with a certain address.

So what’s RabbitMQ? RabbitMQ is a broker which implements AMQP, there are several other AMQP implementations which might work as well with HouseAgent (not tested!). You can read more about AMQP on it’s wikipedia page. You can read more about RabbitMQ on it’s homepage.

Twisted (Matrix)
Twisted is used for serial communication and all networking communication in HouseAgent. Twisted is a networking engine written in Python, supporting numerous protocols. It contains a web server, numerous chat clients, chat servers, mail servers, and more. The main difference between Twisted and other networking engine’s is that Twisted is asynchronous. You can read about the differences between synchronous and asynchronous communication here. Twisted certainly was an eye opener for (thanks Rene) but also required a completely different way of thinking about networking and communication in general.

Among these core components some other frameworks/packages are used:

• Mako Template (for web page templating)
• PyRRD (for historic graphing)
• py-serial (serial communication)
• pywin32 (Windows only)

Although the development of HouseAgent is just getting started, it already includes some nice features. Some core functionality HouseAgent offers right now:

• Storing and logging of device values
• Graphing (based upon RRDtool)
• Event handling (triggers include: time based, device value changes)
• Flexible plug-in development and easy extension

This concludes the short introduction of HouseAgent. In future blog posts I will dive deeper in different aspects of HouseAgent.
Right now a group of beta testers has been selected, I will send out a first beta version a.s.a.p. after that a public version will come available.
As of today the source code is available for the core of HouseAgent! You can review the source code, and watch the development progress on Github. But please don’t expect a complete system out that source code, stand-by for binary releases.

powercfg.exe /h off

But what if we wanted to repeat this task for let’s say 30-40 servers? Do it by hand? No way, Powershell to the rescue!
Here’s the script I came up with, enjoy:

# Ask for credentials used to do remote WMI.
$cred    	= Get-Credential DOMAIN\account

# Filter used for active directory query. Only 2008 server machines.
$strFilter 	= "(&(objectClass=computer)(operatingSystem=Windows *2008*))"

$objDomain 	= New-Object System.DirectoryServices.DirectoryEntry
$objSearcher = New-Object System.DirectoryServices.DirectorySearcher
$objSearcher.SearchRoot = $objDomain
$objSearcher.Filter = $strFilter
$objSearcher.SearchScope = "Subtree"

$colResults = $objSearcher.FindAll()

# Loop through list of servers.
foreach ($objResult in $colresults)
{
	$objItem = $objResult.Properties
	$name = $objItem.name[0]

	Write-Host "Disabling hibernation on: $name"

	try {
		invoke-wmimethod -cred $cred -path win32_process -name create -argumentlist "powercfg.exe /h off" -ComputerName $name
	}
	catch {
		Write-Host "Failed to disable hibernation on: $name, no permission or server down?"
		break
	}
	finally {
		Write-Host "Hibernation disabled on: $name"
	}
}

Onwards!

# Number of days to generate, default = 365
$NumDays 		= 365
$AccessGroup 	= "Gasten"
$ExpiryTime 	= "20:00"
$StartTime 		= "07:00"
$OutputCSV		= "C:\TEMP\wireless.csv"

$SshHost 		= "127.0.0.1"
$SshUser		= "someuser"

$access_codes = @()

# Start SSH session
New-SshSession $SshUser $SshHost
Invoke-Ssh "z"
Invoke-Ssh "conf t"
Invoke-Ssh "wireless F"
Invoke-Ssh "conf t"
Invoke-Ssh "radius-server local"

$i = 0;
do {
	# WSEM format: mm/dd/yyyy hh:mm
	$date = (Get-Date).AddDays($i)
	$date2 = Get-Date $date -Format "dd-MM-yyyy"
	$date = Get-Date $date -format "MM:dd:yyyy"
	$pass = RandomPassword 4
	$user = RandomPassword 4
	$output = "rad-user $user password 0 $pass group $AccessGroup guest expiry-time $ExpiryTime expiry-date $date start-time $StartTime start-date $date"

	# add user through SSH
	Invoke-ssh $output

	$Response = New-Object PSObject
	Add-Member -InputObject $Response -MemberType NoteProperty -Name "Datum" -Value $date2
	Add-Member -InputObject $Response -MemberType NoteProperty -Name "Gebruikersnaam" -Value $user
	Add-Member -InputObject $Response -MemberType NoteProperty -Name "Wachtwoord" -Value $pass
	$access_codes += $Response

	$i++;
} while ( $i -le $NumDays )

# Save and disconnect SSH
Invoke-ssh "write mem"
Remove-SshSession

# Export to CSV
$access_codes | Export-Csv $OutputCSV

# Helper functions
function RandomPassword ([int]$intPasswordLength)
{
   $strNumbers = "1234567890"
   $strCapitalLetters = "ABCDEFGHIJKLMNOPQRSTUVWXYZ"
   $strLowerLetters = "abcdefghijklmnopqrstuvwxyz"
   $rand = new-object random

   for ($a=1; $a -le $intPasswordLength; $a++)
      {
         if ($a -gt 3)
           {
      	      $b = $rand.next(0,3) + $a
      	      $b = $b % 3 + 1
      	   } else { $b = $a }
      	 switch ($b)
      	   {
      	      "1" {$b = "$strNumbers"}
      	      "2" {$b = "$strCapitalLetters"}
      	      "3" {$b = "$strLowerLetters"}
      	   }
         $charset = $($b)
         $number = $rand.next(0,$charset.Length)
         $RandomPassword += $charset[$number]
      }
   return $RandomPassword
}

Special thanks to Joel Bennett’s SharpSSH wrapper for PowerShell (located here: http://huddledmasses.org/scriptable-ssh-from-powershell/) which I used to automate the command line commands for the HP WSEM.
This shows the great power of PowerShell for automating virtually anything!

This happened after the server (suddenly) ran out of free disk space. It turned out that all color settings where reset to “0″ (black), the registry showed the following color values:

The fix for this was easy, I took the color schema settings from a working 2003 server and inserted them remotely from my workstation. The color schema settings are located under the following registry key: HKEY_USERS\.DEFAULT\Control Panel\Colors