LeeG

iowaj The new switch is added with "Remove existing links" option. The options apply to the new switch not the old switch. With rare exceptions remove existing links is the option that should be used when adding a device. Lee

iowaj The two switches that are not being used in Programs, are they currently Insteon devices? If so they are probably defined to the ISY and should be "Replace"d. Otherwise ISY will have a definition for the old device that cannot be addressed which will cause false comm errors. If the old Insteon switches were never defined then the new switches can just be added and no Replace operation done. If the ISY is aware of the master/slave relationship of the old switch(s) that relationship will be maintained with the Replace operation. The master/slave relationship is defined in an ISY Scene. ISY Scenes are listed in the My Lighting Tree below the device definitions. Lee

iowaj To clarify, Replace requires the same general type of device, a dimmer replacing a dimmer. An ICON dimmer can be replaced with a SwitchLinc dimmer and vice versa. What cannot be done is Replace an ICON dimmer with a SwitchLinc relay device or vice versa. Lee

iowaj It is that simple. Add the new switch to the ISY using New INSTEON Device. Specify a Name that does not already exist. It will eventually be deleted. Right click on old switch node and select Replace xxxxx with ..... A popup will display listing compatible replacement devices. Select the new switch Name and the ISY will do the rest. I suggest doing one switch at a time. After the process is complete the new device will be deleted and all references in Programs and Scenes will be updated with the new device address. Note that the old device Insteon address is not used during the Replace operation so the old device can be physically replaced with the new switch before the Replace is executed. Lee

You can have as many time driven Programs controlling X10 and/or Insteon as you want.

Apostolakisl Although some of the symptoms have been categorized as acceptable such as the ICON switch not responding and the comm error messages, it may be useful to add them to the mix when evaluating the SwitchLinc to/from PLM symptoms. These may be separate independent problems but they may be related to something more common. Analyzing the entire picture may reveal something that would not be apparent when evaluating a single problem. I normally pick one symptom and track it down as too many variables can confuse the issue. This may be the exception where looking at the overall pattern may be helpful. There is no track of which devices were in the repeat (hop) path to get from source to destination. Insteon addresses are not changed along the way so even if monitoring the powerline at a low level that information would not be available. Lee

Device to device control is done with Standard messages. Passive coupling must be working as much device configuration is now done with Extended messages. I am amazed your system works at all!

Thanks. The terminology does not matter. The devices that have the black external antenna operate on a different RF frequency than any of the more recent RF devices. They also do not couple Insteon Extended messages. Devices such as Motion Sensors, TriggerLincs, Venstar tstat adaptors, Access Points, the many new Dual Band devices, the RemoteLinc and RemoteLinc2, none of these devices operate on the RF frequency used by the RF coupler with the black antenna. Removing the RF couplers with the black external antenna would only affect RF coupling of Insteon Standard messages on the powerline.

Do they have a black external antenna? I assumed the units removed were pluggable devices, not the hardwired devices.

apostolakisl I'm really not trying to be picky, those are Access Points not SignaLincs. Lee

jpoje Brand of battery is not the variable. The condition of the batteries is. Likely the combined battery voltage was low enough not to be able to communication with the Dual Band PLM (assuming it is a 2413, not a 2412). Every device has a different reception pattern and sensitivity. Could also be the Dual Band PLM is not working as a Dual Band device or there is something in proximity to the PLM that is interfering with RF. Lee

raydoc "Once we get this working I need consults on how to get the lights on kps synced with dimmer states so that I don't have to turn a scene "on" to make it run." Not sure what you want to accomplish. Here are some Insteon facts that may help. A dimmer that is turned On through ISY Program control or the Admin Console does NOT then become a Controller and propagate the command on to its Responders. Insteon does not work that way. If multiple devices should react to a Program or Admin Console action a Scene must be turned On/Off. Secondary KeypadLinc button LEDs cannot be turned On/Off with Insteon Direct commands. The KeypadLinc firmware does not support this. Secondary KeypadLinc button LEDs must be controlled through a Scene. If none of this addresses the question I would be happy to help if you can expand on the scenario. Lee

With the Current State information being displayed and the Event Viewer showing command flow and the commands working I would expect the traced operation to have been successful.

Likely does not require an ISY reboot. Just exit the Admin Console and start it again when no Current State information is displayed from the start.

The last post by IM describes my working theory exactly. Thanks IM. As with most things Insteon when the powerline is concerned it is a theory. What is not a theory is the ability to communicate from A to B does not insure B can communicate with A. In some of the traces even A is having trouble communicating with B as the 2 Max Hop message does not make it from the SwitchLinc to the PLM. In those cases it was the next retry, 3 Max Hops that was successful in reaching the PLM. I’m pretty sure there is an intermittent source of interference. Something that is affecting more than one SwitchLinc as it is reported that this sequence is seen on more than one SwitchLinc.

Select the Scene name and turn the Scene On/Off. Turning an individual device On/Off with Direct commands does not then propagate to the Scene controlled by the device. Not the way Insteon works.

Make sure the power supply plug will fit the ISY jack. Do this with the power supply unplugged. Also make sure the polarity of the plug is correct before connecting plugged power supply to the ISY.

matapan Not everyone who has v35 SwitchLincs have a problem. If the comm problems are caused by the v35 firmware new switches will resolve the problem. Of course, since many other things can also cause comm problems you won't know until they are replaced. I think it is worth the effort to replace them. Lee

The 2413S PLM connects to a Serial port, the 2413U PLM connects to a USB port. The ISY has a Serial port, therefore requires a 2413S Serial PLM. Other than the port type each connects to the PLMs are the same.

ingeborgdot Jumper 5 on both pins. Put the motion sensor into linking mode by pressing the Set button for 4-5 seconds. The red LED will blink regardless of the LED level definition. This will keep the motion sensor awake so that the ISY can read and display the current options. They can be changed to whatever your Programming requires. The motion sensor will stay awake for approximately 4 minutes. Describe what the Programming expects the motion sensor to do. With that information the required options can be identified. Lee

Need some additional information. If the Motion Sensor is a Controller of a Scene with Responder(s) this activity cannot be suppressed, assuming the Motion Sensor is not operating in On Only mode. If using On Only mode (motion On message only, no motion Off message) such that the ISY Program is turning the Responder(s) Off then add a Condition to the Program the blocks the Off activity if say a particular KeypadLinc button is On.

Yes. But an LED draws so little to begin with I have not seen any difference. It will add some additional time if the LED is not used. Once the motion sensor has been positioned and tested the LED serves no real purpose. The Low Bat node stays On. The motion sensor does not send a corresponding message when a new battery is installed. To reset the Low Bat node right click on node and select Query. That does not actually send a Query command as the ISY understands the motion sensor is asleep and would not see it but it does reset the status the ISY is carrying for the node.

Jumper 5 is in place. Jumper 1 which reduces the sensitivity is not in place. No other jumper is in place. The other jumpers do not matter with jumper 5 in place (except jumper 1). The ISY program can have no affect on the Motion Sensor. It is a controller only, sending motion on messages based on the options that are active. The motion sensor has no responder capability and it goes to sleep after sending a motion message. You might try a factory reset. The reason I asked about HouseLinc2 as it had a bug where it turned the RF circuitry On and failed to turn it Off. That would drop battery life very quickly. The ISY does not use the RF circuitry control commands but if the devices came from Smarthome with that options set it would shorten battery life drastically. The only way to insure that option is not set is to factory reset the motion sensor. What kind of problem are you having? Perhaps it is not an actual battery problem since Low Bat is not being signaled.

I run with Sense Off On Only Always On (no dark only) TImeout 30 seconds LED 128 Certainly some of the options have an affect over the long term. Could be the difference between 9 months and 10 months but none of the options result in 2 weeks. Does the Low Bat node say ON? Lee

ingeborgdot Take a look at this topic for an explanation of the Motion Sensor options. viewtopic.php?f=25&t=5184 If your batteries are running down in 2 weeks were these Motion Sensors managed by HouseLinc 2 at some point. None of the options would result in battery life of 2 weeks. Lee