Jump to content

LeeG

Members
 View Profile  See their activity

  • Posts

    12943

  • Joined

  • Last visited

 Content Type 

Everything posted by LeeG

  1. LeeG
    kenibi The Scene and device name are the same. Suggest changing name of Scene or device to a unique value. Then run level 3 trace suggested by jerlands <html><font color="red">----- Outside Garage Lights Test Results -----</font></html> <html><font color="red">[Failed]</font> Hall Keypad B (17 A3 84 2)</html> <html><font color="red">[Failed]</font> Master Keypad Window - E (17 A3 D8 5)</html> <html><font color="red">[Failed]</font> Outside Garage Lights (17 53 3C 1)</html> <html><font color="red">----- Outside Garage Lights Test Results -----</font></html>
  2. LeeG
    Smartlabs has changed the way the newest Leak Sensors work (remaining in Wet state). They rarely explain why a device is changed. I assume so that a Wet condition requires user intervention. Otherwise an intermittent leak could go unnoticed. You may be remembering what happens when tested with the Set button which is not a real leak condition.
  3. LeeG
    First the UI is down level, Install the 4.3.26 UI (Admin Console). Step 4.a of the 4.3.26 topic has UI install procedure. The Heartbeat node issues a message every 24 hours (approx) under normal operation. It will be Blank until first Heartbeat message. The Leak Sensor battery is expected to last 10 years so battery is not likely an issue. Older Leak Sensor devices will cycle from Dry to Wet to Dry if the environment goes Wet and then Dry. The newest Leak Sensors go Wet and remain Wet even if the environment goes back to Dry. What is the firmware level of the Leak Sensor? A Program like this will monitor Heartbeat. If a Heartbeat message is not received in 25 hours send an email, turn On a device, whatever action you chose for a missing Heartbeat. HeartBeat - [iD 0044][Parent 0001] If Control 'Leak Sensor-Dry / Leak Sensor-Heartbeat' is switched On Or Control 'Leak Sensor-Dry / Leak Sensor-Heartbeat' is switched Off Then Wait 25 hours some action of choice to alert for missing Heartbeat. Else - No Actions - (To add one, press 'Action')
  4. LeeG
    Note that resetting the KPL does not cause it to enter 6 button mode if the device was manufactured as an 8 button device. Also a Device Restore will not put it into 6 button mode. Use the procedure in the User Guide to set to 6 button mode. The ISY has no function for changing a KPL button mode.
  5. LeeG
    The update to 4.4.2 ISY Firmware and 4.4.2 Admin Console is done manually. The automatic update is to move to the latest Official ISY Firmware which is 4.3.26 that you are already on.
  6. LeeG
    Cormacs Sound like a Direct command is being sent to the I/O Linc Relay. Direct commands do not use the rules normally associated with the three Momentary modes. It must be a Scene On or Scene Off for the Momentary rules to apply.
  7. LeeG
    Cormacs Normally using Momentary B with a Scene that has the I/O Linc Relay as a Responder resolves the button problem. Using Momentary B allows Relay to turn On and move door whether the Scene is sent an On or Off from the button.
  8. LeeG
    The My Programs folder is created by the ISY. The Condition in that folder is not expected and not defined by ISY. Delete the Condition in the My Programs folder. =================================================================================== My Programs - [iD 0001][Parent 0000] Folder Conditions for 'My Programs' If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Allow the programs in this folder to run.
  9. LeeG
    I have some pretty old Insteon devices that have not had problems. Try using New INSTEON Device rather than Start Linking. Enter Insteon address, Name of your choice, and leave Auto Discover. The newer Insteon devices have a different linking command sequence. I have not seen the newer command sequence cause problems with older devices. No need to press Set button on device being added unless a battery powered device which you would not be using with the 026. What type device have you been trying to add to the 994i? Did you run the 4 tap beacon test?
  10. LeeG
    The device to be added has the Set button pressed for 3-5 seconds. This should not leave the device in linking mode. The PLM may not be in contact with device being added. Are the 2 120v legs coupled? If the PLM is put into beacon test (4 taps of PLM Set button, are the coupling devices responding with one on the opposite 120v leg?
  11. LeeG
    Did you identify which device to add to the Linking in Progress popup? The first popup should have been the Linking in Progress popup. What does Help | About show for Firmware? UI?
  12. LeeG
    Difficult when the most logical means (Admin Console) is not used. Is this for a customer or your personal use?
  13. LeeG
    "I want to get that exact data during the day" Here is what it looks in day time. I don't think it is giving you what you need. <nodeInfo> <node flag="0"> <address>14 C1 C7 2</address> <name>MS I2CS-Dusk.Dawn</name> <parent type="1">14 C1 C7 1</parent> <type>16.1.65.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <pnode>14 C1 C7 1</pnode> <ELK_ID>I12</ELK_ID> <property id="ST" value="0" formatted="Off" uom="on/off"/> </node> <properties> <property id="ST" value="0" formatted="Off" uom="on/off"/> </properties> </nodeInfo>
  14. LeeG
    The REST command for checking State of Dusk-Dawn node is http://192.168.2.2/rest/nodes/14 C1 C7 2 <nodeInfo> <node flag="0"> <address>14 C1 C7 2</address> <name>MS I2CS-Dusk.Dawn</name> <parent type="1">14 C1 C7 1</parent> <type>16.1.65.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <pnode>14 C1 C7 1</pnode> <ELK_ID>I12</ELK_ID> <property id="ST" value="255" formatted="On" uom="on/off"/> </node> <properties> <property id="ST" value="255" formatted="On" uom="on/off"/> </properties> </nodeInfo> The Motion Sensor being accessed is in a dark space so Dusk-Dawn is On
  15. LeeG
    A few points to consider to get the process started.. Jumper 5 only should be in place. The Motion Sensor is configured for Night operation which means it needs to be dark in the area the Motion Sensor "sees". Since you are using a time range in the Program probably better not to set Motion Sensor for Night operation. The Scene definition should have TriggerLinc Responder set to 25% On Level. The Program will trigger on Motion On within the time range assuming no Night mode. Also will turn Off TriggerLinc 2 minutes after last Motion On received during time range. If On Sat, Sun, Mon, Tue, Wed, Thu, Fri From 4:20:00PM To 5:20:00AM (next day) And Control 'Master Bed Room / Mstr Bedroom-Sensor' is switched On Then Set Scene 'Master Bathroom / Mstr Bath Night Light' On Wait 2 minutes Set Scene 'Master Bathroom / Mstr Bath Night Light' Off Else - No Actions - (To add one, press 'Action')
  16. LeeG
    Link table looks good. The PLM looks like it is in that category of possible failing capacitors so the Responder link in the PLM for Dusk-Dawn could be missing. Could verify the Responder link (starts with A2, Group 2, with Motion Sensor address) is in PLM. If the PLM has the required Responder link the Motion Sensor itself is in question. I verified that 4.4.2 is showing Dusk-Dawn Off and On. Although the next string of Betas after 4.3.26 there were no changes for MS Dusk-Dawn.
  17. LeeG
    Here is sample of Motion Sensor link table. Link 0,1,2 are required for the three Motion Sensor functions to communicate with PLM.
  18. LeeG
    It needs to be absolutely black for more than 3.5 minutes for Dusk-Dawn to change. Was the Motion Sensor put into linking mode before setting Night mode? Can check link record table to be sure there are 3 E2 link records pointing to the PLM.
  19. LeeG

    Is Switchlinc Toast?

    LeeG replied to SteveSBE's topic in ISY994

    Would need to see Event Viewer at LEVEL 3 of each failure to be sure. The posted trace shows no device response to the four attempts to get a Set-MSB command to respond. I would put device on extension cord and plug into PLM location and event trace trying to add device. Posted trace could indicate a comm issue or a failed device.
  20. LeeG
    Post 24 has All On Off Scene.
  21. LeeG
    Blackbird I have not been able to relate posted Log entries.to the Programs. If this type event happens with any regularity suggest having Event Viewer at LEVEL 3 running for a few minutes before the activity begins so detail information can be collected and posted.
  22. LeeG
    What does Help | About indicate for Firmware? UI?
  23. LeeG
    larryllix Sorry but a little confused. You have received/triggered a Program that is looking for Low Bat but got no notification?
  24. LeeG
    Blackbird Since the I/O Linc Sensor could not be affected by the All On Off Scene directly, I would look at the Log before what is posted in post 1. Also something invoked the All On Off Scene which also adds to the areas to examine. You've indicated the All On Off Scene has no reference to the I/O Linc so something else is communicating with that device Sensor and Relay.
  25. LeeG
    Blackbird The I/O Linc Sensor Status was logged before I/O Linc Relay which suggests something else moved the door. The I/O Linc Sensor is a Controller only node, not changed by an Insteon command.
×
×
  • Create New...