Eisy programs not being triggered, thinks lights are off

[dbwarner5]

Simple motion detector program turns on my office lights. Have had this program running for >8 years. 

Suddenly yesterday and today, it's not working. Yesterday I picked any line of the program, hit update and then save and all went back to normal. 

today, after it working fine for several hours, it suddenly stopped again... after the lights were auto turned off for lack of motion. 

Program one: 

Office Motion On - [ID 0122][Parent 0132]

If
        From    Sunrise -  1 hour 
        To       9:30:00PM (same day)
    And (
             'MD Office' is switched On
        )
    And (
             'Office Desk' Status is Off
          Or 'Office Cans' Status is Off
        )
 
Then
        Set 'Office' Fast On
 
 

Program two:

Office Motion Off - [ID 0176][Parent 0132]

If
        'MD Office' Status is Off
    And (
             'Office Cans' Status is not Off
          Or 'Office Desk' Status is not Off
        )
 
Then
        Wait  10 minutes 
        Set 'Office' Off
        Wait  1 second
        Set 'Office' Off
 

Notice that the second program is running its THEN right now, even though the lights are off.

And that the EISY knows the lights are off: 

 

Strange.

If you comment, please dont comment on the programs, or other ways or better ways to do it. This set up works and works just fine. The EISY is not reading the data correctly. That seems to be the issue. 

I can see the MD getting triggered

But program one reads this as FALSE, because it thinks the lights are on. Then when the MD goes to OFF, program two turns true, because again, the EISY thinks the lights are on.  The lights are not on. 

I just did this again..<"I picked any line of the program, hit update and then save and all went back to normal. "> and BAMM.. they work just fine again. 

Is the EIsy corrupting itself?  

 

 

 

Edited January 10 by dbwarner5

[Geddy]

47 minutes ago, dbwarner5 said:

Is the EIsy corrupting itself?  

Uh oh! Since it's done it more than once I might open a support ticket to possibly get a deeper dive into the system to see what's going on. Haven't seen this myself, but I don't run motion sensors. 

[Guy Lavoie]

First thing to try with any motion sensor related issues is try a fresh battery.

[dbwarner5]

 Not really sure it’s a motion sensor issue. 
 

as I noted: the motion sensor is turning on and off as expected. I can watch it in UDM 

But the program doesn’t trigger because the eisy thinks the lights are on even though it’s reporting off and is physically off as shown in my screenshots 

but will change the battery next time it happens 
 

Edited January 11 by dbwarner5

[IndyMike]

@dbwarner5, another possibility is that your program became corrupted.  I ran into this a week ago and had a difficult time finding/fixing the problem.

My program is shown below next to the actual XML that my ISY994 was running.  They didn't match.  The RED scene control is incorrect in the XML.  What I saw in the program editor was correct and no number of saves, copy to a new program and saving, etc would correct it.

I corrected the program by deleting the "Set Basement/ SC Basement On" statement, saving the program, and then adding the statement back.

My example dealt with a "then" action that was incorrect.  I could SEE that the program was turning on the wrong scene.  You may have a corrupt "IF statement".  That would be much more difficult to determine.

You could export the program XML and inspect it for errors (somewhat painful), or simply rewrite the program.

 

 

Program	Program XML
If	<if><and />
'19.21.5C.1' is switched Off	<control id="DOF" node="19 21 5C 1" op="IS"></control></if>
Then	<then>
$FirstDining.On  = 1	<var id="11" type="2"><op>EQ</op><val prec="0">1</val></var>
Wait  5 seconds	<wait><seconds>5</seconds></wait>
Set 'Basement / SC Basement' On	<cmd id="DON" node="46453"></cmd>
Wait  23 seconds	<wait><seconds>23</seconds></wait>
$FirstDining.On  = 2	<var id="11" type="2"><op>EQ</op><val prec="0">2</val></var>
Set 'Basement / BSMT Back Room' Off	<cmd id="DOF" node="B B7 F8 1"></cmd>
Set 'Basement / BSMT Back Room Load' Off	<cmd id="DOF" node="16 5C BF 1"></cmd>

[dbwarner5]

Agree. Thst is why it worked again once in”updated” a line and then re-saved it. 
 

am more concerned about the WHY and are other programs also corrupted and how to find them. 
 

thanks

[IndyMike]

10 minutes ago, dbwarner5 said:

Agree. Thst is why it worked again once in”updated” a line and then re-saved it. 
 

am more concerned about the WHY and are other programs also corrupted and how to find them. 
 

thanks

I'm sorry, I'm not being clear...  The following is my guess based on my recent experience with the ISY994 -

Your program is not triggering properly because it is not saved properly.  Said differently, the program that you posted is not what is saved in XML.  It was corrupted some time back and "updating/re-saving" is not changing/fixing the corruption.  I saved and copied my program several times to no avail.  The XML was still wrong.

When you re-save, you are resetting the "last run" status and the state (true/false) of the program.  It's possible that is allowing the program to trigger once.  Can't tell you why without seeing the XML. 

I don't understand what I did to screw up my program.  It was an isolated case.  I had been editing the program frequently throughout the day.  The program is very long with numerous embedded waits. Suddenly it began to execute things that I couldn't explain.  That's what drove me to look at the XML code.

Edited Sunday at 06:21 PM by IndyMike

[dbwarner5]

How do you look at the xml file?

[IndyMike]

Right click on the program and "Export" to a file, or "Export to Clipboard".  You resulting file is a jumbled mess.  You can manually insert carriage returns using clipboard, or find a quick XLM viewer on the web.