Author |
|
jeffw_00 Super User
Joined: June 30 2007
Online Status: Offline Posts: 929
|
Posted: January 28 2023 at 09:55 | IP Logged
|
|
|
Hi - I'm running 2.2 Beta 3, and my wife is at her wits end because of
the side-effects of the Comm problems. (Driving me a little nuts too).
I know Dave has been too busy to work on it, and I respect that. The
thing is - I didn't really need the update (I was just trying to stay
current) but I don't know if there's a way I can go back to a previous
version (I think the last one I have is 2.15c) using the current
database. Anyone know? Thanks!
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: January 28 2023 at 10:46 | IP Logged
|
|
|
Hi Jeff,
Reverting back to an older version is a little tricky if you want to retain the newer database.
Let me know for sure which version you want to revert back to as well as your current version (check Help->About for the full version number)
and I'll figure out what the best approach will be for you.
Dave.
|
Back to Top |
|
|
jeffw_00 Super User
Joined: June 30 2007
Online Status: Offline Posts: 929
|
Posted: January 28 2023 at 10:51 | IP Logged
|
|
|
Hi Dave - that's awfully kind of you, but since you're willing to help,
in this case I'm going to thank you and take you up on it as I really
need to do something.
I'm actually not 100% sure which version I had before this one, but
it doesn't really matter, Since the Comm issue appeared only (I
think) in the latest release. So - Can you recommend which
version I should roll back to to have the most recent release that is
stable, doesn't have the comm issue, and is the easiest and lowest-
risk to convert my database to?
( I don't have any attraction to any particular version. I only
mentioned 2.1.5c because I (usually...) keep the installers of prior
SW versions and the most recent one I have before the latest is
that one, but I may have messed up and not kept a more recent
one. )
TIA!
/j
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: January 28 2023 at 11:31 | IP Logged
|
|
|
Jeff,
2.1.5e was the last version before 2.2 where the Insteon module changed and casued the problems that some
people are having.
I reviewed the changes necessary to go back to 2.1.5e and it's not something you would be able to do on your
own. You would need to zip and email your pwrhome.db file (make sure you shutdown PowerHome before copying)
and I can manually downconvert it for you. Once I complete that and email back to you, you would shutdown 2.2,
rename the c:\powerhome directory to c:\powerhome_22 and then install version 2.1.5c. You would then download
and unzip the 2.1.5e patch on top of that. Copy over your old pwrhome.ini file and the database that I patched
for you and you should be good.
Dave.
|
Back to Top |
|
|
jeffw_00 Super User
Joined: June 30 2007
Online Status: Offline Posts: 929
|
Posted: January 28 2023 at 11:50 | IP Logged
|
|
|
Emailed to you -thanks!
|
Back to Top |
|
|
jeffw_00 Super User
Joined: June 30 2007
Online Status: Offline Posts: 929
|
Posted: January 28 2023 at 11:57 | IP Logged
|
|
|
So I have on my PC 2.1.5.c setup.exe from 2015, and I have 2.1.5.e
patch from here:
http://www.power-home.com/forum/forum_posts.asp?TID=10869
I think I move my 2.2 elsewhere, install 2.1.5.c , unzil 2.1.5.e over the
2.1.5c install, use my new pwrhome.db, and I should be good to go?
Edited by jeffw_00 - January 28 2023 at 11:57
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: January 28 2023 at 18:02 | IP Logged
|
|
|
Jeff,
Just emailed you your downconverted database that should be compatible with 2.1.5.
To go back, follow these steps:
1. Shutdown PowerHome
2. Rename c:\powerhome directory to c:\powerhome_22
3. Install your 2.1.5c setup.exe. This will create a new c:\powerhome directory.
4. Unzip the the 2.1.5e zip on top of the c:\powerhome directory overwriting existing files.
5. Copy the new database file to c:\powerhome\database overwriting what is there.
6. Copy your c:\powerhome_22\pwrhome.ini file to c:\powerhome\pwrhome.ini overwriting the file there.
7. Should be good to start PowerHome version 2.1.5e in c:\powerhome.
Let me know if you have any problems.
Dave.
|
Back to Top |
|
|
Lenny Senior Member
Joined: January 06 2008
Online Status: Offline Posts: 102
|
Posted: January 28 2023 at 18:38 | IP Logged
|
|
|
Are the communications problem you are having look like this and you have to restart powerhome? I been fighting with this for quite a while. I tried new usb serial adapter and checked the PLM for bad caps. I'm at a loss at trying to figure out why it keeps happening. Really regret not buying a spare Serial PLM now. Would make troubleshooting easier.
Dave, if this is the same issue and will fix my problem I would appreciate a downgrade from 2.2 beta 3-3
Lenny
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: January 29 2023 at 00:23 | IP Logged
|
|
|
Lenny,
Not sure if the above is related to Jeff's problem or not. I would need for him to comment if his issues were the same or not. One thing you may
want to try first is loading the 2.2beta3-5 version on top of your 2.2beta3-3. I know 3-5 includes fixes for some of the Insteon problems that
users were experiencing and could possibly eliminate yours.
However, if that doesnt work for you or you'd rather just downgrade, send me a zip of your database file and I can downgrade it for you.
Dave.
|
Back to Top |
|
|
jeffw_00 Super User
Joined: June 30 2007
Online Status: Offline Posts: 929
|
Posted: January 29 2023 at 08:34 | IP Logged
|
|
|
Lenny - I'm not sure what I'm looking at in your photo. My problem is
detailed at the link below, and is specific to sequences using the Delay
command.
http://www.power-home.com/forum/forum_posts.asp?
TID=10959&PN=2
No restarts necessary, just a lot of non-fatal errors that somewhat
effect operation.
Edited by jeffw_00 - January 29 2023 at 08:35
|
Back to Top |
|
|
jeffw_00 Super User
Joined: June 30 2007
Online Status: Offline Posts: 929
|
Posted: January 29 2023 at 09:01 | IP Logged
|
|
|
Thanks Dave - I followed your instructions, and things are -mostly-
working (including fixing my issue, thanks! I sent you the two things
that aren't working right by Email so I could more easily send multiple
screenshots. TIA for any suggestions you have.
/j
|
Back to Top |
|
|
Lenny Senior Member
Joined: January 06 2008
Online Status: Offline Posts: 102
|
Posted: January 29 2023 at 10:30 | IP Logged
|
|
|
PLM comm errors is what I have been fighting with... I have recreated some macro's because I saw that in other posts but that doesn't seem to help. After 5 attempts when I look in insteon explorer i see the "Create I2CS Initial: DEVICE". I reinitialize PH and its Ok for a bit. It really feels like comm issues between PH and the PLM, which is to blame I don't know.
Edited by Lenny - January 29 2023 at 15:15
|
Back to Top |
|
|
jeffw_00 Super User
Joined: June 30 2007
Online Status: Offline Posts: 929
|
Posted: January 29 2023 at 10:31 | IP Logged
|
|
|
HI Lenny - that is different than mine - perhaps for clarity you should
start a separate thread with Dave and move your posts there?
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: January 29 2023 at 12:39 | IP Logged
|
|
|
Jeff,
Got your emails and looks like I missed some changes in views. I'll make some more changes to correct it in the file I already sent and
then send you the updated file to try.
Really sorry to have missed that.
Dave.
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: January 29 2023 at 12:40 | IP Logged
|
|
|
Lenny,
Give the 3-5 version a try as I believe it corrects this specific problem.
If not, let me know and I'll downconvert your file for you.
Dave.
|
Back to Top |
|
|
jeffw_00 Super User
Joined: June 30 2007
Online Status: Offline Posts: 929
|
Posted: January 29 2023 at 12:44 | IP Logged
|
|
|
No problem Dave - happy to be working with you.
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: January 29 2023 at 14:05 | IP Logged
|
|
|
Jeff,
Just emailed you a new version of the database. Took a lot more than I realized as all the views had changed as well as some of the base table structure. I think I
caught everything this time so let me know if you run into any other problems.
Dave.
|
Back to Top |
|
|
Lenny Senior Member
Joined: January 06 2008
Online Status: Offline Posts: 102
|
Posted: January 29 2023 at 15:13 | IP Logged
|
|
|
Dave,
I made backup copy of my PH folder and I extracted the zip over my 2.2B3-3 with to 2.2B3-5. I unblocked all the files and ran the phupg.exe and restart the PC. Shouldn't take long to know if it helped.
Thanks
dhoward wrote:
Lenny,
Not sure if the above is related to Jeff's problem or not. I would need for him to comment if his issues were the same or not. One thing you may
want to try first is loading the 2.2beta3-5 version on top of your 2.2beta3-3. I know 3-5 includes fixes for some of the Insteon problems that
users were experiencing and could possibly eliminate yours.
However, if that doesnt work for you or you'd rather just downgrade, send me a zip of your database file and I can downgrade it for you.
Dave.
|
|
|
|
Back to Top |
|
|
jeffw_00 Super User
Joined: June 30 2007
Online Status: Offline Posts: 929
|
Posted: January 29 2023 at 15:17 | IP Logged
|
|
|
Thank You Dave - All is well and working great. MUCH
APPRECIATED!
|
Back to Top |
|
|
Lenny Senior Member
Joined: January 06 2008
Online Status: Offline Posts: 102
|
Posted: February 02 2023 at 18:24 | IP Logged
|
|
|
Dave,
It's been a few days, crashing is less but still pretty bad. At this point I just need to figure out what switches to change over too. According to the last Insteon webinar PLM's are not going to be available until March. Thanks for your support as usual.
|
Back to Top |
|
|