LeeG

There are actually some 20+ link records (IR codes) that are responding to ISY Scene number 91 (0x5B). The number of IR codes responding may give Illusion a clue as to the Scene that was originally defined which used that many different IR codes. To eliminate the 2411T reacting to Scene 91 all of the Responder link records with Group 0x5B have to be removed.

ELA I think LD3 is an index number into the IR code database which is located in a different area of memory. Similar in concept to the link database except it holds the IR codes which are more than a single hex byte. It was more than 3 years ago when I looked into this so recollection could be fussy but I remember using a Set MSB value to access higher memory locations to retrieve the specific IR code information.

If 13.24.AA is the ISY PLM address all but one of the posted link records will react to Scene 91 (0x5B). The two link records that show mismatch could be a problem retrieving information from the 2411T. In one case (13.00.AA versus 13.24.AA) it looks like a 0x00 was returned which might not actually be in the device. I have seen Peeks return the wrong value. The other mismatch (00.F5.69 versus 12.F5.69) could be another case where Peek returned the wrong value. These two mismatches are not the real concern. It is the long list of links with the 0x5B Scene (Group) number the ISY thinks should be there (no mismatch). A Restore Device to the 2411T will not fix this as the ISY believes these links should be there. Unfortunately now that the problem has been defined I do not have a good suggestion to resolve it. A Delete and Factory reset is always an option but that would mean redefining all the IR codes.

The Scene (Group) number is 91 0x5B. For the 2411T to react to that ISY Scene there has to be a link record with a 0x5B in the 2nd byte (where the 06 is) and the ISY PLM address in the 3rd, 4th and 5th bytes. If the link record is there the first two bytes of the line are the address of the link record 0FF8: A2 5B xx yy zz - where xx yy zz is ISY PLM address - the 0FF8 is arbitrary Once the link record is located then do a Compare and see if the ISY thinks the link record should be there at that address.

Determine the Scene (Group) number of the ISY Scene. A REST command can be used for that. http://192.168.2.2/rest/nodes/scenes 35008 SceneFanSpeedMed 46 J05 - 14 9E F5 2 Then do a Show Device Links Table on the 2411T and look for that Scene (Group) number in the second byte of a link record in the IR 2411T. Note the deviceGroup tag is a decimal value. The 2nd byte in a link record is hex.

No. However, FanLincs are now being shipped as I2CS devices which require an ISY 3.2.x image. ISY 3.2.6 (RC2) is the latest available.

Use a single ISY Scene for a 3-way (or 4-way) setup. Add the two associated devices as Controllers to one ISY Scene. The ISY assumes a Controller is also a Responder, cross-linking the devices such that the load and status LEDs stay in sync. Same with a 4-way. All three switches are added to one ISY Scene as Controllers. EDIT: yes, three separate ISY Scenes. One each for the two 3-way circuits and one for the 4-way.

There was some ELK problem that was fixed in 3.2.6 (RC). Suggest installing the latest ISY firmware and see if the problem remains.

It is not a matter of one condition that triggers a Program trumping another condition. Each condition that can trigger a Program causes the Program to Run. The evaluation of the combined If section determines whether the Then or Else clause executes but not if the Program is triggered to begin with. In the example posted when the From time occurs the Program is triggered when the To time occurs the Program is triggered when the device Status changes the Program is triggered when the Time occurs the Program is triggered Each time the Program is triggered it runs one of the clauses. The evaluation of the If as True or False determines which clause runs but the Program will run one or the other when triggered. As noted a Folder Condition will stop a Program from being triggered.

From the ISY User Guide • 5-30 VDC • 300 mA minimum • Center positive 2mm male barrel jack

The UDI Wiki has some very good information ISY Programs. Don't think there is a FanLinc example as the device is too new but ISY programming in general there is lots of good information. Here is one example of switching from Low to Med using KPL button C On If Control 'KPL Floor Dimmer 6 / KPL Floor Dimmer 6 - C' is switched On And Status 'FanLinc I2CS-Fan' is Low Then Set 'FanLinc I2CS-Fan' Med Else - No Actions - (To add one, press 'Action')

Although the 2412N does contain an internal PLM as all 120V Insteon devices do, it is not a variation of the 2412 PLM. The 2412N is a basic entry level stand alone automation controller. It has basic timer support but no facility to trigger events based on device activity.

MOST IMPORTANT! The Admin Console being used 3.1.17 is not meant to run on the 3.2.x betas. Clear the Java cache and switch to the URL for the 3.2.5 Admin Console. Also note that 3.2.6 (RC) is now available. A single button can be implemented with a few ISY Programs. Using the current On Level of Low for example and a button press the ISY Program Then clause sets the Fan On Level to Med. Another ISY Program uses an On Level of Med and a button press to have the Then clause set the Fan On Level to High, and on so on. The KeypadLinc button can be put into non-toggle mode so that it is not necessary to cycle through an On/Off button sequence.

The Red LED in the motion sensors are independent of communicating with a device. If it senses motion the red LED should flash unless the option to turn Off the LED is in effect. With no devices reporting status changes either the PLM is hung up or the PLM has lost its link database. If a power cycle of the PLM does not work the next thing is a File | Restore Modem (PLM).

Unplug for 30 seconds the Access Points and the Dual Band PLM if using a 2413S. If using a tstat cycle it as well. Are there any other RF only devices that are working? Are the LEDs on the Access Points blinking?

An X10 PLM will not be of any use. The PLM must be a 2412S or 2413S (Dual Band PLM). Indications are the PLM has failed. The 2412S is no longer available. The 2413S Dual Band PLM is the current PLM. It does not provide power to the ISY as the old 2412S did. A small external power supply is required when using a 2413S PLM. Smarthome carries the power supply. The Rx LED is not normally On. Refer to page 60 of the ISY User Guide for a chart of the ISY LEDs. It indicates the Power and Rx LED on is a PLM or cable problem which is consistent with no PLM connection information.

Is the LED on the side of the PLM on? The Rx LED being on indicates a problem communicating with the PLM. Unplug the PLM for 30 seconds which will also bring down the ISY as it is powered from the 2412S PLM. Check the cable between the ISY and PLM. Plug the PLM back in. It will take a minute or two for the ISY to boot up. Is the Rx LED off now?

Select the LampLinc node so the On/Off “Current State†column can be observed. Turn the Lamp manual switch Off and On while watching Current State. If Current State changes (it will with a 2457D2 and possibly others) as the Lamp is manually switched On and Off then a Program can do what you want. Turn the Lamp Off with manual Lamp switch and within 2 seconds turn it back On with the manual switch. The Lamp will turn On and the Program will immediately turn the LampLinc Off so that the other timing Programs will continue to work. The end result is the manual Lamp switch is On and the LampLinc is Off. If the Lamp is Off for more than 2 seconds the Lamp will turn On and stay On the next time the manual Lamp switch is turned On An Integer Variable named iLampLinc must be defined using the Variables tab. Init and Value = 0 LampLincTiming Program If Control 'LampLinc DB' is switched Off And Control 'LampLinc DB' is not switched On Then $iLampLinc = 0 Wait 2 seconds $iLampLinc = 2 Else $iLampLinc = 1 LampLincOff Program If Control 'LampLinc DB' is switched On And $iLampLinc < 2 Then $iLampLinc = 0 Set 'LampLinc DB' Off Else - No Actions - (To add one, press 'Action') This is a working example.

When the device is Deleted the link database in the device is cleared so the switches would stop working. I would look at the Scenes from the other end. Which Scenes have a large number of devices and can anything be done to adjust them. For example, Scene A has 40 devices for an All Off capability. Scene B has 40 devices for an All Off capability. There are a few differences between the device list of Scene A and Scene B but many of the devices are duplicated between the two Scenes. Can this situation be broken down into 3 Scenes which sounds counter intuitive but the total links would be less. Scene C would contain the devices common to Scene A and Scene B. Scene A would contain only the few devices that are unique to Scene A and Scene B the same way. This could reduce the total links even though there are more Scenes. Look at the large Scenes where the biggest bang for the buck can be achieved. Scenes that exist but are no longer used. I would not try to reduce the links by tricking the system. Things like that come back to bite you at all the wrong times. Have you given any thought to treating family to a night at the movies to eliminate the Insteon traffic for a few hours. That way a few good Restore Modem (PLM) and Show PLM Links Table with Count could be run to see just how much of a problem exists.

Reduce the number of links used in Scenes. A review of Scenes by other users who have had similar problems have found changes could be made to eliminate duplication, delete longer used Scenes, combining Scenes, etc. Never having actually done this myself I cannot provide specific examples.

No. Scene created by the ISY will have the device removed if the device is deleted. Otherwise the Controller would get Insteon errors on the assumption when a device is Deleted it will be removed from the powerline.

That is approx 250 PLM links for the devices to be defined to the ISY. The Scenes are difficult to estimate as it depends on the number of Controllers and Responders in each Scene.

Reduce the number links by reducing the number of Scenes. Often Scenes are generated over time which can be combined with other Scenes to reduce the total PLM link count or not actually needed at all. How many Insteon devices are defined to the ISY, how many are KeypadLincs (of what type 6 or 8 button) and how many Scenes.

The number of links in the PLM is an unknown because the persistent Insteon traffic does not allow a good count. I'm inclined to think the PLM capacity has been exceeded but without objective information that is only a guess at this point. Insteon requires three things for a paddle/button press to be recognized. A link record in the device itself which has been verified as present. Good communication between the device and the PLM which looks okay, at least when the device is powered from the PLM plug point. The last requirement is the link record in the PLM which you indicate is not there based on what has been displayed. It could be the link record is there and not displayed because of traffic in which case you have a Zebra. All the requirements exist but it does not work. I don’t think that is the case. Best conclusion at this point is the PLM capacity has been exceeded as that is the only requirement that has not been verified.

Decided to make new post as folks don't always back up. The I/O Linc Relay Momentary hold time value not being displayed correctly was resolved by doing a Diagnostics | Query Insteon Engine. This same solution has worked on other devices where configuration data was not being handled correctly. Thanks Michel.