I just wanted to drop a note here that I am in the process of building up a Homeseer HSTouch template, initially for iPads, that will be made available.
I am working out the details to source professional quality graphics, while building the skin with HS content myself. Due to the large expense both monetarily and time wise, the project will have a cost attached. It will take a while to make ready, as I need to convert some content in the backend from script to plugin, and there is just an overall lot of work to make it happen in a reusable manner.
The objective is a professional quality screen interface with dynamic content. What does this mean?
-Time relevant page content. Example: Home screen shows house option to arm the alarm only if it is disarmed, etc. This is to cut down on the number of buttons and irrelevant content cluttering the screen.
-Reusable video and picture widgets supporting streaming video, fixed image, or image per x second display, with automatic alternative URL sources if the client is not currently on the local network. Configuration of data and URLs in an ini file is all that is needed.
-Per client handling of screens, and on the fly client selection of camera views, and etc.
-Security framework, so that HS can disable certain screens or events on certain client, according to the users desire.
-Typical screens for modern home automation: Listen, Watch, Lights, Weather, Security, Cameras, Climate, and additional Functions (considering under this Energy, Settings, etc).
-to be continued.
As I am trying to abstract as much as possible away from any particular HS install, and due to the various add on features, there will be both skin files, and back end files. The goal will be to make the skin as configurable as possible by way of ini file and HS backend objects, as they are easier to deal with than designer or hard coding in designer.
If you are interested, shoot me a PM, as it will help me gauge interest level, and sorting out of the pricing (largely dependent on cost of graphics for redistribution). I am also interested in any requests for features.
The only uncertainty at this point is how HS3 will impact the project, but as HS2 is the currently stable and fully working version, not to mention the various plugins, is the version that I will initially build support for.
Screenshots to come.
I am working out the details to source professional quality graphics, while building the skin with HS content myself. Due to the large expense both monetarily and time wise, the project will have a cost attached. It will take a while to make ready, as I need to convert some content in the backend from script to plugin, and there is just an overall lot of work to make it happen in a reusable manner.
The objective is a professional quality screen interface with dynamic content. What does this mean?
-Time relevant page content. Example: Home screen shows house option to arm the alarm only if it is disarmed, etc. This is to cut down on the number of buttons and irrelevant content cluttering the screen.
-Reusable video and picture widgets supporting streaming video, fixed image, or image per x second display, with automatic alternative URL sources if the client is not currently on the local network. Configuration of data and URLs in an ini file is all that is needed.
-Per client handling of screens, and on the fly client selection of camera views, and etc.
-Security framework, so that HS can disable certain screens or events on certain client, according to the users desire.
-Typical screens for modern home automation: Listen, Watch, Lights, Weather, Security, Cameras, Climate, and additional Functions (considering under this Energy, Settings, etc).
-to be continued.
As I am trying to abstract as much as possible away from any particular HS install, and due to the various add on features, there will be both skin files, and back end files. The goal will be to make the skin as configurable as possible by way of ini file and HS backend objects, as they are easier to deal with than designer or hard coding in designer.
If you are interested, shoot me a PM, as it will help me gauge interest level, and sorting out of the pricing (largely dependent on cost of graphics for redistribution). I am also interested in any requests for features.
The only uncertainty at this point is how HS3 will impact the project, but as HS2 is the currently stable and fully working version, not to mention the various plugins, is the version that I will initially build support for.
Screenshots to come.
Comment