ski2020

A day or two ago my AC started exhibiting the red flag (everything greyed out) after about 2 hours after each restart. The only thing new is the Java version (build 1.7.0_15-b03) running on my MAC (10.8.2). I am connecting locally via my network so there are no VPNs involved. This has never happened before, but unfortunately it is very repeatable right now. Even once the AC goes to the red flag, the ISY operates fine and I can always access via Mobilinc. Also, according to the Java download site, 7u11 has been disabled by Apple for OSX, so I guess I cannot try an earlier java version (which was working fine). Thanks.

Thanks Lee. I am in heating mode now and it turns out that the cool setpoints were out of range (0) for all the stats. My program tested to see if either the heat or cool setpoint was out of range. So whenever I changed the heat setpoint, the program would send an alert. All set now.

3.3.3 upgrade went smoothly. One new bug - every time I change a stat setpoint (by program or through the AC) it triggers my "stat out of range" email. To clarify, I have an alert email sent whenever any of my 6 stats are set below 60 or above 79. If I use the AC to change a stat from 70 to 69, it triggers the email. I noticed the problem when I started getting sets of 6 email alerts twice a day, when I set programmatically change my setpoints for all my stats. This never occurred in previous versions. Thanks, Ski

The mystery remains what was the stat acking. And since it does not appear to be the ISY, I have to assume that the stat did something strange. Its not linked to anything. Hopefully it won't happen again. Thanks for the time and effort!

Hi Michel, I ran that program minutes later. It reset the cool setpoint to the proper setting. Here is the event log 5 minutes later setting CSP to 76 (98H/2): Fri 09/21/2012 12:10:40 PM : [ Time] 12:10:42 2(0) Fri 09/21/2012 12:10:40 PM : [iNST-TX-I1 ] 02 62 11 B5 F0 0F 6C 98 Fri 09/21/2012 12:10:40 PM : [iNST-ACK ] 02 62 11.B5.F0 0F 6C 98 06 (98) Fri 09/21/2012 12:10:40 PM : [iNST-SRX ] 02 50 11.B5.F0 19.75.3A 27 6C 98 (98) Fri 09/21/2012 12:10:40 PM : [standard-Direct Ack][11.B5.F0-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Certainly well after the phantom command. What caused the cool setpoint to be set to 36 degrees? Thanks.

So according to the log, the stat declared that its cool setpoint was suddenly 36 degrees, seconds after it reported its status temp as 72 degrees. And according to the event log, just after the stat reported its temp as 72 (48H) degrees, the stat sent an ack to the PLM reporting 48H. The event log did not show any command or message to which the stat was acking. And after that ack, the stat reports its cool setpoint as 36 degrees. So, to what was the stat ACKing? It appears that the 48H was interpreted as the setting for the setpoint (double just like temp messages). All of the event log temp messages are 07 6E XX, XX being the value. The ACK is 27 6C XX. You explained that the 27 means ACK. Do you know what 6E versus 6C of the second byte means? Any other thoughts? I know the stat was not changed manually ... Thanks!

HI Michel, Here is the log: Stats / Family Stat Status 73° Fri 2012/09/21 12:00:37 PM System Log Stats / Family Stat Status 72° Fri 2012/09/21 12:03:52 PM System Log Stats / Family Stat Status 73° Fri 2012/09/21 12:04:58 PM System Log Stats / Family Stat Status 72° Fri 2012/09/21 12:06:05 PM System Log Stats / Family Stat Cool Setpoint 36° Fri 2012/09/21 12:06:05 PM System Log Stats / Family Stat / Family Stat- Cool Control Status On Fri 2012/09/21 12:06:09 PM System Log Stats / Family Stat Heat/Cool State Cool On Fri 2012/09/21 12:06:09 PM System Log You can see the cool setpoint is set to 36. Was this sent by the ISY or is it a status message? The device seems to have acked a command that does not show up in the events log.

So according to the level 3 events log: The Stat was sending regular status messages to the PLM (temp 72 or 73) and then suddenly it acks a message from the PLM (this PLM message is not shown in the level 3 events log, should it be?) and then reports that its cool setpoint is now 36 degrees? What was the PLM message the stat was acking and what caused it to change its setpoint? Am I missing something here? Shortly after the phantom command happened I ran a program to reset the setpoint. Here is the level 3 events log: Fri 09/21/2012 12:10:40 PM : [iNST-TX-I1 ] 02 62 11 B5 F0 0F 6C 98 Fri 09/21/2012 12:10:40 PM : [iNST-ACK ] 02 62 11.B5.F0 0F 6C 98 06 (98) Fri 09/21/2012 12:10:40 PM : [iNST-SRX ] 02 50 11.B5.F0 19.75.3A 27 6C 98 (98) Fri 09/21/2012 12:10:40 PM : [standard-Direct Ack][11.B5.F0-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 I assume the first two commands are sent from the PLM and the 3rd is the ack from the stat that the setpoint is now 76 (98H/2). Clearly these first two were not sent or recorded by the log when the phantom command occurred.

Hi Michel, I cannot be sure of the composition of the commands, but I believe it is not the 48 which is the problem, but the 27 before it. As you can see below, all the other status commands are 07 6C XX, where xx is the hex status temp. 48 => 144 (72); 49 => 146 (73) which matches the log entries. But in the phantom command that sets the cool setpoint, the command is 27 6C XX. Fri 09/21/2012 12:03:50 PM : [iNST-SRX ] 02 50 11.B5.F0 19.75.3A 07 6E 48 (48) Fri 09/21/2012 12:03:50 PM : [standard-Direct][11.B5.F0-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 09/21/2012 12:03:50 PM : [ 11 B5 F0 1] ST 144 Fri 09/21/2012 12:04:56 PM : [iNST-SRX ] 02 50 11.B5.F0 19.75.3A 07 6E 49 (49) Fri 09/21/2012 12:04:56 PM : [standard-Direct][11.B5.F0-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 09/21/2012 12:04:56 PM : [ 11 B5 F0 1] ST 146 Fri 09/21/2012 12:06:03 PM : [iNST-SRX ] 02 50 11.B5.F0 19.75.3A 07 6E 48 (48) Fri 09/21/2012 12:06:03 PM : [standard-Direct][11.B5.F0-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 09/21/2012 12:06:03 PM : [ 11 B5 F0 1] ST 144 Fri 09/21/2012 12:06:03 PM : [iNST-SRX ] 02 50 11.B5.F0 19.75.3A 27 6C 48 (48) Fri 09/21/2012 12:06:03 PM : [standard-Direct Ack][11.B5.F0-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 09/21/2012 12:06:03 PM : [ 11 B5 F0 1] CLISPC 72 Somehow that extra bit is being generated or read incorrectly. This command definitely caused the setpoint to change. It was not touched manually. Any thoughts?

Hi Michel, I upgraded to 3.3.2 (which supposedly fixes the phantom stat commands) and just had the cool setpoint for one of my stats set to 36 degrees, right after it provided a status message of 72 degrees. Here is the log: Stats / Family Stat Status 73° Fri 2012/09/21 12:00:37 PM System Log Stats / Family Stat Status 72° Fri 2012/09/21 12:03:52 PM System Log Stats / Family Stat Status 73° Fri 2012/09/21 12:04:58 PM System Log Stats / Family Stat Status 72° Fri 2012/09/21 12:06:05 PM System Log Stats / Family Stat Cool Setpoint 36° Fri 2012/09/21 12:06:05 PM System Log Stats / Family Stat / Family Stat- Cool Control Status On Fri 2012/09/21 12:06:09 PM System Log Stats / Family Stat Heat/Cool State Cool On Fri 2012/09/21 12:06:09 PM System Log Here is level 3 device comm: Fri 09/21/2012 12:00:35 PM : [iNST-SRX ] 02 50 11.B5.F0 19.75.3A 07 6E 49 (49) Fri 09/21/2012 12:00:35 PM : [standard-Direct][11.B5.F0-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 09/21/2012 12:00:35 PM : [ 11 B5 F0 1] ST 146 Fri 09/21/2012 12:03:50 PM : [iNST-SRX ] 02 50 11.B5.F0 19.75.3A 07 6E 48 (48) Fri 09/21/2012 12:03:50 PM : [standard-Direct][11.B5.F0-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 09/21/2012 12:03:50 PM : [ 11 B5 F0 1] ST 144 Fri 09/21/2012 12:04:56 PM : [iNST-SRX ] 02 50 11.B5.F0 19.75.3A 07 6E 49 (49) Fri 09/21/2012 12:04:56 PM : [standard-Direct][11.B5.F0-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 09/21/2012 12:04:56 PM : [ 11 B5 F0 1] ST 146 Fri 09/21/2012 12:06:03 PM : [iNST-SRX ] 02 50 11.B5.F0 19.75.3A 07 6E 48 (48) Fri 09/21/2012 12:06:03 PM : [standard-Direct][11.B5.F0-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 09/21/2012 12:06:03 PM : [ 11 B5 F0 1] ST 144 Fri 09/21/2012 12:06:03 PM : [iNST-SRX ] 02 50 11.B5.F0 19.75.3A 27 6C 48 (48) Fri 09/21/2012 12:06:03 PM : [standard-Direct Ack][11.B5.F0-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 09/21/2012 12:06:03 PM : [ 11 B5 F0 1] CLISPC 72 Fri 09/21/2012 12:06:07 PM : [iNST-SRX ] 02 50 11.B5.F0 00.00.01 C7 11 00 LTONRR (00) Fri 09/21/2012 12:06:07 PM : [standard-Group][11.B5.F0-->Group=1] Max Hops=3, Hops Left=1 Fri 09/21/2012 12:06:07 PM : [ 11 B5 F0 2] DON 0 Fri 09/21/2012 12:06:07 PM : [ 11 B5 F0 2] ST 255 Fri 09/21/2012 12:06:07 PM : [ 11 B5 F0 1] CLIHCS 2 Fri 09/21/2012 12:06:07 PM : [iNST-SRX ] 02 50 11.B5.F0 19.75.3A 42 11 01 LTONRR (01) Fri 09/21/2012 12:06:07 PM : [standard-Cleanup][11.B5.F0-->ISY/PLM Group=1] Max Hops=2, Hops Left=0 Fri 09/21/2012 12:06:07 PM : [iNST-DUP ] Previous message ignored. Fri 09/21/2012 12:06:08 PM : [iNST-SRX ] 02 50 11.B5.F0 19.75.3A 47 11 01 LTONRR (01) Fri 09/21/2012 12:06:08 PM : [standard-Cleanup][11.B5.F0-->ISY/PLM Group=1] Max Hops=3, Hops Left=1 Fri 09/21/2012 12:06:08 PM : [iNST-DUP ] Previous message ignored. Fri 09/21/2012 12:06:09 PM : [iNST-SRX ] 02 50 11.B5.F0 19.75.3A 07 71 24 (24) Fri 09/21/2012 12:06:09 PM : [standard-Direct][11.B5.F0-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 09/21/2012 12:06:58 PM : [iNST-SRX ] 02 50 11.B4.05 19.75.3A 07 6F 30 (30) I have a program that emails me if a setpoint gets set out of range. I received the email and saw that the stat was indeed trying to cool the room to 36 degrees. I reset the cool setpoint, so no problem there. But clearly there is still a problem.

I was able to update to Java 7 on my Mac (Snow Leopard) using OpenJDK. ISY update went smoothly. Thanks!

For MAC, it appears as though Java SE 7 requires OS X 10.7+. I am running 10.6.8 (snow leopard) and therefore cannot upgrade to Java 7. If so, does this mean that I will not be able to connect securely to my ISY99 if I upgrade to 3.3.2?

Over the last two weeks, I have also had one of my 6 Venstar stats (all v2.2+) suddenly report a "random" cool setpoint. Both times, there was virtually no other traffic. The first time, the cool setpoint reported 255 degrees. I was remote at the time (I have a program like you have that alerts me if any of my 6 stats has a setpoint out of normal range) so I do not know if the stat sent an erroneous status message or the stat really was set to 255. I reset it remotely and reported the issue to UD. The second time was yesterday. The log said that the cool setpoint was 190 degrees and when I check the stat, it showed OF and was no longer cooling because of this error. I did not have the event viewer running, but the log is shown below. So this time, the stat was really set to a random setpoint - obviously a real problem. Stats / Office Stat Status 75° Sat 2012/08/11 11:58:07 AM System Log Stats / Family Stat Status 76° Sat 2012/08/11 11:58:21 AM System Log Stats / Office Stat Status 76° Sat 2012/08/11 11:59:14 AM System Log Stats / Office Stat Humidity 37% Sat 2012/08/11 12:00:19 PM System Log 1st / Pantry Status 100% Sat 2012/08/11 12:00:23 PM System Log Motions / t.Pantry Trigger-Opened Status 100% Sat 2012/08/11 12:00:23 PM System Log Stats / Basement Stat Humidity 40% Sat 2012/08/11 12:01:02 PM System Log Stats / Family Stat Status 77° Sat 2012/08/11 12:01:41 PM System Log Stats / Family Stat Humidity 33% Sat 2012/08/11 12:02:47 PM System Log Motions / m.Garage Motion / m.Garage Motion-DuskDawn Status 100% Sat 2012/08/11 12:03:26 PM System Log 2nd / Girls Fan Off 0 Sat 2012/08/11 12:05:17 PM Program Log 2nd / Girls Fan Status 0% Sat 2012/08/11 12:05:17 PM System Log Stats / Family Stat Humidity 34% Sat 2012/08/11 12:06:03 PM System Log 1st / Pantry Status 0% Sat 2012/08/11 12:07:03 PM System Log Motions / t.Pantry Trigger-Opened Status 0% Sat 2012/08/11 12:07:03 PM System Log Stats / Office Stat Humidity 38% Sat 2012/08/11 12:07:54 PM System Log Stats / Office Stat Cool Setpoint 190° Sat 2012/08/11 12:07:58 PM System Log 1st / Pantry Status 100% Sat 2012/08/11 12:08:39 PM System Log Motions / t.Pantry Trigger-Opened Status 100% Sat 2012/08/11 12:08:39 PM System Log 1st / Pantry Status 0% Sat 2012/08/11 12:08:48 PM System Log Motions / t.Pantry Trigger-Opened Status 0% Sat 2012/08/11 12:08:48 PM System Log 1st / Pantry Status 100% Sat 2012/08/11 12:09:40 PM System Log Hopefully, someone can reproduce the problem and debug. If it happens again, I hope to catch the event viewer info also. Any suggestions are welcomed. Thanks.

Hi Michel, Are you recommending buying a new PLM for the new installation? Thank you again. Ski

Thank you for the response. Do you mean to purchase a new PLM and keep the old one as backup? Or can I save the settings of the old PLM and then delete it? How do I back up only the programs? I see how to backup the ISY. When I restore, do I choose to restore only the programs? Best, Ski