Normalize Line Endings in Repository to LF
Merge pull request #317 from krkeegan/eol_normalize

Normalize Line Endings in Repository to LF
Correct two MH_Control Voice Commands

The "re load" and "reload" statements are alternative phrasings and not two different commands and thus should be contained in braces not brackets.
Merge pull request #318 from krkeegan/voice_cmds

Correct two MH_Control Voice Commands
Insteon: Fix Error with DebugLevel in Message.pm
Merge pull request #319 from krkeegan/fix_insteon_msg

Insteon: Fix Error with DebugLevel in Message.pm
Add 2 Second Delay and Print Log Message to Restart Command

Allows for the web interface to at least see that the command was successfully sent, before the http server goes offline.
Merge pull request #320 from krkeegan/restart_fix

Add 2 Second Delay and Print Log Message to Restart Command
Trim Whitespaces in Debug Config Parameter

Pounding my head against the wall trying to figure out why 'debug: insteon:4, json' wouldn't work. (Turns out debugging was enabled for ' json', very annoying).

This trims all leading and trailing whitespaces around the parameters.  It also trims any white space between the ":" allowing for example 'insteon : 4'.

Much more user friendly.
X10/Insteon: Remove Line Which Attempted to Add the X10 Device to the PLM

Symptoms: the PLM states parameter contained the entire hashes of any X10 devices.  This made get_states useless on the PLM (it should return an empty array). Instead it returned a bunch of garbage.  This further lead to crashed in the json and xml servers.

Cause: the $interface->add($X10_Object) command was calling the add subroutine in Device_Item.  I am not even sure how the inheritance allowed this to happen.  But this routine expected a list of states to be passed as the first parameter not an object.

Solution: Remove the offending call to add.  It is not clear why this was used (the commit notes demonstrate that this was added when support for X10 over Insteon was added).  Perhaps the drafter intended to add the X10 device as a member of the PLM?  However, the PLM itself has no members, PLM scenes are allowed to have members.  Alternatively, perhaps the drafter intended to add the object to the list maintained by InsteonManager? Adding some code to the X10_Item would allow this to work in theory, however it isn't clear to me why you would want this. The list is maintained so that the insteon_manager can assist in link management, something not done by X10 devices.  We have also been operating without adding the X10 items to the object list for quite some time without incident.  Indeed no current calls to find_members would even return an X10 device as they all specifiy Insteon packages.  Finally, perhaps this is some vestige of the old Insteon code.

Removing the offending line solves the issue, and does not appear to have any adverse effects.
Merge pull request #321 from krkeegan/fix_debug

Trim Whitespaces in Debug Config Parameter
Merge pull request #322 from krkeegan/fix_x10_plm_issue

X10/Insteon: Remove Line Which Attempted to Add the X10 Device to the PLM
Merge remote-tracking branch 'remotes/hollie/master' into running

Conflicts:
	lib/Insteon/BaseInsteon.pm