JCBond

Have you tried setting the remote in Toggle mode and then have the program react to both changes? something like the above?

If I install Home Assistant on Eisy will IoX and Home Assistant be able to share the same 2413u Insteon PLM connected to one of the USB ports? or will the two services conflict with each other and fight for the PLM?

I do similar but I prefer to keep the font sizes consistent. I have 30+ of these all around the house. Attached is the word template I use.Keypad Templates Kitchen.doc Keypad Templates Kitchen.doc

I have several Motion Sensors 2842-222 v.24 and I have noticed that whenever the Low Bat status turns on. I can't reset it back to off even though I have replaced the battery. The only way I have found so far that works is to delete the sensor and re-add it again to the system. Has anyone else seen this issue? Is there something I am not doing that I should?

Thanks, I will keep it short then.

Is there a limit on the distance between the ISY 994i Pro and the PLM? I know it is a normal Cat5 cable between them but is there a known distance between them that you would recomend not to excede?

Same issue here

I have a network of about 40 Insteon devices. I recenly 'upgraded' 5 KPLs to the latest version and they were working fine with any software version prior to 3.3.6. I even had a program to change the LED levels twice a day. When I installed v3.3.6 they all went crazy. I would press a button on the KPL and many other buttons would turnon at the same time. Since I installed 3.3.7 I removed them all from the software. Manually reset them. Re-added them to the system and added them to their respective scenes. All the scenes are working, and the KPLs seem to work. EXCEPT I can NOT get the LED levels to change using the ISY. They are stuck in the default level. I have tried the recomended Query insteon engine, and no change. I even moved the ISY so that it's PLM was on the same cicuit as the KPLs ALL 5 units are behaving the same way. They all worked before v3.3.6, they all went crazy with 3.3.6 and now none of them work on the LED levels Here is a log of an attempt to change the level: Sun 12/30/2012 10:01:34 AM : [iNST-TX-I2CS] 02 62 1D F5 6B 1F 2E 00 00 03 7F 00 00 00 00 00 00 00 00 00 00 50 Sun 12/30/2012 10:01:34 AM : [iNST-ACK ] 02 62 1D.F5.6B 1F 2E 00 00 03 7F 00 00 00 00 00 00 00 00 00 00 50 06 (00) Sun 12/30/2012 10:01:35 AM : [iNST-SRX ] 02 50 1D.F5.6B 13.26.DF 27 2E 00 (00) Sun 12/30/2012 10:01:35 AM : [std-Direct Ack] 1D.F5.6B-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Sun 12/30/2012 10:02:03 AM : [iNST-TX-I2CS] 02 62 1D F5 6B 1F 2E 00 00 03 09 00 00 00 00 00 00 00 00 00 00 C6 Sun 12/30/2012 10:02:03 AM : [iNST-ACK ] 02 62 1D.F5.6B 1F 2E 00 00 03 09 00 00 00 00 00 00 00 00 00 00 C6 06 (00) Sun 12/30/2012 10:02:03 AM : [iNST-SRX ] 02 50 1D.F5.6B 13.26.DF 23 2E 00 (00) Sun 12/30/2012 10:02:03 AM : [std-Direct Ack] 1D.F5.6B-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Sun 12/30/2012 10:02:07 AM : [iNST-TX-I2CS] 02 62 1D F5 6B 1F 2E 00 00 03 09 00 00 00 00 00 00 00 00 00 00 C6 Sun 12/30/2012 10:02:07 AM : [iNST-ACK ] 02 62 1D.F5.6B 1F 2E 00 00 03 09 00 00 00 00 00 00 00 00 00 00 C6 06 (00) Sun 12/30/2012 10:02:08 AM : [iNST-SRX ] 02 50 1D.F5.6B 13.26.DF 27 2E 00 (00) Sun 12/30/2012 10:02:08 AM : [std-Direct Ack] 1D.F5.6B-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

Anyone out there having problems with kpl and the LED keypad brightness. It is just not working for me with this new software. I have removed the KPL and re-add them without getting it to work

Ever since I upgraded to 3.3.6 I have been having problems with my KPLs v41. Upgrading to 3.3.7 has made no diference. I have a program to change the LED brightness at night and back during the daytime and it seems that that program has corrupted settings on all 5 of my new KPLs. I have since tried to restore the devices, change the LED brightness manually and reset the KPLs to factory default and nothing seems to clear the issues. UPDATE: I have removed several KPLs, Re-added them, and was able to control them, and link them but the LED levels DO NOT WORK at all.

Thanks so much for confirming that this seems to be a limitation. Please let us know when and if an actual bug is discovered and a if and when a fix may be available.

ISY is firmware 3.2.6 KeypadLinc is v.40 RemoteLinc2 is v1.2

I have a scene that includes a FanLinc and 4 buttons of a KeypadLinc. It works great. I have each button programed into the scene as controlers so each of them has a different value for each of the other buttons as well as for the FanLinc. End result is that I have a group of four buttons that control the fan and each other, displaying the correct values as each is pressed. I am trying to ADD a RemoteLinc 2 to this scene and have it behave the same way but I am running into what seems to me a limitation of the current implementation of the RemoteLinc2. I need to be able to control the buttons of the KeypadLinc from each of the buttons of the RemoteLinc2 and this does not seam possible. When I add the four buttons of the RemoteLinc2 all I can program into it is the value of the FanLinc. I don't seem to be able to press one button on the RemoteLinc2 and have it turn on one button on the KeypadLinc and turn Off other buttons on the same Keypadlinc. In essence I dont seem to have control of what the RemoteLinc2 button does to the KeypadLinc buttons, only the fan...

Of course I am selecting Save. If I dont the program does not get re-enabeled. Let me explain a bit more. I have several programs. A few week ago I disabeled some of them for testing purpouses. Later on I enabled them and they worked fine for days. Then Power went off in my area. When ISY powered back up I noticed that the programs were not working. I checked on the console and sure enouth they were disabled. I re enabled them and they worked fine again. If I now pull the power on the ISY again and re-connect it, when the console comes back up they are again disabled. JC

I have several programs that I disabled at some point in the past and have since re-enabled them. But if the ISY looses power, once power is restored the status of those programs reverts back to disabled and I have to manually re-enable them. This is happening with v2.8.8 It seems to me that somewhere in memory the program is being eneabled but wherever you store the "dissabled" bit remains set to dissable. So once power is lost and the programs are re-uploaded the outdated info is being set.

With the new version why does it take so long to rename a device. Renaming a device just to be almost intantateous.

Thank you, that way to call up the Query Worked. I was thrown off by the fact that there was no query button at the bottom of the screen.

I am trying to make the Input 7 work with a 1Wire device. I can use the Simplehomenet Utility Suite to set the Triger points for the particular input. Shouldnt then the ISY just respond to the triger points already set? SEPARATE question Why is there no QUERY command for the EZIO device. I have had instances where the EZIO gets out of sync with the ISY and I would like to triger a Query so that the ISY could verify the status of the inputs.

I have an EZIO8 from SimpleHomeNet and an ISY-99i PRO running v2.8.4. I can link the EZIO8 and send control info to the 8 outputs. But when it comes to the inputs I see no way to Query the device and the input that is the 1Wire temp sensor never updates, even though with SimpleHomeNet's own utility I can verify that the 1Wire temp sensor is working. Any ideas?

Under PLM Info it says v63

I just noticed that the newer ISY-99i are comming with a Dual-Band PLM. My ISY-99i Pro is a couple of years old and obviously does not have a Dual-Band PLM. From time to time the ISY-99i has problems communicating to some devices but not all the time. Would replacing the PLM with one of the new ones help with this situation? What other benefits are there with this replacement? Is there any reason why I should NOT do this replacement? Any information is appreciated