LeeG

The 4 tap test will not be reflected in a device that is not receiving the test RF message. Are the two devices at some distance to each other and/or mounted in a metal box? Try the sitting up the SwitchLinc again. Hard to understand why that feature cannot be set. Are you trying to set "resume brightness" or set "fixed brightness". I though you wanted "fixed brightness" but the last post indicates can't get rid of "fixed brightness".

Mine follows the User Guide although it does take more then a simple tap of the Set button. What is the SwitchLinc hardware level? It is printed on the label attached to the frame of the switch. mine is v6.5.

The SwitchLinc User Guide. Not every device feature can be set pro-grammatically.

Thanks. That means the Local On Level mode described on page 10 determines how the SwitchLinc responds when the On paddle is pressed. It either goes to where the device was when last turned Off or to the preset local On Level.

Teken Battery devices go to sleep normally. It is necessary to issue special commands to keep a battery powered device from sleeping so that link records and configuration data can be written to the device. The command to keep the battery device from going to sleep is very time constrained, not working if the small time slot is missed. HL function was withdrawn for a time because HL was not sending the "don't sleep" command soon enough. Even now HL can miss that time slot and has to put the updates on a pending queue until another message is received from the battery device. So far UDI has not ventured into that area as it can be messy.

If familiar with the Event Trace you can use Start Linking which puts the PLM into linking mode. Then press the Set button on the Motion Sensor for about 5 seconds so that it generates Broadcast message which has the MS device address. The ISY will not establish the MS this way but the event trace will have MS device address.

Insteon has unique Responder On Level and Ramp Rate values for each Controller PLM is Controller when the Scene name is used. Each Red node below Scene name is a Controller All of these Controllers have unique and independent On Level and Ramp Rate values for the Responders. Also take a look at page 10 of the User Guide. The SwitchLinc Local On Level has two modes of operation when the local paddle is used. One mode goes to the defined Local On Level when going from Off to On, the other mode goes to the last On Level before turning the SwitchLinc Off (known as Resume Bright). The User Guide describes how to establish either mode. Need some information about whether the results posted are when the paddle is used or when responding to a Controller and if so which Controller.

Based on the Query response the garage door should be Open as the Sensor node is On for both queries. Comm with the I/O Linc is at the very edge of working. The Hops Left=0 means any interference or slight drop in comm quality could lose a state change. Fri 10/24/2014 12:30:21 PM : [iNST-TX-I1 ] 02 62 2B F8 BB 0F 19 01 Fri 10/24/2014 12:30:21 PM : [iNST-ACK ] 02 62 2B.F8.BB 0F 19 01 06 LTSREQ (01) Fri 10/24/2014 12:30:22 PM : [iNST-SRX ] 02 50 2B.F8.BB 2C.07.70 23 00 01 (01) Fri 10/24/2014 12:30:22 PM : [std-Direct Ack] 2B.F8.BB-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 10/24/2014 12:30:22 PM : [iNST-TX-I1 ] 02 62 2B F8 BB 0F 19 00 Fri 10/24/2014 12:30:22 PM : [iNST-ACK ] 02 62 2B.F8.BB 0F 19 00 06 LTSREQ (LIGHT) Fri 10/24/2014 12:30:22 PM : [iNST-SRX ] 02 50 2B.F8.BB 2C.07.70 27 00 00 (00) Fri 10/24/2014 12:30:22 PM : [std-Direct Ack] 2B.F8.BB-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 10/24/2014 12:30:22 PM : [iNST-TX-I1 ] 02 62 2B F8 BB 0F 19 01 Fri 10/24/2014 12:30:22 PM : [iNST-ACK ] 02 62 2B.F8.BB 0F 19 01 06 LTSREQ (01) Fri 10/24/2014 12:30:23 PM : [iNST-SRX ] 02 50 2B.F8.BB 2C.07.70 23 00 01 (01) Fri 10/24/2014 12:30:23 PM : [std-Direct Ack] 2B.F8.BB-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 10/24/2014 12:30:23 PM : [iNST-TX-I1 ] 02 62 2B F8 BB 0F 19 00 Fri 10/24/2014 12:30:23 PM : [iNST-ACK ] 02 62 2B.F8.BB 0F 19 00 06 LTSREQ (LIGHT) Fri 10/24/2014 12:30:23 PM : [iNST-SRX ] 02 50 2B.F8.BB 2C.07.70 23 00 00 (00) Fri 10/24/2014 12:30:23 PM : [std-Direct Ack] 2B.F8.BB-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Need an Event Viewer trace at LEVEL 3 to be sure. Does not have to be the 3AM Query. Can be from a Query (done twice quickly) executed during the day. I have seen multiple query responses received by the PLM from an I/O Linc Query. A Query of either I/O Linc node results in both nodes (Sensor and Relay) being queried. The 3AM Query is issued twice (once for each node) for an I/O Linc so 4 physical Query commands are issued. If the I/O Linc sends (or the Insteon network produces) a duplicate query response the duplicate message can be applied against the wrong Query command making it appear that the Sensor has changed state when it has not. Also need to know if the Sensor is normally On or Off when door is closed. The Green LED next to the I/O Linc connections indicates the Sensor status (Green LED On when Sensor On). The duplicate message is normally intermittent.

Go this this link and scroll down to Accessories https://www.universal-devices.com/sales/

Check the ISY Log to see if the ISY did reboot.

You have the same problem sanders2222 had back in April 2013, a bad internet cable that would not lock in connector? Use a new cable. I suspect that is not your issue. Are there LEDs besides the Power LED On the face of the ISY On?

There have been issues with the ISY rebooting on its own. If this happens the battery devices will not have status until each device is operated. Should not be necessary to do anything but operate each device if this is the cause. Suggest moving to 4.2.17 which was released a few days ago.

Xathros is right on as usual. 4.0.5 does not know about a hidden Door Sensor. After installing 4.2.16 be sure to delete the Java information including Applications. When all updates complete run Help | About again to confirm both indicate 4.2.16.

Click Help | About, what is displayed for Firmware, what is displayed for UI? Communication with Hidden Door Sensor is fine.

Both the current 2477D Dimmer and 2477S Relay are Dual Band. They will have to be installed on opposite 120v legs to perform coupling.

Look at the information on the back of a SwitchLinc. It will normally say Dual Band if the device is Dual Band. Same with the LampLinc, unplug the LampLinc and look at the back plate for Dual Band.

The Scene Test problem may be related to an old problem with 3.3.10. It marked as failed even devices that worked. After the load is disconnected a positive result will be the devices staying in sync, all showing the correct On or Off status. The devices should cycle On and Off without any load connected.

oberkc reflects what I was suggesting. With your followup question as to which switch to disconnect, there is SwitchLinc1, SwitchLinc2 and a KPL button. Which devices are physically controlling a load (Red wire not capped)?

Having multiple Dual Band devices does not insure that there is good coupling. Many of the SwitchLincs can be on the same phase. Also the ones that are on opposite phases must be able to talk reliably with a device on the other phase. Device A may be able to talk to device B and device C but device B and device C not be able to talk reliably to each other. Disconnect the physical load and see if the Neon lights are causing a problem.

The 99i has the same Scene Test capability as the 994i. This tests communication between the PLM and the devices in the Scene. Those results can be different than communicating device A to device B. If there is correct coupling then some form of interference is probable.

Insteon requires some form is coupling between the 2 120v legs. This is required so that Insteon messages produced on one 120v leg are reproduced on the other 120v leg. This is commonly done with a pair of Access Points (now called Range Extenders), each plugged into a different 120v leg, so that messages on one 120v leg are sent via RF signal to the other 120v leg. It sounds like the devices (SwitchLinc/KeypadLinc) are on opposite 120v legs so that Insteon messages are not reliable between the devices. Could also be some electrical noise interfering with communication between the devices.

That means poor Insteon comm between SwitchLinc2 and the KeypadLinc. What is being used to couple two 120v legs?

One Scene with the three devices as Controllers. The KeypadLinc being on a different circuit is fine. Each of the three devices can be on different circuits. Of course proper 120v phase coupling is required. SceneX SwitchLinc1 - Controller SwitchLinc2 - Controller KeypadLinc button - Controller I reread the initial post. Is the Keypadlinc Dual band? The 99i 3.3.10 does not support Dual Band KeypadLincs.

mrbudin Use this link to open a ticket for support from UDI http://www.universal-devices.com/contact-support