LeeG

A 2413 PLM is Dual Band. A 2412 PLM is powerline only, not Dual Band. The 2412 is no longer sold by Smarthome but you could have a 2412 PLM if using Insteon for years. Before moving ISY and PLM consider adding Range Extenders (Access Points) to the 2nd and third floors.

What is "scene"? What type of device? Perhaps that should be Set Scene "scene" On still need to know what is in "scene" and what actual commands issued. Best to Copy to Clipboard the Program and paste into post as well as cover "scene" context

Turning an individual device On/Off does not affect the Scene or other devices in the Scene. That is an Insteon design point from the beginning of Insteon. Need to turn the Scene On/Off to have all the Scene devices react.

Run Tools | Diagnostics | Event Viewer at LEVEL 3. From the Admin Console turn a specific device On then Off several times. Watch the Hops Left=x count to see if it is at 0 or varies from command. Dual Band devices (if all the existing SwitchLincs are Dual Band) may not have the RF coverage being inside a box, particularly if metal boxes. Repeat the test on different devices around the house. Post the trace if needed. An ISY Scene invoked from the PLM (by a Program, from a remote app, Admin Console) does not have multiple retries so these tend to be where Insteon network issues show first.

The attempt to add an 8 Scene RemoteLinc 2 failed to receive an Extended message showing size/location of the device link database. The Red message below is missing from your trace. Sun 11/09/2014 07:45:19 AM : [iNST-TX-I2CS] 02 62 29 DB A2 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Sun 11/09/2014 07:45:19 AM : [iNST-ACK ] 02 62 29.DB.A2 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Sun 11/09/2014 07:45:20 AM : [iNST-SRX ] 02 50 29.DB.A2 0F.D6.5E 27 2F 00 (00) Sun 11/09/2014 07:45:20 AM : [std-Direct Ack] 29.DB.A2-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 THIS MESSAGE WAS NOT RECEIVED. Sun 11/09/2014 07:45:20 AM : [iNST-ERX ] 02 51 29 DB A2 0F D6 5E 11 2F 00 00 01 0F FF 00 AA 00 0F D6 5E FE 1C 01 BA Sun 11/09/2014 07:45:20 AM : [Ext-Direct ] 29.DB.A2-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sun 11/09/2014 07:45:20 AM : [29 DB A2 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8) Was the V.9C PLM obtained from Smarthome recently?

Run Tools | Diagnostics | Event Viewer at LEVEL 3. Follow steps in post 2, attempt to add Motion Sensor. Post the event trace. Be sure event trace is set for LEVEL 3. Below is from the previous trace which was not at LEVEL 3. Note the 25 second gap in trace where the LEVEL 3 information should be. Fri 10/31/2014 11:25:19 AM : [27 17 6 ] Added to list of devices to link to ISY Fri 10/31/2014 11:25:44 AM : [27 17 6 0 ] Failed to add device, reason 9 Click Help | About What is displayed for Firmware? What is displayed for UI?

That message means the PLM cannot talk to the 2477D. With the 2477D being the only Insteon device the 2 120 v legs are likely not coupled so the PLM could be on one leg and the 2477D on the other.

Looking at the environment from the other perspective ... 4.0.5 has been working fine so the issue is not there Insteon network is fine because other RF devices and powerline devices work That leaves 2 RemoteLincs that are not working, or they are fine If both RemoteLincs are fine then there is no problem. 4.0.5 is good, Insteon network is good, RemoteLincs are good. What is left if everything has been eliminated by process of elimination. Good luck.

Same issue, a command (Set MSB for Write Updates) is sent three times and the device fails to answer any of the three requests. Perhaps something is blocking RF such as a thermostat stuck On. That has been known to happen. Perhaps 4.0.5 has an intermittent issue. Yes, 4.0.5 is the last Official release. There have been many ZWave updates in the last 18 months that have slowed moving something into Official status. I'll step aside and let someone else play with 4.0.5.

Originally 0A.35.31 would not add to the ISY. The last trace shows the device added but will not handle Write Updates. Was the RemoteLinc put into linking mode before clicking Write Updates? The ISY and UI should be updated to 4.2.18.

Tap the Set button on PLM 4 times and check other Dual Band devices to confirm RF messages are being received.

For each pair of 02 62 ..... outbound messages there should have been an 02 50 ...... response from the RemoteLinc. Was each RemoteLinc put into linking mode before starting New INSTEON Device and taken out of linking mode before starting with the next RemoteLinc? What ISY firmware and UI (Help | About) is being used? The new PLM is a 2413? Just realized the second device must have added to the ISY as a Write Update is being tried.

That message indicates NO communication with the RemoteLinc. RemoteLinc did not respond to the first command sent which asks for the Insteon Engine. All devices should respond to this command and it is issued three times before the ISY stops. Move the RemoteLinc near the new PLM or other Dual Band device.

The ToggleLinc has the same temp operating range. It could have more issues with sub freezing temps because of mechanical switch. The 2992-222 Range Extender can be used alone to interface with the Hidden Door Sensor. The electrical system needs to be coupled which is an Insteon requirement independent of the Hidden Door Sensor. I would try the ToggleLinc. It will be outside its spec'ed temp range but SmartLabs devices work pretty well outside of those specs. If it fails try a Dual Band SwitchLinc which would eliminate need for Range Extended. SwitchLinc also has 32 degree limit.

When a State Variable changes value the Program(s) that have that variable in the If section will trigger. A Program that is currently executing statements will trigger when the current clause finishes unless the clause is in a Wait or Repeat or runs into a Wait or Repeat. The program will trigger immediately if in a Wait or Repeat. This trigger can be stopped by having the Program Disabled. Being Disabled does not stop the Program from being invoked by a Run Program but does stop events such as variables changing values from triggering the Program. Also using an Integer variable in the If prevents an event trigger.

A Program that uses Then Run Program 'A' Run Program 'B' Run program 'C' ...... will not know the order Programs A,B,C actually execute. Having the Programs Disabled only means an Event will not trigger the Programs. The Run Actions happen quickly, not waiting for A to complete before the Run 'B' executes, and so on. Basically A,B,C and the sample Program logically Run at the same time. Of course only one Program is physically executing statements at a time but how far A runs before B is given a time slice to execute is under ISY control. A simple way to have each Program run in sequence would be Program 1 Then .... .... .... Run Program2 Else Program 2 Then .... .... .... Run Program3 Else Program 3 Then .... .... .... Run Program4 Else If the subroutines are tracking different thermostats, for example, they could be Event driven, setting Variables with current conditions with a single Program using the Variable values to develop a conclusion/action. There may well be a better way to create Subroutine like sequences. I'll have to give that some thought as I have not tried to create a Subroutine environment. Lots of good folks participate here so if there is simple or best practices way to create a Subroutine structure I'm sure they will jump in.

Programs run independently. The order of invocation does not matter. Programs do not function as subroutines. Program one can Run Program two as the last Action. Program two can Run Program three as the last action. EDIT: from the ISY Wiki In all cases, the order in which the programs run is determined by ISY's internal algorithms, and is not user predictable; specifically, schedules do not necessarily run in chronological order. Link to Wiki segment that covers this http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Scope,_Precedence_and_Execution_Order

Under Action, select Repeat from pulldown.

Prior to SmartLabs introducing the I2CS variant of the Insteon protocol Insteon devices used a retry count of 3. This number was embedded in the device firmware and could not be adjusted. With I2CS devices there is control over some of the retry activity. Right click on device node, select Advanced | PLM Communication to access a retry count (available only on I2CS devices).

The Scene name Responder values are not important since the Scene name is not being used in a Program. The exception would be controlling the Scene name from an application like Mobilinc but that has not been mentioned. Scene "A" ......Cans.A Controller, the Responder values are fine as posted in the image. Buttons .....Cans.B, .....Cans.C, and .....Cans.D set to 0% On Level results in buttons B,C,D turning Off when button A is turned On. Please run Tools | Diagnostics | Event Viewer at LEVEL 3. Select Write Updates for one of the pending nodes and paste the event trace into a post. Understand your belief there "is a bug" which the event trace will show if one exists.

"why am I getting comms issues only when I configure the system this way" communications problems setting up KPL configuration simply means the more updates needed the more likely the probability of seeing errors. do not attach more then comm problems exist. Run Tools | Diagnostics | Event Viewer at LEVEL 3. This will show how well comm to the KPL is working. Usually there is marginal comm all the time. "what am I supposed to set the levels of the buttons at the scene level?" That depends on what you are using the Scenes for. Explain what you are doing with the Scene name in terms of Program usage. "what should (if anything) I do about toggle mode?" Nothing.

Are both KPLs still in the device list? Was the new KPL primary node selected with a right click?

The ON/OFF buttons work as a single function. ON turns the load On, OFF turns the load Off. The 5 button description refers to the fact that 5 ISY nodes are defined rather than 6. The ON/OFF buttons, although physically different buttons, control the single primary node, the one node that represents the load. In Insteon each Controller has a unique set of Responder On Levels. When testing the Scenes through the ISY the PLM is the Controller. When pressing a button on the KPL that button is the Controller for which Insteon has unique Responder On Levels. Click the Red button A node below the Scene name. Set the Responder On Levels for that button. Click on the next Red B button below the Scene name and set the Responder On Levels for that button, and so on. That part of Insteon works well as the KPLs that control my FanLinc Fan speed are set up to have only one KPL Secondary button (A,B,C, or D) On at a time. Hopefully the Buttons Grouping button was not used as the warning messages warned against.

Now that coupling is functional you can try Tools | Diagnostics | Event Viewer at LEVEL 3. Use New INSTEON Device, enter the Insteon address, Name of choice, Auto Discover, with Remove existing links. Post the event trace. The previous event trace had no device activity at all so it was not helpful.

The base 994i is the same. Add the ZWave module to have Insteon and ZWave capability.