HS3 – a peek around the corner
homeseer homeseer 3 hs3 road to hs3

HS3 – a peek around the corner

2013, February 4 – About Z-Wave

we have completely rewritten much of Z-Wave in HS3

2013, February 21 – About SSL support

… will SSL be supported in HS3? Yes this is planned.

2013, February 26 – About the Z-Wave rework

… In HS3, since our Z-Wave support is being vastly reworked, we have the opportunity to enhance this feature. For one thing, devices found on the Z-Wave Alliance certification list may be able to be identified by the software so that you, the consumer, will know whether you are using a device that has passed the Z-Wave Alliance’s tests of interoperability. What we will also be able to do is to identify a device by its product name, so that not only does it make sense looking at it in your own system, but it will also be able to be identified more easily as working with the current version of the Z-Wave plug-in for HS3 before you make a purchase.

2013, March 10 – Status update

We are in final stages of in-house testing, no beta this week, but any time now. As soon we work out reported issues we will move to posting a beta.

2013, March 15 – Another status update

In the middle of HS3 at the moment, trying to get a beta out.

2013, April 8 – About new features

It is almost easier to say what has not changed. Scripting support is still there, but probably most scripts will have to be touched in some way to update them to work with HS3 properly. For example, the device address is no longer the primary way of accessing a device – you can have a device without an address in fact, and you can have a device with an address that includes something specific about the device followed by the old code format if you want. For example, if your Z-Wave network is AABBCCDD, then you will have devices with a full address of AABBCCDD-10-Q05, which is a node 10 child device of network AABBCCDD. The code-only part of the address is Q05, which many people are familiar with. Accessing a device by name is unchanged.
Plug-ins can now run on remote systems and you can run multiple instances of a plug-in. A big part of the delay has been due in part to us removing Z-Wave from the core program and making it a standalone plug-in, and the new features that are being put into that.
It is our hope that testing of that plug-in will resolve some of the last of the more serious issues so that we can begin a public beta period soon.
I wish I could spend all day telling you about it, as there are many things I left out, but please understand that we are working as hard as we can to bring this to you as soon as possible.

2013, April 26 – About Perl scripting

Perl will work on Windows, but not on Linux right now. I realize Linux supports perl but we are using a Windows scripting host to run the process. You can launch a perl script from HS but I am not sure how it can access the scripting API.
The problem is that the scripting in windows is hosted using Windows Scritping Host, and this exposes our API to the script engine. This is not available on Linux, but I will research and see if there is a way to interface to Perl or Python from our application.

2013, May 2 – A HS3 teaser

A taste of things to come. Hang in there… won’t be too long before we can roll out the details for the first beta.

HS3 Teaser (events)

[Pictures & quotes coming from board.homeseer.com]