LeeG

Smarthome did sell a water detection probe in an I/O Linc package but it was unreliable and was withdrawn. Don't think they have found a reliable sensor to put together another leak detection I/O Linc package but that would be one place to look. SH has lots of I/O Linc packages which now may contain a reliable leak detection device. Simplehomenet carries a Dakota Alert Universal Transmitter/water sensor combination that was working well for me. I used it to detect high water washing over the dock to prevent a pump from being damaged. I've since relocated the pump so I no longer use that combination anymore but it was working well during tests. It is a somewhat expensive combination if you do not already have a Dakota Alert system to receive the RF signal from the Dakota Alert Universal Transmitter. It is also battery powered so you have to remember to replace the 9V battery about once a year. I wanted a battery based solution in case power to the dock was lost due to a GFCI trip.

It is only a guess at this point but I'm thinking something does not complete fully during that PLM change. Every link in every device that points to the PLM has to be rewritten to change the Insteon address to reflect the new PLM address and of course the links in the new PLM itself have to be established. If something in this process does not occur on either end the Insteon device will not be able to communicate paddle/button activity to the PLM. I would feed your configuration information into the UDI tool for estimating PLM link record counts to see if it exceeds the 1000 number for the 2413 PLM. You may have to Restore the other devices that no longer communicate paddle/button activity.

However, the end result is hard to explain. Deleting the KPL should have freed up the link records associated with the KPL. Adding it back would have written the new link records back into the same slots or maybe other deleted slots. It would not push otherwise active links out. Have you replaced the PLM lately.

Maybe. There is a UDI tool that estimates the number of PLM link records. Run the tool with your configuration and see what the tool estimates the link record count to be. http://www.universal-devices.com/tools/insteon/calc_plm_links.htm

It does not sound like a communication problem if you can reliably control the KPL load button from the ISY Admin Console. The KPL has to ACK the Insteon Direct command so two way communication seems to exist. When an Insteon device is not presenting the Group On/Off command when the paddle/button is pressed (assuming no communication problem) it is either a missing link in the device (KPL) or the PLM. You have restored the PLM. Try restoring one of the KPLs. The next step would be to “Show†the links in the KPL and the PLM to confirm the needed links between the KPL and PLM exist. It might be easier to follow Michel suggestion and Remove the KPL and add it back to the ISY. This would reestablish the links in both the KPL and the PLM. If the Remove/Add of the KPL does not resolve the problem, Remove/Add it again with the Event Viewer at change level 3 active to trace the link creation process during the device add.

me23 You can have as many EZFlora devices as necessary. They each have a unique Insteon address. There is no means of coordinating multiple EZFlroa devices so if Zone 8 is controlling a "Pump†you would need Zone 8 on each EZFlora to control the same pump. I believe (although not absolutely sure) that relays are NOT used to energize a zone valve. The electronic component in the EZFlora for controlling each Zone valve might read as a Zone valve problem by the other controller if connected in parallel with the other controller. Certainly do not know that to be a problem. The controller I had before using EZFlora had some detection circuit if a valve circuit did not present the expected resistance. Discovered it when the pump control relay went south. The controller went dark when trying to turn on the pump. Easy enough to pull the plug connector on the EZFlora should a parallel connection turn out to be a problem for the old controller and you wanted to go back to that controller for backup. I have not tried to connect my old controller and EZFlora in parallel. Lee

Billy, The Insteon 6A Get Zone Information command being used by the ISY to Query values in the tstat adaptor returns temperature values that are X2 the actual value. The 6A command spec’s this characteristic. It means that temperature values require an X 0.5 conversion to get the correct temperature value. Although the 6A command spec does not mention this for the humidity value it is possible that the humidity value being returned is also X2 the actual value and has to have the same X 0.5 conversion to get the correct humidity. Knowing what the thermostat is displaying for the humidity value compared to the value being returned to the ISY with the 6A command (is the value X2 the actual value) may answer this question. It is further confusing because the values returned by the 6A command are in hex so they first have to be converted to decimal and then X 0.5 applied. I don’t have a Venstar thermostat. Can you confirm that the humidity value being displayed on the thermostat is the “indoor†humidity. Thanks Lee

You do not have to delete the Scene, just Remove the Responder from the Scene. Then add it back as a Controller. If it is defined as a Controller it is assumed to also be a Responder. Only if you no longer want it as a Controller and a Responder (that is you want it only as a Responder) would you need to Remove a Controller and add it back as a Responder.

When the second tap turns the responder Off it means it was not done quick enough to generate a Fast On command. All Insteon devices will generate a Fast On command when the paddle/button is pressed twice quickly. If the Fast On is generated it will defeat what you are trying to accomplish because a Fast On brings all the linked responders to Full Bright at a fast ramp rate. Of course you can override that with programming and bring the responder back to a dim level. You may also want to think about changing the KPL button to non-toggle On mode. In this mode the KPL button always generates an On command rather than Toggling between On and Off. So long as you have linked responders to the KPL button for the immediate response that results in you will have to consider what commands the KPL button press is going to automatically generate and what the linked responders will do with those commands.

Managing links and creating Scenes are the same activity. The combination of any two products trying to do the same job is problematic. The ISY strongly recommends against using anything but the ISY for Scene/link management. HouseLinc2, being a Smarthome product, is more tolerant of creating Set button links outside of HouseLinc2 but there is a performance price for this. HouseLinc2 scans a device for the current link setup before making changes to allow for Set button links. Makes Scene/link management more complex and slower. Stick with the ISY as the only Scene/link manager - IMO.

Try thinking about a Program Folder like a subdirectory. Only in the ISY case you can assign Conditions to a Program Folder (subdirectory). Only if the Conditions assigned to the Program Folder (subdirectory) are True will the Program Conditions (of the Programs in the Program Folder) be evaluated.

Run the Event Viewer in Change level 3 mode and issue the query. An invalid value coming back would indicate an adaptor problem.

Mike, If the device does not work when plugged into the PLM circuit that does not necessarily mean it is DOA. Another Event Viewer with level 3 will show if the device address is responding in any way. It might not add due to the later firmware/PLM level which would be different than not responding at all in the previous Event trace. Lee

I would factory reset this device. Connect it to a 3-wire appliance cord from any home improvement store. They have a plug on one end and bare wires on the other. Connect the black Line and white Neutral wires. Cap the red load wire, it is not necessary for this test. Plug the appliance cord into the same circuit as the PLM. The device address has an 8 in it. Make sure the label does not specify a B. The device could be a DOA but that is very very rare. Using the appliance cord, powering the device from the same circuit as the PLM eliminates many of the possibilities. Since nothing came back from the device address the ISY has no information about the devices firmware level, etc so there is no possibility the ISY/PLM is at fault (assuming you do have communication with other devices). If the device works on the appliance cord then how it is/was wired at the current install location, how well the 120V legs are coupled, lot of questions at that point. If the device fails to respond plugged into the same circuit as the PLM, after a factory reset, and the correct device address is being used, contact Smarthome support and report a DOA.

There is NO communication with that device address. All Insteon commands attempted failed to generate any response from device.

You need to click on the Change level button on the bottom of the Event Viewer window and select level 3 in the popup that is displayed. The Event Viewer results posted do not show the level 3 detail necessary to analyze the problem.

If adding the device failed using the Start Linking method you can try adding it using New INSTEON Device option. If you bring up the Event Viewer and set Change level to 3, then do the device add, I can interpret the trace. It will show if there is a general communication problem with the device or something specific to that firmware/PLM level. Be sure to set Change level to 3.

Have you tried the Link Management | Start Linking method.

mdyod The IOLinc output relay is operating in the default Latching mode. It is the same thing that happens when the manual door opener button is held pressed, none of the other manual opener buttons work. Unfortunately when I went to check on the Get Operating Flags command (the first command in the Event trace) my document does not include the IO Linc device so I cannot verify the content of that command nor the content of memory location 0x0033. All the commands were ACKed so it is not an issue with the communication with the IO Linc. Michel, Someone on your end will have to look at the Event trace for the GOF command content and memory location 0x0033 content to see if the correct values are being used for Momentary C. It has been verified that the IO Linc is in Latching mode as leaving the output Relay On prevents the manual door opener button from working. Any of the Momentary modes (even if it was not Momentary C) would allow the manual door opener button to work once the Momentary mode time value expired.

Bring up the Event Viewer with Change level: 3 and do the Set Options function again. I would like to the see actual commands the ISY is issuing to establish Momentary C. It would also be helpful to know if the manual door control button works when the output relay is turned On and left On.

If you turn the output relay On and leave it in the On state can you use the manual door control button to control door movement. If the IOLinc is in the default Latching mode leaving the relay On should prevent the manual door control button from controlling door movement. If the manual door control button works with the output relay On from the ISY perspective then it is in Momentary A mode. How did you establish Momentary C mode for the output relay.

There were multiple symptoms in the initial post. The sensor was not reporting status and the output relay might not have been in the expected momentary mode. The sensor eventually worked which was thought by the OP to be interference from a near by transformer. Not sure the output relay mode was resolved. What symptoms are you experiencing versus expectations.

I have the same browser problem with IE8 on XP. I've seen it on 2.7.15 and all images since then. Happens about 1 in 8-10 times doing an image update. I cancel the IE session with the task manager with no adverse effects. Regarding the Load Controller, the post refers to it as a "Normally open" load controller, the type number is for the "Normally closed" load controller. Which type is it?

I got the RS232 version this time as I want to test it for compatibility as a standard 2412S equivalent. No reason to think it is not a direct swap for a 2412S. The RS485 version should provide the added distance I need to connect to a remote pump house but have no Serial port that supports RS485 at this point. Hope to put an EZFlora with a pulse water meter on the subdivision well to track water consumption.

Thanks Brian. I'll search for that discussion. Almost a mute point now since the 2412S is discontinued. SHN has started selling a 2412S equivalent, EZICOMM. I received my first last week but have not done any testing with it as yet.