gviliunas

Hi Steve, I am using the NO relay output of an I/O Linc to control my fireplace however I took some steps to reduce the chances of the fireplace coming on when this is not desired. In the past, I have had incidents of one device turning on causing all devices in my house and garage to turn on. In my case the problem occurs about 1 time every 3-4 months. At this point, I think it is related to a motion sensor battery but can't be 100% sure which device is causing the trouble. With this in mind and still wanting an automated fireplace I did the following: 1. The I/O Link relay is wired in series with an existing wall thermostat. If the fireplace does come on, it will not dangerously overheat the house. 2. My 1st Floor All ON program does not trigger the fireplace ON. 3. My 1st Floor All OFF program commands the fireplace OFF, waits 5 seconds and commands it OFF again. 4. My alarm system being set turns off all lights and commands the fireplace OFF. 5. At 1:00AM when I am checking if all the lights are off, a command to turn off the fireplace will be sent as well. 5. I have a Party scene that will set some lights and start the fireplace if a KPL button is triggered with a Fast ON. A regular ON command only triggers the lights. 6. A RemoteLinc button is the only device, other than the PLM linked to the fireplace I/O Linc. I understand that some of this may not be necessary but I want to try to minimize my risk with fire and I love my current implementation. Good Luck and Enjoy your automated fireplace! Greg

Hi Ryan 0751, I use DSCLinc software to monitor my DSC alarm system and set a home/away variable. This enables some programs to run and disables others. Alternatively, if you don't have an alarm, you can set a KPL button to enable or disable your motion sensor notifications through a variable. If I used this method, I would probably forget to re-enable the notifications so I would need another program to re-enable manually after some period of time. Good Luck Greg

Thanks for your response Lee, I think that it may have been coincidental that I began to have trouble with a KPL just after loading 3.2.x The KPLs load would intermittently blink on and off at about 1Hz. I just flipped off the breaker to ensure the wire nuts were tight. They were. When I turned power back on, I heard an arcing sound from the KPL and all of the LEDs were blinking on and off. Factory reset wouldn't work. I think I just have a bad KPL and NOT an ISY problem. Time to call the Gold Line. Greg

Hi Lee, I saw your last post regarding SWLs and I2 database engine and am confused. If I Query Insteon Engine on all of my v.36 and v.39 KPLs, I see in the event log that I2 is not fully supported, reverting to I1. Shouldn't these be I2 devices? 1. Does your statement about SWLs mean that I need to now delete and re-add all of my KPLs in 3.2.4 to regain I2 functionality? 2. Does running a "Query Insteon Engine" change the way devices are controlled by ISY? i.e. Am I "breaking" devices by performing Query Insteon Engine? Greg

Hi Lee, Thanks for your response. Below is the event viewer data taken while attempting to change the ramp rate to 6.5sec. After this was executed, the ramp rate remained at the previous manually-set 2sec: Edit: Sorry, forgot to add that my device's address is: 0D.93.67 Sat 04/07/2012 12:33:36 : [ D 93 67 1] RR 25 Sat 04/07/2012 12:33:36 : [All ] Writing 1 bytes to devices Sat 04/07/2012 12:33:36 : [D 93 67 1 ] Memory : Write dbAddr=0x0021 [19] cmd1=0x2E cmd2=0x00 Sat 04/07/2012 12:33:36 : [iNST-TX-I1 ] 02 62 0D 93 67 0F 28 00 Sat 04/07/2012 12:33:36 : [iNST-ACK ] 02 62 0D.93.67 0F 28 00 06 SET-MSB(00) Sat 04/07/2012 12:33:36 : [iNST-SRX ] 02 50 0D.93.67 19.84.EC 2B 28 00 SET-MSB(00) Sat 04/07/2012 12:33:36 : [standard-Direct Ack][0D.93.67-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 04/07/2012 12:33:36 : [iNST-TX-I1 ] 02 62 0D 93 67 0F 2B 21 Sat 04/07/2012 12:33:37 : [iNST-ACK ] 02 62 0D.93.67 0F 2B 21 06 PEEK (21) Sat 04/07/2012 12:33:37 : [iNST-SRX ] 02 50 0D.93.67 19.84.EC 27 2B 1F PEEK (1F) Sat 04/07/2012 12:33:37 : [standard-Direct Ack][0D.93.67-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Sat 04/07/2012 12:33:37 : [iNST-TX-I1 ] 02 62 0D 93 67 0F 29 19 Sat 04/07/2012 12:33:37 : [iNST-ACK ] 02 62 0D.93.67 0F 29 19 06 POKE (19) Sat 04/07/2012 12:33:37 : [iNST-SRX ] 02 50 0D.93.67 19.84.EC 2B 29 19 POKE (19) Sat 04/07/2012 12:33:37 : [standard-Direct Ack][0D.93.67-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 04/07/2012 12:33:46 : [VAR 2 8 ] 0

Cannot set locally-applied ramp rate or level on v.27 SWL Dimmer (2476D) through ISY. The Single/Double-click set button method at the switch works though. I was having problems with a v.27 SWL Dimmer turning on randomly. All of the device links seemed correct so I tried factory reset followed by restore without success. I then tried completely removing the device from ISY and then re-adding it. After adding the unit to the appropriate scenes, I noticed that although ISY thought the unit's local ramp rate was 2.0 sec, it behaved as if it was 0.1 sec. I tried through ISY to change the ramp rate to several different values. There were no errors and ISY seemed to think that the change was successfully accomplished but when checked at the switch, I found the ramp rate was still 0.1sec. I used the double-click of the units set button and WAS able to successfully set the ramp rate. Perhaps ISY is not writing to the correct EPROM location for this version of SWL or do I have a bad SWL that hears link addresses but not other commands??? Greg

I noticed that the momemtary hold time option for v.33 or v.36 I/O Linc units cannot be changed. You can enter a number and save it but the hold time reverts to 0 upon reopening the IOLinc Options pop-up. I thought that I had a bad IOLinc but I replaced the v.33 with a previously unused v.36 spare. Both versions exhibit the same problem. Greg

Some SwitchLincs, InLineLincs, and KPLs reverting to 0% and 9min ramp (locally Applied Settings in Admin Console) after 3.x upgrade. I noticed that a non-load switch controlling a scene was not turning on a light. When I checked ISY, I noticed that my locally applied settings for: SWL Dimmer v.27, v.28, v.37, v.38 ILL v.53 KPL v.39 had all been changed to 0% and 9min ramp time. Once I changed the settings for > 20 units, everything seems to be working again. Has anyone else noticed this? Greg

I have had some minor problems with my 2413 PLM. After upgrading firmware, adding new devices, extensively changing programs, or rebooting ISY, I sometimes notice that ISY no longer responds to certain devices. Sometimes, the problem is with an EZIO8SA. Sometimes the problem is with an EZIO2x4 and sometimes ISY refuses to hear a remotelinc. Previously, I found that I could only fix this type of problem by deleting the device and re-adding it to ISY. (Restore device or PLM would not fix this. I don't understand this) I don't know the exact cause of my problem but know that it only occurs when I "do something" to my system configuration. Left to itself, my ISY runs and runs with no problems.....but I'm an engineer. I love to change things. Yesterday, I discovered a quick solution to this type of problem: 1. Create a test scene 2. Add the offending device to the scene 3. The PLM links will be repaired at this point and everything will work as before. You can remove the device from the test scene and delete the scene. I am currently using a V.98 version of PLM and have about 658 links in the PLM. Perhaps this problem will disappear when I change the PLM to V.99? I thought I would share this 10-second fix in case others have experienced this issue. I am not knowlegable enough to declare this a definitive solution only that it worked to repair two of my devices with this problem. Greg

Hi Michel, Do you know which version of plm includes this fix? Thanks Greg

Hi apostolakisl, I thought I was the only one seeing this type of problem. I have an 8-button KPL that is used exclusively used to trigger 8 ISY programs. My KPL "A" button controls a program that switches on/off all of my 1st floor lights. The "G" and "H" buttons trigger programs that enable "alarm clock-like" morning lights-on for my children's bedrooms located on the second floor. Intermittently, I have found that pressing either "G" or "H" (I haven't tried this with B, C, D, E, or F) will BOTH trigger the correct program AND ALSO trigger the program that is controlled by button "A." I have learned not to press buttons "G" or "H" when my wife is cooking in fear of all 1st floor lights switching on or off. When the problem occurs, I noticed that it is always the load control button, "A," that is incorrectly activated/deactivated when another button is pressed. To troubleshoot this I have: 1. Verified the KPL device links match ISY's - They do 2. Restored the device (multiple times) - No issue observed but it doesn't resolve the intermittent problem. 3. Checked and re-checked my programs - The morning alarm programs are not tied to the All 1st Floor programs 4. Replaced the KPL with a new Dual Band KPL Relay from SH - Intermittent problem remains. 5. Verifed that no mutually exclusive button or non-toggle mode settings are configured in the KPL - At installation, I performed a factory reset and then added the KPL to ISY with the clear all device links selection. Since I hadn't seen any other reports of this problem, I have been assuming that in my site and at that particular location, there must be a signal load or noise source that intermittently corrupts the signal to ISY from the KPL. I am a litttle more confused having observed the problem with a Dual Band KPL but I don't know if power line or RF signaling takes presedence. Is it possible that KPL's intermittently don't form their commands properly or that ISY intermittently doesn't properly interpret KPL commands? Greg

Here is a possible workaround to consider: Several months ago, I ran into this issue. In checking the forum for information and solutions, I noticed an alternate battery check method that was posted by Mike B. (My apologies if I am attributing this the the incorrect author). Rather than rely on explicit battery low reports from wireless devices, a program was started for each of my wireless sensors at ISY reboot and is retriggered with each wireless device trigger. Once running, the program waits 3 days and then sends me notification of any sensors that have not activated in 3 day. (possible dead battery) Since I trigger most of the sensors in my home each day, I count on that action restarting these watchdog programs and not alllowing the three day limit to expire. Unfortunately, you don't get an early warning of impending battery failure with this method. The again, the 2420M low battery signal has not been that reliable. Greg

Hi Michel, Thanks for the indormation that time changes more than a few minutes may cause Last Run Time and Last Finish Time to be cleared. Unfortunately, I think that this resets the status field of the associated programs to False. Many of my programs were written prior to the availability of variables so I use disabled programs as "master enables" and other runtime flags. Earlier today, I had the admin console configuration screen, system tab open and I was experimenting with daylight savings and time synchronization settings. I noticed that by clicking options in this clock box, The ISY time would vary 8-10 minutes from what was displayed in my computer task bar. Finally, I chose to Synchronize Now andISY and my computer agreed on the time and I closed the session. Later this afternoon, I noticed that all of my programs had once again stopped working. I checked the admin console and again, all of my programs were in False staus and the Last Run / Last Finished columns had been cleared. I believe this was due to my experimenting with the clock configuration. So, in conclusion: 1. If you use programs as flags and if the time changes more than a few minutes, you need to check your programs to ensure they are still running as expected. 2. Can I programmatically have ISY detect this condition and reboot itself when this happens? This may also mean (Michel please comment on this) that if you have a remote system and the possibility for clock changes of more than a few minutes, might you want to disable automatic time updates?? Rgards, Greg

I agree 100% with the OP For medium to large installations, Insteon is THE cost-effective choice for home automation and ISY-99 is the Only Way to Insteon. I've been using ISY since 2006 and couldn't be happier with the product, UD product support, and the help that I've received from contributers to this forum. Greg

I upgraded from 2.8.15 to 2.8.16 with no problems. Everything appears to work as expected.

I followed the new upgrade instructions (as posted at the beginning of this thread) exactly and everything worked properly the first time. Thanks for the great support and a great product! Greg

Possible bug report... I am currently using version 2.8.10 with my ISY and just noticed a problem with older KPLs (2886D) where the four secondary scene buttons can affect the state of scenes controlled by the primary button. Originally I thought that I had a failed KPL. I replaced the unit and then experimented with ISY, the suspected failed unit, and another KPL of the same vintage. Here is what I discovered: Process: 1. Factory reset KPL 2. Add KPL to ISY 3. Click on each node created and note that the current state can be made to toggle ON and OFF. <<>>> 4. Click on the primary node (05.15.98.1) and then toggle the secondary KPL buttons on and off and observe what ISY reports.... When this was done, I noticed that the current state of the primary button remained on or off (as previously set) BUT the current state slider in the properties window was observed to slide from 0 to 100% and 100% to 0 as the SECONDARY buttons were toggled. This does not IMO seem to be correct. 5. I was able to repeat this experiment with another KPL of the same vintage and obtained the same results. I have not observed (nor have I explicitly tested for) button interaction with newer KPLs. I don't know enough about the inner workings of ISY but think that changing the state of secondary buttons should not affect any properties of the primary button. I think that my KPLs might not be defective and suspect that ISY is somehow mis-mapping the secondary buttons allowing them to control scenes that should only be controlled by the primary button. Has anyone else observed this? Greg

Success! I followed Bob Paauwe's recommendation and retried the 2.8.9 upgrade (without re-downloading). On the second retry, my "About" screen indicated version 2.8.9. I did not receive any error messages during the original upgrade attempt or the two additional tries. Thanks for your help! Greg

Hi, I too observed that my ISY version was 2.8.8 after download and installation yesterday. Per your recommendation to another person with the same observation, I just re-downloaded, installed, and cleared my java cache. Still, ISY reports its version as 2.8.8 Is your server still chopping the download file? Greg

Downloaded and installed with NO problems. Thanks for the update. Greg

Thanks for the great information John! I printed your document and then poured through my programs to determine if any were in violation of your recommendations. I found several cases of programs attempting to control scenes containing controllers. These had all been working in the past but I followed your recommendation and created additional scenes with only responders and modified the programs to only trigger these. I'm trying to understand why I needed to do this. Is the problem that programs triggering scenes with controllers will cause the controllers to send additional unneeded traffic that would potentially make the system less reliable or is there some other reason? Thanks! Greg

My upgrade to 2.8.5 went well and everything appears to work however I am now seeing many -170001 error messages in my error log. I have not seen these previously. This particular error is not in the WIKI error message list so I'm not sure what it is. My ISY has a Kingston 16Gb SDHC card that I installed a few weeks ago to try and cure the 2.5.4 file error messages. I formatted the card using "ISY format" in a telnet session according to a process outlined in one of the message threads here. I have the network module installed but have not yet used any of its features. Yesterday, after installing 2.8.5, I received ~200 of the error messages, below. I rebooted ISY and have only experienced 3 instances since midnight. Thu 2010/11/18 06:50:08 PM System -170001 [uDSockets] 22 active/error 6 Thu 2010/11/18 06:50:13 PM System -170001 [uDSockets] 22 active/error 6 Thu 2010/11/18 06:50:19 PM System -170001 [uDSockets] 22 active/error 6 Thu 2010/11/18 06:50:24 PM System -170001 [uDSockets] 22 active/error 6 Thu 2010/11/18 06:50:29 PM System -170001 [uDSockets] 22 active/error 6 Thu 2010/11/18 06:50:34 PM System -170001 [uDSockets] 22 active/error 6 Thu 2010/11/18 06:50:39 PM System -170001 [uDSockets] 22 active/error 6 Thu 2010/11/18 06:50:44 PM System -170001 [uDSockets] 22 active/error 6 Thu 2010/11/18 06:50:49 PM System -170001 [uDSockets] 22 active/error 6 Thu 2010/11/18 06:50:54 PM System -170001 [uDSockets] 22 active/error 6 Thu 2010/11/18 06:50:59 PM System -170001 [uDSockets] 22 active/error 6 Thu 2010/11/18 06:51:04 PM System -170001 [uDSockets] 22 active/error 6 Thu 2010/11/18 06:51:09 PM System -170001 [uDSockets] 22 active/error 6 Thu 2010/11/18 06:51:14 PM System -170001 [uDSockets] 22 active/error 6 Thu 2010/11/18 06:51:19 PM System -170001 [uDSockets] 22 active/error 6 I'm not sure if this is a problem but am reporting as this code is beta. Greg

I am worried that I will soon reach the limit for PLM listening for status changes and have been trying to use the Count feature of Show PLM Links Table . Unfortunately, I seem to get a different count each time I select to re-scan the PLM and then count. In the last 10 minutes, I have received counts of 26, 60, 336, 454, 592, and 772 for the same PLM. Since the PLM is directly connected to ISY, I wouldn't have thought there would be a communication problem when scanning the link table. Do running programs or other Insteon activity in the house affect the scanning of the PLM for links? Will activity here stop a scan in progress? In spite of this, everything appears to work normally in the house. Should I be worried about impending failure? Am I misusing this feature? Thanks for your help!

Thank you Michel and your team for your hard work and dedication to this project. I have been using 2.7.15 for a week and everything in my system is working perfectly! Greg