LeeG

Controlling the pump is not a problem. Smarthome has a 220/240 Load Controller that is powered from 220/240 V (no neutral required) and is Dual Band (sends/receives RF signals as well as powerline). http://www.smarthome.com/2477SA2/INSTEO ... and/p.aspx So control is easy without any wiring changes at the pump/well site. It is monitoring current flow on the pump circuit (pump running) that is the challenge. Assuming there is nothing else on the pump circuit and it is supplied from the house, there are electrical devices that monitor current flow and have an output that can control an Insteon device inside the house. When the device inside shows the pump running for an extended period the Load Controller at the pump site can be commanded to turn the pump circuit off. Could also connect the Load Controller in the house and have it shut off the line going to the well/pump location. A search of the internet for such current monitoring devices should yield several possibilities.

andyf0 Thanks for posting the solution. Apologies, I somehow missed your initial post. The Scene versus Direct commands to the IO Linc Relay is also documented in the following post. http://forum.universal-devices.com/view ... highlight= Lee

rgn2000 With the Trigger Reverse set, when the Sensor physically turns ON the IO Linc sends an Off command. When the Sensor physically turns OFF, the IO Linc sends an On command. The Green LED near the IO Linc connections shows the physical ON/OFF state of the Sensor. It is not affected by the Trigger Reverse option. Trigger Reverse simply reverses the On/Off commands sent by the IO Linc. There is nothing wrong with the instructions and sample Program. It works as the original author wanted it to. That implementation did not anticipate a Query being part of day to day operation. One solution is to stop Querying the IO Linc. Another solution is below. If you used the Smarthome garage kit it came with a magnetic sensor that has both a NO and NC switch built in. Simply use the other wire (red instead of green or green instead of red) from what you are currently using and turn the Trigger Reverse Off. That will restore the IO Linc to default operation where the Query result will match the default ON/OFF state and On/Off command. Note that when changing the Trigger Reverse option and magnetic switch connection it is necessary to cycle the magnetic switch (open/close the garage door) to get the IO Linc in sync with the new setup. Lee

rgn2000 Do you have the IO Linc set for Trigger Reverse? If so that is the answer. Trigger Reverse does not reverse the Query results. Lee EDIT: the default operation of the IO Linc is to send an ON command when the Sensor turns On and an OFF command when the Sensor turns Off. Trigger Reverse reverses that. An OFF command is sent when the Sensor turns On and an ON command is sent when the Sensor turns Off. Trigger Reverse does not change the basic Sensor On/Off operation relative to the Sensor being connected to GND or not. Query is returning the true On/Off state of the Sensor, not the reversed ON/OFF commands.

musicmatters Can you expand on what you are doing when "programming" the ISY? Defining/changing Scenes where the dimmer is in the Scene? Changing dimmer settings such as Local On and/or Local Ramp Rate ? Working with other Insteon devices unrelated to the dimmer? Does the dimmer otherwise work as expected? Turns On/Off/Dims the load with the paddle? Responds to Scene if in a Scene? Controls a Scene if a Controller in a Scene? What type of load, incandescent bulb, CFL, etc. Is it ramping from Off to Full On to Off or changing bright level? How fast is the ramp rate? I know there are lots of questions but it may save the number exchanges. It is not normal for an Insteon device to behave as you have indicated. Could be a wiring problem particularly being in the application of a light in a fan where wiring can be complex. Do you have a meter where the line and neutral connections can be verified? Lee EDIT: there is a reported problem with the Dual Band Dimmer being affected by the Ted 5000 powerline communication. See the following topic http://forum.universal-devices.com/view ... ker+dimmer

Okay. Will not work without link records. Perhaps the Input cycling interfered with the New INSTEON Device processing. Delete the device. Run Tools | Diagnostics | Event Viewer with Device Communications Events selected and the add the device to the ISY. Save the Event Viewer Log file. Try the Input test by opening and closing the I1- GND connection and see if that causes an Input state change. If not send the Event Viewer Log from the device add to lwgwork@embarqmail.com or post the log file

No problem. Link database display is still garbage. I'm sure this is the result of the analog inputs cycling because they are not locked On or Off. The constant traffic from the EZIO2X4 is interfering with the link database display. Look at my post just above your typo post.

Actually things are getting better. I missed the flashing LED in your last post. The links are likely correct and AN1 and AN2 (Inputs 3 & 4) are cycling because they are not locked to GND. Connect AN1 and AN2 to GND. That will stop the Input cycling (LED flashing). AN1 and AN2 operate in digital mode (ON/OFF) by default or Analog mode. Because they can operate in analog mode there are no pullup resisters built into AN1 and AN2. Either lock AN1 and AN2 to GND or with 2 1/4 watt 10K resisters connect AN1 and AN2 to +5V. Connecting to GND will lock AN1 and AN2 ON. Connecting AN1 and AN2 to +5V through the pullup resisters will lock AN1 and AN2 OFF. Sorry I missed the flashing LED the last time.

I tested 3.1.0. All worked as expected. The Show Device Links Table is correct and the Input state changes are reflected in the My Lighting display. That link database display is garbage. Try moving the EZIO2X4 to a different plug point and display the link database again. Not sure if the link database is not displaying correctly or was not written correctly.

The lack of any link records does look like the ISY did not know it was an SHN device when it was added. There is code specific to SHN devices that must be run when a device is added to the ISY which is run only when a specific SHN Device Type is entered. I'll also update to 3.1.x and verify nothing has regressed.

oskrypuch What ISY firmware level are you running? SHN device support requires the SHN device be added to the ISY with one of the 2.8.x images specify the explicit Device Type of EZIO2X4. You are correct about -9 representing Input 1, -A represents Input 2 and so on. The lack of messages from the EZIO2X4 Inputs indicates a problem with the link records either in the EZIO2X4 or ISY PLM (assuming wiring correct and on a 2.8.x release). Try a Tools | Diagnostics | Show Device Links Table. Confirm that an E2 entry exists with a Group number of 09,0A,0B and 0C. Lee

robin71 The 220V Load Controller would be a natural choice as it switches 220V as well as sense the load drawing current. Unfortunately no one has been able to get a Load Controller that has working load sensing. The switching of 220V is rock solid on the Load Controller so that aspect can be used. A simple solution is wire a 220V relay in parallel with the pump motor circuit. The relay is energized when the pump is running. Connect the relay contacts to an IO Linc Sensor so that the Sensor signals On when the pump is running. By triggering a Program with the Sensor On message it should be possible to establish a Wait for whatever duration is considered a failure. When a failure is detected a 220V Load Controller can be controlled to turn the pump circuit off completely. The Program can also generate an email alert. Lee

Do you have an ISY-26 or ISY-99?

Traditore Although the RemoteLinc has no Responder function it does receive RF messages. Every Group command sent from the RemoteLinc must receive an ACK message from the controlled device(s). Lee

I ran the same test with the same positive result. Manually linked an ICON Dimmer to a RemoteLinc All On button. ICON Dimmer turns On/Off with the All On and All Off buttons. The Group number in both link records is 255 as expected. The RemoteLinc was originally added specifying the specific Device Type so the firmware is listed as v00. Would be nice if the ISY fixed that aspect of adding a device to the ISY with a specific Device Type and picked up the firmware level during that flow.

Gadgetfreak Your conclusion is right on. The parentheses make no difference in the execution of two simple statements ORed together. Sometimes adding parenthesis makes it easier to follow the AND/OR relationships even when no actual change to the logic is accomplished. It can also eliminate the need to know/remember order of precedence between AND/OR. In this simple case there is no real advantage to that. The Wiki has a good article on parentheses and order of precedence. http://www.universal-devices.com/mwiki/ ... tion_Order Lee

No. Insteon devices do not send messages on a power up. A house full of Insteon devices all trying to send messages when power comes back on would be near impossible to manage.

oskrypuch My 2450 IO Linc does the same thing. The relay is Off after a power cycle regardless of the state of the Relay when power goes off. matapan My IO Linc Relay does not turn On during a power cycle. Tried Latching Mode and the 3 Momentary modes. I would assume the Relay turning On is the result of a Program action if the door movement is related to the IO Linc and not the door opener itself. My garage door openers are controlled by EZIO2X4 relays which never open or close the garage doors because of a power failure. Lee

My I/O Linc does not maintain a Relay On state across a power cycle. Tried it three times. Each time the Relay is Off after a power cycle. The ISY would not be aware of this until a Query because the device does not present status when it powers up. Have not tested any of my EZIO2X4s but expect the same result. EDIT: same result with one of my EZIO2X4s. All Relays are Off sfter a power cycle. Lee

andyf0 What may not be obvious to someone just starting out with Insteon, ISY and Scenes, when multiple Controllers are assigned to an ISY Scene, under the covers the ISY is actually defining multiple Insteon Scenes. Where SwitchLinc A and SwitchLinc B are assigned to an ISY Scene as Controllers, three Insteon Scenes are defined. Scene 1 has SwitchLInc A as Controller, Scene 2 has SwitchLinc B as Controller, and Scene 3 has the ISY PLM as the Controller. The statement that an Insteon Scene has only 1 Controller is correct. An ISY Scene can have multiple Controllers because an ISY Scene is composed of multiple Insteon Scenes. Lee

garybixler The link records are stored in the 2412S PLM, not the EZIO8SA. It is not normal to have to restore the PLM after a power cycle. Lee

Do you know the technique the HS plugin uses to keep track of device status. A few days ago a user was having problems adding a TriggerLinc because the I2 Extended commands were not working correctly. Motion Sensors are dependent on the same commands. The problem was resolved by unplugging the tstat adaptor. It looks like the tstat adaptor problem is also interfering with Extended command communication in some way. Might not be your motion sensor problem but worth a try unplugging the tstat adapter and see if motion sensors can be added.

Steve The link record at 0FF8 is created when the device was added to the ISY. The entry at 0FF0 that starts with 00 is the end of list marker (remainder of data is irrelevant). There are no Scene link records in this device. The new PLM is being used as it is connected to the Serial port of the ISY. The question is whether the ISY is aware of the PLM change. The Tools | Diagnostics | PLM Info/Status display should show the new PLM address. Lee

Under Tools | Diagnostics | PLM Info/Status, does this show the new or old PLM address. If the new PLM address, pick a device that is not responding to a Scene = run Tools | Diagnostics | Show Device Links Table. The link records that have a PLM address, is it the new or old PLM address. If the new PLM address, run Tools | Diagnostics | Show PLM Links Table. The device that is not responding to the Scene, does that device address appear in a link record that starts with an E2, has the Scene Group number, and has the device address.

Jeff That is correct. Some history around the wording. At 2.8.3 additional V2 Motion Sensor option support was added to that popup. At that level the text was as it is now. In hind sight the On Only option when checked would be more logical to have On Only commands but that is not what the popup text said at 2.8.3 and the code worked as the text described. At 2.8.11/12 (don't remember the exact image) the text was reversed for the On Only option BUT the code was not changed. The effect was the Motion Sensor was set opposite to what the text said. The solution was to put the text back the way it was or change the way the code worked. At 2.8.15 the text was restored to the way it was at 2.8.3 which is the way the code has worked all along. It looks like the User Guide was changed back when the text was changed around 2.8.11/12. When the text was restored at 2.8.15 so the text and the code are in sync the User Manual was not updated. I just checked the operation of the motion sensor On Only option at 2.8.16. The current popup text matches the way the code works. When the On Only option is checked the motion sensor issues ON and OFF commands. Not sure if this explanation helps or just adds to the confusion. Lee