| Author |
|
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: September 12 2007 at 16:13 | IP Logged
|
|
|
The latest beta of PowerHome version 1.03.4.12 is now available for download. Also available are new Remote Clients.
Lots of changes and lots of fixes. Let me know if anyone has any problems or if Ive forgotten anything.
One thing to note that I didnt stress in the docs is that if you were using a Startup, Shutdown, or ReInit macro, this functionality is now changed. There is a new System trigger with Startup, Shutdown, and Reinitialize. Just create a trigger using these parameters and choose the macro of your choice to achieve the same functionality.
Dave.
|
| Back to Top |
|
| |
BeachBum
Super User
Joined: April 11 2007
Location: United States
Online Status: Offline
Posts: 1880
|
| Posted: September 12 2007 at 17:49 | IP Logged
|
|
|
Clean install as usual.. Thanks Dave
__________________
Pete - X10 Oldie
|
| Back to Top |
|
| |
sharby
Groupie
Joined: May 13 2007
Location: United States
Online Status: Offline
Posts: 50
|
| Posted: September 12 2007 at 23:13 | IP Logged
|
|
|
I'm rocking with .12 !!! Thanks for a great update! I am playing with the ph.comm and will update my progress.
-=*Sharby*=-
|
| Back to Top |
|
| |
sharby
Groupie
Joined: May 13 2007
Location: United States
Online Status: Offline
Posts: 50
|
| Posted: September 13 2007 at 00:49 | IP Logged
|
|
|
Error found in the Plugins "HELP" section.
The correct ActiveX Classname is PH_Comm.phcomm not PH_Socket.phsocket
See the CORRECTION below
Raw COMM
Launch Data (ActiveX Classname): PH_Comm.phcomm
Initialization Data: The COM port, a space, the comma separated settings string. Can be left blank to establish a connection manually. In all cases where a "settings" string is required, it consists of the BPS, the data bits, the parity, and the stop bits all separated by commas. An example of 9600 BPS, 8 data bits, No parity, and 1 stop bit would be: 9600,N,8,1
Dave works so hard and his design made me learn how to fix it.
THIS WORKS AWESOMELY!
-=*Sharby*=-
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: September 15 2007 at 10:51 | IP Logged
|
|
|
What is the default install structure for the remotes? I think I have old and new versions clashing and all appear to have the same version level (1.0.0.1) per Explorer.
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: September 15 2007 at 11:14 | IP Logged
|
|
|
N/M I think I have it. 
|
| Back to Top |
|
| |
ginigma
Senior Member
Joined: June 18 2006
Location: United States
Online Status: Offline
Posts: 127
|
| Posted: September 15 2007 at 18:33 | IP Logged
|
|
|
After install, when PH starts up, I get the following error while "opening main frame":
Script Server
An error occurred while creating the script server: -3
If I click Ok, PH continues to load and start successfully. Any thoughts? While it looks like the error is benign, it does stop PH from starting without user intervention, so I do need this fixed.
__________________
Insteon (40 devices) ^ PowerHome (435 links) ^ Logitech Harmony 880
|
| Back to Top |
|
| |
jbbtex
Senior Member
Joined: February 15 2007
Location: United States
Online Status: Offline
Posts: 181
|
| Posted: September 15 2007 at 19:23 | IP Logged
|
|
|
ginigma wrote:
After install, when PH starts up, I get the following error while "opening main frame":
Script Server
An error occurred while creating the script server: -3
If I click Ok, PH continues to load and start successfully. Any thoughts? While it looks like the error is benign, it does stop PH from starting without user intervention, so I do need this fixed. |
|
|
I had this same problem after I upgraded. I found the solution here in an old post from Dave.
HTH,
Brady
|
| Back to Top |
|
| |
jeffw_00
Super User
Joined: June 30 2007
Online Status: Offline
Posts: 929
|
| Posted: September 15 2007 at 20:14 | IP Logged
|
|
|
so if I want to futz with powerhome for the first time, should I use this or the release version (I'd rather use the beta if it's pretty stable).
also - can this run concurrently with Houselinc? Or will they conflict using the TimerApp (basically I want to let Houselinc continue to run my house while I get familiar with PowerHome)
|
| Back to Top |
|
| |
cmhardwick
Senior Member
Joined: July 08 2006
Location: United States
Online Status: Offline
Posts: 290
|
| Posted: September 15 2007 at 20:34 | IP Logged
|
|
|
Just put in the .12 release (was still using 10). Works great and cleared up the issue I was having with manual changes (dimming/brightening from keypad or remotelinc, etc) not being registered in the PH database. Local control changes are also working correctly now so if the wife (or I) turn on a lamp manually, it will register when it's polled.
Thanks Dave! Now just to work on the UPD part ... and the CC part ... and the ..............
__________________
Cicero, Enjoying automation!
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: September 15 2007 at 22:03 | IP Logged
|
|
|
The script server error is caused by installing PowerHome in other than the default directory. I need to work out a clean way to handle this for the next version.
In the PowerHome directory should be installed a file named phscr.reg. It has the path to the script server component hardcoded within it towards the end. When PowerHome is initially installed, it will automatically register the script server in whatever directory PowerHome is installed in so all is well initially (this is the way it's been working for some time). However, in the latest version, in order to handle PowerHome being run as a service, all of the components need to be registered from within PowerHome as the service user. PowerHome attempts to do this automatically for you using the new "activex" table and the phscr.reg file. PowerHome does this automatically every time that it is run. So, PowerHome is installed and everything registers properly, but whenever PowerHome is run, it will re-register to the wrong location because the phscr.reg file points to the default install directory which will be incorrect if PowerHome was not installed there.
The best way to fix this for now is to edit the phscr.reg file in the PowerHome directory (wherever it was installed if the default was not accepted) and correct the filepath towards the very bottom. Be sure to use the double \\ to represent a single backslash. Save the file and restart PowerHome. PowerHome should now re-register the script server using the information in the modified phscr.reg file and if all is correct, the problem should be fixed.
Hope this helps,
Dave.
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: September 15 2007 at 22:06 | IP Logged
|
|
|
Jeff,
Definately use the latest .12 beta. It's much more stable that the current release version and has infinitely more features. The release doesnt support Insteon or any of the newer features that most of the people are posting message about or taking advantage of.
Cicero,
Glad to hear it's working for you and that I got several of your bugs fixed  . Just curious, what is the UPD part? A mistype of UPB or UDP or something else that I cant think of at the moment  .
Dave.
|
| Back to Top |
|
| |
jeffw_00
Super User
Joined: June 30 2007
Online Status: Offline
Posts: 929
|
| Posted: September 15 2007 at 22:13 | IP Logged
|
|
|
Thanks Dan - will it co-exist with Houselinc Desktop and the TimerApp that it uses? I'd like to keep my house running while I futz with Powerhome 8-}
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: September 15 2007 at 23:48 | IP Logged
|
|
|
Heh, Dave...
Im not entirely sure, but I would think so. They both should be able to share the SDM activex control and talk at the same time. I would probably disable one or the other while attempting to do any linking...it may be possible for one or the other to get confused. For standard control though, I would expect they would co-exist.
The Timercoreapp12 that PowerHome uses is the standard, latest core app that SmartHome supplies. It should be the same as HouseLincs.
Dave.
|
| Back to Top |
|
| |
jeffw_00
Super User
Joined: June 30 2007
Online Status: Offline
Posts: 929
|
| Posted: September 16 2007 at 00:04 | IP Logged
|
|
|
sorry Dave! (That's D-a-v-e! 8-}) - (I know a "Dan Howard" in my non-virtual life...my bad)
as to the other, I'll be fine then - i primarily want to power up the program and play around with it - will be issuing very few commands down the powerline.
Thanks!
/j
|
| Back to Top |
|
| |
BeachBum
Super User
Joined: April 11 2007
Location: United States
Online Status: Offline
Posts: 1880
|
| Posted: September 16 2007 at 00:08 | IP Logged
|
|
|
That's a good question Dave. I migrated from one app and PLC to another although at times both were talking but to have one PLC and two apps running is interesting. Jeff keep us informed.
__________________
Pete - X10 Oldie
|
| Back to Top |
|
| |
cmhardwick
Senior Member
Joined: July 08 2006
Location: United States
Online Status: Offline
Posts: 290
|
| Posted: September 16 2007 at 19:14 | IP Logged
|
|
|
sorry, UDP. Was so excited the other stuff was working right, didn't check my spelling hehehe. Trying to brush up on my coding so I can maybe write a plugin for xLobby, but it will be a while. currently, I'm still using Manny's coding and it does great.
__________________
Cicero, Enjoying automation!
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: PowerHome 1.03.4.12
