LeeG

There have been some users reporting devices turning On that I think have been resolved by replacing the PLM. Unless it is a finger check the post indicates running a 99i which would have to be at 3.3.10 with an Admin Console at 4.2.2. That opens up all kinds of questions as to the results.

I would take Michel conclusion as fact. I did not see the issue controlling my water valves but that may not have had the factors Michel was discussing.

Was that topic related to not being able to assign multiple relays to a Scene?

Here is ISY Scene with 3 EZIO8SA relays.

That is the procedure for reloading the existing PLM. Here is the Wiki link (section 6.1) for replacing PLM. http://wiki.universal-devices.com/index ... _.28PLM.29 NEVER Delete Modem (PLM). Neither rebuilding old PLM link database (first case) nor replacing PLM (second case) will lose any programming. Be sure to have a current ISY backup. Rebuilding the old PLM link database takes a few minutes. Replacing the PLM is a much longer process because every device has to be changed to the new PLM address. Do not worry about the battery devices when initially replacing PLM. After initial work is complete all the battery devices will be marked with pending operations. Put ONE battery device into linking mode and select Write Updates to Device. When that battery device update is complete take it out of linking mode, put the next battery device into linking mode and do a Write Updates to Device. Proceed one battery device at a time being sure to take the current battery device out of linking mode before proceeding to the next.

Multiple EZIO8SA relays can be controlled (turned On/Off) with an ISY Scene.

I used rainbird valves with hose connections on the input and output side. Google "rainbird valve". They run on 24v AC with low current draw. If memory is correct I had 5 or 6 valves feed from the outside water line. Only ran a few valves On at any given time as they were supplying a few sprinkler heads on each line. With soaker hoses several could be turned On at once. Depends on the amount of water available.

These Programs are not set up to handle multiple KPL buttons. One Program concludes the button is On, the other concludes the button is Off. That does not relate to having multiple buttons where one button is On and the other button is Off. I suggest waiting until the original author comes back from vacation and can redesign the Programs.

Post the Program(s). ANDing multiple KeypadLinc buttons does not sound correct. More likely they need to be ORed with existing logic. Placement of parens is also important. Also how were the additional KPL buttons added to the Scene(s).

With this example the Program is triggered each time the Motion Sensor sends an On message, and at 10 PM and 6AM. The Then clause executes between 10PM and 6AM when the Motion Sensor sends an On message. The Time triggers (10PM and 6AM) will always evaluate as False because "If Control" will not exist at those exact times. If Control 'Motion Sensor' is Switched On and From 10:00PM to 6:00AM Then Do It Else -

Both from/to and from/for are evaluated twice. Once at "from time" which will be True if no other conditions and once at "to time"/"for end time" which will be False. The from/to and from/for are simply two ways of establishing a start time and an end time. The from/to establishes specific times (sunrise and sunset would vary of course). The from/for establishes an ending time relative to the from time.

A False Folder prevents the Programs under the Folder from executing.

Right click on the Blue Load Controller entry in the Scene. Select Remove from Scene to remove Load Controller from Scene. Then drag the Load Controller back to the Scene and drop it. Click the Controller/Responder button to change Load Controller entry to Controller and click Ok.

pauliep Strongly urge NO manual linking. The ISY will not be aware of that link and it will eventually be overwritten by ISY. Also any Device Restore of the KeypadLincs or Load Controller will eliminate the manual link. The two KeypadLinc buttons and the Load Controller should be in the same ISY Scene as Controllers (as Red nodes). That way no matter how the Load Controller is turned On the KeypadLinc buttons should come On.

"Can a KeypadLinc communicate with an ISY-994i?" Certainly.

Do you have an actual security system or the ISY is performing as a security system? Search the Smarthome site for siren. Several will be presented. My security system runs on 12v DC so any small 12V DC power supply will power the siren. The KeypadLinc Relay is the simple choice since no load is being controlled. There is only one I/O Linc. Whether an ISY can do this depends on who manufactured the security system if there is one.

The 99i is End of Life. Check the UDI web site for the upgrade offer to a 994i. KeypadLincs cannot be added to a 99i as SmartLabs changed the device identifier (cat/subcat) of KeypadLincs well after the 99i firmware was frozen.

Okay. If unable to diagnose further then wait until the next release.

The OP is running an Admin Console that is 5-6 releases back level. I think it best to get he system at a level where it should be and then see what symptom remains. I suspect windows going to sleep may be an issue since the ISY is consistently sending device state changes to an Admin Console that is not responding. I would expect that could result in the IP connection closing if the Admin Console is really not responding (asleep). If the admin console continues to lock up the windows system should not be allowed to sleep to see if that helps.

Under Java there are three check boxes on the Delete popup. The third check box that deletes the Applications has to be checked. When the Icon you are using is deleted go to the 4.2.2 announcement and select the option you prefer. Likely either d. http://isy.universal-devices.com/994i/4.2.2/admin.jnlp - Java application or Dashboard - http://isy.universal-devices.com/994i/4 ... board.jnlp

The Admin Console is down level compared to the ISY Firmware. Clear the Java cache including the Applications and start the 4.2.2 level of Admin Console.

Exit the Admin Console and invoke again. The device Insteon address is already defined to the ISY. Click on My Lighting, click Address column heading to sort by Insteon address. Check the Insteon address label on the Hidden Door Sensor. Make sure 8's are not B's, etc

A KeypadLinc backlight level is setting how bright ALL the KPL buttons are when turned On. The setting affects ALL buttons, not just one button. Define a Scene with KPL buttons A and B as Responders. Have the Program that is triggered by button C turn this Scene On to turn On buttons A and B.

Scenes produce less traffic for sure. A Scene On or Off uses a single Insteon command no matter how many Responders in the Scene. A Scene can be less reliable than Direct commands if the Insteon network is marginal in areas. A Direct command has multiple retries, a Scene has no retries. I would try using a Scene to see if it is reliable. If there are Insteon network issues that cannot be resolved go back to Direct commands.

There is no camera support in the ISY. The Network Module is sending messages to the camera(s) but that is the general capability of the Network Module. Nothing specific for cameras.