LeeG

Xathros can help with the programming to limit to a single notify. It is not unusual for the Leak Sensor to cycle between Wet and Dry even when sitting in water. Using a Wet sponge will not provide enough conductivity between the metal sensors to keep the Leak Sensor in a solid Wet state. Even water varies in conductivity depending on the mineral content.

Another user found Start Linking did not work (New INSTEON Device does work) due to a bad PLM. Take a look at the following topic as it may help in identifying if your PLM has a problem. viewtopic.php?f=27&t=11969

Settings can be changed from the ISY only if it is on an external power supply. Otherwise it sleeps to conserve battery power. I have an older 2441ZTH which Humidity readings jump around, changing by a few % often. May not be an issue with later 2441ZTH firmware.

Thanks James. Appreciate you taking the time to post back the resolution. There is another user who mentioned he was not able to get Start Linking to work. That was not the primary complaint but he may also have a bad PLM. Now the challenge is to find his original post. Good luck with the rest of your ISY activity. Hope you find it as good an experience as most of us have.

Having multiple PLMs in the same house is not a problem. I have several PLMs that are active at the same time. I also have two ISYs that are currently active at the same time (not sharing devices). The PLM is like any other Insteon device in that it repeats Insteon messages it receives that are not specially sent it. The PLM chip in a PLM device is the same PLM chip in other 120v Insteon devices. Sharing devices will be a problem. Neither ISY knows about the other which nets down to multiple HA applications trying to manage the links in the same device. That has not worked with combinations such as HouseLinc and ISY trying to manage the same devices. Link records are deleted, overlaid, etc. There is a user on this forum that is using the Network Module to send REST commands between two ISYs but devices are not being shared.

If Status 'xxxxx' is On triggers the Program when the device turns On. Status has to change so the Program does not trigger because the device is On but because the device was turned On. The Program triggers when the device is told to turn On regardless of how. Could be paddle/button, could be Direct command or Scene command from a Program or the Admin console.

If Control looks at commands flowing from the device (paddle/button press). Turning a device on by another controller (PLM when done from the Admin Console) does not trigger a Program with If Control as no commands flow from the device.

Local On Level and Local Ramp Rate affect the device where the paddle is pressed. When the Slave SwitchLinc paddle is pressed On the Local On Level and Local Ramp Rate affect how the Slave SwitchLinc reacts. How the Master SwitchLinc reacts to the Slave SwitchLinc paddle On press is based on what is in the Responder Link Record for On Level and Ramp Rate stored in the Master SwitchLinc link database. I suspect for whatever the reason there is a Responder link record in the Master SwitchLinc left over from the manual Set button linking. Defining a new ISY Scene creates new link records which are later in the Master SwitchLinc link database. The Master SwitchLinc searches its link database for a record that matches the Slave SwitchLinc Insteon address when the Slave SwitchLinc paddle is pressed. I think it finds the old Set button link record and stops the search at that point. The Show Device Links Table would confirm this. A Show Device Links Table can be issued for the Master SwitchLinc followed by a click of the Compare button to compare what is actually in the device versus what the ISY thinks should be there.

GPG Clear the Java cache and insure the URL being used to invoke the Admin Console is for 4.0.5. The Admin Console at 3.3.3 would not know anything about the Dual Band KPLs as they had not been released. After the changes click Help | About and verify the UI indicates 4.0.5

GPG What does Help | About show for UI line?

Right click a SwitchLinc node, select Diagnostics | Show Device Links Table. Post the image. Do the same thing for the other SwitchLinc Identify the Insteon addresses of each SwitchLinc and whether it is the Master or the Slave. Were the existing Set button links created before using the ISY maintained when the devices were added to the ISY or was the default option used 'erase existing links'?

The Slave SwitchLinc paddle will only turn On the Master SwitchLinc with Fast On? OR The Master SwitchLinc paddle will only turn On the Slave Switchlinc with Fast On?

An ISY Scene consists of one or more Insteon Scenes. Each Controller in an ISY Scene represents one Insteon Scene with its own unique set of Responder On Level and Responder Ramp Rate values. Click on the Red slave SwitchLinc node name below the ISY Scene name. The other SwitchLinc (the master) will have a unique On Level and Ramp rate that is in effect when the slave paddle is pressed.

Cannot hurt. They can confirm that an invalid PLM response will result in the Start Linking popup being removed. Have you tried a factory reset of the PLM (not the ISY). If you do a factory reset of the PLM a File | Restore Modem (PLM) is required to rebuild the PLM link database.

I traced a Start Linking on my system to double check my memory. It looks like your PLM did not respond to the Start Linking command as expected Tue 07/23/2013 10:50:19 PM : Start Insteon Device Linking Mode Tue 07/23/2013 10:50:19 PM : [LNK-BGN ] 02 64 01 00 06 Tue 07/23/2013 10:50:48 PM : Stop Insteon Device Linking Mode, Final processing to follow Tue 07/23/2013 10:50:48 PM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65) Tue 07/23/2013 10:50:48 PM : [All ] Writing 0 bytes to devices Tue 07/23/2013 10:50:48 PM : [All ] Writing 0 bytes to devices Note the lack of the 06 on the end. The PLM should return an 06 or a 15. The 00 on the end of the message in your trace is not spec'ed. Tue 07/23/2013 08:29:09 PM : [LNK-BGN ] 02 64 01 00 00

The SwitchLinc is an older device (not I2CS) which takes longer to add. The event trace does not show anything abnormal with the PLM when entering Start Linking. It looks like the Admin Console shutdown Start Linking for some reason. What is the level of Java? Check Help | About and verify both Firmware and UI lines indicate 4.0.5.

New Insteon device? Insteon devices do not broadcast their presence so the answer would be no. Of course there is the Start Linking function which looks for a device identification when the device Set button is pressed but that requires a specific device activity (pressing the Set button). Also requires the PLM be put into linking mode to listen for those messages which is what happens when Start Linking is invoked.

LEVEL 3 is an option on the Event Viewer display.

The PLM can be tested by running Tools | Diagnostics | Event Viewer at LEVEL 3. Select Link Management | New INSTEON Device, enter the Insteon address of a device, Name of choice, Device Type at default Auto Discover. Click Ok. Post the event trace. If nothing appears in the event trace something is blocking the ISY pushing data to the Admin Console. If there is a PLM issue I would expect to see it in the event trace.

That generally means Start Linking was done before, the first Start Linking Popup did not display because of a firewall or AV problem so the Finish button cannot be clicked to terminate Start Linking. The PLM will timeout of linking mode but the ISY sits in Start Linking waiting for a device Set button press that will not be seen because the push of data from the ISY to the Admin Console is being blocked by the firewall or AV. Kaspersky, Avast and others by default will not allow the ISY to push data to the Admin Console. Reboot the ISY to clear the Start Linking. Set up the firewall/AV to accept the ISY IP address as a trusted address.

ISY Programs are event driven. The Program with a From/To time will produce a True If section at Sunset which causes the Then clause to run and a False if section at Sunrise which causes the Else clause to run. Issuing a Run Then for the program with the From/To of Sunset/Sunrise will run the Then clause. Issuing a Run If for the same program will result in the Else clause executing because it is not exactly Sunset.

Question 1.. if I set the max value to 50% will the max the light can go on be 50% with the buttons? or will it still go to 100% No. The load will ramp to 100% On if the button is held long enough. The Local On Level (max? don't know what that is) controls what the load does when the button/paddle is pressed on the device physically controlling the load. Reason I ask is because I have criteria (a program) that will turn on the light as well. except i only want the light to go on to 50%. A Direct command specifies the On Level. A Scene controls the On Level with the Responder On Level when the Scene is created. The Adjust Scene statement can alter the value. So in my program, should I set the scene on? or should I set the light on? I can set the light on to any value I want in the program. I assume the scene control will still control the light. Your choice. Direct command affects that specific device. A Scene can control a single device or a collection of devices. Question 2 Can you set a scene on to a certain value? If so how? Or is this value the value you set in the scene ie 50%? so a scene on command will yield 50% but the buttons can still ramp to 100? The Scene On Level is initially determined by how each Responder On Level is set. An Adjust Scene statement can be used to alter each Responder On Level. The Adjust Scene statement changes the Responder link record On Level value. The Scene still has to be turned On after the Adjust Scene statement makes the change to the Responder On Level.

Autonow Correct with one minor point. The Leak Sensor sends only On commands for the Dry and Wet nodes. When the Dry node sends an On command the ISY marks the Wet node Off. When the Wet node sends an On command the ISY marks the Dry node Off. The Heartbeat node does send On and Off commands. On command when the Leak Sensor is Dry, Off command when the Leak Sensor is Wet. Not sure if that makes the mud more dense.

I see no reason to Factory Reset the ISY. Delete the devices that didn't auto detect Make a backup Do a reset on the KPLs (pull out the tab on the bottom of the face for 10 seconds) Pulling the Air Gap switch is the first step in doing a device Factory Reset. After power has been removed long enough for the power supply to drain off press the Air Gap switch all the way in past the level of the frame and hold it for 5 seconds. This amount of time should be verified in the device User Guide. Unplug PLM & ISY wait 30 seconds Plug in PLM & ISY Factory reset (hold in the button on the back right? ) I see no reason to Factory Reset the ISY Will I have to reinstall the 4.0.5 firmware or will that be preserved? No. Restore the backup (all info on the deleted devices should not be in the backup right? ) Start adding devices and see what happens I think the approach to identifying the cause is to run Tools | Diagnostics | Event Viewer at LEVEL 3. Add a device and if it does not add post the trace. A simple way to determine if a device is functional is to connect it to an Appliance cord (plug on one end, bare wires on the other). Plug the Appliance cord into the PLM plug point. This eliminates any question about device install location and verifies the device is functional.

Secondary KeypadLinc buttons cannot be acted upon directly. There is no Insteon command available to turn On/Off a Secondary KeypadLinc button. Define a Scene, assign the KeypadLinc Secondary button as a Responder. Turn the Scene On/Off from MobiLinc. Programs that trigger with an If Status 'kplbutton' is On should trigger fine. Programs that trigger with If Control 'kplbutton' is switched On' will NOT trigger.