Motion sensor to control scene problem

[autoperformance]

Hi everyone, I have issue with a very simple program. I use a motion sensor between 9:30PM to sunrise to turn on exterior lights during 5 min and turn off.

So right now the turn on after motion is ok. The problem is the exterior light never turn off after 5 min. I have strange communication error in the device event.

 

My program :

Back Flood Light - [ID 000E][Parent 0001]

If
        From     9:00:00PM
        To      Sunrise - 30 minutes (next day)
    And Status  'Motion Backyard' is not Off
 
Then
        Set Scene 'Ext Lighting' On
        Wait  5 minutes
        Set Scene 'Ext Lighting' Off
 
Else
   - No Actions - (To add one, press 'Action')

 

 

The Communication EVENT :

 

ven. 04/27/2018 22:05:28 : [INST-SRX    ] 02 50 27.B4.2F 00.00.01 CB 11 01    LTONRR (01)
ven. 04/27/2018 22:05:28 : [Std-Group   ] 27.B4.2F-->Group=1, Max Hops=3, Hops Left=2
ven. 04/27/2018 22:05:28 : [D2D EVENT   ] Event [27 B4 2F 1] [DON] [1] uom=0 prec=-1
ven. 04/27/2018 22:05:28 : [  27 B4 2F 1]      DON   1
ven. 04/27/2018 22:05:28 : [D2D-CMP 0004] CTL [27 B4 2F 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true
ven. 04/27/2018 22:05:28 : [D2D EVENT   ] Event [27 B4 2F 1] [ST] [255] uom=0 prec=-1
ven. 04/27/2018 22:05:28 : [  27 B4 2F 1]       ST 255
ven. 04/27/2018 22:05:28 : [D2D-CMP 000E] STS [27 B4 2F 1] ST op=6 Event(val=255 uom=0 prec=-1) != Condition(val=0 uom=0 prec=-1) --> true
ven. 04/27/2018 22:05:28 : [D2D-CMP 000A] STS [27 B4 2F 1] ST op=6 Event(val=255 uom=0 prec=-1) != Condition(val=0 uom=0 prec=-1) --> true
ven. 04/27/2018 22:05:28 : [INST-SRX    ] 02 50 27.B4.2F 00.00.01 CB 11 01    LTONRR (01)
ven. 04/27/2018 22:05:28 : [Std-Group   ] 27.B4.2F-->Group=1, Max Hops=3, Hops Left=2
ven. 04/27/2018 22:05:28 : [INST-DUP    ] Previous message ignored.
ven. 04/27/2018 22:05:28 : [INST-SRX    ] 02 50 27.B4.2F 3D.96.69 41 11 01    LTONRR (01)
ven. 04/27/2018 22:05:28 : [Std-Cleanup ] 27.B4.2F-->ISY/PLM Group=1, Max Hops=1, Hops Left=0
ven. 04/27/2018 22:05:28 : [INST-DUP    ] Previous message ignored.
ven. 04/27/2018 22:05:28 : [INST-SRX    ] 02 50 27.B4.2F 3D.96.69 46 11 01    LTONRR (01)
ven. 04/27/2018 22:05:28 : [Std-Cleanup ] 27.B4.2F-->ISY/PLM Group=1, Max Hops=2, Hops Left=1
ven. 04/27/2018 22:05:28 : [INST-DUP    ] Previous message ignored.
ven. 04/27/2018 22:05:29 : [INST-SRX    ] 02 50 27.B4.2F 11.01.01 CB 06 00           (00)
ven. 04/27/2018 22:05:29 : [Std-Group   ] 27.B4.2F-->11.01.01, Max Hops=3, Hops Left=2
ven. 04/27/2018 22:05:29 : [INST-INFO   ] Previous message ignored.
ven. 04/27/2018 22:05:29 : [INST-SRX    ] 02 50 27.B4.2F 11.01.01 CB 06 00           (00)
ven. 04/27/2018 22:05:29 : [Std-Group   ] 27.B4.2F-->11.01.01, Max Hops=3, Hops Left=2
ven. 04/27/2018 22:05:29 : [INST-INFO   ] Previous message ignored.
ven. 04/27/2018 22:05:29 : [INST-TX-I1  ] 02 62 00 00 10 CF 11 00
ven. 04/27/2018 22:05:29 : [INST-ACK    ] 02 62 00.00.10 CF 11 00 06          LTONRR (00)
ven. 04/27/2018 22:05:29 : [D2D EVENT   ] Event [23 5F D4 1] [ST] [255] uom=0 prec=-1
ven. 04/27/2018 22:05:29 : [  23 5F D4 1]       ST 255
ven. 04/27/2018 22:05:29 : [D2D EVENT   ] Event [29 C9 82 1] [ST] [255] uom=0 prec=-1
ven. 04/27/2018 22:05:29 : [  29 C9 82 1]       ST 255
ven. 04/27/2018 22:05:29 : [D2D EVENT   ] Event [2B 69 2D 1] [ST] [255] uom=0 prec=-1
ven. 04/27/2018 22:05:29 : [  2B 69 2D 1]       ST 255
 

 

 

Thank you for your help

Jeff

 

[paulbates]

Jeff

I would replace this statement

And Status  'Motion Backyard' is not Off

with this statement

And  'Motion Backyard' is switched on

The MS send multiple messages for each on and off, that cancels the Wait. This will cancel and restart it until the last motion is sensed, then the light is switched off.

Paul

[autoperformance]

On ‎2018‎-‎04‎-‎27 at 10:18 PM, paulbates said:

Jeff

I would replace this statement

And Status  'Motion Backyard' is not Off

with this statement

And  'Motion Backyard' is switched on

The MS send multiple messages for each on and off, that cancels the Wait. This will cancel and restart it until the last motion is sensed, then the light is switched off.

Paul

Hi Paul, first thank you for your help.   I made the changes to the program, but it did not change the behavior of the program.

 

[webminster]

Paul's suggestion is good.  Another thing I'd try is to try to turn on/off a device, not the scene, just to prove it's not a problem with the scene (I've had comm problems where scenes turn on but turn off unreliably).

BTW, what sort of device is in the scene, and what sort of load is the exterior lights?

[paulbates]

It could be the load as webminster suggested. Some loads inject noise in the powerline once powered up that can prevent further communications,  even rf. Can you turn the light on and back off manually using the admin console? 

If you can turn the load and off reliably from the Admin Console, the only other way I know to fix this then is to take the "Then" lines and put them in a separate program that has no 'If' clause. In place of those statements in the original program, put a "run then" program statement calling the other program. That will decouple the actions from the if clause changing. No 100% clear why its needed here but this technique doe solve this kind of issue

Paul

**** Program 1

Back Flood Light - [ID 000E][Parent 0001]
If
        From     9:00:00PM
        To      Sunrise - 30 minutes (next day)
    And Status  'Motion Backyard' is not Off
 
Then
      Run Program 'Back Floodlight 2' (Then Path)  
 
Else
   - No Actions - (To add one, press 'Action')

*** Program 2

Back Flood Light 2 - [.....
If
  - No Condiitons
Then
  Set Scene 'Ext Lighting' On
  Wait  5 minutes
  Set Scene 'Ext Lighting' Off

 

[oberkc]

I agree second program should not be needed if “status” was replaced by “control...on”.  Check program status (between 9 and sunrise).  Status should be true if motion was detected (last run time after 9:00).  Also, make sure you SAVE the he new program (if not saved, it will continue to operate as before).   Feel free to post new program.

[autoperformance]

On ‎2018‎-‎04‎-‎29 at 12:40 AM, webminster said:

Paul's suggestion is good.  Another thing I'd try is to try to turn on/off a device, not the scene, just to prove it's not a problem with the scene (I've had comm problems where scenes turn on but turn off unreliably).

BTW, what sort of device is in the scene, and what sort of load is the exterior lights?

I closed the lights manually to find out if it was interference one of the light could  induced on the power line once turn on, but once the 5 minutes passed in the event log, no order to close the lights has been sent. It's like a programing problems... I really don't know what's going on here

[autoperformance]

On ‎2018‎-‎04‎-‎29 at 7:29 AM, paulbates said:

It could be the load as webminster suggested. Some loads inject noise in the powerline once powered up that can prevent further communications,  even rf. Can you turn the light on and back off manually using the admin console? 

If you can turn the load and off reliably from the Admin Console, the only other way I know to fix this then is to take the "Then" lines and put them in a separate program that has no 'If' clause. In place of those statements in the original program, put a "run then" program statement calling the other program. That will decouple the actions from the if clause changing. No 100% clear why its needed here but this technique doe solve this kind of issue

Paul

**** Program 1

Back Flood Light - [ID 000E][Parent 0001]
If
        From     9:00:00PM
        To      Sunrise - 30 minutes (next day)
    And Status  'Motion Backyard' is not Off
 
Then
      Run Program 'Back Floodlight 2' (Then Path)  
 
Else
   - No Actions - (To add one, press 'Action')

*** Program 2

Back Flood Light 2 - [.....
If
  - No Condiitons
Then
  Set Scene 'Ext Lighting' On
  Wait  5 minutes
  Set Scene 'Ext Lighting' Off

 

I just cut and paste that ?

 

[paulbates]

6 hours ago, autoperformance said:

I just cut and paste that ?

 

You can't cut and past the whole thing. The way the ISY programming environment works, you do it one line at a time.

• You'll create the second program using the programs tab, then
• Remove the lines under Then in the first program and replace them with the Run program statement (It Program in the drop down)

Paul

[autoperformance]

On ‎2018‎-‎04‎-‎29 at 7:29 AM, paulbates said:

It could be the load as webminster suggested. Some loads inject noise in the powerline once powered up that can prevent further communications,  even rf. Can you turn the light on and back off manually using the admin console? 

If you can turn the load and off reliably from the Admin Console, the only other way I know to fix this then is to take the "Then" lines and put them in a separate program that has no 'If' clause. In place of those statements in the original program, put a "run then" program statement calling the other program. That will decouple the actions from the if clause changing. No 100% clear why its needed here but this technique doe solve this kind of issue

Paul

**** Program 1

Back Flood Light - [ID 000E][Parent 0001]
If
        From     9:00:00PM
        To      Sunrise - 30 minutes (next day)
    And Status  'Motion Backyard' is not Off
 
Then
      Run Program 'Back Floodlight 2' (Then Path)  
 
Else
   - No Actions - (To add one, press 'Action')

*** Program 2

Back Flood Light 2 - [.....
If
  - No Condiitons
Then
  Set Scene 'Ext Lighting' On
  Wait  5 minutes
  Set Scene 'Ext Lighting' Off

 

Hi Paul, sorry for the delay, but I do not have much time these days.
So here is the program and the event journal screeshot. This time no light works. Absolutely nothing lights up.
Even I am surprised and at the same time I do not understand anything. I did tests if everything worked manually and the test was positive. So it's a programming problem.

Thank you in advance for your help.

EVENT LOG:

 

jeu. 05/10/2018 23:50:33 : [INST-SRX    ] 02 50 27.B4.2F 00.00.01 CB 11 01    LTONRR (01)
jeu. 05/10/2018 23:50:33 : [Std-Group   ] 27.B4.2F-->Group=1, Max Hops=3, Hops Left=2
jeu. 05/10/2018 23:50:33 : [D2D EVENT   ] Event [27 B4 2F 1] [DON] [1] uom=0 prec=-1
jeu. 05/10/2018 23:50:33 : [  27 B4 2F 1]      DON   1
jeu. 05/10/2018 23:50:33 : [D2D-CMP 0004] CTL [27 B4 2F 1] [DON] op=is --> true
jeu. 05/10/2018 23:50:33 : [D2D EVENT   ] Event [27 B4 2F 1] [ST] [255] uom=100 prec=0
jeu. 05/10/2018 23:50:33 : [  27 B4 2F 1]       ST 255 (uom=100 prec=0)
jeu. 05/10/2018 23:50:33 : [D2D-CMP 000E] STS [27 B4 2F 1] ST op=6 Event(val=255 uom=100 prec=0) != Condition(val=0 uom=0 prec=-1) --> true
jeu. 05/10/2018 23:50:33 : [INST-SRX    ] 02 50 27.B4.2F 00.00.01 CF 11 01    LTONRR (01)
jeu. 05/10/2018 23:50:33 : [Std-Group   ] 27.B4.2F-->Group=1, Max Hops=3, Hops Left=3
jeu. 05/10/2018 23:50:33 : [INST-DUP    ] Previous message ignored.
jeu. 05/10/2018 23:50:33 : [INST-SRX    ] 02 50 27.B4.2F 3D.96.69 45 11 01    LTONRR (01)
jeu. 05/10/2018 23:50:33 : [Std-Cleanup ] 27.B4.2F-->ISY/PLM Group=1, Max Hops=1, Hops Left=1
jeu. 05/10/2018 23:50:33 : [INST-DUP    ] Previous message ignored.
jeu. 05/10/2018 23:50:33 : [INST-SRX    ] 02 50 27.B4.2F 11.01.01 CB 06 00           (00)
jeu. 05/10/2018 23:50:33 : [Std-Group   ] 27.B4.2F-->11.01.01, Max Hops=3, Hops Left=2
jeu. 05/10/2018 23:50:33 : [INST-INFO   ] Previous message ignored.
jeu. 05/10/2018 23:50:34 : [INST-SRX    ] 02 50 27.B4.2F 11.01.01 CB 06 00           (00)
jeu. 05/10/2018 23:50:34 : [Std-Group   ] 27.B4.2F-->11.01.01, Max Hops=3, Hops Left=2
jeu. 05/10/2018 23:50:34 : [INST-INFO   ] Previous message ignored.
jeu. 05/10/2018 23:51:02 : [INST-SRX    ] 02 50 27.B4.2F 00.00.01 CF 13 01    LTOFFRR(01)
jeu. 05/10/2018 23:51:02 : [Std-Group   ] 27.B4.2F-->Group=1, Max Hops=3, Hops Left=3
jeu. 05/10/2018 23:51:02 : [D2D EVENT   ] Event [27 B4 2F 1] [DOF] [1] uom=0 prec=-1
jeu. 05/10/2018 23:51:02 : [  27 B4 2F 1]      DOF   1
jeu. 05/10/2018 23:51:02 : [D2D EVENT   ] Event [27 B4 2F 1] [ST] [0] uom=100 prec=0
jeu. 05/10/2018 23:51:03 : [  27 B4 2F 1]       ST   0 (uom=100 prec=0)
jeu. 05/10/2018 23:51:03 : [D2D-CMP 000E] STS [27 B4 2F 1] ST op=6 Event(val=0 uom=100 prec=0) != Condition(val=0 uom=0 prec=-1) --> false
jeu. 05/10/2018 23:51:03 : [INST-SRX    ] 02 50 27.B4.2F 00.00.01 CF 13 01    LTOFFRR(01)
jeu. 05/10/2018 23:51:03 : [Std-Group   ] 27.B4.2F-->Group=1, Max Hops=3, Hops Left=3
jeu. 05/10/2018 23:51:03 : [INST-DUP    ] Previous message ignored.
jeu. 05/10/2018 23:51:03 : [INST-SRX    ] 02 50 27.B4.2F 3D.96.69 45 13 01    LTOFFRR(01)
jeu. 05/10/2018 23:51:03 : [Std-Cleanup ] 27.B4.2F-->ISY/PLM Group=1, Max Hops=1, Hops Left=1
jeu. 05/10/2018 23:51:03 : [INST-DUP    ] Previous message ignored.
jeu. 05/10/2018 23:51:03 : [INST-SRX    ] 02 50 27.B4.2F 13.01.01 CF 06 00           (00)
jeu. 05/10/2018 23:51:03 : [Std-Group   ] 27.B4.2F-->13.01.01, Max Hops=3, Hops Left=3
jeu. 05/10/2018 23:51:03 : [INST-INFO   ] Previous message ignored.
jeu. 05/10/2018 23:51:03 : [INST-SRX    ] 02 50 27.B4.2F 13.01.01 CF 06 00           (00)
jeu. 05/10/2018 23:51:03 : [Std-Group   ] 27.B4.2F-->13.01.01, Max Hops=3, Hops Left=3
jeu. 05/10/2018 23:51:03 : [INST-INFO   ] Previous message ignored.
 

 

 

Program:

Back Flood Light - [ID 000E][Parent 0001]

If
        From    10:30:00PM
        To      Sunrise - 30 minutes (next day)
    And Status  'Back motion sensor' is not Off
 
Then
        Run Program 'Back Flood Light 2' (Then Path)
 
Else
   - No Actions - (To add one, press 'Action')

 

 

Program 2 :

Back Flood Light 2 - [ID 0010][Parent 0001]

If
   - No Conditions - (To add one, press 'Schedule' or 'Condition')
 
Then
        Set Scene 'Front Lighting' On
        Wait  5 minutes
        Set Scene 'Front Lighting' Off
 
Else
   - No Actions - (To add one, press 'Action')
 

 

 

 

[autoperformance]

ven. 05/11/2018 00:06:37 : [INST-SRX    ] 02 50 27.B4.2F 00.00.01 CF 13 01    LTOFFRR(01)
ven. 05/11/2018 00:06:37 : [Std-Group   ] 27.B4.2F-->Group=1, Max Hops=3, Hops Left=3
ven. 05/11/2018 00:06:37 : [D2D EVENT   ] Event [27 B4 2F 1] [DOF] [1] uom=0 prec=-1
ven. 05/11/2018 00:06:37 : [  27 B4 2F 1]      DOF   1
ven. 05/11/2018 00:06:37 : [D2D EVENT   ] Event [27 B4 2F 1] [ST] [0] uom=100 prec=0
ven. 05/11/2018 00:06:37 : [  27 B4 2F 1]       ST   0 (uom=100 prec=0)
ven. 05/11/2018 00:06:37 : [D2D-CMP 000E] STS [27 B4 2F 1] ST op=6 Event(val=0 uom=100 prec=0) != Condition(val=0 uom=0 prec=-1) --> false
ven. 05/11/2018 00:06:37 : [INST-SRX    ] 02 50 27.B4.2F 00.00.01 CF 13 01    LTOFFRR(01)
ven. 05/11/2018 00:06:37 : [Std-Group   ] 27.B4.2F-->Group=1, Max Hops=3, Hops Left=3
ven. 05/11/2018 00:06:37 : [INST-DUP    ] Previous message ignored.
ven. 05/11/2018 00:06:37 : [INST-SRX    ] 02 50 27.B4.2F 3D.96.69 45 13 01    LTOFFRR(01)
ven. 05/11/2018 00:06:37 : [Std-Cleanup ] 27.B4.2F-->ISY/PLM Group=1, Max Hops=1, Hops Left=1
ven. 05/11/2018 00:06:37 : [INST-DUP    ] Previous message ignored.
ven. 05/11/2018 00:06:37 : [INST-SRX    ] 02 50 27.B4.2F 13.01.01 CF 06 00           (00)
ven. 05/11/2018 00:06:37 : [Std-Group   ] 27.B4.2F-->13.01.01, Max Hops=3, Hops Left=3
ven. 05/11/2018 00:06:37 : [INST-INFO   ] Previous message ignored.
ven. 05/11/2018 00:06:37 : [INST-SRX    ] 02 50 27.B4.2F 13.01.01 CF 06 00           (00)
ven. 05/11/2018 00:06:37 : [Std-Group   ] 27.B4.2F-->13.01.01, Max Hops=3, Hops Left=3
ven. 05/11/2018 00:06:37 : [INST-INFO   ] Previous message ignored.
ven. 05/11/2018 00:06:40 : [INST-SRX    ] 02 50 27.B4.2F 00.00.01 CF 11 01    LTONRR (01)
ven. 05/11/2018 00:06:40 : [Std-Group   ] 27.B4.2F-->Group=1, Max Hops=3, Hops Left=3
ven. 05/11/2018 00:06:40 : [D2D EVENT   ] Event [27 B4 2F 1] [DON] [1] uom=0 prec=-1
ven. 05/11/2018 00:06:40 : [  27 B4 2F 1]      DON   1
ven. 05/11/2018 00:06:40 : [D2D-CMP 0004] CTL [27 B4 2F 1] [DON] op=is --> true
ven. 05/11/2018 00:06:40 : [D2D EVENT   ] Event [27 B4 2F 1] [ST] [255] uom=100 prec=0
ven. 05/11/2018 00:06:40 : [  27 B4 2F 1]       ST 255 (uom=100 prec=0)
ven. 05/11/2018 00:06:40 : [D2D-CMP 000E] STS [27 B4 2F 1] ST op=6 Event(val=255 uom=100 prec=0) != Condition(val=0 uom=0 prec=-1) --> true
ven. 05/11/2018 00:06:40 : [INST-SRX    ] 02 50 27.B4.2F 00.00.01 CB 11 01    LTONRR (01)
ven. 05/11/2018 00:06:40 : [Std-Group   ] 27.B4.2F-->Group=1, Max Hops=3, Hops Left=2
ven. 05/11/2018 00:06:40 : [INST-DUP    ] Previous message ignored.
ven. 05/11/2018 00:06:41 : [INST-SRX    ] 02 50 27.B4.2F 3D.96.69 45 11 01    LTONRR (01)
ven. 05/11/2018 00:06:41 : [Std-Cleanup ] 27.B4.2F-->ISY/PLM Group=1, Max Hops=1, Hops Left=1
ven. 05/11/2018 00:06:41 : [INST-DUP    ] Previous message ignored.
ven. 05/11/2018 00:06:41 : [INST-SRX    ] 02 50 27.B4.2F 11.01.01 CF 06 00           (00)
ven. 05/11/2018 00:06:41 : [Std-Group   ] 27.B4.2F-->11.01.01, Max Hops=3, Hops Left=3
ven. 05/11/2018 00:06:41 : [INST-INFO   ] Previous message ignored.
ven. 05/11/2018 00:06:42 : [INST-SRX    ] 02 50 27.B4.2F 11.01.01 CF 06 00           (00)
ven. 05/11/2018 00:06:42 : [Std-Group   ] 27.B4.2F-->11.01.01, Max Hops=3, Hops Left=3
ven. 05/11/2018 00:06:42 : [INST-INFO   ] Previous message ignored.
 

[larryllix]

If you don't use "If control MS is switched On" as Paul suggested, and your MS is not set up right it will never trigger the program as ISY will think the MS is on all the time and never changes.

The second program serves no purpose  in your case, except that with two programs, "sunrise - 30 minutes" cannot turn off the lights if that was installed in your program.

 

You need to simplify this program, losing the times frame and the scenes, and get it working first then add the time frame back in. Scenes are a waste of time unless directly coupled to the MS and/or you have multiple lights. Use a simple program to get it going first.

If
     Control MS is Switched On
Then
    set Light On
   set Light2 On
   Wait 5 minutes
    set Light Off
    set Light2 Off
Else
   --

 

[oberkc]

I agree with suggestion most recently made by larryllix , and others in the past.  You really need to try "control" rather than "status".  I don't see anywhere in this post where you have tried this suggestion.  One point that may confuse things is that the syntax may have changed between ISY software version 4.x and 5.x.  Which are you on?  

Assuming you are on v4.x, a program such the following will work:

if

control mostion sensor is switched on

and time is from xx:xx to yy:yy

then

set scene "zzzzzz" on

wait a little bit

set scene 'zzzzz" off

else

set scene 'zzzzz' off

[autoperformance]

23 hours ago, larryllix said:

If you don't use "If control MS is switched On" as Paul suggested, and your MS is not set up right it will never trigger the program as ISY will think the MS is on all the time and never changes.

The second program serves no purpose  in your case, except that with two programs, "sunrise - 30 minutes" cannot turn off the lights if that was installed in your program.

 

You need to simplify this program, losing the times frame and the scenes, and get it working first then add the time frame back in. Scenes are a waste of time unless directly coupled to the MS and/or you have multiple lights. Use a simple program to get it going first.

If
     Control MS is Switched On
Then
    set Light On
   set Light2 On
   Wait 5 minutes
    set Light Off
    set Light2 Off
Else
   --

 

Check Up the thread. I do that first and the light go on but never go off. Because the MS don't stay on so the program don't go further when it's time to turn off the light. So I decide to do that to avoid this problem.

[autoperformance]

17 hours ago, oberkc said:

I agree with suggestion most recently made by larryllix , and others in the past.  You really need to try "control" rather than "status".  I don't see anywhere in this post where you have tried this suggestion.  One point that may confuse things is that the syntax may have changed between ISY software version 4.x and 5.x.  Which are you on?  

Assuming you are on v4.x, a program such the following will work:

if

control mostion sensor is switched on

and time is from xx:xx to yy:yy

then

set scene "zzzzzz" on

wait a little bit

set scene 'zzzzz" off

else

set scene 'zzzzz' off

I'm on 5.x

[lilyoyo1]

I agree with Larry. A simple on should allow you to accomplish what you want. 

If time is from 5-10pm

And control motion is switched on

Then

Set light on

Wait 5 min. 

Set light off. 

 

[oberkc]

5 hours ago, autoperformance said:

I'm on 5.x

Then, I think, the syntax is more consistent with the suggestion by paulbates in the first response on April 27th.  I think he correctly identified your problem in the first post, but I do not see any response by you that indicated you tried his suggestion. 

In the 4.x version of software, there was a "control" statement, as opposed to the "status" statement.  I believe this changed in 5.x to the form in paulbates' version.  Iunderstand the function is the same, but form is a little different.  There is a difference between that type of condition and a "status" condition.

Given this, the program you are looking for is:

if

 'Motion Backyard' is switched on  <<<no "status" statement!!!

and time is from xx:xx to yy:yy

then

set scene "zzzzzz" on

wait a little bit

set scene 'zzzzz" off

else

set scene 'zzzzz' off

 

Since I have not moved to 5.x, I am hoping others will confirm.

[larryllix]

6 hours ago, autoperformance said:

Check Up the thread. I do that first and the light go on but never go off. Because the MS don't stay on so the program don't go further when it's time to turn off the light. So I decide to do that to avoid this problem.

That is not how the prorams work. Then continues unless it is stopped by something. Control MS is Switched On is a one time signal that can restart but cannot stop the Then program lines.  Status can.

This sounds like you have a MS with a dying battery that is sending On signals erroneously.

You have always shown the Status On program line in your posts, and haven't shown that you tried the suggestions yet.

[oberkc]

13 hours ago, autoperformance said:

Check Up the thread. I do that first and the light go on but never go off. Because the MS don't stay on so the program don't go further when it's time to turn off the light. So I decide to do that to avoid this problem.

Neither do I see any of your examples where you have done this.

[autoperformance]

HI everybody. I replaced the status command of the MS with the command control of the MS and I was going to make some tests when suddenly all my programs appeared like "Not loaded Out of Memory ???" With a pop up Not Implement. What does it mean ?

 

[larryllix]

This would typically mean your UI and firmware version do not match.

You posted you are using 5.x. Which exact version and which version is your UI?

In Admin Console click on Help | About.

[autoperformance]

6 minutes ago, larryllix said:

This would typically mean your UI and firmware version do not match.

You posted you are using 5.x. Which exact version and which version is your UI?

In Admin Console click on Help | About.

I upgrade to 5.x and clear the cash in javascript and reinstall Dashboard. it's what I done.

 

What is UI ? I think it was Dashboard ?

[lilyoyo1]

Which 5.x? go to help about. There you will find firmware/UI info

[autoperformance]

7 hours ago, autoperformance said:

I upgrade to 5.x and clear the cash in javascript and reinstall Dashboard. it's what I done.

 

What is UI ? I think it was Dashboard ?

Reinstall the 4.6.2 firmware with the admin consol 4.6.2.

NOW no more  not loaded out of memory problem. But I don't have device state anymore

 

But the good thing is... Now my program work perfectly. The light turn on with MS and off after 5 min

 

If somebody can just tell me why I don't have device state  it will be appreciated.

Thanks.

After the downgrading Firmware and admin console to 4.62 clearing the java memory, I was an issue with the isy. Error led go on. So I did a factory reset and formats the SD card. Now like I said no more device state and no more connection with mobilinc connect even if the portal was installed.

 

So it's almost that.