brad77 Posted January 22, 2010 Share Posted January 22, 2010 Notice:Due to the relatively high severity of bugs found in 2.7.9, it's strongly advised to either wait for release 2.7.10 or install 2.7.7 instead. If you would like to get instructions for 2.7.7, please send an email to support@universal-devices.com. Please note that if you so choose to install 2.7.9, all your INSTEON changes will be lost in 2.7.10 as you would have to restore a backup from a release prior to 2.7.8. If you are already using 2.7.9:: 1. Please do not make any changes to your INSTEON configuration (i.e scenes, devices, restoring devices, restoring PLM, etc.). Program changes are OK 2. Please do not use any backup of 2.7.9 on 2.7.10 and above Yikes! I don't remember seeing this when I chose to upgrade to 2.7.9a! When was this updated? Had I know this before upgrading, I certainly wouldn't have done so. I am starting to regret that decision. I suppose that's the price you pay for being an alpha tester. Quote Link to comment Share on other sites More sharing options...
gfridland Posted January 22, 2010 Share Posted January 22, 2010 After reading the updated bugs summary for 2.7.9a and haveing a significantly modified insteon installation since upgrading to 2.7.9, I decided to downgrade to a version that would allow me to maintain a solid backup file for future use. Not sure if I was lucky or just good, but I was able to successfully downgrade to 2.7.7 from 2.7.9a. All devices, programs, settings were maintained. I am now in 2.7.7 and created a backup file for the system. The only issues I encountered were: Had to rebuild only those programs that had notifications as they appeard to be damaged...I was not able to delete or alter the notifications that were converted from specific addresses to "notify all" I had 3 "notify all" in my program and when I would try to delete this line, I was unable to do so. I'm not sure if this would have caused issues, so I rebuilt these programs and deleted the problem ones. Also, I lost one of the notification addresses...this was a text notification. Also an easy fix. Hope this may work for others that are feeling lucky! Quote Link to comment Share on other sites More sharing options...
AnthemAVM Posted January 22, 2010 Share Posted January 22, 2010 I tried to down grade my ISY back to 2.7.7 from the 2.7.9. I see old items that I removed in 2.7.9, but the ISY still shows that it has 2.7.9 firmware. Any ideas? Quote Link to comment Share on other sites More sharing options...
gfridland Posted January 22, 2010 Share Posted January 22, 2010 I'm able to see 2.7.7 in the Help...About pop-up. I would try clearing cache if you didn't already. I noticed a few more issues after the downgrade to 2.7.7 from 2.7.9a: 2 of 6 KPL's links had to be removed and then added back into scenes to function properly...not sure why, but it appears that there were some broken links after the downgrade. Interestingly, this only affected 2 KPL's and no other devices. The links still existed in the devices, but when I tried to trigger a scene from the Java console, the KPL buttons would not respond. After the "remove from scene" and add beck into same scene, all works well. Quote Link to comment Share on other sites More sharing options...
upstatemike Posted January 22, 2010 Share Posted January 22, 2010 I am running 2.7.8 and since upgrading have swapped a large number of devices due to paddle problems and also manually renamed and assigned folders to all 440 of my devices, scenes and programs. Am I going to lose all of this work? Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted January 22, 2010 Share Posted January 22, 2010 Hello all, Apologies for causing a panic! We put that notice up there to discourage new installations. Please note the following: 1. 2.7.10 will automatically migrate your system from 2.7.8/9 2. The only things you might lose (are not going to be in synch with ISY) are KPL related settings: -- Mutually exclusive button for the same KPL -- Buttons from the same KPL controlling one another 2. If you really want to go back to 2.7.7, you will have to RESTORE the backup from 2.7.7 ... 2.7.7 cannot backward migrate file system With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
brad77 Posted January 22, 2010 Share Posted January 22, 2010 2.7.10 will automatically migrate your system from 2.7.8/9 That's much better! Thanks for clearing that up. Quote Link to comment Share on other sites More sharing options...
gfridland Posted January 22, 2010 Share Posted January 22, 2010 Michel, can you clarify: "If you really want to go back to 2.7.7, you will have to RESTORE the backup from 2.7.7 ... 2.7.7 cannot backward migrate file system" Is this true in all cases? Are there specific devices that pose issues? The reason I ask is that I simply Upgraded the firmware to 2.7.7 without resoring the database from my prior 2.7.7 install (main reason was that I have modified the install significantly since going to 2.7.9.) All devices/ programs/ scenes migrated to the 2.7.7 and left me with a few issues as described in recent posts to correct. Thanks again in advance! Quote Link to comment Share on other sites More sharing options...
rlebel Posted January 22, 2010 Share Posted January 22, 2010 Hello all, 2. The only things you might lose (are not going to be in synch with ISY) are KPL related settings: -- Mutually exclusive button for the same KPL -- Buttons from the same KPL controlling one another Does that mean that a restore of any problem KPL will put it back in sync? Quote Link to comment Share on other sites More sharing options...
AnthemAVM Posted January 23, 2010 Share Posted January 23, 2010 I tried to down grade my ISY back to 2.7.7 from the 2.7.9. I see old items that I removed in 2.7.9, but the ISY still shows that it has 2.7.9 firmware. Any ideas? A good glass of red wine and I just figured it out. I figured if you just reloaded your 2.7.7 backup it would roll back. I think you need to reinstall 2.7.7. and then load up your back up. Michael Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted January 24, 2010 Share Posted January 24, 2010 gfridland, The issues are KPL related: 1. Mutual exclusive buttons 2. Buttons from the same KPL in the same scene If you do not have any of these conditions, then everything should be migrated automatically. rlebel, No, because once 2.7.10 migrates 2.7.9 files, it's going to ignore certain bytes and thus restore will not work. With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
jkraus Posted January 26, 2010 Share Posted January 26, 2010 so how do you know which of our backups are from 2.7.7 as it is not in the name of the saved file? so if I get this right, we reinstall 2.7.7, install our backup and migrate to 2.7.10? Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted January 26, 2010 Share Posted January 26, 2010 jkraus, Unfortunately you have to go by date. The procedure is this: 1. Upgrade to 2.7.10 2. Restore your back up from 2.7.7 3. After reboot, ISY migrates everything for you With kind regards, Michel so how do you know which of our backups are from 2.7.7 as it is not in the name of the saved file? so if I get this right, we reinstall 2.7.7, install our backup and migrate to 2.7.10? Quote Link to comment Share on other sites More sharing options...
CopyRon Posted January 26, 2010 Share Posted January 26, 2010 Is 2.7.10 available? I haven't received notice. Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted January 27, 2010 Share Posted January 27, 2010 Hi Ron, Not yet but shortly. With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
rlav Posted January 28, 2010 Share Posted January 28, 2010 Hello, Sorry if this has been reported. Running 2.7.9, I have a problem with the EZIO6I. Whatever input port is closed it always reports as port 1 being use. Thu 01/28/2010 06:12:34 PM : [ 1 70 FD 9] DON 0 Thu 01/28/2010 06:13:37 PM : [ 1 70 FD 9] DOF 0 I was running 2.7.6 for a long time without this problem. Thank You, RLav Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted January 29, 2010 Share Posted January 29, 2010 Hi RLav, Would you be kind enough to be more specific? Are you saying that every time the state of that device changes to on it goes back to off (or vice versa)? With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
rlav Posted January 29, 2010 Share Posted January 29, 2010 Here is the situation with my EZIO6I. I am using the 4 input ports to monitor the status on my alarm system. I have 4 output relays on my alarm that are connected with the EZIO6I: Port 1 is Alarm Stay Port 2 is Alarm Away Port 3 is Alarm Disarm Port 4 is Aralm Burglar With version 2.7.6 everything was working fine. Now with version 2.7.9, whatever the mode of my alarm system, I only have the Stay mode to On. To explain differently, the status of the 4 input ports on EZIO6I are reported as port 1. Should I try to load Alpha 2.7.10 or revert back to previous version? Thank you for your help. Quote Link to comment Share on other sites More sharing options...
JBNY Posted January 29, 2010 Share Posted January 29, 2010 So I upgraded from 2.7.6 to 2.7.9 to 2.7.10 and am not sure what backup is the right one, as they do not have the firmware version on it. I have 4 KPL that two of them have some extensive linking that was done before I had the ISY99i. In v2.7.9 I removed and re-added a KPL because the ISY99i was not reading the the version correctly. But other than that I have not made any changes with 2.7.9 Do really need to hardware reset all my KPL? Everything looks to be fine on FW 2.7.10. Can I just delete them from the ISY99i and re-add them? I think I would rather wipe the ISY99i clean and start again, than reset and wipe all my KPLs. -Joe Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted January 29, 2010 Share Posted January 29, 2010 Hi rlav, Yes, it's best to try 2.7.10 and keep us posted. Apologies for the inconvenience. With kind regards, Michel Here is the situation with my EZIO6I. I am using the 4 input ports to monitor the status on my alarm system. I have 4 output relays on my alarm that are connected with the EZIO6I: Port 1 is Alarm Stay Port 2 is Alarm Away Port 3 is Alarm Disarm Port 4 is Aralm Burglar With version 2.7.6 everything was working fine. Now with version 2.7.9, whatever the mode of my alarm system, I only have the Stay mode to On. To explain differently, the status of the 4 input ports on EZIO6I are reported as port 1. Should I try to load Alpha 2.7.10 or revert back to previous version? Thank you for your help. Quote Link to comment Share on other sites More sharing options...
JBNY Posted January 29, 2010 Share Posted January 29, 2010 So after running 2.7.10 for a few hours I still am getting the System Busy when accessing the ISY99i. Basically at this point no programs run and I can not get status on any devices. If I reboot the ISY99i it goes away for a while, same problem I was having on 2.7.9. Can I fall back to the release fw at this point? Or do I need to work through this on 2.7.10? Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted January 29, 2010 Share Posted January 29, 2010 Hello JBNY, I am so very sorry to hear this. This might be due to the system trying to synch up all devices with ISY. If you have not restored your 2.7.7 backup yet, please do try it. With kind regards, Michel So after running 2.7.10 for a few hours I still am getting the System Busy when accessing the ISY99i. Basically at this point no programs run and I can not get status on any devices. If I reboot the ISY99i it goes away for a while, same problem I was having on 2.7.9. Can I fall back to the release fw at this point? Or do I need to work through this on 2.7.10? Quote Link to comment Share on other sites More sharing options...
rlav Posted January 29, 2010 Share Posted January 29, 2010 Michel, I upgraded from 2.7.9 to 2.7.10 succesfully. But I still have the same problem with EZIO6I. I have a spare unit that I know was working that I also try. I needed to add it to ISY. I got the following error message: [-200000] Node not added - failed restoring device [1 70 EF 1] [-100002] Couldn't open file [/CONF/170EF.REC] Here is the Log: Fri 01/29/2010 06:23:25 PM : ---- Initializing the linked devices ---- Fri 01/29/2010 06:23:25 PM : ---- All Linked Devices are now initialized ---- Fri 01/29/2010 06:23:25 PM : ---- Add remaining devices ---- Fri 01/29/2010 06:23:25 PM : [ 1 70 EF 1] Removing all links Fri 01/29/2010 06:24:04 PM : [1 70 EF 1] i2 data transfer commands do not work. Reverting to i1 Fri 01/29/2010 06:24:05 PM : [ 1 70 EF 1] Adding device to ISY t=07.07.0000 Fri 01/29/2010 06:24:05 PM : [test - 9] Start : Adding device to ISY Fri 01/29/2010 06:24:44 PM : [1 70 EF 9] i2 data transfer commands do not work. Reverting to i1 Fri 01/29/2010 06:24:45 PM : [test - 9] Finish : Adding device to ISY was Successful Fri 01/29/2010 06:24:46 PM : [test - A] Start : Adding device to ISY Fri 01/29/2010 06:24:46 PM : [test - A] Finish : Adding device to ISY was Successful Fri 01/29/2010 06:24:46 PM : [test - B] Start : Adding device to ISY Fri 01/29/2010 06:24:46 PM : [test - B] Finish : Adding device to ISY was Successful Fri 01/29/2010 06:24:47 PM : [test - C] Start : Adding device to ISY Fri 01/29/2010 06:24:47 PM : [test - C] Finish : Adding device to ISY was Successful Fri 01/29/2010 06:24:47 PM : [test - D] Start : Adding device to ISY Fri 01/29/2010 06:24:47 PM : [test - D] Finish : Adding device to ISY was Successful Fri 01/29/2010 06:24:47 PM : [test - E] Start : Adding device to ISY Fri 01/29/2010 06:24:47 PM : [test - E] Finish : Adding device to ISY was Successful Fri 01/29/2010 06:24:47 PM : [ 1 70 EF 1] ** Not Added ** Restore node Failed Fri 01/29/2010 06:24:47 PM : ---- All Remaining Device Added ---- Fri 01/29/2010 06:24:47 PM : [ 1 70 EF 9] ST 0 Fri 01/29/2010 06:24:47 PM : [ 1 70 EF A] ST 0 Fri 01/29/2010 06:24:47 PM : [ 1 70 EF B] ST 0 Fri 01/29/2010 06:24:47 PM : [ 1 70 EF C] ST 0 Fri 01/29/2010 06:24:48 PM : [1 70 EF 9 ] Link 0 : 0FF8 [E2010FD840FF1F01] Writing [E2010FD840FF1F01] Fri 01/29/2010 06:24:56 PM : [PLM ] Group 1 : Writing Responder Link matching [1 70 EF 9 ] Link 0 : 0FF8 [E2010FD840FF1F01] Fri 01/29/2010 06:24:56 PM : [1 70 EF 9 ] Memory : Write dbAddr=0x0045 [0E] Fri 01/29/2010 06:24:57 PM : [1 70 EF 9 ] Memory : Write dbAddr=0x0044 [0D] Fri 01/29/2010 06:24:58 PM : [1 70 EF 9 ] Memory : Write dbAddr=0x0043 [0C] Fri 01/29/2010 06:24:59 PM : [1 70 EF 9 ] Memory : Write dbAddr=0x0042 [0B] Fri 01/29/2010 06:25:00 PM : [1 70 EF 9 ] Memory : Write dbAddr=0x0041 [0A] Fri 01/29/2010 06:25:01 PM : [1 70 EF 9 ] Memory : Write dbAddr=0x0040 [09] So now what should I do or try. Revert back to 2.7.6, 2.7.7, or 2.7.8? Will I need to reload a backup from 2.7.6? Or shall I wait for the fix in the next release? If the fix is only 1 or 2 weeks away, I can wait. Thank you again, RLav Quote Link to comment Share on other sites More sharing options...
hart2hart Posted January 30, 2010 Share Posted January 30, 2010 This issue still exists. Just added every device from scratch and created scene with same results as 2.7.9 version. EDIT:Unless I misread, the following describes the issue and that it is resolved. Should have read a few more posts before typing... http://forum.universal-devices.com/viewtopic.php?t=3785 --------------------------------------------------- I've got a scene with: 3 Switchlinc Dimmers 1 Keypadlinc Dimmer as load 1 button on above kpld 2 IRLinc Devices one on and one off I can set the scene with 100% on with a 30 second ramp and it sets up but setting the keypadlinc button with same settings appears to work until you click another device and and then back to button device and it either shows a very low on level or 100% on and .1 second ramp rate. Ive removed and added devices and the scene and it does not fix. Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted January 31, 2010 Share Posted January 31, 2010 Hi rlav, We are going to do more investigation on this issue. In the meantime, it would be great if you could go back to 2.7.7 and let me know if you still have the same issue. hart2hart, Thanks so very much for bringing this up. It's being investigated and shall be fixed shortly. With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.