Jump to content

clarkes71

Members
  • Posts

    50
  • Joined

  • Last visited

Profile Information

  • Occupation
    Network Infrastructure Manager

clarkes71's Achievements

New

New (2/6)

0

Reputation

  1. If I follow, you are saying that HDS v.43 sends an 'On' (all is good) and HDS v.44 sends an 'Off' (all is good).
  2. I am finally getting around to adding heartbeat programs to my ISY. I have 6 hidden door sensors. All have fresh batteries. ISY was rebooted over 3 days ago and no heartbeat status on 3 of the HDS. After a closer look... all HDS V.43 are reporting 'on' heartbeat status and all HDS V.44 are reporting 'off' ?? Is this a bug or V.44 not supported for heartbeat?
  3. After a device restore from ISY... it now works !?! I find that strange considering a factory reset on KPL, but it is now all good. Thanks!
  4. V 4.6.2 for both UI and Firmware The KPL is and has always been an 8 Button KPL. ISY thinks it is (2334-2) KeypadLinc Dimmer 8 Button v.43
  5. It had been some time since I refreshed my ISY and thought I'd factory reset ISY and Insteon devices. I have a KPL 8 Button that had no problem adding back to ISY. All buttons work normally, meaning I press the button and the LED lights up. However, when looking at ISY, Buttons E-H do not register as being on? In short, buttons E-H do light up when pressed, but ISY current state never goes to on? Buttons A-D work normally.... lost on how to troubleshoot this issue? Bad KPL?
  6. Sent a screen shot of looking at the MorningLinc device in the Admin GUI
  7. If I follow these steps: - Pulled MorningLinc from outlet. Waited 10 seconds. While holding down set button, plug back in. The LED will stay off until you let go (I held it for 20 seconds) and then the LED will come on (no factory reset). If I: - Pull MorningLinc from outlet. Wait 10 seconds. While holding down set button, plug back in. The LED will stay off until you let go (I held it for 20 seconds and let it go). Press and hold the set button (LED flashes fast, slow, etc.). I let the button go after the LED went solid again. Factory reset worked I assume cause the lock is no longer controlled by the MorningLinc. I re-link the doorset with no issues. Pressing set button locks and unlocks door. Next, I try to add the MorningLinc to ISY. Using the 'Start Linking' method (choosing option 3) and pressing the set button. ISY never pops up with found device. Tried Double-tap, single you name it. Nothing. Next, tried to 'New Insteon Device'. Selected option 3 and enter name and address and select MorningLinc device (not auto-discover). It proceeds to read and fully completes process with no errors. This is why I thought problem solved before... however, the controls in ISY to lock and unlock door are still missing? I am running the Alpha 5.0, not sure if that may be the issue?
  8. Mine is also v.42
  9. On the back I have 2 lables: 2458A1 and Rev 1.2 1310
  10. Hey Guys- I've been so busy lately, I haven't had time to reply to this, but I think I have the same MorningLinc as eduardo. I thought the issue was resolved for me, but not so. I get the same thing when trying to factory reset the MorningLinc. Plugging in unit while pressing the set button for 1 minute (any amount of time) does not work. I am still able to control lockset, so that tells me that a factory reset never takes place. So it really boils down to why the MorningLinc is not doing a factory reset?
  11. Worked like a charm... thanks LeeG
  12. When I upgraded my ISY to Alpha Version 5, I decided to start fresh on my home automation network. Been quite a while since I added the MorningLinc to ISY, but when I did, I forgot this... Select the third option 'Add devices found in links and keep existing links'. If you select 'Remove existing links' it removes all links from the MorningLinc and due to the security measures on the MorningLinc the PLM can no longer send commands to it. So now the MorningLinc is added, but I cannot do anything with it. How to correct this? Do I link it with the PLM using the 'set' button on the PLM first?
  13. That will work ! A couple of days ago I removed a variable that I thought was no longer needed... days later I remember it's purpose... using the Find feature will prevent this mistake again. Thanks!
  14. Not sure if this has been asked before, but couldn't locate it.... Is there a way to identify where a variable is being used? or Device? or Program? For example, if I have a variable that I'm not sure where it is being used, how do I locate? If I had a Device that I wanted to remove.... how do I locate all programs it is being used in? etc.
  15. This is the only way I know of to get the current temp to variable. One program for each temp or maybe break up into temp ranges, like temp between 85-90 and set $i.tstat to 87.5 (or something like that). If Status 'Hallway 01 / Thermostat- Main' is 90° (Temperature) Then $i.tstat = 90 Else - No Actions - (To add one, press 'Action')
×
×
  • Create New...