LeeG

rickholloway That device is listed in the Device Type pulldown on 3.1.10. [01.21] If it is not in the pulldown list the Admin Console is not at 3.1.10. Try clearing the Java cache and be sure the URL is accessing the 3.1.10 version of the Admin Console Lee

When using Auto Discover, after Unsupported should be two numbers, x.yy What are they?

This also works on the Programs | Summary page. Clicking Find after selecting the device to locate highlights all the Programs containing a reference to the device.

Robandcathy Use the From/To to define a range of time rather than two individual times. Be sure to use (next day) on To value. Note that Status works if not using On Only. If using On Only Control must be used. If From Sunset To Sunrise - 1 second (next day) And Control 'Motion Sensor 3-Sensor' is switched On Then Set 'LampLinc 6' 80% Else - No Actions - (To add one, press 'Action') Lee

creeble The Controllers and Responders themselves hold the link records that allow the Controller(s) to turn the Responder(s) On/Off. These links are created by ISY based on Scene definitions and operate independent of the ISY or the ISY PLM. There are links between all Controllers and the ISY PLM. These are created when each device is added to the ISY and allow the ISY to keep track of individual device state changes as well as trigger Programs based on button/paddle presses (state changes). It is the links created when the device is added to the ISY that requires the ISY PLM to be functional all the time to avoid powerline communications errors when a button/paddle is pressed. Lee

Creeble “First, to turn *all* devices off, I still need a Scene with *all* of the devices in it, correct? I mean, there's no general "broadcast" equivalent to "all units off" like x10?†There is no Insteon function that can be put on the powerline in the blind (like X10 messages) that turns All device Off. A few devices such as the RemoteLinc have an All Off button but this still requires links between the RemoteLinc and its Responders. A Scene with the devices that should respond to the All Off is the approach. †The optional A10/X10 Module is not needed for an ISY Program to control X10 devices. ISY Program Actions can turn On/Off X10 devices with the option Module. The optional module allows X10 devices to the defined in the My Lighting tree as Insteon devices and refer to the symbolically. “ My apologies, I missed a “not†- ISY Program Actions can turn On/Off X10 devices without the optional A10/X10 Module. The optional module allows symbolic reference to X10 devices by name but does not provide any new X10 functional capability than the basic ISY. “a 99i Scene actually sets up the link tables for the Insteon devices, such that the 99i isn't actually called upon for direct controller->responder actions like turning a "scene" (said group of responders) on and off?†That is absolutely right. Scenes that have Insteon devices as Controllers and Responders have links between the Controller(s) and Responder(s) such that the ISY is not involved in the interactions. The ISY could be powered down or under maintenance and the device to device control is fully functional. This is the way Insteon itself works. The ISY PLM needs to be powered as button/paddle presses inform the ISY PLM of the action. If the PLM itself is not available the Controller will retry the communications with the PLM causing unnecessary powerline traffic. Lee

CPUjohn Some information. The lack of current device status is almost always a router/firewall/AV issue. The ISY pushes device status to the Admin Console which can be blocked by the above. Also likely the cause of the 9 minute ramp rate and 0 On Level as both of these are zero values which have probably not been pushed out from the ISY to the Admin Console. The Wiki describes how to configure the various components. Kaspersky is well known for blocking the push of data if not configured and the latest Avast update has caused problems. There are a number of posts which detail how to work around the Avast problem. This topic viewtopic.php?f=27&t=6908&hilit=avast toward the bottom has a good description of the Avast solution. A device can be added to a Scene as a Responder or a Controller. Once added as a Responder it has to be deleted from the Scene and added back as a Controller. Note that the ISY assumes a device to be a Responder to the Scene when added as a Controller (assuming the device has responder capability). Since battery devices sleep it is often a problem when the ISY wants to update the device. The update will be queued and retried. Put the battery device into linking mode, right click on the node in the My Lighting tree and select Write Updates to Device. That should clear any pending writes for the device. Lee

stef2 There is another possibility. 3.1.10 must be installed before installing 3.1.11. If 3.1.11 was installed without going to 3.1.10 first the 3.1.10 Admin Console will not be on the ISY as 3.1.11 is a fix to the ISY image only, there is no UI in the 3.1.11 install. Lee

tdmarra It sounds like the old RemoteLinc has pending activity. Put it into linking mode(Dim/Bright butteons), right click the old RemoteLinc node and select Write Updates to Device. Once that activity is cleared up then trying linking the RemoteLinc 2 again. Lee

Creeble The implementation will consist of multiple Scenes and multiple ISY Programs. To have a group of devices react together at the same time the easiest way is to define a Scene with the specific devices as Responders and an ISY Program that triggers with the appropriate condition. For several of your examples the ISY Programs would be triggered at a specific time, Sunset -30 as an example, turning the appropriate Scene On. A Program can have multiple Actions if needed. As a Scene can have some devices turn On full, others turn On to different % On and even some turn Off the decision is more when things happen as far as whether different Scenes are needed. The All Off is simple. Assuming it is driven by a button on a Controller (RemoteLinc button for example) an ISY Scene is defined with the RemoteLinc button as Controller and whatever devices should turn Off as Responders. No ISY Program is needed in this case. Pressing the Controller button Off turns all the Responders Off. The All Off function can be driven from multiple Controllers simply by adding additional Controller buttons/paddles as Controllers of the Scene. Multi-way switch configurations also require an ISY Scene. If 3 Insteon devices control the same load, one directly and two indirectly in a virtual multi-way configuration, one ISY Scene with all three devices defined as Controllers is used. This cross-links all the devices such that any can turn On/Off/Dim the load and the other switches status LEDs will stay in sync. The optional A10/X10 Module is not needed for an ISY Program to control X10 devices. ISY Program Actions can turn On/Off X10 devices with the option Module. The optional module allows X10 devices to the defined in the My Lighting tree as Insteon devices and refer to the symbolically. Hope this helps get you stated. Post back any additional questions as needed. Lee

Are you putting the devices into linking mode before attempting any communication and selecting the correct Device Type entry from the pulldown? If in linking mode and the correct Device Type is selected move the RemoteLincs closer to a Dual Band device (not a SignaLinc).

The Help | About is the firmware level of the ISY, not the Admin Console. If the RemoteLinc 2 device types are not near the top of the Device Type pulldown list it is not the Admin Console for 3.1.10. Clear the Java cache and be sure to use the URL that invokes 3.1.10 Admin Console.

gabbott My Dual Band PLM LED blinks when in Start Linking mode. The only thing I can suggest since a power cycle has not resolved the problem is to Factory Reset the PLM and then do a Restore Modem (PLM). Lee

Would someone who uses a Dual Band PLM and Start Linking, does the PLM LED blink or is it solid bright when Start Linking is entered? I've not seen anyone note that the Dual Band LED does not blink but it may just not have been noted.

When the device add failed did you click the Finish button on the first Start Linking before clicking start linking again?

gabbott If the PLM LED is blinking and the Start Linking popup is not visible things have gotten out of sync. Remove power from ISY and PLM for 60 seconds. When the ISY is back up after restoring power, before another attempt is made with Start Linking, does the Current State column show device status for most of the devices? If not the ISY is not able to push status out to the admin console and start linking will not work. Exit the admin console and invoke it again. If the Current State column is always blank that usually indicates a router/firewall/AV issuing blocking the ability of the ISY to push device state information which includes the information for Start Linking to work. Lee

"Motion triggers the sensor, but the sensor does not reset immediately afterwards." Not sure about v1 motion sensors but v2 motion sensors have an Occupancy mode which causes the motion sensor to trip for each motion independent of the timeout value. Generates lots of messages if there is heavy traffic. I have no pets but I have successfully blocked part of the field of view with opaque tape. Had one tripping as traffic passed close to the closet door. Solved that with a piece of tape mounted vertically along one side. I would think the same thing could be used across the lower part of the lens to block low traffic. Of course if there is a climbing cat that will not work. Jumper 1 will reduce sensitivity but it lowers overall sensitivity rather than a particular quadrant.

wwat The single Scene command that is issued to turn a Scene On does not include device addresses and it is not ACKed by any responder. The ISY looks at the Scene definition and marks the responders according to what should happen, not what does happen. Lee

wwat When a failure attributed to an image upgrade turned out to be a surge suppression power strip that should not have been used was determined to be the cause I stopped trying to explain why symptoms occur only when an image is changed. There are message retries associated with a Scene Test that do not occur for a Scene On/Off from a Program. When the Scene Test works it indicates the link records in the ISY PLM and devices are intact. When the Scene On/Off does not then communications are the question because a single message must result in all the Responders reacting for a Scene On/Off compared to multiple message attempts for a Scene Test. Direct commands have the same retries as the Scene Test. If it takes two or three attempts (all automatic by Insteon hardware) before a Direct message or Scene Test message is successful the result is the same, the device has responded. All devices must respond to a single message for a Scene On/Off making good communications much more important. Lee

wwat When a device will reliably turn On/Off with Direct commands but not respond to a Scene it is either a Scene link record problem in the device or a communications problem with that device. Suggest running a Scene Test for that Scene. Right click on Scene name in My Lighting tree, select Diagnostics | Scene Test. If the Scene Test is successful but the device continues to not respond to the Scene Action in the Program there is likely a communications problem with the device. If the device fails the Scene Test do a Restore Device for the failing device to restore the device link records and repeat Scene Test. If that does not resolve the problem delete the device from the Scene and then add it back. Lee

May not be an Insteon or X10 device but something generating noise that is being interpreted as an X10 signal. The House code M is all bits Off for the House code portion of the message. Any new appliances, new cell phone charger, new electronics. One approach is to turn the circuit breakers Off one at a time to see if the issue can be isolated to a particular circuit as the source. If that can be identified then unplugging devices (not Insteon or X10) on that circuit.

edilks Check Help | About to insure 3.1.10 is installed. Clear the Java cache and be sure to use the URL that invokes the 3.1.10 level of the Admin Console. The RemoteLinc2 entries are very near the top of the Device Type pulldown list if running 3.1.10 Admin Console. If they are not in the list the 3.1.10 Admin Console is not being invoked or the Java cache was not cleared. Lee

Davonavo Not through the ISY. Lee

mualexander Using the Admin Console under Help | Purchase Modules lists the Modules available which can be selected and ordered. Lee

"the KeypadLinc A buttons that control the three SwitchLincs should also be Responders in the Scene controlled by KeypadLinc B button C." I think the KeypadLinc A button was added as a Controller to the KeypadLinc B Scene rather than a Responder as was suggested.