LeeG

I'm not sure this is an I/O Linc issue. If this is the same problem the Insteon network presents a duplicate message after the next Query is done to the I/O Linc. The duplicate message looks like a response to the last Query which changes the I/O Linc Sensor status. I don't think the duplicate message is physically sent by the I/O Linc which makes it hard for any change to the I/O Linc itself to resolve this.

All battery powered devices must be manually put into linking mode with their Set button before using New INSTEON Device to add them to the ISY. Be sure it is in range of a Dual Band device.

Anytime. Meant to put this in the previous post, even the buttons on the 4 Scene model show the right side buttons are marked with an up arrow for On and the left side buttons are marked with a down arrow for Off. A little hard to see but the sales page for the 4 Scene shows the same buttons.

The native 4 Scene in default 4 Scene mode works the same as the 8 Scene in 4 Scene mode. Went through the current sales pages for both the 4 Scene and 8 Scene devices. Everything indicates your device is not working correctly.

Both of my 8 Scene devices show as an 8 Scene device even though the mode was changed. I'm charging my 4 Scene and expect it to show as 4 Scene regardless of mode selected. Now your button B toggles Scene 1; D,F,H do nothing; does C,E,G toggle Scene 2,3,4? Sounds like either the battery is low or the device is defective.

The hardware level of the first 8 Scene to 4 Scene is v1.1. Just did the same test on a second 8 Scene to 4 Scene, hardware v1.1C, firmware v.36. Same results as first, right side always sends On, left side always sends Off. Perhaps a factory reset will help.

I converted an 8 Scene to a 4 Scene to run the previous tests. Right side press sends an On command each time it is pressed. Left side button sends an Off command each time it is pressed. What level ISY Admin Console is being used?

hart2hart I don't think the User Guide says Scenes must be used. From Smarthome perspective all of their products communicate with Scenes. None of the Insteon devices can send Direct commands so I assume they do not see the need to explain what happens that way. Really same with other devices as well. The Keypadlinc Secondary buttons cannot be managed with Direct commands but this is not discussed in the Keypadlinc User Guide.

It is not the ISY. Here is event trace of X10 being received from X10 controller. Sat 06/28/2014 01:19:52 PM : [X10-RX ] 02 52 56 00 Sat 06/28/2014 01:19:52 PM : [ X10] G1 Sat 06/28/2014 01:19:54 PM : [X10-RX ] 02 52 53 80 Sat 06/28/2014 01:19:54 PM : [ X10] G1/Off (11) Sat 06/28/2014 01:19:54 PM : [X10-RX ] 02 52 56 00 Sat 06/28/2014 01:19:54 PM : [ X10] G1 Sat 06/28/2014 01:19:56 PM : [ Time] 13:20:00 1(0) Sat 06/28/2014 01:19:59 PM : [X10-RX ] 02 52 56 00 Sat 06/28/2014 01:19:59 PM : [ X10] G1 Sat 06/28/2014 01:20:01 PM : [X10-RX ] 02 52 53 80 Sat 06/28/2014 01:20:01 PM : [ X10] G1/Off (11) Sat 06/28/2014 01:20:01 PM : [X10-RX ] 02 52 56 00 Sat 06/28/2014 01:20:01 PM : [ X10] G1 Try plugging the X10 controller into the same circuit the PLM is on.

The I/O Linc Relay always turns On with a Direct On regardless of Momentary mode. The I/O Linc is designed on the assumption it is being controlled from another Insteon device which requires the use of a Scene. Only HA products going through a PLM can send Direct commands.

Yes, blinks Green sending On, Red sending Off

A Scene is the best choice. All the Responders react at once and with a single Insteon command. A Program can issue the Scene On/Off but best to have a Controller initiate the Scene directly. A Program can issue 15 Direct commands but that is very slow in comparison. The only down side is there is no automatic retry when using a Scene. The Insteon network has to be in good working order. The Insteon network should be in good working order whether a Scene is used or not.

"Can I change it to a 4 scene toggle?" Yes. The ISY can set a mini remote to the three possible choices. "I would like the A button to turn a light on and only blink green and the B button to turn it off and only blink red." The right side button sends an On, the left side button sends an Off. No other choice.

Use "if Control" rather than "If Status" If Control "TV" is switched On AND status Dining Room Light = on Then: set status Dining Room Light = off set status Den Lamp = on $DR = 1

Currently only one manufacturer of PLM, SmartLabs. Smartenit carries an EZIComm which is a SmartLabs PLM. A Serial version is required for the ISY. There has been some discussion that UDI will develop their own PLM but that is months away.

If the events are related to an I/O Linc Sensor it sounds like the Trigger Reverse option is being used. Although that option reverses the commands sent as the Sensor turns On and Off it does not reverse the Query results. The 3AM query will change the state of the Sensor when Trigger Reverse is used. The best solution is change the magnetic switch to the NO/NC version so the NO magnetic switch can be used and Trigger Reverse turned Off.

Some KPL history. Originally KPLs were of one cat/subcat (device type) regardless of which mode the KPL was configured to operate. Later SmartLabs started manufacturing a 6 button KPL and an 8 button KPL, assigning a unique cat/subcat (device type) to each. The 8 button KPL identifies its cat/subcat (device type) as an 8 button KPL regardless of which mode it is operating in. The ISY displays what the device indicates is its device type, 8 button KPL in this case. Does not matter that it was configured to operate in 6 button mode. It was manufactured as an 8 button KPL and that is what the device indicates is its device type. Apparently MobiLinc uses the device type and adds 8 buttons even though the KPL indicates it is operating in 6 button mode which is what the ISY uses to determine the number of nodes to define. This looks like something MobiLinc will have to react to as it has the wrong number of nodes based on how the 8 button KPL is configured to operate, as 6 buttons.

Try using an incandescent in place of the CFL. Many CFLs give Insteon dimmers a problem.

What type of load, CFL, LED, etc.

What type of load is being controlled?

"Is this an issue with the 2477D firmware (these are brand new v.41 switches), or with ISY?" This is the design of the 2477D. The fact that the load controlling device does something special with the second On tap is limited to that particular switch. The Insteon Scene Responder(s) react to the Responder link record in each Responder device. One approach is to double tap (Fast On) the switch which will turn the load on full and send Fast On to the Responders of the Scene. If that is not acceptable then working around the switch design with an ISY program is another approach.

That is exactly right, devices talk to the PLM, never to the ISY directly.

If Momentary B is used and a Scene with Relay as Responder turned On/Off both the Scene On and Scene Off would move the door. Perhaps not the graphic desired but the function would work.

Switching PLMs requires every device link record (1 to many per device) containing the PLM address be changed. Not something to done in a few minutes. The UDI Wiki describes the process. Not complex but it takes time to change many link records over 100 Insteon devices. Plus the battery powered devices have to be done one at a time.

Each Insteon device has 1 to many link records that have the PLM Insteon address. Changing PLMs requires all devices be updated with the new PLM address. The Wiki describes the process of changing to a new PLM.