LeeG

If you know the specific model number of the Dakota Alert device on the gate now I will take a look. The Dakota Alert Universal Remote UT-3000 has terminals for connecting any kind of external switch such as a magnetic switch similar to what is used in garage door application. For the high water detection I used a marine bulge pump switch. They are about as water proof a switch as one can get. The UT-3000 itself is mounted under the roof of one of the boat slips so it is not directly exposed to the elements but sitting over water. I used another UT-3000 mounted in a similar location connected to a simple 120v relay from Radio Shack. If power to the dock is lost, usually a trip of the GFCI breaker, the relay opens and sets off the power detection UT-3000. The only down side is the batteries in the UI-3000's have to be replaced about once a year. I normally do that in late fall so they are fresh during the winter. The WPA-3000 contains the sensor and WR-3000 receiver. Each can be purchased separately. There is also a passive motion sensor WMT-3000. All the xxx-3000 devices work together on the same RF frequency. I mounted the transmitters on the outside of a storage shed. They are water proof. Have been using them for many years with no problems being mounted outside. The box has a rubber seal on the hinged cover. I might have looked into a good 9v supply to replace the batteries in the transmitters if I lived where you do. Would depend on how well a 9v battery holds up in very low temps. I don't know if the I/O Linc could interface with the Dakota device directly. Need the model number of the Dakota device. The I/O Linc would have to be mounted in a weather proof box of some kind. A magnetic switch on the gate itself is a good choice because they are inherently water proof. Depending on how far the shed is from the gate itself a run of direct burial irrigation cable could be run from the gate switch to the shed with the I/O Linc in the shed. Gets the I/O Linc out of the weather and closer to the house. I used a flat blade shovel to open a small slot to bury the cable from the Dakota Alert buried sensor to the transmitter location.

Sorry to hear the Dakota Alert has been a problem. The only issue I had was the magnetic sensor at the mailbox was too sensitive. Picked up passing cars in addition to the mail carrier. Finally moved the sensor further away from the mailbox so only a vehicle passing very near the mailbox would trip it. Still get a false trip from very large trucks but they don't enter the subdivision very often and I ignore the trip when not around mail delivery time. North Carolina weather is much less harsh than a winter I spent in Rochester Minnesota decades ago. The 9v batteries would likely be a problem in an environment that drops to 30 below. Not sure what Dakota Alert devices you are using. All of mine, the magnetic sensors, the universal remotes at the dock for high water level and power loss detection all transmit back to the wr3000 receiver. The only serial PLM that Smarthome now sells is the 2413S Dual Band PLM. Command wise it is a functional equivalent to the 2412S. The 2413 has a slightly faster processor and supports approx 1000 links rather than the 2000 links supported by the 2412 PLM. The 2413 does not provide 12v power as the 2412 did so a small external power supply is needed for the ISY. Most of the Insteon devices now shipping including KeypadLinc Dimmers are I2CS devices which require the Official 3.2.6 or Beta 3.3.3. Theoretically the new KPLs should replace existing KPLs with the same number of buttons. I ran into a problem two weeks ago when replacing a KPL. Most of my devices in the main house are early I1 Insteon ICON devices and old I1 KPLs. The old devices do not understand or repeat the extended I2/I2CS commands. This created a problem building the link database in the new KPL because the extended commands did not reach the new KPL which is at the end of a long circuit with many I1 ICON and old KPLs on it. Finally had to add a Dual Band SwitchLinc along side the new KPL Dimmer to get I2 communications to work. This type problem would not exist for most users. I happen to start with Insteon almost from the day the products were announced and I have been lucky to have had very reliable devices for all that time. Most users have more modern versions which do understand and repeat I2 commands. As far as the I/O Linc is concerned, it is not a Dual Band device so the AP in the shed would only be useful to perhaps get the Insteon signal over RF to the house if the power line distance was an issue. If the Access Point helps only one is needed. I would try the I/O Linc at the gate without the additional AP to start with. If it turns out to be unreliable due to power line length then try adding the AP in the shed

Upgrading to the latest firmware, either Official 3.2.6 or Beta 3.3.3, along with an ISY 994 and 2413S Dual Band PLM is the path. The 2413 PLM does not provide power so an external power supply is required to run the 994.

That distance may work for a wired Insteon device. I have a good 300 wire feet to my detached garage and have good Insteon control of lights and garage doors at that distance. I'm thinking changing the power to unswitched (or at least leave it On) and use some Insteon device at the gate to switch On/Off rather than at the house. That might also allow an I/O Linc to function to signal gate Open/Closed. The Dakota Alert devices have an advertized range of 600' for the wireless RF devices. Not sure about the total distance but 400' would seem to be well within range. The Dakota Alert line has a WR3000 receiver that works very well. I have used their buried magnetic wireless sensors around my mailbox and at the head of the driveway for vehicle and mail announcements. Has worked well for many years. The Dakota Alert receiver distinguishes four unique channels with corresponding relays which are connected to the four opto-isolated Inputs on an EZIO6I to get Insteon messages for the four different Dakota Alert channels. The buried magnetic sensors are battery powered with 100' of cable so the transmitter could be positioned closer to the house. Dakota Alert is expensive but I have found it rock solid.

Are there a large number of devices and Scenes involved? If so run Show PLM Links Table followed by a Count. The Show/Count sequence should be run 3-4 times to be sure the Count is consistent. Any inbound Insteon traffic reaching the PLM will produce a false PLM link record count (too high or too low). What is the Count? This test will make sure the capacity of the PLM has not been exceeded.

When a KeypadLinc is added to the ISY each button is automatically defined as a Controller with the PLM as a Responder. The E201...., E202....., E203....., etc link records in the KeypadLinc are Controller link records pointing to the PLM 1C.FB.73. The PLM will have an A201...., A202...., A203.... etc Responder link records. The only thing I can suggest at this point is to Factory Reset the KeypadLinc, followed by a Restore Device to recreate the link database erased by the Factory Reset.

No to both at this time. With many Programs the current On Level could be tested for a specific On Level value (If Status 'xxxxx' is 85%) and set a variable accordingly. With ranges (5%-10% or 10%-20%) the number of Programs could be reduced if absolute values were not necessary.

Install a backup from the 99i onto the 994i.

That leaves a problem with the link records in the PLM or a comm problem. Since the KPL can be reached with Direct commands for Query, Backlight LED level, etc that makes the PLM link table the probable cause. Next thing to try is a Restore Modem (PLM) which will compress out all duplicates and rebuild the PLM link table. As a sanity check verify 1C.FB.73 is the PLM Insteon address.

The Program is triggered when the Opened node changes state, at 5:35 PM (From Time) and at 6:35 PM (To Time). When the combined If conditions are True the Then clause runs. The TriggerLinc Opened node must be On for the Program to run the Then clause at 5:35. Either code the same Set Scene Off two or three times or add a Repeat 2 or 3 before the Set Scene Off

The Programs | Summary will show when the Program is running. After the fact the ISY Log (Tools | Log) will show activity. I set the Program to run a 7:15 PM with the first few Zones running for 1 minute each as a test of Log activity. EZFlora On 255 Mon 2012/10/22 07:15:00 PM Program Log EZFlora Status 100% Mon 2012/10/22 07:15:00 PM System Log EZFlora / EZFlora - 2 On 255 Mon 2012/10/22 07:16:00 PM Program Log EZFlora Status 0% Mon 2012/10/22 07:16:00 PM System Log EZFlora / EZFlora - 2 Status 100% Mon 2012/10/22 07:16:00 PM System Log EZFlora / EZFlora - 3 On 255 Mon 2012/10/22 07:17:00 PM Program Log EZFlora / EZFlora - 2 Status 0% Mon 2012/10/22 07:17:01 PM System Log EZFlora / EZFlora - 3 Status 100% Mon 2012/10/22 07:17:01 PM System Log EZFlora / EZFlora - 4 On 255 Mon 2012/10/22 07:18:00 PM Program Log EZFlora / EZFlora - 3 Status 0% Mon 2012/10/22 07:18:00 PM System Log EZFlora / EZFlora - 4 Status 100% Mon 2012/10/22 07:18:00 PM System Log EZFlora / EZFlora - 5 On 255 Mon 2012/10/22 07:19:00 PM Program Log EZFlora / EZFlora - 4 Status 0% Mon 2012/10/22 07:19:00 PM System Log EZFlora / EZFlora - 5 Status 100% Mon 2012/10/22 07:19:00 PM System Log

Remove the thermostat from the ISY. Factory Reset, set mode to Off Use New INSTEON Device, enter Insteon Address, Name of choice, Device Type at default Auto Detect. If on battery put the thermostat into linking mode. Once added it may take a few minutes for all the data to fill in. If on an external power supply a Query can be issued.

When a single device does not show status changes there is a link record problem either in the device or in the PLM (assuming no comm problems). Suggest doing a Show Device Links Table followed by a Compare when display is complete. What is the result of the Compare? What is the ISY firmware level?

It is possible for a Scene and Program initiated Insteon activity to trip over each other. I would not worry about that for now. Use Scenes where you want them. I prefer Scenes when they make sense for the reasons you indicated. There is no delay with a Scene and if the ISY or network is down Scenes tend to work. There are situations where Programs make sense and they should be used in those cases. There is a very slight delay to trigger a Program and have it do the same activity a Scene would do directly but there are cases where that is useful. Code the ISY Programs the way you want them. If something does not work as expected post the situation. There are lots of really helpful folks on this forum that are more than willing to help.

Unforturnately there are no "right" settings. Depends on which magnetic switch is used (NO or NC). Is the Sensor preferred On or Off when the door is closed? How is the I/O Linc Relay being controlled, Scene versus Direct command from Program. Each of these affects what I/O Linc options are appropriate. It sounds like the wrong Momentary mode is being used as each Momentary mode responds differently to Scene On and Off commands but that is only a guess without knowing the variables above. The I/O Linc User Guide covers how Scene commands work with the three Momentary modes. Descrbe how the I/O Linc is connected, using NO or NC, is Green LED On or Off when door is closed? How should the door state be presented in the house if at all. How should the door movement be controlled; one KPL button that both opens and closes the door. Separate KPL buttons for Open/Close.

The Motion Sensor is an I2CS device which 3.2.6 supports. The new designation has to do with it supporting different RF frequencies for different countries. The actual device type cat/subcat is the same as the older motion sensor even though the Item number is new.

The Java cache should be cleared before using the new ISY. The URL I posted is for the latest Beta. The ISY will have the latest Official release (probably 3.2.6) which will be a few images before the 3.3.3 Beta.

The configuration information is stored in the ISY so nothing can be configured until the ISY is available. The following URL will pull the Admin Console application from the UDI web site but since it cannot locate an ISY UUID not sure what will actually display. http://www.universal-devices.com/99i/3.3.3/admin.jnlp

I was thinking about a Factory reset of the KPL (KPL User Guide covers the procedure) followed by a Restore Device. Right click the KeypadLinc Primary node, select Restore Device. That will rebuild the link database that was erased by the Factory reset of KPL. I am continuing to test as well but I don't know what might be the key. Let me know the results if you do decide to do a Factory reset of the KPL. There is no issue beyond needing to Restore Device to rebuild the link database. What type of load is connected to the KPL?

You may have a defective KPL or something else is in play that has not been recognized yet. When I issue a Fade Down (without a Fade Stop), using both a Scene with Main A as a Controller or with a Direct command Fade Down to Main A, the load fades down, the Main A button LED turns Off, and when I press Main A the load turns On to 100% On. It is a KeypadLinc 8 button Dimmer at v.40 with hardware revision 5.9. EDIT: forgot to add this variation. Adding a Wait 5 seconds followed by a Fade Stop does not change the result. Main A LED goes out, pressing Main A turns load on to 100%

If the I/O Linc Sensor state Green LED does not come on the issue is the magnetic sensor, wiring to magnetic sensor or the I/O Linc is defective (least of likely possibilities). Try shorting the wires from the magnetic switch near the I/O Linc terminal strip. If the Green LED comes on it is an issue with the magnetic switch or wiring to the switch. If the Green LED does not come on try a new piece of jumper wire from the I/O Linc GND to the Sensor input.

Try a Restore Device of the SwitchLinc that is physically controlling the load.

ISY Programs reside in the ISY only. They are not in the PLM and not in any device.

I doubt the KPL is defective. I do have a KPL dimmer at v40. I'll see if I can recreate. It sounds like the Fade Stop Scene command did not make it to the KPL. No explanation why that Scene command would not arrive unless some other device activity generated some interference. I'll post back the results of my testing with a v40 KPL

The commands are being executed according to the event trace. That means it is a KeypadLinc issue. Not much you can do about that unless it is a timing issue. What is the KPL firmware? The KPL firmware level is displayed below the device name in the right pane when the primary node is selected in the My Lighting tree. I test on that level if I have one. I tested this on a v29 KPL which is pretty old. It does not turn the load on to 100% when the Fade Stop is not issued. Works okay when I issue the Fade Stop 15 seconds after the Fade Down.