to_lighter

One final disturbing observation. In my setup, if the door is obstructed, it will close anyway if triggered by an Insteon command. If something moves in front of the obstruction sensor while the door is closing then the door will stop and open back up again, but the fact that the door is obstructed is ignored if the obstruction is present when the Insteon command is sent. Cheers!

OK, A bit of experimentation revealed something quite terrifying. The garage door opener will ignore the door's obstruction sensor and continue to close the door even if something is in the way if the door is closed by an Insteon command. This is if you set up the I/O link in the default manner. The only way to get things to work properly is to follow the Wiki, set Tigger Off and Momentary: A. I don't understand why this works, but it does, and allows for local control, stopping of the door by the obstruction sensor, etc. This is potentially a huge safety issue. I'm glad I took a moment to experiment this morning. Cheers!

Thanks Brian, Starting to understand the lingo a bit better. The following paragraph from the wiki is what has me confused: "If you wired the sensor according to the directions provided with the kit, you used the black and green wires from the reed switch. These are the normally open leads from the sensor. If you sensor is normally open then you need to enable the Trigger Off option in the I/O Linc options dialog to make it behave as if it was a normally closed sensor. Be sure the Relay is set to Momentary: A as this allows the relay to return to the off state after it triggers the garage door opener (after the Timeout). Without this, you may lose the ability to control the door locally since the garage door button is essentially being held down by the relay. Select the I/OLinc Relay in the tree view and click the Set Options button in the view pane. Enable Trigger Off if you are using a normally open sensor. Be sure Momentary: A is enabled and all other Momentary options are disabled." First off, the sensor doesn't have a normally open or normally closed position. It is wired with a sense and a ground. You can select to wire the relay as either normally open or normally closed. If I understand the Smartlabs directions properly, then they had suggested wiring the relay in the normally open position, which I interpret to mean that normally there is no electricity flowing to the garage door opener terminals from the I/O Link. Only when the relay is triggered does it close, completing the circuit between the I/O Link and the door opener. I'm not sure why the wiki suggests changing the setting to normally closed, that makes no sense to me. The other suggestion to switch to Momentary mode makes sense to me. If the default setting is "latching" mode, then the relay will stay open or closed until it is triggered again. Useful for turning on sprinklers and leaving them on, but not so useful for garage doors. In the link that you sent, Smartlabs suggests using Momentary Mode C for garage doors. Finally, and most importantly, is there any safety issue here? Will a command from the Insteon system triggering a garage door closure overrule the door's object detecting sensor? Cheers!

Hi gang, My installer installed two garage door openers for me (INSTEON model 74551). As far as I know, he installed them as per the written instructions that came with the kit. I have added them to the ISY 99i. I decided to have a go at programming them, and read the article on the wiki with growing dismay. http://www.universal-devices.com/mwiki/ ... e_Door_Kit It seems to me that the door sensor is ON when the garage door is closed. The relay status seems random. The doors only change position when the ON command is sent to the relay. Is this the normal activity? There was a discussion in the Wiki in how to set the options for the control kit. Are these steps necessary? How do I know if my relay is open or closed? I certainly didn't like the part about losing local control of the door if the options were not set correctly Is there a i/o link for dummies course? Could someone explain the meaning of the technical terms in the wiki for this device? Maybe that info could be added to that page in the wiki ... Cheers!

Some more info. If I check the status of a different light, the program will execute properly. It is when it is checking the front door light (which is part of the scene) that it will fail to execute properly. I tried sending the commands as individual instructions to the lights (i.e. set each light to 50% one by one). As soon as "Main Entrance Door Pots" is set to 50% the program becomes false and stops. I have another program set to check the status of the Main Entrance Door Pots and email me if it is not off, and that program is never triggered. In other words, there is no short period of time where the status is actually off, which would stop the program. Is this a bug? Cheers!

Hi gang, I have a motion detector that turns on a scene of lights, then turns them off in stages. When the motion detector sends the off command, the lights dim to 50% then 30 seconds later they turn off. As part of this, I need to make sure that the lights were actually on in the first place. For example, if I hit a button on my KLM, I can turn off all of the lights on the floor. If I turned off all of the lights, when the motion detector sends the OFF command, the 50% brightness scene will be triggered, and the lights will come back on! To get around this, I have tried checking the status of the light. Example: If Control 'Motion-Front Hall-Sensor' is switched Off And Control 'Motion-Front Hall-Sensor' is not switched On And Status 'Main entrance - door pots' is not Off Then Set Scene 'Main Floor Front Motion-50%' On Wait 30 seconds Set Scene 'Main Floor Front Motion-50%' Off Else - No Actions - (To add one, press 'Action') When running this program, the motion detector sends OFF, and the "Main Floor Front Motion-50%" scene is activated, and then for some reason, the program becomes false and stops. It does not proceed to Wait 30 seconds and then turn off the lights. The status of the lights is not off, but for some reason, having that line in there causes the program to quit. If I take the status line out, then the program will complete itself properly (i.e. turns the lights to 50%, waits 30 seconds, then turns them off). I think this may be a bug in the ISY 99. Any thoughts? Cheers!

I see the requester to put the MS in linking mode is not called for the Links Table function. I will enter this as a bug. To read the Links Table the MS must be in linking mode. If you linked the Motion Sensor in one of the 2.6.x betas you will most likely have to Remove the MS from the ISY and re-link it rather than Replace it. Rand Thanks Rand, I removed all of the motion detectors, then re-added one by one (they were originally added in a 2.6.x beta). Now they all seem to work fine. Cheers!

Hi there, I am trying to add a motion detector after changing my PLM. I tried reseting the device (factory reset, then replace device from the ISY menu, then hold button for 5 seconds until light on detector flashes, then hit OK on ISY pop-up). I've done this but the detector doesn't seem to be detecting motion I thought I might try checking the link count, but I got a request failed error. Are you supposed to be able to check the link count on a motion detector? Cheers!

For comparison sake, here is the ISY log when I activate the scene from the ISY rather than with the KPL button. 2009/03/13 09:46:15 : [iNST-ACK ] 02 62 00.00.2B CF 11 00 06 LTONRR (00) 2009/03/13 09:46:15 : [ F 17 5A 1] ST 191 2009/03/13 09:46:15 : [iNST-ACK ] 02 62 00.00.1E CF 11 FF 06 LTONRR (FF) 2009/03/13 09:46:16 : [iNST-ACK ] 02 62 00.00.64 CF 11 FF 06 LTONRR (FF) 2009/03/13 09:46:16 : [iNST-ACK ] 02 62 00.00.75 CF 11 FF 06 LTONRR (FF) 2009/03/13 09:46:17 : [iNST-ACK ] 02 62 00.00.49 CF 11 FF 06 LTONRR (FF) 2009/03/13 09:46:17 : [iNST-ACK ] 02 62 00.00.4F CF 11 FF 06 LTONRR (FF) 2009/03/13 09:46:18 : [iNST-ACK ] 02 62 00.00.77 CF 11 FF 06 LTONRR (FF) I'm not an expert at reading these, but there are 6 INST-ACKs at the end of the output when triggered from the ISY, and only one when triggered from the KPL button. Any ideas? Cheers!

Thanks Mike, Part of the issue is that I can't get a reliable PLM link count. Last night I did it when there was no activity. I got 700 twice, and over a thousand once. In any case, I have put in a request for a v85 PLM. I'm really stuck now. Most of my devices don't respond to my KPL buttons. In the event log the button press is noted, and the scene activated, but then the devices don't respond. Here is an example of a scene that has 5 devices (4 switchlinks and one outletlink). On the KPL keypress, the scene is supposed to be activated. Here is what happens: 2009/03/13 09:19:43 : [iNST-SRX ] 02 50 0B.F7.5A 0C.00.02 C3 11 00 LTONRR (00) 2009/03/13 09:19:43 : [standard-Group][0B.F7.5A-->Group=2] Max Hops=3, Hops Left=0 2009/03/13 09:19:43 : [iNST-SRX ] 02 50 0F.43.1E 0F.17.5A 62 11 02 LTONRR (02) 2009/03/13 09:19:43 : [standard-Cleanup Ack][0F.43.1E-->0F.17.5A] Max Hops=2, Hops Left=0 Only one of the lights comes on. If I activate the scene from within the ISY, all of the lights come on perfectly. Any ideas? Cheers!

Hello Michel, I am interested in your answer, as I think my supplier of Smarthome equipment was quite skeptical about your response. The issue has been reproduced on two occasions. A reset of the PLM leads to none of my keypad programs working. The first time was due to a power outage. This time was a deliberate reprogramming of the PLM based on your advice. The result was exactly the same both times. I am wondering whether you guys at ISY have tried this scenario with your equipment on a large setup like mine. It feels like I have been given advice that feels very definitive (i.e. swap your PLM for a version .85) when it seems that this advice is more conjecture than fact. Have you guys at Universal Devices tested a scenario like mine and determined that it can only be solved by a PLM v.85? If I insist that my supplier take back another PLM and provide me with a v.85, will it solve the issues that I am having? I feel like I am heading down a dead end here, and that there is something wrong with my ISY setup. So far my supplier has been very helpful, but there is a bit of silence happening since I forwarded some of your replies. Thanks PMC

Yes, the proliferation of RF devices appears to have left us a bit unprepared. Our original plan was to Restore all the RF devices first so the chances of a timeout were minimized. That is why there is one Requester when the process begins. We are certainly going to have to rethink this. Do you think we should do the RF devices first or last or interspersed or separately? We have a bit of a quandary here. We appreciate your input, thank you very much, Rand Hi Rand, Thanks for your reply and your interest. As I mucked about with the motion detectors, it seemed to me that the limitation was on how they were designed (i.e. there was no "program by ISY" mode). As such, I would suggest that if you could, you would arrange a "walk through" from the ISY, where the ISY resets all non-wireless devices, then walks you through programming each wireless device in turn. Too bad it couldn't be done some other way, as climbing ladders about the house to pull all of these things down adds another level of unfun to the process. Cheers!

Thanks Michel, I'm back to the inconsistent counts, even with a totally silent system. First count was 700, next was 1153. Cheers!

Will putting the motion detector into unlinking mode still allow it to be programmed? Can you put multiple detectors into unlinking mode simultaneously? Cheers! Yes, the sensors can be programmed in unlinking mode. As for all at once I don't know how that will work. I have a feeling each will quit when the next one is activated. But if you take Michel's advice and watch when they are programmed you can activate one at a time and deactivate when done without waiting for the time out. The other option is to let them fail in the Restore and then Restore them individually with the new PLM. Rand Thanks Rand, I think the fail then restore individually method is probably easier. The instructions from the ISY are obviously not helpful. If you have one motion detector, you are very likely to have more than one, and so this technique should be incorporated into future instructions. Cheers!

Will putting the motion detector into unlinking mode still allow it to be programmed? Can you put multiple detectors into unlinking mode simultaneously? Cheers!

Thanks Rand, The link was very informative, thank you. I now feel better about the Scene Test results differing from what I was seeing with my own eyes. My link count on the PLM is 1748. I'm going to run it a few more times to see if it is consistent. Cheers! Hi Michel, I have obtained a new PLM v7A. Is this a sufficiently new version? As an FYI, after restoring the new PLM, the ISY has stopped seeing my KPL switches again, same issue as the start of this thread. When I get home, I'm going to try the removing a switch - reinsert a switch trick and see if that works. Is this a symptom of something larger being wrong with my system? Cheers!

Hi Michel, I did a rough count of my devices today and came up with 144 (this includes counting KPL buttons as separate devices. If I leave out motion detectors and KPL buttons the count is about 82, which is similar to the successful count in the log. I found one device that was not successfully reset in the log. I think I was distracted by the progress bar. I guess it doesn't actually reflect the % complete. I'll try factory reseting the problematic device from the log, and see if that does the trick. Cheers!

Thanks Michel, I scrolled through the event viewer. There are no errors. The 2nd last line in the event viewer is "Replacing PLM links successful", followed by "Replacing PLM links: incomplete". Instead of moving on to the next device, it fails always after completing this one particular switch. This is about 1/3 of the way through the devices. Any ideas?

Hi gang, I got a new PLM today (v7A). I have been trying to follow the PLM Restore procedure, but I keep getting a Request Failed error about 20% of the way through. It seems to always fail at the same place. Looking at the event viewer on level 3 doesn't seem to help. The last device before the failure seems to have been reset successfully (the log says Replacing PLM links successful for that device). The next line simply says Replacing PLM links: incomplete. I've tried factory reseting the PLM. Any ideas? Cheers!

Hi again, As part of the Restore PLM procedure, you are supposed to put the motion detectors into program mode. I have 4 detectors. I have been trying to put them into program mode by holding down the button for 10 seconds. After about 4 or 5 seconds, the LED begins to blink. When I move on to the next detector and press and hold its button, instead of going into program mode, I think it is making a link with the first detector, as the LED never begins to blink on the 2nd detector, and the LED stops blinking on the first. How do I get 4 motion detectors into program mode at the same time? Cheers!

Hi gang, I am changing my PLM as per previous recommendations. How do I do it? Do I just plug it in, attach the ISY, and then run the Restore PLM command? Cheers!

Hi gang, I have been running through the ISY diagnostics on some on my problematic switches. On some, I have entries marked "Identical", which I assume is good, and I have some that are marked as "Ignore", which I am not so sure about. I have learned to ignore the last entry, which is always "Ignore", however, some of my switches have "Ignore" entries earlier in the list. For example, one problem switch has four "Ignore" entries. Can I really safely ignore these? Cheers!

It would be nice if there were an option for the PLM link count to ignore traffic and proceed with the count. The only way that I'm going to get a consistent count is to turn off the timer query for my thermostat, and make sure that noone hits any switches. Cheers!

Thanks for the replies, gentlemen. I use different scenes to make sure that the lights are at the appropriate brightness for the time of day when they are turned on. For particular lights that are most often turned on in the house, I have scenes that turn them slowly down after dusk. I think I'll keep the scenes as they are, as it sounds like the program route would be even more complicated. Next week I'll look into one of the PLMs that can handle over 2000 links. Cheers!

Hi gang, It has been suggested that I get a new PLM as my link count is too high. One thing that is strange is that I can't get my PLM and ISY to agree on a link count. Every time I run the PLM link count function, I get a different result. Here are some recent values: 358 390 623 1045 239 Does activity on the PLM (ex. people turning on and off lights) make a difference? Is this a symptom of a PLM that needs replaced? Are there other explanations for an inconsistent PLM link count? Cheers!