Do Not Move Tabbed 'Add' Entries in User Code to Global Declaration

Misterhouse merges all of the User Code files into a single file at runtime.  When merging the files, MisterHouse moves certain commands and declarations to the top of the merged file.  The purpose is to allow these "global records" to be defined early on, to avoid errors.  They include variable instantiaions and other routines.

In order to avoid moving lines which are meant to be part of a subroutine or logical statement, MisterHouse will only move theabove "global records" if they occur at the start of a line.  The thought being that coders practicing even the most basic level of standard formatting will indent statements inside of logical routines or subroutines.

The one exception to this rule is the add statement. This is generally used to add an item to a group, but a few other items have add functions as well, notably the Process_Item.

For some reason, MisterHouse will allow anywhere from 0-3 whitespaces to proceed the add statement while still considering it to be a "global record"

This is somewhat logical in that tabs are usually at least 4 spaces.  But it is unclear why this exception only applies to add functions, and not to the other functions as well.

Eitherway, a white space in perl is defined as [\ \t\r\n\f].  [\r\n\f] are unnecessary, since they would be interpreted as a newline.  The problem arose by including [\t].  In so doing, MisterHouse was moving add functions which were tabbed in 3 times.

By changing this to simply [\ ] the code at least does what the author originally intended it to do.  I think the odds that this change would cause an error for any currently existing user code files is small, but there is some remote possibility that it might.

Personally, I think the spacing should be removed entirely, but I am hesitant to change a function that is so fundamental to MisterHouse.
Add some clarity to the I2CS device is not linked error message, teling us WHICH device.
Merge pull request #217 from krkeegan/insteon_linking

Insteon: Change "initiate linking as controller" Group to 00
Merge pull request #244 from krkeegan/user_code_fix

Do Not Move Tabbed 'Add' Entries in User Code to Global Declaration
Merge pull request #256 from pmatis/Insteon_Clarity

Insteon clarity
Merge pull request #259 from krkeegan/Zero_State

Allow for State of 0
Insteon: Add Success_Callback to Message Object

Success_callback is eval'd when the ACK for the message is received.
- Note: There are so many callbacks all over the place within the code, it might be nice to condense as many as possible into this routine.
Insteon: Add routine for Linking I2CS devices

The routine requires a few steps to complete
Insteon: Add Callback to Routines used by Link to I2CS

Each routine needs to have success and failure callback parameters
Insteon: Convert Link_to_Interface to Handle i2cs or non-i2cs devices

The routine first checks to see if the device will respond to a get_engine_version request.
If any ACK is received the routine continues as normal.  In this case even if the device is an I2CS, the device must already have link entries as it responds to the PLM.
If a NAK is received, it is assumes that this device is an i2cs and the link_to_interface_i2cs routine is called.
Merge branch 'insteon_i2cs_linking' into running