LeeG

An I2CS device cannot be correctly added to the ISY below 3.2.x. Some I2CS device types present command failures such that the device add process fails. Other device types look like they add successfully but do not. Some I2CS devices will work with basic On/Off commands, others will not. Scenes cannot work on an I2CS device when created by software/firmware that does not support I2CS. That means no device linking and no status updates. Depends on what/how/how much of I2CS protocol changes the device developer chose to implement in the first device firmware that requires I2CS. Experience has shown it varies across the 12+ device types that now require I2CS support. How I2CS device failures will evolve on software/firmware that does not support I2CS is unknown. Bottom line, one cannot realistically remain on any software/firmware that does not support I2CS. The solution is to move to the later ISY where code memory is large enough to support the evolving Insteon protocol and device types.

Thanks, that explains things. Edit: I suggest moving the magnetic switch to the door header so that it indicates "door fully closed"/"door not fully closed" rather than "door fully open"/"door not fully open" in the existing arrangement.

Does the Sensor change state just before it reaches fully closed? That is, is the magnetic switch mounted such that the door has to be closed before it turns the Sensor Off? If so it would seem the door closure is too sensitive rather than an obstruction. You can put a Wait 5 minutes before the email for door closed. If the door opens within the 5 minutes the Status changes to On, the Program If is reevaluated because it is in the Wait which will now be False so the Else clause runs so no email.

The ISY does not support the FanLinc software settable options.

Connect an external magnetic switch that has the reverse characteristic. There is no trigger reverse option like the I/O Linc has.

Obviously UDI will comment but I would not think that physically possible. It is not a simple matter of adjusting the cat/subcat values. The SwitchLinc Relay is an I2CS device and the Dimmer will be eventually. There are at least 12 different device types being shipped as I2CS and that number will only increase over time. Don’t think the memory in the 26 is large enough to support such a large update to I2CS support.

Under the Configuration tab, the System section, Reboot button.

It is a function of Java, not the ISY. Invoke Java from the Control Panel (not sure if that is what Win7 calls it), select the Security tab and click Certificates.

"Is it possible to change status of a Keypadlinc LED when turning an Outletlinc On/Off via its set button?" Unfortunately no. The OutletLinc Relay is a Responder only device. As such it does not indicate local changes to any other Insteon device. ApplianceLinc is in the same category of Responder only. A Responder only device can be identified by looking at the Quick Start and User Guide. There is information on linking the OutletLinc Relay as a Responder but no information on linking the OutletLinc Relay as a Controller which would be necessary for another device to be notified of a local change in status. EDIT: the OutletLinc Dimmer will function as a Controller but the load must be dimmable.

The From time triggered the Program at 12:07 AM Saturday morning as Sunset +4 hours occurs past midnight at my geographic location. The Program is scheduled to run at 11:30 AM Sat to satisfy the To time. If On Fri From Sunset + 4 hours To 11:30:00AM (next day) Then Send X10 'A1/On (3)' Else Send X10 'A1/Off (11)' "is it the next day of the last day in the selection? For example if I select Sunday & Monday, would the program end on Tuesday?" If On Sun, Moni From Sunset + 4 hours To 11:30:00AM (next day) Then Send X10 'A1/On (3)' Else Send X10 'A1/Off (11)' The From/To applies to each selected day. Assuming the From Offset creates a trigger time after Midnight, Sunday would give a From/To range that covered Monday morning, 12:07AM to 11:30AM in my case; Monday would give a From/To range that covered Tuesday morning, 12:07AM to 11:30AM.

"Is #4 possible? Could you change the status of a KPL button using an ISY program?" Number 4 is possible. A KeypadLinc Secondary button can only be controlled with a Scene that contains the KeypadLinc button as a Responder. A program that looks something like this ... If Status 'devicea' is On or Status 'deviceb' is On or Status 'devicec is On Then Set Scene 'KPL button scene' On Else Set Scene 'KPL button scene' Off

What do you need it to do?

Is this an actual case that is going to be used or some "what if" exercise? Do you really want to use Sunset +offset that takes the From start point into the next day EDIT: If this is an actual implementation that must be done 4+ hours after Sunset (which could result in starting the next day) does the To time trigger point to run the Else clause need to actually be the "next" day after the actual From start time or need to be the day after Sunset regardless of the day the From time resolves to.

There is no need to wait. The PLM will not handle concurrent Direct commands (ISY waits before sending next command) and there is no cleanup for a Scene On/Off.

Check the Current State column for that KeypadLinc button node. Likely it still shows On because of a comm problem between the KPL location and the ISY PLM. If the Status changes to Off the Program will be triggered with a False condition which will stop the program from looping. The other possibility (rather than comm issue) is the Program issued one of the commands to change the state of the primary load control button. If this is done at the same time the Secondary KPL button is pressed it could prevent the button press message from reaching the PLM. This possibility can be reduced by issuing a Query for the KPL prmary load button which will refresh the state of all the KPL nodes.

I believe when a button is tapped in MobiLinc it actually runs the Scene the button is defined as a Controller of. Tapping KPL button A I would expect Scene A to be turned On since the KPL button is defined as non-toggle On mode. This can be confirmed by running the Event Viewer with Level 3 selected and tapping button A in MobiLinc. The Admin Console does not work the same way. To do the same thing in the Admin Console select Scene A and click On button. Tapping button C in MobiLinc would be expected to turn Scene B Off since KPL button C is defined as non-toggle Off mode. This would turn both KPL buttons Off. To do the same thing in the Admin Console select Scene B and click the Off button. I do not know if MobiLinc understands and honors a KPL button non-toggle mode. The Event Viewer trace will show what Scene command (On or Off) MobiLinc is using for each KPL button tap.

KPL Secondary button A is in non-toggle On mode. KPL Secondary button C is in non-toggle Off mode. "Each button is in its own scene" KPL Secondary button A is a Controller in ISY Scene X KPL Secondary button C is a Controller in ISY Scene Y "with the addition of the C button 'toggle off' as a controller in the A button scene" Based on posted information KPL button C would be a Controller in ISY Scene Y and ISY Scene X. That is not possible as a button can be a Controller in only one Scene. Please correct the above assumptions about Scenes and what buttons are in what Scenes and as what (Responder or Controller). Once there is an accurate picture of what is assigned to what as what then how to accomplish the same thing with a PLM driven Scene can be constructed (if it is physically possible).

What is the KeypadLinc firmware level? The operation of KPL buttons when pressed locally is different than when driven bya Scene from another Controller (ISY PLM in this case). Did you select the Scene name and adjust the Responder On Levels when the Scene is used versus when a KeypadLinc button is pressed where the KPL button is the Controller,.

Thanks for the update. A UPS will do it. Putting the UPS on a FilterLinc should allow the PLM to be plugged into the original location.

The Event Viewer is showing no response from the device. I would say PLM failure except a new PLM is being used. That leaves 120v coupling questions, some appliance/device is interfering with Insteon communication, that type of issue. If you have a pluggable device such as a LampLinc move it to the PLM plug point and see if a Query to the LampLinc works there. If so the PLM and LampLinc are working close in and other powerline issues such as coupling problems or interference are in question. Be sure the PLM is not plugged into a surge suppressor power strip. They often have noise suppression as well which will prevent powerline communication through them. If the LampLinc works move it to other locations to see where it works and where it does not. That may provide a pattern.

If device 14.66.27 is a thermostat it is reporting a temperature or humidity change. Some tstats come without the humidity sensor installed so the humidity reporting should be turned Off. If 14.66.27 is a thermostat what type is it and how old? EDIT: I think that is a temperature report. The tstats report in .5 degree increments so the ST xxx value needs to x 0.5 to get actual temperature.

Run Help | About, check Firmware and UI lines both show 3.2.6 (assuming that is what was upgraded to). Run Tools | Diagnostics | PLM Info/Status. Does show the Insteon address listed match the PLM in use and does it show Connected? Was the ISY rebooted after the PLM was replaced before the Restore Modem (PLM) was run? Is the new PLM the one being used now? Run Tools | Diagnostics | Event Viewer with Level 3 selected. Right click one of the switches in the My Lighting tree and select Query. Did the Red ! go away? If not post the Event Viewer trace.

Nuttycomputer I have not seen that issue with my 2441TH but others have. Was the back of the thermostat covered over with the circular disc included with the 2441TH. I think that might help prevent any air from between the walls reaching the insides of the thermostat. I have noticed the humidity reading to be very sensitive.

Don't think anything is being missed. Perhaps a different approach though. Does the actual temperature spread need to cover 15 degrees? Maybe a few actual degrees, then just knowing it is > X or < Y would allow the same function but with far less possible discrete values.

Sure. Define an ISY Scene with the ToggleLinc as a Controller. Use the Program Adjust Scene statement, selecting the ToggleLinc switch for both the In Scene and Set parameters. This combination changes the Local On Level (or Local Ramp Rate) of the ToggleLinc. If From Sunset To Sunrise (next day) Then In Scene 'ICON Dimmer 1' Set 'ICON Dimmer 1' 35% (On Level) Else In Scene 'ICON Dimmer 1' Set 'ICON Dimmer 1' 65% (On Level)