andrewm

No. This was all done via ISY scenes.

I have 6 KPLs around the house. They are all set up in 8-button (/ switch) mode, but actually have 6-physical buttons - so it's sort of working in a hybrid manner. I find this gives me the best flexibility. One consequence of this setup is that I have to cross link many of the KPL switches - eg the local load on the large button at the top can be controlled by underlying switch A or B. I recently had a KPL failure where the device went completely blank and unresponsive. I factory reset it and then restored it from ISY. Most functionality returned OK, but I found that the internal crosslinks within the KPL didn't work. I assumed the KPL had an unrecoverable fault so purchased a new one from SH, but that exhibited exactly the same behavior when I restored that. In both cases the device link table matches the ISY link table. AT this point I used my ISY with the original KPL that failed to create scenes with crosslinks that worked fine. So I guess my SH purchase wasn't necessary:( It's a long time since I set these KPLs up so I'm wondering if I've forgotten something, or does the ISY restore not work for local crosslinks? Or is this a potential bug. FWIW My current ISY verson is 2.8.1 and the KPL that failed was 1.6.5 Thanks, - Andrew

Just installed an EZIO4O for use on my ISY using the latest 2.8.1 firmware, and still had to use SimpleHomeNet's utility to set the timers. I also had a problem with the ISY. If I turned on relay 0, the ISY marked relay 1 as being on, not relay 0 as expected. The physical output was correct.

I've upgraded to the Insteon V2 adapter, but I kept my ISY on v2.7.6 while the releases stabilize a little. I was assuming that everything should be backwards compatible and that ISY should be able to correctly operate the adapter without taking advantage of the newer features - is that correct or do I need to move to a new rev? I'm noticing issues with my T1700 Thermostats in my Family Room (I also have a T1900 in my Living ROom which seems more stable). It appears to be operating randomly and the log to me is nonsensical. Note I've done the thermostat humidity fix (though it's currently showing 109%!) - I actually have my suspicions about the thermostat itself. Below is my log. I have a program set to run at 6pm which will try twice to set the temperature of both thermostats (Liviing Room=68, Family Room =69). The log values seem suspicious- or is that because of my ISY rev? Living Room - Thermostat Thermostat Mode Heat Sat 02/13/2010 06:00:00 PM Program Log Living Room - Thermostat Heat Setpoint 68░ Sat 02/13/2010 06:00:02 PM Program Log Living Room - Thermostat Setpoint 136 Sat 02/13/2010 06:00:02 PM System Log Living Room - Thermostat Heat Setpoint 68░ Sat 02/13/2010 06:00:02 PM System Log Family Room - Thermostat Thermostat Mode Heat Sat 02/13/2010 06:00:05 PM Program Log Family Room - Thermostat Setpoint 32 Sat 02/13/2010 06:00:06 PM System Log Family Room - Thermostat Heat Setpoint 16░ Sat 02/13/2010 06:00:06 PM System Log Family Room - Thermostat Heat Setpoint 69░ Sat 02/13/2010 06:00:06 PM Program Log Family Room - Thermostat Setpoint 138 Sat 02/13/2010 06:00:07 PM System Log Family Room - Thermostat Heat Setpoint 69░ Sat 02/13/2010 06:00:07 PM System Log Living Room - Thermostat Thermostat Mode Heat Sat 02/13/2010 06:00:11 PM Program Log Living Room - Thermostat Heat Setpoint 68░ Sat 02/13/2010 06:00:12 PM Program Log Family Room - Thermostat Thermostat Mode Heat Sat 02/13/2010 06:00:16 PM Program Log Family Room - Thermostat Setpoint 124 Sat 02/13/2010 06:00:17 PM System Log Family Room - Thermostat Heat Setpoint 62░ Sat 02/13/2010 06:00:17 PM System Log Family Room - Thermostat Heat Setpoint 69░ Sat 02/13/2010 06:00:18 PM Program Log Family Room - Thermostat Setpoint 138 Sat 02/13/2010 06:00:18 PM System Log Family Room - Thermostat Heat Setpoint 69░ Sat 02/13/2010 06:00:18 PM System Log Living Room - Thermostat Status Query░ Sat 02/13/2010 06:07:55 PM Program Log Living Room - Thermostat Status Query░ Sat 02/13/2010 06:07:55 PM Program Log Family Room - Thermostat Status Query░ Sat 02/13/2010 06:08:05 PM Program Log Family Room - Thermostat Status Query░ Sat 02/13/2010 06:08:05 PM Program Log Family Room - Thermostat Status 66░ Sat 02/13/2010 06:08:06 PM System Log Family Room - Thermostat Setpoint 124 Sat 02/13/2010 06:08:07 PM System Log Family Room - Thermostat Heat Setpoint 62░ Sat 02/13/2010 06:08:07 PM System Log Living Room - Thermostat Status Query░ Sat 02/13/2010 06:18:05 PM Program Log Living Room - Thermostat Status Query░ Sat 02/13/2010 06:18:05 PM Program Log Family Room - Thermostat Status Query░ Sat 02/13/2010 06:18:15 PM Program Log Family Room - Thermostat Status Query░ Sat 02/13/2010 06:18:15 PM Program Log Family Room - Thermostat Status 67░ Sat 02/13/2010 06:18:15 PM System Log

I agree the Wiki topic is not entirely correct, but it gives the general idea - the key being to use 2 scenes. I'm noticing a problem though with my setup "in the lab" using rev 2.7.6 - I don't know if the issue is release specific or even an IOLinc problem. In this example I'm not touching the magnetic switch when I press the KPL - effectively simulating the IOLinc not receiving the control command. In which case, regardless of the current sensor value, after the KPL button is pressed the KPL button light will always flash and then stay on (because the KPL button is in non-toggle-on mode). From this I surmise that there's no automatic query done on the device proper after the control command, or even just check of the current value known to ISY. The net effect is the button light doesn't match the sensor status. Of course if the door actually moved, then this wouldn't be an issue. My workaround for this was to then trigger a short program when the KPL button is pressed and set the sensor scene state programmatically after a short delay. However I noticed that turning ON that scene actually triggers the relay - even though the relay is not in that scene. That really doesn't seem right!

Never mind. Just found your JNLP utility (http://www.universal-devices.com/99i/2.7.6/admin.jnlp) which allowed me to enter the address of my isy99, and then the console started ok. The upgrade to 2.7.6 also worked OK this time

I've encountered the same Java exception as the original poster (Exception: java.lang.ClassNotFoundException: com.universaldevices.client.ui.UDClientApplet.class) in very similar circumstances. In my cases I did a successful upgrade to 2.7.0 from 2.6.13, took a backup then tried to upgrade to 2.7.6 (with AV disabled and no Windows firewall, just as with the prior upgrade). I encountered the "Invalid Length" error. Trying to access the Admin console then gives the Java exception. My case then differs from the OP. If I use the http://www.universal-devices.com/99i link, a Java console is displayed but no devices, and no ability to retry the upgrade. I've tried clearing the cache. This is on Vista + Firefox. So now I'm a little stuck and wondering how best to proceed?! Thanks, - Andrew

I did as you suggested and went to 2.6.13 last night - it seems to have improved the operation considerably. I no longer see any changes to auto-mode on the Thermostat display Thanks for all your responses.

That issue was from March 2008, and it looks like the fix was released in rev 2.6.4. I'm on 2.6.8. The only change to thermostat operation I see since 2.6.4 is 2.6.13 (the latest) which has the following fix: "thermostat query puts a 0 in the log before the actual value".

Thanks for the reply. Do you have a link to where this issue (or the fix) is described, as I couldn't see anything when I searched before?

I just repeated the above test and got slightly different results. The lower setpoint was triggered OK, as before. Then triggering the higher setpoint resulted in the blower coming on and the thermostat getting stuck on the Cool 31 / Heat 0 display. Previously I'd only seen this when I didn't send the command to put the thermostat in Heat Mode command (as described in issue #3). Suggestions welcome!

I've just installed a Venstar Thermostat with V.28 firmware being controlled by ISY 99 v2.6.8. I don't know if the issues I'm seeing are normal are not (we could do with a Wiki topic for this whacko device!) so I'd appreciate some feedback Note that I use the thermostat purely for heating. Auto changeover is disabled in the thermostat. Firstly I learnt the hard way that it doesn't appear that you can change the setpoint of the Thermostat in Program mode. I can live with that, but it means I have to completely program the operaton with the ISY. So I manually put the thermostat in heat mode and used a test program triggered by a RemoteLinc to change the setpoint either to 59° or 62°. Eg: If Control 'Bedroom 1 - Remote2: KeyD' is switched Off Then Set 'Living Room - Thermostat' Mode Heat Set 'Living Room - Thermostat' 59° (Heat Setpoint) Else - No Actions - (To add one, press 'Action') When I pressed the remote key to trigger lowering the setpoint the Thermostat operated as expected - the setpoint changed after a few seconds. When I pressed the button to trigger increasing the setpoint, the thermostat's display changed as though the thermostat was in auto mode (ie both cooling and heating setpoints were displayed - 31° & 0° respectively - despite me not having that mode enabled). Then the display changes to just show a heat setpoint of 0°, then finally the display changes again to show a heat setpoint of 62°. So that's my first issue - why the intermediate steps with suspect values? The second issue is that occasionally when doing this latter operation, the fan blower turns on very briefly, even though the new setpoint is below the current temperature. This is obviously unnecessary and undesirable. The third issue is that if you notice above I send the command to put the Thermostat into heat mode, even though that should already be the case. If I didn't do that then the operation was unreliable - eg the thermostat display sticks on the 0° setpoint display! This is bizarre - is it normal, or could I have a faulty unit FWIW here's the ISY log during some of the above operations: (ENQUIRY) 2009/01/06 23:47:04 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 00 06 (00) 2009/01/06 23:47:04 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 88 (88) 2009/01/06 23:47:04 : [ E 6A 46 1] ST 136 2009/01/06 23:47:04 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 20 06 (20) 2009/01/06 23:47:05 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 7C (7C) 2009/01/06 23:47:05 : [ E 6A 46 1] CLISP 124 2009/01/06 23:47:05 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 60 06 (60) 2009/01/06 23:47:05 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 09 (09) 2009/01/06 23:47:05 : [ E 6A 46 1] CLIHUM 9 2009/01/06 23:47:05 : [iNST-ACK ] 02 62 0E.6A.46 0F 6B 02 06 (02) 2009/01/06 23:47:06 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6B 01 (01) 2009/01/06 23:47:06 : [ E 6A 46 1] CLIMD 1 (Press Remote key to trigger setting setpoint at 59°) 2009/01/06 23:47:31 : [iNST-SRX ] 02 50 0A.15.36 00.00.04 C7 13 00 LTOFFRR(00) 2009/01/06 23:47:31 : [ A 15 36 4] DOF 0 2009/01/06 23:47:32 : [iNST-SRX ] 02 50 0A.15.36 0C.A5.7A 41 13 04 LTOFFRR(04) 2009/01/06 23:47:32 : [ A 15 36 4] ST 0 2009/01/06 23:47:32 : [iNST-ACK ] 02 62 0E.6A.46 0F 6B 04 06 (04) 2009/01/06 23:47:33 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6B 04 (04) 2009/01/06 23:47:33 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 00 06 (00) 2009/01/06 23:47:34 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 00 (00) 2009/01/06 23:47:34 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 20 06 (20) 2009/01/06 23:47:34 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 7C (7C) 2009/01/06 23:47:34 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 60 06 (60) 2009/01/06 23:47:35 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 09 (09) 2009/01/06 23:47:35 : [iNST-ACK ] 02 62 0E.6A.46 0F 6B 02 06 (02) 2009/01/06 23:47:35 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6B 01 (01) 2009/01/06 23:47:35 : [iNST-ACK ] 02 62 0E.6A.46 0F 6D 76 06 (76) 2009/01/06 23:47:36 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6D 76 (76) 2009/01/06 23:47:36 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 00 06 (00) 2009/01/06 23:47:36 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 00 (00) 2009/01/06 23:47:36 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 20 06 (20) 2009/01/06 23:47:37 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 76 (76) 2009/01/06 23:47:37 : [ E 6A 46 1] CLISP 118 2009/01/06 23:47:37 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 60 06 (60) 2009/01/06 23:47:37 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 09 (09) 2009/01/06 23:47:37 : [iNST-ACK ] 02 62 0E.6A.46 0F 6B 02 06 (02) 2009/01/06 23:47:38 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6B 01 (01) (Press Remote key to trigger setting setpoint at 62°) 2009/01/06 23:48:18 : [iNST-SRX ] 02 50 0A.15.36 00.00.04 C3 11 00 LTONRR (00) 2009/01/06 23:48:18 : [ A 15 36 4] DON 0 2009/01/06 23:48:18 : [ A 15 36 4] ST 255 2009/01/06 23:48:18 : [iNST-ACK ] 02 62 0E.6A.46 0F 6B 04 06 (04) 2009/01/06 23:48:18 : [iNST-SRX ] 02 50 0A.15.36 0C.A5.7A 42 11 04 LTONRR (04) 2009/01/06 23:48:19 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 00 06 (00) 2009/01/06 23:48:19 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6B 04 (04) 2009/01/06 23:48:20 : [uNKNOWN ] 15 15 2009/01/06 23:48:20 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 27 6A 00 (00) 2009/01/06 23:48:24 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 60 06 (60) 2009/01/06 23:48:24 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 09 (09) 2009/01/06 23:48:24 : [iNST-ACK ] 02 62 0E.6A.46 0F 6B 02 06 (02) 2009/01/06 23:48:25 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6B 01 (01) 2009/01/06 23:48:25 : [iNST-ACK ] 02 62 0E.6A.46 0F 6D 7C 06 (7C) 2009/01/06 23:48:25 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 27 6D 7C (7C) 2009/01/06 23:48:25 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 00 06 (00) 2009/01/06 23:48:26 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 88 (88) 2009/01/06 23:48:26 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 20 06 (20) 2009/01/06 23:48:26 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 27 6A 7C (7C) 2009/01/06 23:48:26 : [ E 6A 46 1] CLISP 124 2009/01/06 23:48:26 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 60 06 (60) 2009/01/06 23:48:27 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 09 (09) 2009/01/06 23:48:27 : [iNST-ACK ] 02 62 0E.6A.46 0F 6B 02 06 (02) 2009/01/06 23:48:27 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 27 6B 01 (01)

Any answer on this one?

I have an ISY99 v2.6.7. We had a 1 hour power outage this morning and then my night lights didn't come on this evening - I've noticed this before. The outage was from around 6:30am to 7:30am. Looking at the program summary the night lights have no "last run time" and have a "next scheduled run" time of 4:26pm tomorrow (it's based on an offset from the sunset time). Interestingly I have another program set to run at a random time around 9:15pm nightly, which IS correctly scheduled for today! So why didn't the ISY correctly schedule the lights in the original program to come on today rather than tomorrow? - Andrew

I'm using the newer KPL's (v1.65) which allow the KPL primary load to be controlled from a secondary button on the same KPL, but with on-level etc. different to the local on-rate. I just also bought a new ISY99, but I notice that the ISY doesn't support this feature yet (firmware 1.0), or indeed any linking between KPL buttons. Any ideas what firmware rev will add support for linking secondary buttons to the primary load, and when we can get our hands on it?