PowerHome does not currently have support for Z-Wave. We are however currently investigating the requirements for licensing the SDK and adding support for this exciting new technology.

Yes. The latest versions of PowerHome now have support for a generic plugin SDK. Using this SDK, you can create plugins for PowerHome in any language that supports the creation of activeX controls. In addition to the plugin SDK, PowerHome is also capable of interfacing with other programs through both it's Windows Messaging Interface and its Socket Server Interface.

Upgrades are free for life. While this policy could possible change in the future, anyone who is a registered user before the change will still be entitled to free upgrades.

PowerHome currently supports SAPI 4.0 for both Voice Recognition and Text to Speech. PowerHome also currently supports SAPI 5 for Text to Speech. Development has not yet started for Voice Recognition under SAPI 5 but we will be going in that direction.

PowerHome is having problems locating the database file (pwrhome.db). Shut down PowerHome and locate the pwrhome.ini file (this file is default located in C:\Program Files\PowerHome). Edit the pwrhome.ini file with Notepad and locate the [Database] section. Edit the "DBF" parameter so that it points to the PowerHome database file.

Not Currently. We will be looking into this new technology shortly.

PowerHome uses an ODBC connection to communicate with the Sybase Adaptive Server Anywhere database. This database is also accessible to any other program capable of connecting to ODBC databases (Microsoft Access, etc). The userid/password for access to the database is ph/ph

From within the PowerHome Explorer, navigate to Setup->Web. From within this screen all aspects of the webserver can be controlled. If PowerHome is the only webserver running, you can use a default port of 80. If another webserver or application is already using this port, you select another. Common ports for HTTP are 88,8000, and 8080.

The Adaptive Server Anywhere runtime engine opens port 3072 for remote access. You must allow this port to open in order for PowerHome to function.

No. However, a simple VB app could be written and interfaced to PowerHome using the Windows Messaging Interface. The internal COM routines could also be used to communicate with the NetRemote Interface. Once I acquire this interface, I will add support for it.

No. We will be creating an interface for Girder shortly. This should allow for interfacing to MainLobby.

YES! Beginning with version 1.03.4.3, PowerHome supports this popular interface.

Yes. PowerHome has the ability to both read and write values to the SECU-16 via an Ocelot controller. PowerHome is also aware of X-10 and IR commands that are generated by internal programming within the Ocelot.

No. PowerHome does not support the downloading of code to any of its currently supported controllers.

Yes. Caller ID support is now available using the PH_CID plugin available on the downloads page. This plugin supports most caller ID modems and the NetCallerID box and includes hangup support for flagged numbers.

Yes. PowerHome allows the user to declare System Process triggers for Startup, Shutdown, and Reinitialize and allows the user to execute macros or other code when these triggers are fired. PowerHome also has support for System Process triggers that allow code to be executed everytime the Control Center data is reloaded.

Yes. PowerHome supports any language that is supported by WSH (Windows Script Host). VBScript and JScript are included by default. Others are available for download from Microsoft.

Yes. Use the ph_runscript_? functions.