Jump to content

slammers

Members
  • Posts

    9
  • Joined

  • Last visited

slammers's Achievements

Newbie

Newbie (1/6)

0

Reputation

  1. I just upgraded from a isy944i to an EISY. I restore my backup and things were working until I updated the EISY from 5.7.1 to 5.8.0. Now when I try and login to the Admin Console on my I get an error saying my admin console version 5.7.1 is not compatible with EISY firware 5.8.0. How do I upgrade the Admin Console?
  2. So I ended up doing the factory reset but now I am getting a popup error saying it can not open a config file. Does anyone know how to fix this issue?
  3. Thanks for the reset link. I was trying to find that. I was hoping not to have to go to that extreme as I did not want to lose the programs and network configuration. But I guess I will have to do this as I have not found a solution for these rouge devices. I may try and restore my backup and delete again and see if that helps before I go there.
  4. No All the folders are empty. The steps I took was to remove all devices from the sub folders. Then I could delete the device under my lighting. So now all folders are empty including My Lighting but those 4 devices still show up when I click on the My Lighting node. When I start the program it tries to communicate with those four devices as well and I get four communication error alerts I have to close.
  5. I recently moved and left all my Insteon light switches behind but did take my ISY944i and PLM with me. I removed all my devices using the Admin console but for some reason when I click on the My Lighting node I still see 4 devices. These do not show up on the tree view, only in the detail pain. When I use diagnostics->PLM Links table its empty When I use diagnostics->ISY Links table I can select one of these four devices and it shows the link table for each. I do I remove these last 4 devices??
  6. Yes. Jumper 5 is shorted. I have tried sensitiviy values of 30, 50, 80, 100, and the original value was 128. I have tried night mode check box both ways. Does that check box disable the function of that feature? I was hoping I could get the motion sensor to work at all times and still use the light sensor state in programs for another purpose.
  7. I have three motions sensors, 2 are v1.1 and 1 is v2.0. The 2.0 sensor never has status for dusk/dawn. They all show up in my list as v.00 as bellow. (isy version 3.1.13) The Foyer sensor is a 2.0 version and the current state of the DuskDawn is always blank. I have performed a factory reset on it, removed and re-added to the ISY multiple times, adjusted the light level setting to numerous different values, but nothing seems to fix the problem. Anyone know why this may be?
  8. I moved the Or of the state variable outside the bracket and this works. So it seems that the problem is the Control check statement Control 'Sensors / Motion Entrance-Sensor' is switched On is re-evaluated once the scene is turned off and is resulting in false. I guess this makes sense I just do not understand why if I turn the light off alone the program worked but if I turned the scene off it does not. btw I have actually been testing it with a different trigger. I have been using an IRLinc to trigger the program instead of my motion sensor. Shawn
  9. I am new to ISY programming and have been struggling with this simple program. I would like my front entrance motion sensor to turn on my front entrance light for 30 seconds but only if the light is currently off. If the light is on I do not want to motion sensor to turn it off. So I wrote this program which does work If ( Status 'LightSwitches / Front Entrance Switch' is not On Or $EntranceMotionActive is 1 ) And ( Control 'Sensors / Motion Entrance-Sensor' is switched On ) And From Sunset To Sunrise (next day) Then $EntranceMotionActive = 1 Set 'LightSwitches / Front Entrance Switch' On Wait 30 seconds Set 'LightSwitches / Front Entrance Switch' Fast Off $EntranceMotionActive = 0 Else - No Actions - (To add one, press 'Action') I had to add the state variable because without it the then clause would stop running as soon as the light was turned on. So setting the state variable to 1 just before turning on the light holds the program status to true. So I then changed the program as I have a keypad link also connected to the front entrance and I wanted its button light to also turn on. If ( Status 'LightSwitches / Front Entrance Switch' is not On Or $EntranceMotionActive is 1 ) And ( Control 'Sensors / Motion Entrance-Sensor' is switched On ) And From Sunset To Sunrise (next day) Then $EntranceMotionActive = 1 Set Scene 'Front Entrance' On Wait 30 seconds Set Scene 'Front Entrance' Fast Off $EntranceMotionActive = 0 Else - No Actions - (To add one, press 'Action') With this code the program runs, the front light turns on as does the Keypadlinc light, but the then clause stops immediately so the wait does not happen and the lights never turn off. I have confirmed that the variable is set to one so I do not understand why the program exists prematurely. Is it a problem with the scene being turned on to soon after the variable is set one so the OR condition is failing? So I added a 5 second delay between setting the variable and turning off the scene and as soon as the scene is turned off the program exits. Is this a bug? I am running firmware 3.1.13 Thanks Shawn
×
×
  • Create New...