Michel Kohanim Posted March 30, 2012 Share Posted March 30, 2012 Hello all, I am happy to announce the availability of our 3.2.2 release! For a list of changes, please take a look at this post. This is a minor release to fixed the bugs introduced in 3.2.0/1 when we introduced support for I2CS devices (including FanLinc). In addition, we added support for a couple of new INSTEON devices. Know Issues None Things to test: - Overall performance - Register and manage I2CS devices, FanLinc, TempLinc, and v95 Thermosats Important Information 1. Important If you have already installed a self signed certificate and your current firmware is 2.7.10 and below, you must reinstall a new one before the upgrade. 2. Please note that Safari does not support SSL session reuse and thus might take an exorbitant amount of time to communicate with ISY. As such, when using 2048 bit SSL, it's best not to use Safari. 3. If you are using the Irrigation Module and are upgrading from releases prior to 3.1.5, you must edit the programs using Irrigation variables and save the programs again. Irrigation module is no longer on promotion 4. Upgrading from 3.1.3 and below: If you are using WeatherBug Module's Rain Today in your programs, please note that the precision has changed from 1/10 to 1/100 and thus your programs might not run properly 5. For a discussion of variables, please look at our Program Variables forum. Instructions: 1. Please backup your ISY (File | Backup ISY). If you are backing up a 3.1.6 system, please note that the backups are corrupted. If you have a backup from prior releases, you should be OK 2. Please download the firmware for your platform - please do not unzip ISY 99i Series ISY 994i Series 3. Login to the Admin Console and choose Help | Manually Upgrade [the name of your system] 4. Choose the file saved in step 2 5. After the upgrade, ISY reboots. Please do ensure to clear your Java Cache 6. IMPORTANT Once upgrade is completed and ISY reboots, use any of the following methods to access your ISY's Admin Console: a. 99/994i - http://isy/admin - applet (Windows only) b. 99/994i - http://isy/admin.jnlp - Java application (Windows only) c. http://your.isy.ip.address/admin - applet d. http://your.isy.ip.address/admin.jnlp - Java application e. http://www.universal-devices.com/99i/3.2.2 - applet f. http://www.universal-devices.com/99i/3.2.2/admin.jnlp - Java application Dashboard - not fully supported - http://www.universal-devices.com/99i/3. ... board.jnlp 8. Please backup your system again Thanks and with kind regards, Michel Quote Link to comment Share on other sites More sharing options...
Teken Posted March 30, 2012 Share Posted March 30, 2012 Installed 3.2.2 with out incident. I however continue to experience problems with the SwitchLinc Timer(s). As some of you may recall I have four of these devices in various rooms with two specific firmware versions .38 & .63 A few months ago I noticed when the 3.X.X firmware was released that the 15 minute timers stopped working. Upon selecting the options button the ISY showed that some of the timers were either set for 0, 15, 200 minutes?? Changing the timer value always greeted me with errors and no change could be applied. Since this new 3.2.2 Beta release those values have all since changed to 0?? There is something affecting these 2476ST relay timers. In the interim I have made some programs to replicate the desired on / off times. For me this is not a long term solution as I require these devices in specific zones to have a level of redundancy with out the need for a HA controller being present. The other down side is that Smarthome in their infinite wisdom has killed off this device! Below are the screen captures along with the log entries. Insight Teken . . . Quote Link to comment Share on other sites More sharing options...
Teken Posted March 30, 2012 Share Posted March 30, 2012 Fri 03/30/2012 05:03:16 PM : [iNST-TX-I1 ] 02 62 11 DC 42 0F 1F 00 Fri 03/30/2012 05:03:16 PM : [iNST-ACK ] 02 62 11.DC.42 0F 1F 00 06 GOF (FLAGS) Fri 03/30/2012 05:03:17 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 1F 00 GOF (FLAGS) Fri 03/30/2012 05:03:17 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 03/30/2012 05:03:17 PM : [All ] Writing 0 bytes to devices Fri 03/30/2012 05:03:17 PM : [All ] Writing 0 bytes to devices Fri 03/30/2012 05:03:23 PM : [All ] Writing 0 bytes to devices Fri 03/30/2012 05:03:30 PM : [All ] Writing 0 bytes to devices Fri 03/30/2012 05:03:37 PM : [iNST-TX-I1 ] 02 62 11 DC 42 0F 20 04 Fri 03/30/2012 05:03:37 PM : [iNST-ACK ] 02 62 11.DC.42 0F 20 04 06 (04) Fri 03/30/2012 05:03:38 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 20 04 (04) Fri 03/30/2012 05:03:38 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 03/30/2012 05:03:38 PM : [All ] Writing 0 bytes to devices Fri 03/30/2012 05:03:43 PM : [iNST-TX-I1 ] 02 62 11 DC 42 0F 20 05 Fri 03/30/2012 05:03:43 PM : [iNST-ACK ] 02 62 11.DC.42 0F 20 05 06 (05) Fri 03/30/2012 05:03:44 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 20 05 (05) Fri 03/30/2012 05:03:44 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 03/30/2012 05:03:44 PM : [All ] Writing 0 bytes to devices ===================================== You will note 0 bytes are being written to these devices. The various entries are me simply selecting different box's to see what is happening and also to gather more data for those to review. Teken . . . Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted March 30, 2012 Author Share Posted March 30, 2012 Hello Teken, Please right mouse click on the device | Diagnostics | Query Insteon Engine. After you are done with that, retry and let me know if you are still having problems. Writing 0 bytes to devices does not mean anything significant: it just means that there was nothing to write. If you wish, you can try restoring your device. With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
Teken Posted March 31, 2012 Share Posted March 31, 2012 Hello Teken, Please right mouse click on the device | Diagnostics | Query Insteon Engine. After you are done with that, retry and let me know if you are still having problems. Writing 0 bytes to devices does not mean anything significant: it just means that there was nothing to write. If you wish, you can try restoring your device. With kind regards, Michel Hello Michel, Performed the query insteon engine. It did restore the original values back to 0, 15, 255 minutes. Performing a restore device still does not allow me to change any of the 4 switches. I also removed and re-added the one device to see if it would correct the issues. All four devices still will not accept any changes in the timer values. Also, please note regardless of the values 0, 15, 255 minutes. None of them actually work any longer? Teken . . . Quote Link to comment Share on other sites More sharing options...
beachfront71 Posted March 31, 2012 Share Posted March 31, 2012 I have been having trouble with IO Linc connectivity (garage door kit) .. We have swapped out 3 now and am starting to think it is related to upgrading from 3.1.17 Quote Link to comment Share on other sites More sharing options...
LeeG Posted March 31, 2012 Share Posted March 31, 2012 What type of problems are you having? I have an I/O Linc in my configuration that works fine on 3.2.2. Quote Link to comment Share on other sites More sharing options...
beachfront71 Posted March 31, 2012 Share Posted March 31, 2012 Hi Lee. THe prob I am having is they are dropping off the radar .. I can see the status of the sensor but can not use the Relay to open / close, I have been by the SHome store 3 times this week trying to resolve.. I will factory reset it, link it, it will work, then it will dissapear after XX amount of minutes .. Originally I thought this was somehow weather related as it started during a time we were having storms but then I looked at my backup history and realized this was also the same time I went from 3.1.17 to 3.2.xx I am in the process of reverting back to .17 and am going to see if that solves the issues.. I only use Mobilnc to see the status so the IO is not linked to anything else .. I use Mobilinc to see if the sensor is on or off and to cycle the door via the relay .. which is in MomC .. Up to this point, I have had zero prob's with ISY since I purchased it earlier this year .. Quote Link to comment Share on other sites More sharing options...
LeeG Posted March 31, 2012 Share Posted March 31, 2012 I don't think going back to 3.1.17 will solve this. Momentary C is dependent of the state of the Sensor as to which commands will cause the relay to react. Is the Relay being commanded with an ISY Scene or direct commands to the Relay? If using a Scene and the I/O Linc is running with Trigger Reverse it could result in the wrong command being used if under ISY Program control and Sensor On/Off is being used to control which command to use. Trigger Reverse reverses the commands the Sensor sends but does not reverse the actual state of the Sensor. If a Query is done the reported Sensor state will change because Query reports the true state of the Sensor not the command reversed state. Quote Link to comment Share on other sites More sharing options...
excessivechaos Posted March 31, 2012 Share Posted March 31, 2012 Just updated to 3.2.2 and my v95 thermostat is now responding to commands. I had to query insteon engine first, and it is still not working within scenes (maybe it's not supposed to?), but programs are working, which is all I need. Quote Link to comment Share on other sites More sharing options...
excessivechaos Posted March 31, 2012 Share Posted March 31, 2012 Okay, one more thing to add. After a little testing, the status is not being reported to the ISY. The commands are being sent and the thermostat is changing, but if I change the temp on the thermostat manually, the status is not showing in the ISY. Is that normal? If so, I will setup a program to query status. Quote Link to comment Share on other sites More sharing options...
blueman2 Posted March 31, 2012 Share Posted March 31, 2012 I have the Venstar with v2.4. I upgraded to the 3.2.2 firmware on my ISY-99i. Finally got everything working both as a responder and controller. By the way, my Venstar shows up as v.95 in the ISY screen. Quote Link to comment Share on other sites More sharing options...
cwintermeyer Posted April 1, 2012 Share Posted April 1, 2012 I upgraded my ISY-99i from 3.1.17 to 3.2.2 and, as usual, the install went smoothly with no issues. Now I can control my ToggleLinc Relay 2466SW (hardware Rev 5.7 and firmware Rev v.41) that is apparently a I2CS device. With 3.1.17, I could control the switch with a manual On/Off in the ISY-99i but it wouldn't respond to any scenes or All On/All Off commands. Now, the new ToggleLinc works flawlessly. Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted April 1, 2012 Author Share Posted April 1, 2012 Hi Teken, I am so very sorry to hear this. SWL Timer must be one of those in-between devices that reports as I2CS but does not really support i2cs. We shall have a closer look to see if can add some traps for specific devices. Hi excessivechaos, I think the problem is that the links were not added properly to your PLM. Please remove the thermostat and register it back in. This should solve the status issue. With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
excessivechaos Posted April 1, 2012 Share Posted April 1, 2012 Hi Teken, Hi excessivechaos, I think the problem is that the links were not added properly to your PLM. Please remove the thermostat and register it back in. This should solve the status issue. With kind regards, Michel I'm sorry, I forgot to mention this, but I did try to remove and re-add the device, but that did not work. Here is what I did: 1.) right-click, delete device from My Lighting 2.) make sure thermostat is in off mode 3.) remove adapter from thermostat for 20 secs 4.) hold set button while plugging adapter into thermostat and hold for 3 secs to reset to default 5.) start linking 6.) hold set button for 3 seconds 7.) finish linking 8.) query insteon engine Is that correct? Quote Link to comment Share on other sites More sharing options...
Teken Posted April 1, 2012 Share Posted April 1, 2012 Hi Teken, I am so very sorry to hear this. SWL Timer must be one of those in-between devices that reports as I2CS but does not really support i2cs. We shall have a closer look to see if can add some traps for specific devices. With kind regards, Michel That would be greatly appreciated and most helpful. I look forward to a fix in these devices. Teken . . . Quote Link to comment Share on other sites More sharing options...
andyf0 Posted April 1, 2012 Share Posted April 1, 2012 Sometimes, when I go to Programs (first time after AC is brought up I think) some folder names are abbreviated, shown below, even though there is plenty of room in the frame to display them. Opening the folder causes the name of the folder to be displayed correctly. This has happened for a little while now, not just this release. Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted April 1, 2012 Author Share Posted April 1, 2012 Hello all, excessivechaos, The process is almost correct: you have to make sure your thermostat is in the Off position before you start linking. Teken, my pleasure. andyf0, can you tell me what version of Linux and what version of Java you are running? With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
andyf0 Posted April 1, 2012 Share Posted April 1, 2012 andyf0, can you tell me what version of Linux and what version of Java you are running? With kind regards, Michel I'm running Mac OS X Lion and Java 6 Quote Link to comment Share on other sites More sharing options...
excessivechaos Posted April 1, 2012 Share Posted April 1, 2012 Michael, so sorry, I did have the thermostat off, but forgot to include that step in my previous post, I have edited the it to include that step. I have attempted to remove and add back the thermostat a couple times and have been unsuccessful in getting it to report status back to the ISY without a query. Quote Link to comment Share on other sites More sharing options...
LeeG Posted April 1, 2012 Share Posted April 1, 2012 Can anyone confirm that the dongle does report manual changes to the temp settings when done at the tstat. That is the specific case excessivechaos is asking about. Quote Link to comment Share on other sites More sharing options...
andyf0 Posted April 1, 2012 Share Posted April 1, 2012 Can anyone confirm that the dongle does report manual changes to the temp settings when done at the tstat. That is the specific case excessivechaos is asking about. Yes, it does. Here's what got sent, I did one down button push, then one up button push: Sun 04/01/2012 02:54:24 PM : [iNST-SRX ] 02 50 14.29.66 18.CF.62 07 71 51 (51) Sun 04/01/2012 02:54:24 PM : [standard-Direct][14.29.66-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Sun 04/01/2012 02:54:24 PM : [ 14 29 66 1] CLISPC 162 Sun 04/01/2012 02:54:28 PM : [iNST-SRX ] 02 50 14.29.66 18.CF.62 07 72 49 (49) Sun 04/01/2012 02:54:28 PM : [standard-Direct][14.29.66-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Sun 04/01/2012 02:54:28 PM : [ 14 29 66 1] CLISPH 146 Sun 04/01/2012 02:54:29 PM : [iNST-SRX ] 02 50 14.29.66 18.CF.62 67 93 ED (ED) Sun 04/01/2012 02:54:29 PM : [standard-Cleanup Ack][14.29.66-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Sun 04/01/2012 02:54:33 PM : [iNST-SRX ] 02 50 14.29.66 18.CF.62 07 71 52 (52) Sun 04/01/2012 02:54:33 PM : [standard-Direct][14.29.66-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Sun 04/01/2012 02:54:33 PM : [ 14 29 66 1] CLISPC 164 Sun 04/01/2012 02:54:37 PM : [iNST-SRX ] 02 50 14.29.66 18.CF.62 07 72 4A (4A) Sun 04/01/2012 02:54:37 PM : [standard-Direct][14.29.66-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Sun 04/01/2012 02:54:37 PM : [ 14 29 66 1] CLISPH 148 Sun 04/01/2012 02:54:43 PM : [iNST-SRX ] 02 50 14.29.66 18.CF.62 07 6F 35 (35) Sun 04/01/2012 02:54:43 PM : [standard-Direct][14.29.66-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Sun 04/01/2012 02:54:43 PM : [ 14 29 66 1] CLIHUM 53 Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted April 1, 2012 Author Share Posted April 1, 2012 Hi Andy, Is your thermostat v95? As far as the MAC issue, I have looked into it and can't reproduce here. It does not happen all the time, correct? Are there any specific instances that it does happen: for instance, when everything is collapsed or when some are expanded and others collapsed, etc. With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
andyf0 Posted April 1, 2012 Share Posted April 1, 2012 Hi Michel, My thermostat adapter is a V.92. My other Integrated Thermostat is a v.93 although I didn't test that. I just tried to reproduce the abbreviated program names but couldn't. I'll keep watching to see if I can figure out how it happens. Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted April 1, 2012 Author Share Posted April 1, 2012 Hi Andy, thank you. I think the problem is isolated to v95 thermostats. 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.