wwat

Thanks Lee, Indeed it was the magnets, perhaps they have lost some of their magnetism. I attached a more powerful rare earth magnet to the bottom of the existing one screwed onto the door and its working now. Many thanks for you help, Wayne

Hi, I've been using the door kit for about 2 years and up until about 6 months ago it was working perfectly. I first noticed that the keypadlinc light wasn't going off when the door was closed, the light stays permanently on. The door is still working, it goes up and down via the KPL or the actual garage door opener but the light always stays on. Today I had some time and tried to do some checking. I noticed that the IO Linc green light remains permanently off. Does anyone know what the problem could be? Is there any further info I can provide that would assist? Here is a link to my set up which hasn't changed: http://forum.universal-devices.com/viewtopic.php?t=4092 Door open events: Thu 10/18/2012 02:44:53 PM : [iNST-SRX ] 02 50 12.BA.68 00.00.03 CB 11 00 LTONRR (00) Thu 10/18/2012 02:44:53 PM : [standard-Group][12.BA.68-->Group=3] Max Hops=3, Hops Left=2 Thu 10/18/2012 02:44:53 PM : [ 12 BA 68 3] DON 0 Thu 10/18/2012 02:44:54 PM : [iNST-SRX ] 02 50 12.BA.68 19.75.00 41 11 03 LTONRR (03) Thu 10/18/2012 02:44:54 PM : [standard-Cleanup][12.BA.68-->ISY/PLM Group=3] Max Hops=1, Hops Left=0 Thu 10/18/2012 02:44:54 PM : [iNST-SRX ] 02 50 12.BA.68 19.75.00 41 11 03 LTONRR (03): Process Message: Ignored Thu 10/18/2012 02:44:54 PM : [standard-Cleanup][12.BA.68-->ISY/PLM Group=3] Max Hops=1, Hops Left=0 Door close events: Thu 10/18/2012 02:46:01 PM : [iNST-SRX ] 02 50 12.BA.68 00.00.03 CB 11 00 LTONRR (00) Thu 10/18/2012 02:46:01 PM : [standard-Group][12.BA.68-->Group=3] Max Hops=3, Hops Left=2 Thu 10/18/2012 02:46:01 PM : [ 12 BA 68 3] DON 0 Thu 10/18/2012 02:46:01 PM : [iNST-SRX ] 02 50 12.BA.68 19.75.00 41 11 03 LTONRR (03) Thu 10/18/2012 02:46:01 PM : [standard-Cleanup][12.BA.68-->ISY/PLM Group=3] Max Hops=1, Hops Left=0 Thu 10/18/2012 02:46:01 PM : [iNST-SRX ] 02 50 12.BA.68 19.75.00 41 11 03 LTONRR (03): Process Message: Ignored Thu 10/18/2012 02:46:01 PM : [standard-Cleanup][12.BA.68-->ISY/PLM Group=3] Max Hops=1, Hops Left=0 Thanks, Wayne

With the adoption of version 3.1.16 this issue seems to be resolved. The ON/OFF count has continued to match perfectly since the update. Thanks, Wayne

I don't know how many switches you have, even if it was 100 it still wouldn't take that long to set up the program. Here is an example of a way to shorten it a little. If Status 'Furnace Room / Furnace Room SL' >= Off Or Status 'Ensuite / Ensuite SL' >= Off Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action')

Thank you for the replies. I'm currently on version 3.1.14 so I'll upgrade and keep an eye on it. Tim said: Indeed it was a left over from an attempt at troubleshooting the issue, sorry for the confusing code. In theory it shouldn't matter, the program should still work as intended, lets see how 3.1.16 goes. Appreciate your help, all the best for the new year. -Wayne.

Hi, I have two programs, one that turns the humidifier on and the other turns it off. For some reason the program that turns it on runs more often than the other despite certain criteria which should prevent this. The idea is that once the humidifier is on, and only once it reaches a certain humidity percentage will it turn off. Only once its off should it turn on. Can anyone see how the 'On' program might run more often and the 'Off' program. There are two variables that keep track of the number of times that each program runs and at the end of each 'Off' cycle the count is checked and an email alert sent if there is a difference. Thanks, Wayne [Humidifier On] If Status 'Venstar House' < 37% (Humidity) And ( Status 'Living Room / Living Rm KPL - Track Light / Humidity Control' is On Or Control 'Living Room / Living Rm KPL - Track Light / Humidity Control' is switched On ) And Status 'Furnace Room / Humidifier-Sensor / Humidifier-Relay' is Off Then $Int_Humidity_On_Count += 1 $Int_HumidifierFanStatus = 1 $State_HumidifierWHOverride = 1 Run Program 'Humidifier Fan On Control' (If) Set 'Furnace Room / Humidifier-Sensor / Humidifier-Relay' On Else - No Actions - (To add one, press 'Action') Run Program Override (Then Path) - removed this line temporarily [Humidifier Off] If Status 'Venstar House / House - Fan' is On And ( Status 'Venstar House' > 39% (Humidity) Or Status 'Living Room / Living Rm KPL - Track Light / Humidity Control' is Off ) And $Int_HumidifierFanStatus is 1 Then $Int_Humidity_Off_Count += 1 $Int_HumidifierFanStatus = 0 $State_HumidifierWHOverride = 0 Set 'Furnace Room / Humidifier-Sensor / Humidifier-Relay' Off Run Program 'Humidifier Fan Off Control' (If) Run Program 'Humidity Count Alert Wrong' (If) Else - No Actions - (To add one, press 'Action')

Hi Michel, In the last version myself and a few other users reported what appears to be a problem with program evaluation in ISY. In relation to my report you mentioned that you were concerned that the program had a 'wait' statement which could have caused the issue and you also mentioned that you were looking into the issue. A few days ago I rewrote the program to exclude the wait statement and to use variables instead of programs to hold certain info. The updated program was working without issues until today. Today I noticed that the program remained with a status of 'False' despite everything within the 'If' statement evaluating to 'True' I was able to take screen shots to prove the point. I also attempted to manually run the 'If' statement, it also susequently failed. I then ran the 'Then' statement manually which triggered without any problems. Regards, Wayne Copy of new code (without 'wait' statement): [Humidifier Off] If Status 'Venstar House / House - Fan' is On And ( Status 'Venstar House' > 39% (Humidity) Or Status 'Living Room / Living Rm KPL - Track Light / Humidity Control' is Off ) And $Int_HumidifierFanStatus is 1 Then $Int_Humidity_Off_Count += 1 $Int_HumidifierFanStatus = 0 $State_HumidifierWHOverride = 0 Set 'Furnace Room / Humidifier-Sensor / Humidifier-Relay' Off Run Program 'Humidifier Fan Off Control' (If) Else - No Actions - (To add one, press 'Action')

Hi Michel, re: UDQFull errors There was no such error in the error log, actually no errors since November. If it was false then it was incorrectly false because I know all the elements that made up the 'If' statement evaluated to 'True', I'm not sure were to go from here. It would be good if there was a detailed debug trail we could review for just these unexpected situations. Perhaps something to think about including in the betas, give us the ability to turn it on and off and save to disk, or email directly to you for further analysis. Regards, Wayne Here is a copy of the event log, I have coloured the event that should have triggered the program. Venstar House Humidity 39% Thu 2011/12/08 02:59:20 PM Workshop / Workshop TL - Light Status 100% Thu 2011/12/08 03:00:49 PM Workshop / Workshop TL - Light Status 0% Thu 2011/12/08 03:14:27 PM Workshop / Workshop TL - Light Status 100% Thu 2011/12/08 03:19:12 PM Workshop / Workshop TL - Light Status 0% Thu 2011/12/08 03:19:31 PM Workshop / Workshop TL - Light Status 100% Thu 2011/12/08 03:26:28 PM Workshop / Workshop TL - Light Status 0% Thu 2011/12/08 03:27:32 PM Venstar House Status 75â–‘ Thu 2011/12/08 03:31:26 PM Venstar House Status 76â–‘ Thu 2011/12/08 03:33:36 PM Workshop / Workshop TL - Light Status 100% Thu 2011/12/08 03:34:19 PM Venstar House Status 75â–‘ Thu 2011/12/08 03:34:46 PM Venstar House Humidity 40% Thu 2011/12/08 03:36:56 PM Garage / Garage Door - (Sensor) Status 100% Thu 2011/12/08 03:40:36 PM Living Room / Living Rm KPL - Track Light / Garage Door KPL - A Status 100% Thu 2011/12/08 03:40:36 PM Workshop / Workshop TL - Light Status 0% Thu 2011/12/08 03:40:38 PM Workshop / Workshop TL - Light Status 100% Thu 2011/12/08 03:44:14 PM Garage / Garage Door - (Sensor) Status 0% Thu 2011/12/08 03:44:31 PM Living Room / Living Rm KPL - Track Light / Garage Door KPL - A Status 0% Thu 2011/12/08 03:44:31 PM Workshop / Workshop TL - Light Status 0% Thu 2011/12/08 03:45:40 PM Furnace Room / Furnace Room SL Status 100% Thu 2011/12/08 03:50:13 PM Furnace Room / Furnace Room TL - Opened Status 100% Thu 2011/12/08 03:50:13 PM Furnace Room / Furnace Room SL Status 0% Thu 2011/12/08 03:56:01 PM Furnace Room / Furnace Room TL - Opened Status 0% Thu 2011/12/08 03:56:01 PM Venstar House Status 74â–‘ Thu 2011/12/08 03:58:21 PM Venstar House Status 75â–‘ Thu 2011/12/08 03:59:28 PM Venstar House Status 74â–‘ Thu 2011/12/08 04:01:38 PM Main Bedroom / Main Bedroom - Waynes Lamp On 114 Thu 2011/12/08 04:01:57 PM Main Bedroom / Main Bedroom - Waynes Lamp Status 45% Thu 2011/12/08 04:01:57 PM Venstar House Status 75â–‘ Thu 2011/12/08 04:02:46 PM Venstar House Status 74â–‘ Thu 2011/12/08 04:04:57 PM Venstar House Humidity 41% Thu 2011/12/08 04:09:15 PM Venstar House Humidity 40% Thu 2011/12/08 04:10:20 PM

I know what you're suggesting but in this case it would not have mattered, at least once the humidity rose above 40% and stopped fluctuating between 39 and 40%, it got to 44% before I arrived home. The fan status was always ON and the program 'Humidifier Fan Status' was always 'True' because I sat and watch everything while the humidity rose from 44 to 45% without triggering the program. This is the very first time anything like this has happened, it was not a communication error and it has triggered correctly so far since yesterday. Remember I attempted to trigger the 'If' statement manually and it didn't evaluate to 'True' even though all the individual statements were true. Regards, Wayne

Hi, Program failed to evaluate 'If' statement correctly. The particular program in question has been running without fail for the last 6 months, it was running this morning. Suddenly it failed tonight. I checked the 'If' statement and everything evaluated to true and status updates were arriving as evidenced by the history and event log, so the programs 'Then' statement should have been triggered. After waiting for some time to make sure it was in fact broken I then tried to run the 'If' statement manually but it failed to cause the 'Then' part to run. I then ran the 'Then' part manually and it worked. Some further details: - The fan was on because I could hear it and it was reported as on from the Administrator and the stat itself. - By the time we got back home the humidity was up to 45% and should not go above 40%. - I double checked the status of program ''Humidifier Fan Status' and it was 'True'. - There has been no communication issues for years now and I haven't added new electronics, the program was working fine this morning. I'm at a lose as to what may have gone wrong. Wayne If Status 'Venstar House / House - Fan' is On And ( Status 'Venstar House' > 39% (Humidity) Or Status 'Living Room / Living Rm KPL - Track Light / Humidity Control' is Off ) And Program 'Humidifier Fan Status' is True Then Set 'Venstar House' Query Wait 10 seconds Run Program 'Humidifier Fan Off Control' (If) Run Program 'Humidifier Fan Status' (Else Path) Set 'Furnace Room / Humidifier-Sensor / Humidifier-Relay' Off $State_HumidifierWHOverride = 0 Else - No Actions - (To add one, press 'Action') Run Program Override (Else Path) - removed this line temporarily

Done, new card in place with 3.1.12. We'll see how it goes from here. Thank you very much for your help. Regards, Wayne

Hi Joe, Not these devices, in the past I have had issues with missing links from the ISY links table but that may or may not be related. I was sitting here at the time of the upgrade and there were no power issues at all and these devices are hardwired devices. Thanks for your input, W.

Hi Michel, For the scenes in which the devices were still present the links didn't appear to be missing. Since last night I noticed two other devices that were missing and required adding again. I did try restoring a knowable good last backup but those devices would not load up, the only way to get them back was to actually enter them individually as a new device. I noticed in the Excel log (first column 'Insteon Device') at a date previous to the upgrade that one of the devices was actually named using its code i.e 12 43 6E 1 instead of 'Fireplace Lights'. Regards, Wayne ps. another thing I just noticed. Performing a scene test on any of the scenes does nothing. So I right click on the scenes click diagnostics --> Scene test but nothing happens.

It appears that at least one device was missing. So after the upgrade the 240V N/C relay was missing from the device list and programs that used it were affected. I tried restoring the backup but it didn't help, I then tried reinstalling the previous version of software and still no luck. I actually had to add that device back into the ISY and fix the programs manually. W.

After upgrading I noticed that many of the device names within the code of the programs where listed as W.

I have a little more infomation. After discovering that it wasn't a single light that was not working but everything that depending on the ISY links table, I discovered that the ISY links table was completely empty of data. I'm not entirely certain when it happened but it seemed to coincide with the upgrade from 3.1.2 to 3.1.10. This is not the first time this has happened, back in 2010 when upgrading to 2.7.15 the exact same problem occured, the data in the ISY links table disappeared after the upgrade. I reported the problem but I don't think the issue was ever replicated. Actually its happened numerous times, probably 3 or 4 time all up. I'm not sure where to go wit this issue, its almost impossible to replicate on demand. Wayne ps. I was able to restore the backup prior to the upgrade which restored the links table so I'm back up and running (for now).

Lee, Why would the Admin console indicate that the light is on when in fact it isn't. So if I look under the My Devices tab, and select the light in question the 'Current State' is ON. If there was communication issues shouldn't the status be off.

Hi Lee, Below are the scene test results, it appears that it succeeded. According to you this indicates a communication problem but this issue has only started since upgrading (on the 23rd Oct), prior to that the light came on every night at the correct time. It manually works without fail from the Admin console, if it was a communication issue it would fail occassionally from the Admin console but it doesn't. I have already removed and added the device back into the scene. I'll try removing the device from ISY and re-adding it. Many thanks, Wayne Fri 10/28/2011 07:29:30 PM : [GRP-RX ] 02 61 15 13 00 06 Fri 10/28/2011 07:29:30 PM : [iNST-SRX ] 02 50 13.1B.10 19.75.00 61 13 15 LTOFFRR(15) Fri 10/28/2011 07:29:30 PM : [standard-Cleanup Ack][13.1B.10-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Fri 10/28/2011 07:29:30 PM : [CLEAN-UP-RPT] 02 58 06 Fri 10/28/2011 07:29:30 PM : [iNST-SRX ] 02 50 0F.49.0C 19.75.00 61 13 15 LTOFFRR(15) Fri 10/28/2011 07:29:30 PM : [standard-Cleanup Ack][0F.49.0C-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 ----- Night Lights Test Results ----- [succeeded] External SL - Wall Sconce (13 1B 10 1) [succeeded] Furnace Room OL - Pot Lights (F 49 C 1) ----- Night Lights Test Results ----- Fri 10/28/2011 07:29:38 PM : [iNST-ACK ] 02 62 00.00.15 CF 13 00 06 LTOFFRR(00)

Since installing version 3.1.10 there is a problem with one of the lights within a scene, it wont turn on when the scene is activated using a program at a certain time. The other light in the scene works and the lights in question does turn on if I manually activate it via the Administrator interface. The status of the light is 'ON' in the administrator but the light doesn't actually turn on. How else can I trouble shoot this issue. Thank you, Wayne

Below is a snippet from the error log. Upgraded to 3.1.10 on 23rd Oct. I'm not sure what 17001 Queue Full means and whether its a problem. Sun 2011/10/23 01:29:16 PM System -60006 n/a Sun 2011/10/23 05:36:43 PM System -170001 UDQ:Queue Full: LOG Sun 2011/10/23 05:36:01 PM System -5 Start Sun 2011/10/23 05:36:19 PM System -170001 [Network] Established Mon 2011/10/24 05:56:14 AM System -100002 /LOG/A.LOG Tue 2011/10/25 09:19:16 PM System -5012 29

Thanks for the feedback, I suspected this was the case. I've found a few other reports of this nature however I suspected that it could be happening more than we are aware of. If users get the faulty product replaced without reporting on a public forum we would never know how much its happening. Its not the type of component you can spend time messing with either because any downtime/unreliability affects the entire house. I appreciate your companies quick response with the ISY power adaptor which was required with a change to the new PLM, excellent service. Thanks again. Wayne.

Today was the second time in as many weeks that the PLM lost all its links. The first symptom was that there were no status updates back to ISY although ISY can still send commands. I checked the PLM links table and it was empty, exactly the same happened a few weeks ago. A PLM restore resolved the problem both times. Anyone experienced this or know why it could be happening? The first time there was a light storm but nothing else in the house was affected, again yesterday there was a small amount of lightning but nothing else was affected either. Thanks, Wayne

Great, thank you both for the replies, I'll take a look tonight and make some comments. Wayne

Thanks, So what I'm looking for is; a) a physical solution, and some programmatical solutions (which you have provided). I'm thinking about purchasing an 8 button keypadlink, this would allow me to create 8 override switches which is more than enough for now. I can see a case where it might be more appropriate to leave a light on even if the normal schedule determined that it should be off, but normal scheduling should begin right after the user turns the actual light off. For the water heater it should turn off if we are currently in a peak power time of day and stay on if in off-peak. So it should be configerable by device but I could probably live with the easier solution and revert everything back to the normal schedule. This again is device dependant, heater should turn ON which would leave it under control of internal thermostat. Lights should stay at their current status, if ON then leave On, if Off then leave them Off. Thanks for the few examples. Wayne

I need to set up a few manual overrides for some of the programs, the manual override switch needs to be easily accessible for anyone in the house to use and understand. I'm wondering what is the best way to go about this is. As an example I have the hot water heater on a timer to come on during off-peak times, I would like the ability for any member of the house to by-pass this ISY program if needed. I'm the only one that has access to the ISY administrator and that wont change. Another example is night lighting, its set to come on at a certain time and switch off at a certain time, I'd like to be able to over ride that so the lights remain uneffected by the ISY program. Thanks, Wayne