LeeG

Crusty Good to hear things are working now. Having the Admin Console open should have no affect on the operation of the sensor flood lights. Removing the switch from the Scene would result in a fair amount of Insteon command activity while the link database in several of the devices were changed. There are Green Icons to the left of the nodes while they are being changed. Perhaps it took longer than what was anticipated to complete those updates. Lee

Crusty Removing a device from the scene would not normally cause that symptom. What is the Smarthome item number of the sensor flood lamp? Do the sensor flood lights themselves come on? If this is the Smarthome flood light kit with an InLineLinc the flood lights themselves are not affected by any device link. If the flood lights do not turn On with motion look to that device. Motion head problem, InLineLinc problem, was a Fast Off used to turn the flood lights Off which keeps them Off until reset by a normal On/Off. Some of the possibilities depends on the type of sensor flood light device. Assuming the KeypadLincs are Controllers in the Scene do they turn the flood lights On/Off? Lee

The devices are not wired correctly. Insteon devices require unswitched 120V AC. When a device goes blank as you describe it is not being powered by unswitched 120V AC. EDIT: likely the switch is being powered from Load side of the KeypadLinc. When the KeypadLinc load is turned Off power is removed from the switch and its LEDs goes blank. Insteon switches are NOT like a standard 3-way switch. The traveler wires to the switch have to be retasked to provide unswitched 120V AC to the switch. If you cannot figure it out suggest posting on the Smarthome forum. There are a number of users who are present and retired electricians who may be able to guide you through the process of changing the wiring between the KeypadLinc and switch location.

Put the RemoteLinc into linking mode by pressing the Dim/Bright buttons until the LED blinks continuously. Right click on the device entry under the Scene name and select Remove from Scene.

The difference between showing v.00 and v.xx is how the device is added. Using New INSTEON Device and explicitly selecting a Device Type from the pulldown results in v.00 (at least for all the cases I have seen). Selecting (defaulting) to Auto Discover results in the ISY obtaining both the device type and firmware level. Not all devices can be added with Auto Discover but I find that the better approach when it can be used. The User Guide and the Wiki covers most of the devices that must be added by specifying the actual Device Type.

Smarthome is looking for the results of a Restore Device only. They want to know if the links in the KeypadLinc have been compromised.

The Venstar tstat adaptor has a problem that interferes with communication with the tstat and/or other RF devices. Some users see this occurring every few days to a few weeks. Other users have never seen this symptom. There is a topic on the forum specifically discussing this problem. Unplugging the tstat adaptor has been a good way to determine if they are causing a problem. Nothing you have posted so far indicates you have that problem but it is something to consider when evaluating communications problems. Does the TCP error message from the Weatherbug occur when you adjust the thermostat on a regular basis? The thermostat adaptor does not use any IP/TCP communication so I take that message as coincidence until evidence indicates otherwise. The Pool Light communication problem does sound powerline related. Could be noise, distance, both.

Ditto on BLH comment regarding the tstat dongle. Smartlabs is close to a fix for that problem. Probably have to replace the dongle as the firmware is not upgradable in the field. Not sure that has a relationship to the TCP message as there is no IP traffic associated with tstat commands. The TCP client message is Weatherbug access. Don't think it is related to the tstat. I’m not the right person for IP and Weatherbug questions. The Pool Light is consistent with powerline problems. From its name the Pool Light device may be outside at some distance from the ISY PLM. The Pool pump could be a source of noise. Placing an Access Point close to the Pool Light device may help. Identifying what was running when the Pool Light did not respond might help. Powerline analysis is often a process of elimination. Unplug devices, just turning them Off is not enough because the power supplies are still active when plugged in.

jellis There is normally a Red Icon to the left of the device entry in the My Lighting tree. Right click the device entry and select Query. This will access the device (assuming the device is reachable) and clear the Red Icon. Intermittent failure to communicate is generally a powerline issue. Noise on the powerline, signal attenuation such as an unfiltered UPS. Some devices such as cell phone chargers are well known noise producers. Some flat screen TVs can be a problem. PC, Laptop power supplies are good at reducing noise to the respective device they can also attenuate powerline signals. Some CFLs, some florescent ballasts, generate enough noise to cause problems. Not having the 120V legs correctly coupled. Lee EDIT: some things to consider. Is it only one device, if multiple devices are they on the same electrical circuit, do the errors happen only when certain devices are On, do the problems occur at particular times of the day.

Dogan Bora What ISY firmware level is installed? How old is the EZRain? Lee

ergodic The following is an actual Program. Variables can be compared and assigned values from other variables. If Time is 5:54:00PM And $IVar1 is $SVar1 Then $SVar1 += $IVar1 Else - No Actions - (To add one, press 'Action')

ingeborgdot Keeping the basement KPL buttons and their individually controlled switches in sync are as simple as making the KPL button and switch a Controller of the Scene for those two devices. To turn Off the basement KPL buttons and the switches controlled by those buttons from KPL button H upstairs, each basement KPL button and each switch controlled by those buttons should be responders to the Scene controlled by KPL button H. Also the Program that detects all switches Off would need those additional switches added to the list of devices in the If statement if those devices should also control the Program operation. As far as Insteon is concerned the world is flat. Only those devices that are explicitly defined as responders to a Scene are controlled by the Scene. As I mentioned before, Scenes do not cascade. Turning a KPL button Off does not cause the responders of the KPL button to turn Off. Lee

ingeborgdot Is there a button on the KPL downstairs for each switch it controls or does a single button control multiple switches (like KPL button H). If the later, a single KPL button that controls multiple switches, simply replicate what you did for KPL button H for the downstairs KPL button. If there is a one for one relationship, one KPL button for 1 switch, then simply cross link the switch and KPL button. Make the KPL button and the switch Controllers of the same Scene. This arrangement keeps both devices in Sync. If there is a one for one relationship and the KPL button turns the switch On/Off but the switch does not turn the KPL button On/Off the KPL button is linked as a Controller and the switch is linked as a Responder only. The switch needs to be both a Controller and a Responder in a one for one relationship. The ISY automatically makes a device a Responder when it is defined as a Controller of an ISY Scene. Lee

Scene commands DO NOT cascade. Sending a Scene On/Off to a KeypadLinc button does NOT cause the responders of that KPL button to turn On/Off. Any devices that you want to turn On/Off need to be responders of the Scene.

"Part of the problem is there is no way to do variable-to-variable assigment, so that limits things you could otherwise do." Is this what you want to do with variable to variable If Control 'REMOTELINC-2 / REMOTELINC-2 - 3' is switched Off Or Control 'REMOTELINC-2 / REMOTELINC-2 - 2' is switched Off Then $SVar1 = $IVar1 Else - No Actions - (To add one, press 'Action')

There is absolutely nothing wrong with being an external only user. Many users are very happy staying with the externals, never crossing over to the dark side. For those who want to expand into understanding "how" things work, “why†they work the way they do, analyzing the Event Trace Insteon commands and associated responses, it is necessary to move into hardware publications where the terminology is different. Even the insteondetails.pdf document on the insteon.net site does not mention the term Scene, everything is in the context of a Group. One might wish the left and right hand used the same words but that is not the Insteon reality. Engineers look at the world one way, peddlers look at the world differently. Nature of the beast.

The term Scene and Group are synonymous. If a person’s background is the Insteon hardware, the term Group is what is understood. The term Scene does not appear in the Insteon Command document or the PLM development guide. From the hardware side everything is a Group. When a button/paddle is pressed a Group protocol message sequence is initiated with a Group number in the message identifying the button/paddle pressed. If a person’s background is from an external view point only then Scene is what is understood. All the sales related documents and the Smarthome web pages discuss Scenes. Bottom line, a Group is a Scene is a Group.

ingeborgdot Some basic things to check Be sure the Save Changes button was clicked to make the Programs active Are the Programs marked Enabled When the basement light is turned On does the Admin Console show the Current State as On for the basement light Cycle the basement light Off to On as if the light was already On before the Program was saved it needs to detect a change in status to run If the Current State is On what does the “last run time†column say for the Program that turns On the KPL button H Scene Lee EDIT: do not not worry about it. We were ALL at one time where you are now. Asking questions is one way to learn. Some really nice things can be done with the ISY once you get the hang of the basics.

ingeborgdot The Program would have If Status switch A is Off and Status switch B is Off and Status switch C is Off Then Set scenekplH Off Lee

ingeborgdot If KeypadLinc button H should turn On and Off ALL the basements light switches, an ISY Scene with KPL button H as a Controller and all the basement light switches as Responders. If any basement switch turning On should also turn On KPL button H, a Program that checks the Status of all the basement light switches, turning On an ISY Scene that has KPL button H as a Responder when any basement switch is On is needed. Another Program which checks that all basement switches are Off and turns the ISY Scene Off that has KPL button H as Responder. Defining the objective would be good if the above does not cover what you are looking for. Lee

ingeborgdot Define an ISY Scene, right click on KeypadLinc button H, select Add to Scene…, add the KPL button as a Responder. In the Program select Insteon, from the device/scene pulldown list select the ISY Scene defined above, select On or Off to turn Scene On/Off which will turn Secondary KPL button H on/off. Lee

ingeborgdot In addition to the Program approach. you can create a Scene where both the KPL button and the switch controlling the basement lights are defined as Controllers of the Scene. In this way both the KPL button and the switch can control the basement lights and both will indicate when the basement light is on. If there are multiple switches involved in controlling the basement lights the Program is perhaps a better approach. Remember that if the KPL button is a Secondary button, it will have to be a Responder in a Scene and the Program turn the Scene On/Off to control the KPL button LED. Secondary KPL button LEDs cannot be turned On/Off directly. Lee

Michel It does the same thing with the On button. It is timing related, how quickly the button presses are done rather than the number of times pressed. I'll go through the trace again later today with fresh eyes. I’m sure this is not a functional issue with the ISY, simply an information message question. Lee

Thanks Michel The scenario being used and traced is a RemoteLinc button 3 Off press which sends Group Broadcast messages and a Group Cleanup message to the ISY PLM. Standard Group protocol sequence which is not in question. What the OP is looking at (I can recreate on my system) and considered a failure by the OP (which it is not) is sometimes the Event Trace has an additional DOF 3 entry in the trace following the Group Cleanup Direct message. Most of the time the DOF 3 message does not appear in the event log after the Group Cleanup Direct message .The Group Cleanup Direct messages themselves are valid and expected, just have not been able to determine why the additional DOF 3 message appears in the trace at times. It is going to be one of those embarrassing cannot see the forest for the trees once I figure it out. In the following Event Trace there is a RemoteLinc button 3 Off press with the expected Group Broadcast messages and a Group Cleanup message, all as expected. At the end of the sequence there is no DOF 3 message in the trace after the Group Cleanup Direct message. This is the case most of the time. If the RemoteLinc button 3 Off is pressed multiple times close together, sometimes the Event Trace contains a DOF 3 message added after a Group Cleanup Direct message. Sun 05/22/2011 04:12:24 PM : [iNST-SRX ] 02 50 11.AD.CF 12.9F.E4 41 13 03 LTOFFRR(03) Sun 05/22/2011 04:12:24 PM : [standard-Cleanup][11.AD.CF-->ISY/PLM Group=3] Max Hops=1, Hops Left=0 Sun 05/22/2011 04:12:24 PM : [iNST-ACK ] 02 62 0D.4B.82 0F 14 00 06 LTOFF-F(00) Sun 05/22/2011 04:12:25 PM : [iNST-SRX ] 02 50 0D.4B.82 12.9F.E4 2B 14 00 LTOFF-F(00) Sun 05/22/2011 04:12:25 PM : [standard-Direct Ack][0D.4B.82-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sun 05/22/2011 04:12:25 PM : [iNST-ACK ] 02 62 12.A9.F9 0F 14 00 06 LTOFF-F(00) Sun 05/22/2011 04:12:25 PM : [iNST-SRX ] 02 50 12.A9.F9 12.9F.E4 2B 14 00 LTOFF-F(00) Sun 05/22/2011 04:12:25 PM : [standard-Direct Ack][12.A9.F9-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sun 05/22/2011 04:12:25 PM : [iNST-ACK ] 02 62 12.B4.E1 0F 14 00 06 LTOFF-F(00) Sun 05/22/2011 04:12:26 PM : [iNST-SRX ] 02 50 12.B4.E1 12.9F.E4 2B 14 00 LTOFF-F(00) After the following Group Cleanup Direct message from the RemoteLinc there is an additional trace entry “DOF 3â€. Sun 05/22/2011 04:13:15 PM : [iNST-SRX ] 02 50 11.AD.CF 12.9F.E4 47 13 03 LTOFFRR(03) Sun 05/22/2011 04:13:15 PM : [standard-Cleanup][11.AD.CF-->ISY/PLM Group=3] Max Hops=3, Hops Left=1 Sun 05/22/2011 04:13:15 PM : [ 11 AD CF 1] DOF 3 Lee

eximer168 I do not know why the ISY chooses to annotate some Group Cleanup Direct messages and not others. The Group Cleanup Direct messages that are annotated look the same as those that are not. I see the same situation on my system. I was able to screen capture one of the popups (banners). It is an outbound Fast Off command which would not normally be written anywhere. Perhaps something to do with the Beta but that is only a guess. Assuming the IO Linc address is 15.E5.18, the outbound command to turn the relay On was issued Fri 05/20/2011 11:45:01 AM : [iNST-ACK ] 02 62 15.E5.18 0F 11 02 06 LTONRR (02) with no ACK being received from IO Linc. Since the relay did not turn On I have to conclude the command did not make it to the IO Linc. Lee