LeeG

I am surprised that the v.28 EZFlora works at all on 3.3.10. That version of EZFlora is I2CS (I have one) which I did not think the 3.3.10 Admin Console would accept. What does Help | About show for Firmware and UI levels. I'm concerned a later level Admin Console is being used on 3.3.10 ISY. The EZFlora could be on the opposite 120v leg as the PLM. Can the EZFlora be plugged into the same circuit as the PLM? With the possibility the Admin Console level may be an issue along with what looks like a comm issue it is hard to know which direction to pursue. Run Tools | Diagnostics | Event Viewer at LEVEL 3 and trace a few EZFlora zone On/Off commands. It may help direct where the corrective action should be taken.

Can you indicate which codes you are looking for additional infor, Insteon itself, ISY info.

Is this on the 99i or the 994i? If the 994i what ISY firmware and UI is being used? (Help | About) How far away is the EZFlora from the PLM?

Did not mean that no information is available. See this Wiki section http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Using_the_Event_Viewer

Not that I have seen. One of the issues is that to understand the event viewer requires a knowledge of Insteon. I doubt UDI ever plans on that level of information. Need to look at SmartLabs documents to learn/understand Insteon.

"So does this mean I won't be able to use a scene, but rather a program to shut the water off in the event of a flood/leak detected?" Correct. The Leak Sensor does not send a Dry Off nor a Wet Off. It sends Dry On or Wet On only at your firmware. Later firmware sends a Wet On only. The latest Leak Sensor firmware does not cycle back to Dry On if the condition goes back to Dry.

Wed 09/23/2015 09:38:17 AM : [iNST-SRX ] 02 50 2E.09.48 00.00.02 CF 11 02 LTONRR (02) - Group 2 (Wet) - On 11 Wed 09/23/2015 09:38:17 AM : [std-Group ] 2E.09.48-->Group=2, Max Hops=3, Hops Left=3 Wed 09/23/2015 09:38:17 AM : [D2D EVENT ] Event [2E 9 48 2] [DON] [2] uom=0 prec=-1 Wed 09/23/2015 09:38:17 AM : [ 2E 9 48 2] DON 2 Wed 09/23/2015 09:38:17 AM : [D2D EVENT ] Event [2D 1 8E 1] [sT] [255] uom=0 prec=-1 Wed 09/23/2015 09:38:17 AM : [ 2D 1 8E 1] ST 255 Wed 09/23/2015 09:38:17 AM : [D2D EVENT ] Event [2E 9 48 2] [sT] [255] uom=0 prec=-1 Wed 09/23/2015 09:38:17 AM : [ 2E 9 48 2] ST 255 Wed 09/23/2015 09:38:17 AM : [D2D-CMP 0064] STS [2E 9 48 2] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> true Wed 09/23/2015 09:38:17 AM : [D2D EVENT ] Event [2E 9 48 1] [sT] [0] uom=0 prec=-1 Wed 09/23/2015 09:38:17 AM : [ 2E 9 48 1] ST 0 Wed 09/23/2015 09:38:17 AM : [D2D-CMP 0064] STS [2E 9 48 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Wed 09/23/2015 09:38:17 AM : [iNST-SRX ] 02 50 2E.09.48 00.00.02 CF 11 02 LTONRR (02) Wed 09/23/2015 09:38:17 AM : [std-Group ] 2E.09.48-->Group=2, Max Hops=3, Hops Left=3 Wed 09/23/2015 09:38:17 AM : [iNST-DUP ] Previous message ignored. Wed 09/23/2015 09:38:18 AM : [iNST-SRX ] 02 50 2E.09.48 33.5E.55 45 11 02 LTONRR (02) Wed 09/23/2015 09:38:18 AM : [std-Cleanup ] 2E.09.48-->ISY/PLM Group=2, Max Hops=1, Hops Left=1 Wed 09/23/2015 09:38:18 AM : [iNST-DUP ] Previous message ignored. Wed 09/23/2015 09:38:18 AM : [iNST-SRX ] 02 50 2E.09.48 11.02.02 CF 06 00 (00) Wed 09/23/2015 09:38:18 AM : [std-Group ] 2E.09.48-->11.02.02, Max Hops=3, Hops Left=3 Wed 09/23/2015 09:38:18 AM : [iNST-INFO ] Previous message ignored. Wed 09/23/2015 09:38:18 AM : [iNST-SRX ] 02 50 2E.09.48 11.02.02 CF 06 00 (00) Wed 09/23/2015 09:38:18 AM : [std-Group ] 2E.09.48-->11.02.02, Max Hops=3, Hops Left=3 Wed 09/23/2015 09:38:18 AM : [iNST-INFO ] Previous message ignored. Wed 09/23/2015 09:38:21 AM : [iNST-SRX ] 02 50 2E.09.48 00.00.01 CB 11 01 LTONRR (01) - Group 1 (Dry) - On 11 Wed 09/23/2015 09:38:21 AM : [std-Group ] 2E.09.48-->Group=1, Max Hops=3, Hops Left=2 Wed 09/23/2015 09:38:21 AM : [D2D EVENT ] Event [2E 9 48 1] [DON] [1] uom=0 prec=-1 Wed 09/23/2015 09:38:21 AM : [ 2E 9 48 1] DON 1 Wed 09/23/2015 09:38:21 AM : [D2D EVENT ] Event [2E 9 48 1] [sT] [255] uom=0 prec=-1 Wed 09/23/2015 09:38:21 AM : [ 2E 9 48 1] ST 255 Wed 09/23/2015 09:38:21 AM : [D2D-CMP 0064] STS [2E 9 48 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> false Wed 09/23/2015 09:38:21 AM : [D2D EVENT ] Event [2E 9 48 2] [sT] [0] uom=0 prec=-1 Wed 09/23/2015 09:38:21 AM : [ 2E 9 48 2] ST 0 Wed 09/23/2015 09:38:21 AM : [D2D-CMP 0064] STS [2E 9 48 2] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> false Wed 09/23/2015 09:38:21 AM : [iNST-SRX ] 02 50 2E.09.48 00.00.01 CF 11 01 LTONRR (01) Wed 09/23/2015 09:38:21 AM : [std-Group ] 2E.09.48-->Group=1, Max Hops=3, Hops Left=3 Wed 09/23/2015 09:38:21 AM : [iNST-DUP ] Previous message ignored. Wed 09/23/2015 09:38:21 AM : [iNST-SRX ] 02 50 2E.09.48 33.5E.55 45 11 01 LTONRR (01) Wed 09/23/2015 09:38:21 AM : [std-Cleanup ] 2E.09.48-->ISY/PLM Group=1, Max Hops=1, Hops Left=1 Wed 09/23/2015 09:38:21 AM : [iNST-DUP ] Previous message ignored.

The DON 4 is the Heartbeat test message. If there is a pause between taps whether the DON 1 or DON 2 test is sent, the DON 4 will follow. This is the expected response. Latest Leak Sensor firmware does not send the Heartbeat test message with the Set button.

Although the ISY marks the Wet node Off the Leak Sensor did not send that command. The Leak Sensor sent a Dry On so the ISY marked the Wet node Off. Marking the Wet node Off in the ISY does not generate a Scene Off command. You can run a LEVEL 3 event viewer to see that the Leak Sensor did not send an Off message for the Wet node.

haroldlunger Here is an example of an 8 button KPL that was changed to 6 button mode before adding to ISY. Note line two on right side indicates 8 button, there are only 5 nodes generated by ISY. Even though the factory type indicates 8 button, ISY also checks KPL configuration information that indicates 6 button (5 nodes). Your situation would be the reverse, line two may indicate a factory 6 button KPL but the ISY will generate 8 nodes. I looked for the opposite case but I normally order 8 button KPLs.

haroldunger The ISY does not change the KPL from 6 button mode to 8 button mode. This must be done at the KPL using the procedure in the Owners Manual. Once done add the KPL to the ISY (after deleting the 6 button definition). It may carry the "2334-232" 6 button type (if the latest I2CS KPL) but it will have 8 nodes (rather than 5 nodes) if the manual change to 8 button mode was successful.

File | Backup ISY. A popup will prompt for location to write backup file.

" Will setting the scene "on" cause these lights to ramp up at the scene ramp rate to the scene "on" level?" Yes, if I understand correctly what the various sliders are set to. "Will telling them to "fade up" cause them to ramp up at the local ramp time to the local "on" level?" Fade Up command is paired with a Fade Stop. The Fade Up ramp rate is something like 0.2 or 0.3 seconds (from memory). which is built into the device firmware. All devices have the same Fade Up/Down ramp rate. The device will Fade Up/Down until device receives a Fade Stop or 100%/0% reached. A Fade Stop should always be issued. Fading a device by pressing a button/paddle will always end with a Fade Stop.

If the I/O Linc Sensor remains On longer than the Momentary hold time the I/O Linc will turn Off the Relay when hold time expires. However, if the Sensor turns Off before hold time expires the "Relay follows input" will turn the Relay Off when the Sensor turns Off. I think another set of devices may work better. Perhaps the Micro On/Off module which has a Latching mode would not turn Off when the Open/Close module changed states (operate in 2 node mode). The Micro Module turning Off would then be under control of an ISY Program where Wait times could be refreshed and how quickly the ISY Program responded would not be a factor.

The "Relay follows input" option does cause the Relay to turn On when the Sensor turns On. Unfortunately that means when the Sensor turns Off so does the Relay. The Open/Close module does not remain On for the entire trip on the stairs so the Relay will open and the stair lights go out while a person is still using the steps.

From the I/O Linc Owners Manual Momentary A Either an ON or OFF command can be programmed to trigger the I/O Linc relay. The other command will be ignored. For example, if an ON command is programmed to trigger the relay, an OFF command will be ignored Momentary B Send either an ON or an OFF command to trigger the I/O Linc relay. The I/O Linc relay will respond to both.

Momentary A - either the On command or the Off command will turn the Relay On but ONLY ONE command, either On or Off, is functional. Momentary B - either On or Off command will turn Relay On. Both commands work. EDIT: my I/O Linc Relays will not act as a Responder to a Scene with the I/O Linc Sensor as Controller. I have one or two KPLs that have the same limitation.

If the desire is for button A to turn On when ON is pressed then button A could be included in SceneX. There can be an issue with that but lets assume it works. Turning button A On or Off with a Scene is not affected by the toggle/non-toggle on/off mode of the KPL button. What is needed is input from the OP as to how button A should react.

larryllix The OP did not request ON button to turn On button A. The posted requirement is for the OFF button to turn Off button A. Of course if the actual requirements are different the solution would be different.

With the I/O Linc Relay nor garage door opener functional I have to think the Relay is not connected to the correct location. Can you post a picture of where the Relay wires are connected

Inside the multi button garage door opener where the open/close button connects to the PCB?

The garage door opener has multiple buttons. The I/O Linc Relay cannot be connected to the wires going to the opener. The Relay wires need to connect to the actual open/close button inside the opener. Also the I/O Linc may be in Latching mode as the garage door opener will normally operate after the Relay turns Off in one of the Momentary modes.

"KPL Floor Dimmer 6" is the ON/OFF buttons - On commands from ON button press and Off commands from OFF button press are reflected in this KPL node. SceneButtonA has KPL button A as Responder When the OFF button is pressed the Program is triggered as True running Then. The Wait in the Then allows the Off processing of all devices before sending the command to turn Off button A. This Wait time may need to be increased if a large number of devices is being turned Off by OFF button. ButtonAOff - [iD 002B][Parent 0001] If Control 'KPL Floor Dimmer 6' is switched Off Then Wait 5 seconds Set Scene 'SceneButtonA' Off Else - No Actions - (To add one, press 'Action')

" I added one first. The device showed up in the top level of the tree, with Insteon address. I clicked on it and selected replace with" The "Replace with" is done against the old device, not the new one. The new device is identified later in the "Replace with" processing. The old device Insteon address is not sent any commands as it could no longer exist or able to respond to commands. When the "Replace with" processing is done the Admin Console terminates. When the Admin Console is restarted the old device name is still there but with the Insteon address of the new device. The new device no longer exists, it is automatically deleted.

Timeout affect depends on other settings. Sensing mode: checked - MS sends an On command for each motion detected. Starts new Timeout interval On Only mode: checked - MS sends On and Off commands - Off command when Timeout expires Night mode: checked - MS functions regardless of ambient light With the options as posted the MS will Timeout only when no motion sensed for 10 minutes; the MS sends an Off command when Timeout expires because no motion sensed; MS operates all day EDIT: no Program is required