Plugin: InControl For SageTV/HomeSeer - Version 1.4.6

[lamanmi]

Plugin: InControl For SageTV/HomeSeer - Version 1.4.0

IMPORTANT - UPGRADE PROCEDURE FROM 1.0.x:

• Close Sage (server/service) and do a backup of the entire Sage directory, should you need to return to the pervious verison.
• Close HomeSeer (server/service) and do a backup of the entire HomeSeer directory, should you need to return to the pervious verison.
• Access HomeSeer Updater and download/isntall InControl version 1.3.1.
• Go to Sage TV and update the UI Mod plugin for InControl to version 1.3.1 through the Sage Plugin options
• Select Control from the Sage main menu, you will be prompted to correct any settings that were not previously set.

Description:

InControl is a plugin for HomeSeer and SageTV. It provides a real-time interactive interface between SageTV and Homeseer. With InControl, you are provided with easy to use, graphical interface in SageTV to control and monitor any HomeSeer devices. In addition, you can use HomeSeer to broadcast messages to SageTV.

Features:

• Control and/or monitor Thermostats in HomeSeer from within SageTV
• Control and/or monitor any device in HomeSeer from within SageTV
• Advanced button configuration of your HomeSeer devices
• Send messages and alerts from HomeSeer to Sage with Events or Scripts
• Send any SageCommand commands from HomeSeer to Sage with Events or Scripts
• HomeSeer Devices for each of your Sage Server UI, Clients, extenders to monitor status and control directly from HomeSeer
• Web based remote control available from the InControl HomeSeer web page
• Custom graphic library included for SageTV
• Secure connection with SageTV via HomeSeer user id and password

Requirements:

• SageTV 7.0.8 or higher
• InControl For Sage Plugin (available through SageTV plugin library)
• HomeSeer 2.0 or higher
• InControl For HomeSeer Plugin (available through HomeSeer store and updater)
• HomeSeer and SageTV must be on the same PC or connected via a network

Installation:

• Be sure to download and install the InControl Plugin for HomeSeer first. It is available through the HomeSeer Updater and Store.
• Once InControl is running on your HomeSeer server, you can download and install the SageTV component through the plugin manager.
• Please be sure to review the links below for more information.

More Information:

• Installation Guide
• User Guide
• Screenshots within HomeSeer
• Screenshots within SageTV

Feeback:

• Enhancment Requests - There are many other features I am planning to add to this plugin. However, please feel free to post any enhancment ideas and I will do my best to add the capability.
• Defect Reports - Please post any bugs or issues in this forum.

Version Information:

1.4.6

New Features:

• Added support for HS devices that receive values for changing (i.e. Z-Wave Door Lock) - Now working properly

1.4.5

New Features:

• Added support for HS devices that receive values for changing (i.e. Z-Wave Door Lock) - Experimental, Still in development

1.4.0

New Features:

• Added support for thermostats. There are two types of thermostats that can bee added. (1) Thermostats Supporting the HomeSeer Thermostat API - this will automatically determine the thermostat capability and be pre configured. (2) Custom Thermostats (do not support HomeSeer Thermostat API) - this will require custom interfaces using Scripts to the thermostat.
• Added capability to customize and send any device control buttons to the client
• Within HomeSeer scripting, there are 2 new commands available, these will return the full path to the currently playing file:
  

  hs.plugin("InControl_Sage").GetSagePlayingByID "<Sage Device id>"
  hs.plugin("InControl_Sage").GetSagePlayingByName "<Sage Device Description in HomeSeer>"

• Changed send methed to use threads to avoid delay between events
• Fixed issue with configuration settings being saved in settings.ini instead of hspi_incontrol.ini
• HTML being sent as Device Strings was causing issues, added logic to strip out HTML
• Fixed event not being sent properly when activated by client causing event not to trigger
  

1.3.6

New Features:

• Within HomeSeer changed logic for sending updates to Sage to include only Sage devices that have logged in to correct delay when firewalls are involved or when a client is powered down.
• Within Sage, added property "lamansoft/incontrol/IgnorePing" when set to "true" in Sage.Properties, Sage will not ping for the HomeSeer Server. This will allow easier set up when firewalls are involved.
• Within Sage changed logic when first registering HomeSeer to ask if a Firewall will be used, if so, "lamansoft/incontrol/IgnorePing" will automatically be set to "true"
• Refined the Message display in Sage when images are sent to optimize the display.

1.3.5

New Features:

• Added "Stop" as a status that will appear for the Sage HomeSeer device and as an event to trap. NOTE, with this new status, the an idle device will be "On" until a program is watched and stopped, then the idle status will be "Stop".
• Fixed erronous triggers (Panel Trigger and Panel Trigger2) from appearing
• Fixed issue where "Stop" was triggering the Sage On event
• Fixed issue that caused the messages appearing on Sage to display internal system messages replacing the actual message
• Fixed issue where the HomeSeer device for Sage does not contain all of the values/graphics causing them to appear blank

1.3.4

New Features:

• Added "Paused" as additional status to the HomeSeer device for display and event triggering and its associated graphics
• Added ability for showing the title of the media file playing on the HomeSeer Device for Sage in the device status message
• Added ability to execute Sage API commands from Event Action Or HomeSeer script (http://download.sage.tv/api/index.html):
  a) hs.plugin("InControl_Sage").SendSageAPIByID "<Sage Device id or All Device>","<Sage API>"
  b) hs.plugin("InControl_Sage").SendSageAPIByName "<Sage Device Description in HomeSeer>","<Sage API>"
• Added EXPERIMENTAL ability to display a picture on the Messages sent to Sage (the path needs to be full path accessible by Sage):
  a) hs.plugin("InControl_Sage").SendSageMessageByID "<Sage id or All Devices>","<String message>","<Timeout in seconds>","<path to picture file>"
  b) hs.plugin("InControl_Sage").SendSageMessageByName "<Sage Description>","<String message>","<Timeout in seconds>","<path to picture file>"

1.3.3

New Features:

• Fixed bug where "TV" and "Temperature" were not showing as graphic options in the HomeSeer Device setup
• Fixed bug where Sage TV combo commands were not listed correctly (i.e. Channel Up & Page Up)

1.3.2

New Features:

• Added timeout (seconds) for how long messages sent to Sage will appear (0 seconds will keep message on screen until a button is pressed):
  Modified "Action" in HomeSeer event to allow entry of timeout
  hs.plugin("InControl_Sage").SendSageMessageByID "<Sage Device id or All Device>","<String message>","<Timeout in seconds>"
  hs.plugin("InControl_Sage").SendSageMessageByName "<Sage Device Description in HomeSeer>","<String message>","<Timeout in seconds>"
• Added "Channel Up" and "Channel Down" to the Sage Commands (for Events and Devices)
• Fixed bug where "Delete" a button on the HomeSeer Device was not working properly
• Fixed bug where "Right" from a location column with many buttons skipped over the devices column.
• Added UI control in Sage such that if a Location is "Selected" the focus will move over to the first Device
• Added Sage graphics for "Garage" and "Sprinkler" status

1.3.1

New Features:

• Enhanced HomeSeer Device creation and communication, including the ability to assign any SageCommand as a HomeSeer Device Button. Please note, you will need to manual remove the old HomeSeer Devices for Sage.
• Locations and devices are now sorted alphabetically.
• Within HomeSeer Device setup, now added the ability to send optionally the Device String or Device Value, instead of the Device Status. This will allow devices, such as temperature sensors or other similar devices to pass their status to HomeSeer. In addition, it will also send the default graphic properly.

1.3.0

New Features:

• Added "Sage Device" configuration in HomeSeer to allow for each Sage Device (Server UI, Client, Extender or Placeshifter) to have its own settings within Sage. In addition, to showing the basic configration, it will also highlight if the device is on/off and/or playing any media. Note, Sage Servers running as a service will NOT have a "Sage Device" in HomeSeer.
• InControl now allows HomeSeer to control Sage in the following ways:
  a) While in the "InControl" main web page, you can send basic commands to Sage (including Sending a message to Sage, Sleep, Stop, Extender On/Off, Exit-which will close Sage on a PC).
  b) While in the "InControl" main web page, you can bring up a Web Remote with most options to directly control the "Sage Device" of your choice.
  c) Within HomeSeer Event Actions, you can now select "Sage Command" to send most available actions to all or a specific "Sage Device".
  d) Within HomeSeer Event Actions, you can now select "Sage Message" to send a message to all or a specific "Sage Device".
  Each "Sage Device" can be set up with its own name and can be tied to a HomeSeer device
  e) Within HomeSeer scripting, there are 4 new commands available:
  

      hs.plugin("InControl_Sage").SendSageCommandByID "<Sage Device id or All Device>","<Sage Command>"
      hs.plugin("InControl_Sage").SendSageCommandByName "<Sage Device Description in HomeSeer>","<Sage Command>"
      hs.plugin("InControl_Sage").SendSageMessageByID "<Sage Device id or All Device>","<String message>"
      hs.plugin("InControl_Sage").SendSageMessageByName "<Sage Device Description in HomeSeer>","<String message>"

• While editing a "Sage Device" in HomeSeer, you may now allow it to create a normal HomeSeer device that will show a status of "On", "Off" or "Playing" for any "Sage Device" that is running InControl. This will allow normal HomeSeer Events to monitor the Change in its DeviceValue to trigger actions when Sage is turned on, off or contect starts playing.
• Added an InControl background to Sage

1.2.0

New Features:

• Added capability to Control Events with InControl. To select the Events that Sage will see, click on the "Events" link on the main InControl plugin page. The events will by default go to Sage with the group name being the location and the name of the event being the device. This can be changed to provide a more Sage friendly name. (HomeSeer and Sage)
• Significantly improved and added step by step progress indication as the Sage configuration is being performed. This will significantly assist in selecting the correct settings for HomeSeer and Sage to communicate (Sage)
• Added port to the Sage Server/Clients listing in the initial InControl screen Sage Listing (HomeSeer)
• In Options menu, will automatically try changed port if listner is not active, otherwise will prompt to restart Sage. This eliminates the need to restart Sage while trying to find an available port. (Sage)
• Added configuration parameter to set custom text for the button that appears in HomeSeer (HomeSeer)
• Added check for Client vs. Server to set RecPort to different numbers (to avoid conflict of Sage running as a service and running Sage Client on the server)

Bug Fixes:

• Corrected issue where plugin is being set up initially through an extender prevents the settings to be saved correctly for the server.
• Corrected issue where running Sage as a service and then starting the Sage UI on the same server as the service would conflict in the port they are using.

1.1.0

New Features:

• Reconfigured SageTV and HomeSeer Pairing process to eliminate false connections and multiple entries in HS
• Added capability in HomeSeer to clear all Sage connections
• Modified each Sage UI to access its own Sage properties fileAdded additional debug tracking capability

1.0.9

Bug Fixes:

• Added additional debug tracking capability

1.0.8

New Features:

• Initial version

[lamanmi]

B) Custom Thermostat Devices (use if your thermostat is not listed above)

DEVICE CONTROL (beyond On, Off and Dim): This version now supports the ability to execute any of the custom buttons that may be on your device. For example, in UltraMon, you can have a button that wakes a PC. Please Note the following:

A) By default your existing configuration and buttons will work as they have always done.

B) However, the next time you edit a device in HomeSeer, you will see a new set of options at the bottom to select which buttons you want Sage to see. For example, the control may support ON, OFF and DIM, however, you can choose for Sage to only allow ON and OFF. Or there may be a custom button called WAKE PC, you can now select this button to be sent to Sage. In fact, even the devices created to control Sage, can then be sent to Sage itself.

So for example, you can have a HomeSeer Device for an Extender in your bedroom and you can add a custom button to turn off that extender (Extender Off). This way when you are downstairs and you remember that extender is on, you can use Sage / InControl to turn it off.

Enjoy the new features. Thanks for your support.

[heatvent]

i get a valid connection to hs, but i can't get the sage plugin to login to hs even though the incontrol user settings are correct. I have had issues like this with past versions but seemed to get it working eventually. I have tried clearing all settings, uninstalling and installing the plugin, adding a new user for incontrol, all with no success. Again, the connection settings all appear as valid, I just can't login using good credentials. How can I best troubleshoot the issue?

[lamanmi]

I'm sorry to hear it is giving you problems. Were you previously running 1.3.6? If so, 1.4.0 corrected an issue in that all of the settings were previously going to the homeseer settings.ini instead of the hspi_incontrol.ini, so I suspect there may have been a specific setting that did not get migrated over.

To get started, let's make sure all of the existing configuration is removed by following the steps in http://board.homeseer.com/showpost.p...26&postcount=1.

Then if you are still having problems, lets enable logging by following the steps at http://board.homeseer.com/showpost.p...42&postcount=2.

Thanks!

i get a valid connection to hs, but i can't get the sage plugin to login to hs even though the incontrol user settings are correct. I have had issues like this with past versions but seemed to get it working eventually. I have tried clearing all settings, uninstalling and installing the plugin, adding a new user for incontrol, all with no success. Again, the connection settings all appear as valid, I just can't login using good credentials. How can I best troubleshoot the issue?

[heatvent]

I tried removing the configuration settings as described above and no luck. I will enable debugging but it may be until next weekend before I get a chance to send to you.

Thanks

[heatvent]

OK. I enabled logging but there is an issue prior to not being able to login. When trying to set the HS Connection, I press click to set but nothing happens. Previously, I manually edited the sage.properties sageclient.properties files to add a SageID. I stopped at this error this time so you can troubleshoot this problem. Maybe it has something to do with not logging in?? Attached is my SageTV log file. I don't have one for HS because this was just getting Sage configured.

[Xiphoid]

Extenders showing up on HS?

Just downloaded this plug-in and got it up and running. Is there a way for me to send a "Power On" command from HS to my HD300's?

[lamanmi]

Just downloaded this plug-in and got it up and running. Is there a way for me to send a "Power On" command from HS to my HD300's?

Xiphoid, yes, see the FAQ post at http://board.homeseer.com/showpost.p...45&postcount=3.

[heatvent]

Is there somewhere that details changes. The latest version seems to be 1.4.5.0 in the updater. What changed since 1.4.0?

[lamanmi]

Heatvent,

I'll update the main document. This version added additional device recognition to devices that use the devicevalue for controlling the device (i.e. Schlage door lock). However, this version still is not properly triggering the lock to lock or unlock. I have a ticket open with HS on how to do this through a plug in. No other aspects of the plug in were updated.

Thanks!

Is there somewhere that details changes. The latest version seems to be 1.4.5.0 in the updater. What changed since 1.4.0?