| Author |
|
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: May 11 2013 at 22:15 | IP Logged
|
|
|
Well, Im still in Korea but will be returning soon. Once I get back home I'll be back on it. Theres not much more to go but its obvious I still havent the nailed the hard hang problem as evidenced by all the problems Ive had since Ive been gone. It may be unique to my setup but before this rewrite, my system was as solid as a rock. I would hate to release in this state but could if necessary.
Anyways, Im hesitant to give any hard dates since fixing a bug is very difficult to estimate and I wouldnt want to end up missing another date. I can say that its close, my family obligations are pretty much done for the near future and I'll be able to devote a good portion of my off work time to finishing 2.1.5 up.
Hope this helps,
Dave.
|
| Back to Top |
|
| |
syonker
Senior Member
Joined: March 06 2009
Location: United States
Online Status: Offline
Posts: 212
|
| Posted: October 04 2013 at 19:32 | IP Logged
|
|
|
Hi Dave,
So I have a flawed Windows XP Pro VM that I can limp to the point that I can grab files and things on which PowerHome 214b runs...
At this point I'm wanting to give up on Windows XP here and move to Win7 or something modern that you might recommend.
That said,
1) Do you (or does anyone out there in PH land) recommend any particular OS as the host?
2) How in the *heck* do I do that exactly...is there another thread with detailed instructions for preserving one's data and exporting it to be available for another 214b installation?
3) For "prepping" the machine beyond the OS, what are the specific steps to getting to 214b again...?
4) Any other "gotchas" that folks can think of off-hand? My brain is TOTALLY clouded up right now because of this strep  I'm fighting while working, while dealing with setting up this VMware ESX Server. 
5) I should probably ask, but 214b is still *the* current platform, right?
Thanks in advance for any advice offered...
-S
__________________
"I will consider myself having succeeded when my house becomes sentient and attempts to kill me."
><(((º>`·.¸¸.·´¯`·.¸><(((º>¸.
·´¯`·.¸. , . ><(((º>`·.¸¸.·´¯`·.¸><(((º>
|
| Back to Top |
|
| |
GadgetGuy
Super User
Joined: June 01 2008
Location: United States
Online Status: Offline
Posts: 942
|
| Posted: October 06 2013 at 18:36 | IP Logged
|
|
|
Sorry Syonker. It took me longer to respond than I planned, as I realized my documentation cheat sheet was out of date so I had to update it first.
Here is my self-help guideline . . .
Terminate PH so it is not running.
Rename the c:\powerhome directory to something like “c:\powerhome_old” so it will be different from the directory name the Installer will create.
Reinstall the 2.1.2 beta full install (http://power-home.com/download/ph212setup.exe) or version 2.1.3 (http://power-home.com/download/ph213.zip) into “c:\powerhome (the default install folder).”
Unzip the 2.1.4 beta (http://www.power-home.com/download/ph214.zip) on top of it (that is, into the same folder c:\powerhome). You should be able to launch this virgin install and PH should work without getting a "Enter a username" message. This is just to verify that PH is able to launch properly and you don't have other problems with your PC.
If that all works . . .
Shutdown PH and copy over your pwrhome.ini and pwrhome.db filesfrom your renamed “old” PH folder into the proper locations and overwrite the virgin ones.
Also if you are running a custom web server via PH, then copy the contents of the old “web” folder into (overwriting) the new install ‘web’ folder.
Relaunch PowerHome and you should be fully recovered (you may have some graphics, plugin INI files, web files, etc. that are missing but you'll have the originals in your renamed c:\powerhome_bk directory).
If you have the newer Insteon devicces that use I2CS protocol then the I2CS Patch should be installed on top of everything. The patch is available with info here . . . (http://power-home.com/forum/forum_posts.asp?TID=3126&KW=I2C S+protocol)
A tutorial on adding I2CS devices after I encountered some major issues is available here . . .. ( http://power-home.com/forum/forum_posts.asp?TID=3173&PN=4)
NOTE: Enable Pending and Status Scan must be checked to complete adding an I2CS device.
ALSO NOTE: “phupg.exe” saved in the software folder is newer than what is installed by 2.1.4 so after the Installation, copy this newer phupg.exe over the older one.
Edited by GadgetGuy - October 06 2013 at 18:43
__________________
Ken B - Live every day like it's your last. Eventually, you'll get it right!
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: October 08 2013 at 21:15 | IP Logged
|
|
|
S-,
Was out of town this weekend and just got back so I
apologize for not answering sooner. However, Ken's
excellent instructions above should have gotten you going.
Just wondering how your upgrade went or if you need any
additional info.
Dave.
|
| Back to Top |
|
| |
syonker
Senior Member
Joined: March 06 2009
Location: United States
Online Status: Offline
Posts: 212
|
| Posted: October 09 2013 at 12:41 | IP Logged
|
|
|
Hi Ken,
You are AWESOME for providing this. I have been out of town for a few days so am just getting started on this transition now. That said, I have a few notes/questions on above:
1) For all practical purposes, this is a *totally new* install to a new Win7 VM box (currently running on a WinXP box), so I don't need to worry about over-writing anything and if I mess up too bad, I can just axe the box and start over with a new VM.
2) 2.1.3's link is not a "full install" but rather appears to be a "copy over patch" much like 2.1.4b. I was wondering if I need to do both the 2.1.3 and 2.1.4b patches in succession, or if after installing 2.1.2 I can just put in the 2.1.4b patch?
3) I don't really use the custom web server as I have been using Skip's PHCA Android application (which if you haven't tried is really outstanding  ). I did all of my own 3D renders of the house/rooms/controllable items so it's 100% "pictorial" in nature and is, in a word, "fun". However, I am thinking of putting in a new control center...but there is an "old" one in the database...what's the best way to clean the old one out to make room for a new one...?
4) If I don't have I2Cs already (I believe I do have at least one - garage door controller) I will soon, so will make sure that's all happy.
5) Can I just grab phupg.exe from the install folder after putting 2.1.2 in place and save it for re-instantiation after I have 2.1.4b in place (meaning, is the version installed with 2.1.2 the correct one to save off and copy back in later?).
Thanks in advance...the 2.12. install is completing as I write this.
-s
__________________
"I will consider myself having succeeded when my house becomes sentient and attempts to kill me."
><(((º>`·.¸¸.·´¯`·.¸><(((º>¸.
·´¯`·.¸. , . ><(((º>`·.¸¸.·´¯`·.¸><(((º>
|
| Back to Top |
|
| |
syonker
Senior Member
Joined: March 06 2009
Location: United States
Online Status: Offline
Posts: 212
|
| Posted: October 09 2013 at 15:53 | IP Logged
|
|
|
FYI - I ran into the problem mentioned in *this* thread: http://www.power-home.com/forum/forum_posts.asp?TID=2743
NOTE: Keeping a record of what I did after this for troubleshooting and knowledge-sharing purposes**
To solve it, I first installed version 2.1.b (downloaded from the main website link at: http://www.power-home.com/download/ph21bsetup.exe
Didn't bother with the extra installs...after this v2.1.2 from the link above installed seamlessly. Let the machine reboot after that.
Then I copied PowerHome v2.1.4's files (http://www.power-home.com/download/ph214.zip) into the "Program Files(x86)/powerhome" directory.
I then copied "phupg.exe" and the zip folder of the same name out of the Program Files(x86)/powerhome" directory to the desktop so I had a copy of them to re-instantiate later.
I then shutdown PowerHome on the old XP VM, and moved pwrhome.ini, from the XP machine to the "Program Files(x86)/powerhome directory on the new Windows 7 VM.
Then I moved pwrhome.db from the XP machine (sub-directory "Database") to "Program Files(x86)/powerhome/Database" directory on the Windows 7 VM as well.
Following that, I installed the I2Cs patch (http://power-home.com/forum/forum_posts.asp?TID=3126&KW=I2C S+protocol) by copying and replacing the two files in the package into the Windows 7's "Program Files(x86)/powerhome" directory.
Finally, I removed (with VM console) the USB interface to the Insteon Controller, and loaded it into the new VM (which was interesting since I didn't actually unplug or re-plug any USB devices...ESXi is pretty neat stuff that way). That seemed to install fine.
Rebooted the new box, and launched PowerHome and (drumroll please)........
Ouch.
1) It failed to accept my license key.
2) It comes up with a critical error.
3) Absolutely nothing from my database is showing up.
4) Shutting down also causes a critical error.
Ouch. Any ideas where I messed up?
-S
__________________
"I will consider myself having succeeded when my house becomes sentient and attempts to kill me."
><(((º>`·.¸¸.·´¯`·.¸><(((º>¸.
·´¯`·.¸. , . ><(((º>`·.¸¸.·´¯`·.¸><(((º>
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: October 09 2013 at 16:15 | IP Logged
|
|
|
Spencer,
On Windows Vista and up, you must install PowerHome into
c:\powerhome vs c:\program files(x86)\powerhome. This
will solve a number of problems.
The simplified steps should be:
1. Install version 2.1.2 into c:\powerhome
2. Unzip version 2.1.4 into c:\powerhome and overwrite
3. Unzip I2CS patch into c:\powerhome and overwrite
4. Copy your old pwrhome.db into c:\powerhome\database
and overwrite
5. Copy your old pwrhome.ini into c:\powerhome and
overwrite
6. Update pwrhome.ini with the directory change. Search
for "program files" and anywhere you see the old
directory, update to the new directory
7. Run phupg.exe to upgrade your database.
8. Launch PowerHome and it should open without requiring
registration or anything. It should have all of your old
settings.
9. Once open, you'll probably have to update any old
directories in the PowerHome Explorer for icons,
graphics, etc. Use the "Where used in database" report
to search for "%program files%" (without the double
quotes) to find all occurrences.
Hope this helps,
Dave.
|
| Back to Top |
|
| |
GadgetGuy
Super User
Joined: June 01 2008
Location: United States
Online Status: Offline
Posts: 942
|
| Posted: October 09 2013 at 16:24 | IP Logged
|
|
|
Right on Dave. I should have probably BOLDed the
c:powerhome directory reference as it is easy to miss.
Thanks for jumping in!
Hey. Hey. Hey. Winter is coming. Getting the RV ready to
visit your awesome (in the winter especially) home state.
See you in a few months!
__________________
Ken B - Live every day like it's your last. Eventually, you'll get it right!
|
| Back to Top |
|
| |
syonker
Senior Member
Joined: March 06 2009
Location: United States
Online Status: Offline
Posts: 212
|
| Posted: October 09 2013 at 16:47 | IP Logged
|
|
|
Ok, I killed the Program Files version and re-installed everything in "c:\powerhome".
It installed with success and shows my config as well as bypassed registration, but it's unfortunately still not happy.
It is throwing a critical error on startup (same one related to sockets) and the GUI works after that, but no I/O. The "Socket" error piqued a memory and I installed the command-line socket server and rebooted (PHCA uses sockets). Still the same results there though with the socket critical error.
Side Note: I was not able to run the upgrade the database, phupg proclaimed, "The databases is version 2.1.2" (I copied it from a 2.1.4 working system, so kind of figured it should just launch without conversion so am running it anyway...is that right?)
I could just re-vamp the old XP PH VM but it seems so wasteful. Running out of ideas though.
__________________
"I will consider myself having succeeded when my house becomes sentient and attempts to kill me."
><(((º>`·.¸¸.·´¯`·.¸><(((º>¸.
·´¯`·.¸. , . ><(((º>`·.¸¸.·´¯`·.¸><(((º>
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: October 09 2013 at 17:37 | IP Logged
|
|
|
Spencer,
Check out the second post on this thread: http://www.power-
home.com/forum/forum_posts.asp?
TID=2723&KW=cswskax6&PN=0&TPN=3
Should solve your problem.
Dave.
|
| Back to Top |
|
| |
syonker
Senior Member
Joined: March 06 2009
Location: United States
Online Status: Offline
Posts: 212
|
| Posted: October 09 2013 at 21:45 | IP Logged
|
|
|
Hi Dave,
Yup, that totally did it. NOTE: the OCX controls were all located in "C:\Windows\SysWOW64\..." on this machine...but still worked. 
-S
__________________
"I will consider myself having succeeded when my house becomes sentient and attempts to kill me."
><(((º>`·.¸¸.·´¯`·.¸><(((º>¸.
·´¯`·.¸. , . ><(((º>`·.¸¸.·´¯`·.¸><(((º>
|
| Back to Top |
|
| |
cmhardwick
Senior Member
Joined: July 08 2006
Location: United States
Online Status: Offline
Posts: 290
|
| Posted: October 10 2013 at 13:41 | IP Logged
|
|
|
Ok, I've just now upgraded to the latest/greatest. I have a question about the direct support of the thermostats. I have gadget guy's old script working without using the new thermostat entries in the Insteon Explorer. Is it worth deleting my device and adding it to the Thermostat area?
Thanks!
__________________
Cicero, Enjoying automation!
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: October 10 2013 at 14:28 | IP Logged
|
|
|
You wouldnt want to delete it from the Insteon devices. It actually needs to exist there. You would want to just add an entry to the Thermostats screen and then it will show on your Device Status screen.
Dave.
|
| Back to Top |
|
| |
cmhardwick
Senior Member
Joined: July 08 2006
Location: United States
Online Status: Offline
Posts: 290
|
| Posted: October 10 2013 at 21:45 | IP Logged
|
|
|
Got it. Current temp and Mode are pulling just fine, but the cool and heat set points are not pulling when the device is polled.
raw log:
2013-10-10 22:52:19.412 TX &nbs p; 02 62 14 B9 43 0F 6B 02
2013-10-10 22:52:19.522 RX &nbs p; SENTINSTEON=0F 43 16 14 B9 43 0F 6B 02 06
2013-10-10 22:52:19.819 RX &nbs p; RECEIVEINSTEONRAW=14 B9 43 0F 43 16 27 6B 03
2013-10-10 22:52:20.131 TX &nbs p; 02 62 14 B9 43 0F 6A 00
2013-10-10 22:52:20.194 RX &nbs p; SENTINSTEON=0F 43 16 14 B9 43 0F 6A 00 06
2013-10-10 22:52:20.647 RX &nbs p; RECEIVEINSTEONRAW=14 B9 43 0F 43 16 27 6A 92
2013-10-10 22:52:21.116 TX &nbs p; 02 62 14 B9 43 0F 6A 60
2013-10-10 22:52:21.147 RX &nbs p; SENTINSTEON=0F 43 16 14 B9 43 0F 6A 60 06
2013-10-10 22:52:21.741 RX &nbs p; RECEIVEINSTEONRAW=14 B9 43 0F 43 16 27 6A 4F
2013-10-10 22:52:22.147 TX &nbs p; 02 62 14 B9 43 0F 6A 20
2013-10-10 22:52:22.178 RX &nbs p; SENTINSTEON=0F 43 16 14 B9 43 0F 6A 20 06
2013-10-10 22:52:22.678 RX &nbs p; RECEIVEINSTEONRAW=14 B9 43 0F 43 16 27 6A 88
2013-10-10 22:52:23.053 RX &nbs p; RECEIVEINSTEONRAW=14 B9 43 0F 43 16 02 6A 90
2013-10-10 22:52:29.569 TX &nbs p; 02 62 14 B9 43 0F 19 00
2013-10-10 22:52:29.663 RX &nbs p; SENTINSTEON=0F 43 16 14 B9 43 0F 19 00 06
2013-10-10 22:52:29.975 RX &nbs p; RECEIVEINSTEONRAW=14 B9 43 0F 43 16 27 00 00
Some additional info:
If I run ph_gettstat("UPTHERM","setpoint",1) I get the heat setpoint (stat is set to AUTO).
If I run ph_gettstat("UPTHERM","coolsp",1), execution time is 0.000 and I get a -1 result, meaning invalid, correct? Same for heatsp and fanstat
Edited by cmhardwick - October 10 2013 at 22:21
__________________
Cicero, Enjoying automation!
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: October 11 2013 at 09:43 | IP Logged
|
|
|
Checking the raw log, it appears that everything is ok.
The request for setpoint is the line at 2013-10-10
22:52:22.178 with the response the next line with a value
of 88. 88 hex is 136 decimal, divide by 2, and the
setpoint should be 68.
What the problem may be is that the thermostat is
currently in auto mode. The Insteon protocol does not
have a command to query the "Cool" setpoint or the "Heat"
setpoint...only the "Setpoint" (I always thought this was
a huge oversight). With the thermostat in auto and no
current references in either heat or cool setpoint, PH
does not know where to apply the return value. To
correct this, I would open the Device Control screen and
use it to set the desired setpoints of your thermostat
for both heat and cool. With references to go by, PH
will use the current temperature to try and determine if
the thermostat is in a heat or cool mode (when it is in
auto) to try and set the appropriate setpoint with the
returned value.
Concerning your ph_gettstat commands....the fanstat is
not valid for the Insteon thermostat. Even though there
is an Insteon command for this, it has never worked.
Since the ph_gettstat function is designed to be generic
for all thermostats, the fanstat parameter may still be
applicable such as for an Elk thermostat. The -1 on the
coolsp would be due to the above mentioned problem where
there are no starting reference points to assign the
value for a thermostat in "auto" mode.
Dave.
|
| Back to Top |
|
| |
cmhardwick
Senior Member
Joined: July 08 2006
Location: United States
Online Status: Offline
Posts: 290
|
| Posted: October 11 2013 at 10:13 | IP Logged
|
|
|
makes perfect sense. i agree not having a protocol for coll and heat setpoint when in automode is crazy.
thanks for the great product and support
__________________
Cicero, Enjoying automation!
|
| Back to Top |
|
| |
cmhardwick
Senior Member
Joined: July 08 2006
Location: United States
Online Status: Offline
Posts: 290
|
| Posted: October 19 2013 at 18:32 | IP Logged
|
|
|
Ok, "setpoint" is showing up as the heat setpoint, and the cool is not changing at all. can I capture this value programmatically and make the correct entries? I'm assuming those entries are global variables somewhere.
Thanks
__________________
Cicero, Enjoying automation!
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: PowerHome Beta 2.1.2
