LeeG

The ISY-26 cannot be updated with any 2.8.x or 3.1.x image. See the post for the Official 2.8.16 release. Also means the discussion in the other thread about the RemoteLinc and variables does not apply as variables are not available until 3.1.x.

andrew77 This can be done with an ISY Program. The ISY Program is triggered by button B On. Through the use of ISY variables, the Program will know when it is the first button B On and Set Scene A On. This will establish the responders to whatever level is desired. When button B On triggers the Program again the variable will have been set to a value which indicates Scene A was last turned On. Thus this button B On press will Set Scene B On which will establish the responders to a different On Level. Each button B On press will cause the Program to look at the current variable value to determine what action should be taken. The variable will be set to some new value representing the action by the current button B On press. This approach allows several variants to be executed in sequence, for each button B On press. The button B Off could be incorporated into the sequence for additional variations. Each button B On could turn the responders On to ever increasing On Levels. The button B Off could turn the responders On to ever decreasing On Levels. Again, the RemoteLinc button would not directly control any Scene. Which Scene is used is all determined by ISY Program logic. Lee

KEVINLT I have seen those posts and have no explanation why Extended messages over RF would not work and then did work the next day. The ISY (Insteon) has no function to block executed Extended commands or RF by the Insteon mesh network. There are reports that motion sensors need to sit for a few minutes after changing the battery but that would not be the case here. With the PLM and the Access Point on the same circuit the Access Point must be seeing the Extended commands used to program the motion sensor. With the motion sensor within range of the Access Point things should be working, Venstar thermostat dongles have been known to block RF activity but I don’t think you have any of those. Lee

robandcathy The Harmony remote supports many different IR code formats. It has predefined codes for the ISY that can be downloaded into the Harmony remote. The ISY codes use RC5 (Philips device generally use RC5 or RC6 IR code format). Another user noted that the Harmony remote also has predefined codes for the IRLinc. When these codes are downloaded into the Harmony remote it will use NEC IR code format. The specific device type manufacturer and model are entered into the internet application that loads the IR codes into the Harmony remote. If Sony is specified the IR code format for that device would be Sony IR code format, and so on. Each Device button on the Harmony remote can use a different IR code format. One Device button can be using RC5, another Device button can be using NEC, another Device button can be using Sony. The Harmony remote is very flexible IR remote. Lee

andrew77 Any Controller button will do the following .... Press the On button turns the Scene On. Assuming the Scene results in the Responder turning On to 40% for example, if the On button is pressed again and held, the Responder will Brighten until the On button is released. Pressing the On button again and holding it will again Brighten the Responder until On button released or device reaches full Bright. This happens without any ISY Program intervention. Standard Insteon Responder stuff not unique to the Remotelinc. Another approach is for the On button to invoke an ISY Program. The ISY Program is implemented so the result in the same behavior. In this case the On button does not directly control the Responder. Lee

KEVINLT One thing to check is the Insteon address. Make sure 13.ED.BA is the address. Sometimes B’s and 8’s can be misread. Lee

KEVINLT Great information. The ISY PLM is not able to communicate with the motion sensor. Note the time stamp on the following outbound messages are 9 seconds apart. They are being retried because the motion sensor did not respond. Move an Access Point to the ISY PLM plug point and move the motion sensor near the access point. Put the motion sensor into linking mode and try again. Sun 07/24/2011 04:22:34 PM : [iNST-ACK ] 02 62 13.ED.BA 0F 0D 00 06 (00) Sun 07/24/2011 04:22:43 PM : [iNST-ACK ] 02 62 13.ED.BA 0F 0D 00 06 (00) Sun 07/24/2011 04:22:52 PM : [iNST-ACK ] 02 62 13.ED.BA 0F 0D 00 06 (00) un 07/24/2011 04:22:56 PM : [iNST-ACK ] 02 62 13.ED.BA 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sun 07/24/2011 04:23:05 PM : [iNST-ACK ] 02 62 13.ED.BA 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sun 07/24/2011 04:23:14 PM : [iNST-ACK ] 02 62 13.ED.BA 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Lee

j0dan The link database labeled Broken looks okay. Two Scenes have the responder On Level and Ramp Rate changed. Other than that the correct number of link records exist with the same Scene numbers as the right example. In fact the sequence of the Broken example is what I would expect to see when the device was added to the ISY and then the device added as a Responder to 4 Scenes. The right example looks like the device has had a Restore Device issued. The E2 01 18.D1.59 FF 1F 00 link record is first in the Broken example. It is the link record created when the device is added to the ISY and allows the ISY to be aware of a paddle press. It is expected to be the first link record. In the example on the right it is the 3rd link record which happens only when a Restore Device is executed (as far as I know). Removing a device from a Scene as a responder would affect link records 2,3,4,5 in the Broken image but would have not cause the E2 link record to be moved away from its link record 1 location. There is more going on here than can be explained with simple remove device from Scene and add it back to the Scene and Scene responder On Level and Ramp Rate adjustments. I do not have the Network Module. Those initial messages appear to be related to rules defined for the Network Module. What device is the Network Module controlling and what are those rules accomplishing. Lee

Regarding the ISY IR capability, YES, it requires RC5 IR code format. The IRLinc R requires NEC IR code format.

robandcathy I was not able to recreate. The first example is not functional (as from/to should be used) but I was able to specify a Sunset after and a Sunrise before. The second example using From/To is the correct way to specify a Sunset/Sunrise time range. Be sure to use (next day) on Sunrise. Suggest posting what you can define and we can go from there. If Time is Sunset + 15 seconds And Time is Sunrise - 15 seconds And Status 'Motion Sensor-2-Sensor' is On Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') If From Sunset + 15 seconds To Sunrise - 10 seconds (next day) And Status 'Motion Sensor-2-Sensor' is On Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') Lee

j0dan Dynamically changing Scene characteristics involves changing link records in the SwitchLinc. No specific reason to think that is the cause. Just sounds like a link record issue and that function happens to make changes to link records. Should be able to tell something when a good base line link table can be compared to the link table when things stop working. The LED level is maintained in memory away from the link database itself. Would not expect that to be affected by or cause a link table problem. Thanks for all the information. I like to form a theory about a possible cause and then either prove it right or wrong and move on from there. All the symptoms suggest a link record problem even though I don't really know how or what is doing the damage. Once we know what is wrong then more theory about how. Thanks again. Lee

j0dan Okay, thanks. Just to be sure, location A with SwitchLinc A produces the symptoms described. Installing a new SwitchLinc B at location A, location A still has the problem. This suggests something in the way the SwitchLinc is being used. Perhaps the dynamic changing of the Scene characteristics (only a guess). Now, SwitchLinc A is installed in location B and there are still problems with SwitchLinc A at location B. Are the Scenes in SwitchLinc A at location B being dynamically changed while at location B? Lee

j0dan "I have the same problems with the new switch in that new location." I'm sorry but I don't understand this statement. SwitchLinc A has a problem at location A. I think SwitchLinc A was moved to location B and a completely new SwitchLinc is now installed in location A. Now, which location has the problem, location B where the old SwitchLinc was moved to or location A where a new SwitchLinc is installed? It sounds like a link record issue in the SwitchLinc. The SwitchLinc cannot control Scenes if the link records are lost or damaged. When the SwitchLinc is working, run Tools | Diagnostics | Show Device Links Table and note the exact results. When the failures occur run the Show Device Links Table again and note any differences. The SSL errors are a total mystery. Insteon devices have no relevance to SSL. Let us know what if any differences exist in the device links table and we can go from there. Also did the failure follow the SwitchLinc or stay at the original location? Also what is the firmware level of the SwitchLinc? V.35 firmware ia famous for Scene communication problems. Lee

gregseigs1 At some point the Link Management | Start Linking option was probably selected. The PLM LED would be blinking initially as Michel described. That option is used to add devices to the ISY when the device addresses are not known or devices are to be discovered by pressing the Set button for example. The Start Linking option should have displayed a modal popup message. Being modal it should have prevented access to ALL underlying ISY function until Start Linking is complete. Sounds like the modal popup message was not displayed which can happen when there is a fire wall problem. The Discovering nodes message comes up when other ISY function is being attempted while in Start Linking mode, at least that is what was happening the last time I saw a user report that symptom. The firewall prevented the modal popup from being displayed so no visible indication (except PLM blinking LED) the ISY was waiting for hear from Insteon devices. Also without the popup there was no “Finish†button to click on. I believe that user was running Kaspersky which had not been configured. There is a Wiki (I think) article on how to configure Kaspersky. Are you using Kaspersky? Lee

gregseigs1 I believe they are meant to indicate the general type of device, not whether the device is On or Off. The On/Off state is shown in the Current State column/box. Lee

sperok I was asking if the outputs actually turned On. The trace entries are evaluating the bits in the cmd2 field of the ACK with an EE cmd1 field. There is no EE command for the EZIOxx family of devices so the cmd2 field may have nothing to do with the status of the output triacs. Is the EZIO8T running irrigation zones? Is this trace entry a common occurance? Does it happen when Input 2 turns On? Lee

Sperok Are relays actually turning On at 03:18:28? If so which ones? There is no EE command code for an EZIOxx device so interpretation of cmd2 for relay numbers may not be relevant. The trace indicates Input 2 turned Off at 03:18:08, then turned On at 03:18:27. Is that what actually happened to Input 2. Has any configuration of the EZIO8T been done through the SHN Utility? Lee

intellihome Try unplugging the ISY/PLM for a few minutes and then restoring power. When commercial power comes back after an outage it can be a little erratic as everythinge is being restored at once. Don't about the old 2.7.15 backup running against 2.8.16 Lee

klundy Any given Controller device can be a Controller of only one Scene. This is an Insteon architecture design point. Insteon does not support Scene A controlling Scene B. So using those requirements the simplest way to define the interrelationship between the KPL button and the ToggleLincs is a single ISY Scene with the KPL button and both ToggleLincs as Controllers of the single ISY Scene. The ISY assumes a Controller device of a Scene is also a Responder device in the Scene (assuming the device has Responder capability). Under the covers the ISY cross-links all three devices such that pressing the KPL button or either ToggleLinc will cause all three devices to react in sync. This may require deleting some of the Scenes which were automatically created (and assigned numbers) when devices were added to the ISY with the option to keep existing links. Must have used that option if Scenes were not explicitly created using the ISY. EDIT: from Insteon’s point of view the result is three Insteon Scenes. One Scene is the KPL button as Controller with both ToggleLincs as Responders. Another Insteon Scene is ToggleLinc1 as Controller with ToggleLinc2 and the KPL button as Responders. The last Insteon Scene is ToggleLinc2 as Controller with ToggleLinc1 and the KPL button as Responders. Devices can be Responders in many Scenes but they can be a Controller of only 1 Scene. For the most part it is not necessary to think about what the ISY is doing under the covers. Coming from HL2 it may help understand what is actually happening when an ISY Scene has multiple Controllers. Actually a very simple way of defining cross-linked devices once you get use to it. Lee

Or the variable does not have a value that supports the AND condition. The ISY does not make mistakes about devices. Click on the Mostion Sensor Sensor node and look at the Insteon address shown at the top of the right pane. Compare that to the Insteon address in the trace. If the Programs are in folders the folder condition is also a question.

Assuming the Program is Enabled and the version posted has been Saved, the Anded variable value is in question if the Program really is not being triggered versus not doing what you want. Simple way to determine which is to add an X10 On as the first Action statement in the Then clause. An X10 device is not needed, in fact better to use an X10 House/Unit that does not exist. The X10 activity will be traced in the Event Viewer. If there is an X10 event after each MS On then the overall logic needs to be checked. If there are MS Ons with no X10 then the value in the Anded variable is in question.

Sensing Mode (Occupancy Mode) should be checked; On Only Mode should be unchecked. Probably Night Only should be checked based on initial post. Jumper 5 must be installed. The other Jumpers (except sensitivity) do not matter when Jumper 5 is installed. Occupancy Mode has to be set with the ISY (programmatically). None of the jumpers specifically controls Occupancy Mode. After setting the options and clicking OK, if Set Options is clicked again are the correct boxes checked? EDIT: correction to which boxes to check. This post first said On Only mode should be checked. I changed that to unchecked. On Only mode should be unchecked to suppress the Off command.

Yes. Click on Motion Sensor node in My Lighting tree and select Set Options in right pane. The Motion Sensor has to be in linking mode (Set button pressed for 4 seconds) so options can be read and written. EDIT: Jumper 5 has to be in place to be able to set Motion Sensor options programmatically. The Motion Sensor Quick Start Guide describes this and how to have it active.

The Motion Sensor options need to be On Only Mode and Occupancy Mode. Sounds like you do not have Occupancy mode set. Without that the Motion Sensor will not send another On command until the Motion Sensor timeout value has expired, which continues to be restarted for each new motion detected even though no On command is sent. “Is the MS smart enough to know when the load is on to not take any new photocell values?†No. The Motion Sensor is simply looking at ambient light. However, the ambient light has to exist for 3.5 minutes before for it affects Dusk/Dawn.

ryarber I just Deleted and added using New INSTEON Device my ICON Relay 2876SB with v.39 firmware. Used Auto Discover. Looks like that device type does work in general under 3.1.5. Lee