LeeG

After going to 3.2.2 was the SynchroLinc Deleted and added back under 3.2.2.

Does Help | About show 3.2.2 for both the Firmware line and the UI line? How long ago was the SynchroLinc acquired?

The parent Folder had to be True at Sunset +10 minutes for the Program to trigger. Getting the parent Folder into a True condition after Sunset +10 does not cause the Program to trigger. All conditions have to be good (True Parent Folder, Enabled Program) at the exact From time for the Program to trigger.

The ON is Enabled. The Programs will not be triggered until the From time or To time is reached. In a simple If with From/To at the From time the Program will be triggered and the Then clause will run because the If is True. At the To time the Program will be triggered and the Else clause will run because the If is False.

What does the Admin Console show for the firmware level of the SynchroLinc? v.?? The device is not responding with Extended response to the Extended request. What is being used to couple the 120V legs? Pluggable SignaLincs perhaps with black external antenna? Brian. the Extended 2E command is the normal I2 Extended Set/Get. Not unique to I2CS.

First, 3.2.2 should be the beta installed if using 3.2.x. Several fixes and enhancements in 3.2.1/3.2.2 over 3.2.0. Did you export a new ELK file from the ISY and install on the ELK. I think I remember old posts that indicate ELK changes that require a new export and install on ELK. I don't use ELK so this is from memory without benefit of searching old forum posts.

If you are referring to the Programs | Summary page not showing the Folder, try clicking the Refresh button at the top right. A Folder that does not have Conditions specified does not show up. Also Folders appear in collating sequence at the bottom of the list.

If the Folder Status does not show True the Programs under the Folder will not run. Try clicking Save Changes. What ISY firmware is being using. Also the Folder If should be If Status '0F.15.D6.G - Secure Lights' is switched On rather than If Control. With If Control the Folder only triggers when an On command is received. There is no way to turn Status to False.

Look at Programs | Summary for the Status of the Folder. Does it show True or False. If False the Programs in the Folder will not run. Time ranges (From/To) have to cross the From time before the Folder would indicate True. Just being inside the range does not make it True. Suggest posting the Folder and what the Folder Status is.

When one of the KeypadLinc buttons is pressed the FanLinc Fan motor goes to the correct speed but the Admin Console Fan node does not change to show the current speed of the Fan motor? Are you running 3.2.2?

Can anyone confirm that the dongle does report manual changes to the temp settings when done at the tstat. That is the specific case excessivechaos is asking about.

The Insteon address is on the metal face plate of the SwitchLinc. The Decora plastic cover has to be removed but the SwitchLinc itself does not have to be removed. Using the Set button with Start Linking is normally fine. I am pretty sure this is a new I2CS device which requires 3.2.2. There is an exchange between the ISY PLM and the SwitchLinc when the Set button is held long enough to generate the device identifier message. If the SwitchLinc does not get an answer from the ISY PLM the new I2CS devices might blink the LEDs as a positive indicator an answer was not received. These I2CS devices have not been out long enough to know all the things they do in exception conditions. There could be a coupling issue if the new SwitchLinc is on the opposite 120V leg, there could be interference on that specific electrical circuit. The SwitchLinc could be connected to noisy CFLs. The reason for suggesting the use of New INSTEON Device is twofold. If the ISY PLM cannot communicate with the new SwitchLinc some new messages will be seen since the ISY is initiating contact with the SwitchLinc. Also if an I2CS device the Event Viewer trace will show that.

SmartLabs is updating the Insteon protocols. This one is referred to as I2CS because it adds a CheckSum (CS) to some of the Insteon messages to improve message validation. There are other changes as well. Many devices being shipped now require I2CS support. Motion Sensor, FanLinc, SwitchLinc, LampLinc are some of the ones that have surfaced in the last few weeks with I2CS. I expect all the devices will eventually evolve to I2CS.

The KeypadLinc is not likely I2CS. The LampLinc could be I2CS being in the last week or two. I think a better trace would be of adding the LampLinc to the ISY. Delete the LampLinc, run Tools | Diagnostics | Event Viewer with Level 3-device communications events selected. Then add the LampLinc. Just looked at the event trace. Thanks, that answers the question. Device 18.9C.88 is an I2CS device. Move to 3.2.2 to use that device. EDIT: the device will have to be Deleted and added back under 3.2.2

Are you trying to link the device to another using the Set button or are you trying to identify the device for Start Linking. If using Start Linking switch to New INSTEON Device. Enter the device Insteon address, a Name of your choice and leave the Device Type set to Auto Discover. Does the device add successfully. It could be an I2CS device which requires 3.2.2.

What ISY firmware is being used? How recently was the LampLinc and KeypadLinc purchased? Suggest deleting the LampLinc and KeypadLinc from the Scene. Run Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected. Add the LampLinc and KeypadLinc to the Scene, post the event trace.

I don't think going back to 3.1.17 will solve this. Momentary C is dependent of the state of the Sensor as to which commands will cause the relay to react. Is the Relay being commanded with an ISY Scene or direct commands to the Relay? If using a Scene and the I/O Linc is running with Trigger Reverse it could result in the wrong command being used if under ISY Program control and Sensor On/Off is being used to control which command to use. Trigger Reverse reverses the commands the Sensor sends but does not reverse the actual state of the Sensor. If a Query is done the reported Sensor state will change because Query reports the true state of the Sensor not the command reversed state.

What type of problems are you having? I have an I/O Linc in my configuration that works fine on 3.2.2.

It is an I2CS device. I've been running 3.2.2 since it came out Friday and it is stable. The Motion Sensor will have to be Deleted and added back to the ISY under 3.2.2. To post an event trace, save the file (it is a .txt file). Use Wordpad or something similar to edit the trace file. Copy the few lines associated with the MS update and Paste in the post. Being able to read the Motion Sensor but not write to it is one of the ways I2CS shows up.

bfish Is this a new Motion Sensor (just purchased)? What ISY firmware are you running? Sounds like the Motion Sensor requires ISY 3.2.x for the I2CS support. The last Motion Sensor I purchased from Smarthome a few weeks ago is I2CS which requires the 3.2.x beta. 3.2.2 is the latest beta. If you run Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected and try updating the Motion Sensor options I can tell if it is an I2CS device. The reads work okay before 3.2.x but the write of the configuration data requires 3.2.x if this is an I2CS device. Remember to put Jumper 5 back and put the MS into linking mode. As far as On Only mode, it still honors the timeout value before it will send another Motion On message. On Only simply stops the Off command. To eliminate the timeout wait select Occupancy Mode.

I do not have the Network Module so this is only a guess. The Admin Console where you are pressing the Test button is a Java application running on the PC. I suspect the Admin Console issues the network call which would have the source as the PC IP. Code a simple ISY Program that sends the Network Resource (be sure to Save Changes), right click the Program name and select Run Then. That will have the ISY issue the network call with the subsequent ISY IP address. As I mentioned before this is only a conclusion based on reported results rather than knowing for sure.

"Curious if this is a reasonable DIY project." I designed and installed my own irrigation system. Covers about 1/2 acre with 7 zones, no 8 actually. Takes much research to understand water flow rates through the various types of heads and distribution pipe used. I pump from a lake so there was not much room for error with each Zone. Easier if using municipal water system. The physical installation is a chore. Lots of trenching, lots of plumbing and low voltage wiring. Broke it into two phases, backyard, from yard. That worked well. The system works great. Well worth the months of planning and weeks of install. Saved several thousand dollars compared to a professional install. Must have a good plan! Laid out all zones, where all the heads would be, type of heads, head coverage, flow rates, valve locations on scale drawing before ever lifting a shovel. Do not scrimp on heads. A head or two can always be capped off but dry spots are hard to fix. Throwing something in the ground hoping it will work is not the answer. Go with a professional install if a good plan is not possible.

My PLM came with the Serial cable although I did purchase the PLM separate from the ISY.

Thanks for the trace. It is an I2CS device. These devices require 3.2.1. Note that 3.2.2 is projected to be released today (Friday). That is an estimate so it could be a few days past today.

bdw72 What firmware are you running? Are these very new (just purchased) devices? Run Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected. Try discovering one of the new devices. Post the event trace.