Jump to content

Using "Time is Sunset + "as a condition


BigDigger

Recommended Posts

I hoping someone can help me out with this puzzling but simple piece of code.

I am controlling a lighting scene based on the condition;

If Time is Sunset + 4 hours Then .....turn off scene

For some reason this condition does not work 100% all of the time. As an interim I have also added an OR with the sunset condition that uses the Dusk-Dawn value for one of my outdoor sensors.

If there a specific reason why the Sunset condition is not working?

 

 

Thank you ....

Link to comment

Hello BigDigger-

 

Welcome to the forum.

 

Are the sunrise/sunset times displayed in the admin console accurate for your location?

 

There is no reason that I can think of that would cause that not to work. It is more likely a comm problem that is preventing the Off command from being heard. Try running a level 3 event viewer trace and run a few scene tests on that scene. Post the resulting trace.

 

What kind of load(s) are being controlled with that scene? Some loads can cause noise or attenuate the signals when they are on making it possible to reliably turn ON a device/scene but not reliably turn OFF the device/scene.

 

-Xathros

Link to comment

Like Xathros said, if it is working sometimes, you probably have a comm issue. If you truly only have that single "if" condition, then there can't be a logic issue.

 

Do you have a whole bunch of other things all triggering at sunset plus 4 hours? Is there some electrical device in your house that might be on at that time that is impairing communication?

 

Check your program summary page. It should list the last time that program ran, the next time it is scheduled to run, and whether it ran true or false last time. You should see that it last run at roughly MN last night and was true. It should be scheduled to run tonight at about the same time. If indeed that is what it says, then you are for sure dealing with a comm issue.

Link to comment

Thank you all for your assistance.

As I mentioned I have also added an OR condition based on the Dusk-Dawn input from an outside sensor.

The last 3 days it has been the sensor that has been shutting off my outdoor light scene which is comprised entirely of CFL's.

If I had a communication problem to the switches wouldn't it also apply when the ISY turns off the scene after receiving input from the sensor?

My outdoor light scene is the only thing that is being triggered at Sunset + 4 hours.

 

Also, where can I find the procedure to run a level 3 event viewer trace?

 

Thanks again.

Link to comment

The "or" line won't block the sunset line from running true.

 

The level 3 is in the tools, diagnostics, event viewer menu, but before confusing yourself with that, just look at the program summary page and report that. The level 3 check will tell you about communications, but you won't understand it without a lot of research.

 

You need to open the event viewer and set it to level 3 shortly before sunset plus 4 hours so that it is running when that program is supposed to execute. You can then copy and paste that to the forum for interpretation.

 

Also you can run a "scene test" on that scene. This will give you an idea of how strong the comm is. If you are needing multiple hops that is a sign of weak comm.

Link to comment

Here is the log from the scene test .... I will also ensure it runs tonight..

 

Thu 03/27/2014 02:01:20 PM : [GRP-RX ] 02 61 19 13 00 06

 

Thu 03/27/2014 02:01:20 PM : [iNST-SRX ] 02 50 22.CB.5B 24.1B.E3 61 13 19 LTOFFRR(19)

 

Thu 03/27/2014 02:01:20 PM : [std-Cleanup Ack] 22.CB.5B-->ISY/PLM Group=0, Max Hops=1, Hops Left=0

 

----- Front House-Garage Test Results -----

[Failed] Garage Outdoor Lights (23 F2 6E 1)

[Failed] MB C - Front House (24 16 3B 5)

[succeeded] Hallway A - Front House (22 CB 5B 3)

[Failed] Front House Lights (23 F2 B0 1)

----- Front House-Garage Test Results -----

Thu 03/27/2014 02:01:29 PM : [iNST-ACK ] 02 62 00.00.19 CF 13 00 06 LTOFFRR(00)

 

Thu 03/27/2014 02:01:29 PM : [Ext MH ] Unexpected Ack imCmd=62 cmd1=LTOFFRR 0x13

 

Thu 03/27/2014 02:01:29 PM : [iNST-TX-I2 ] 02 62 1C 48 4C 1F 2F 00 00 02 0F CF 08 E2 02 24 E3 E5 FF 00 02 18

 

Thu 03/27/2014 02:01:30 PM : [iNST-ACK ] 02 62 1C.48.4C 1F 2F 00 00 02 0F CF 08 E2 02 24 E3 E5 FF 00 02 18 06 (00)

 

Thu 03/27/2014 02:01:39 PM : [iNST-TX-I2 ] 02 62 1C 48 4C 1F 2F 00 00 02 0F CF 08 E2 02 24 E3 E5 FF 00 02 18

 

Thu 03/27/2014 02:01:39 PM : [iNST-ACK ] 02 62 1C.48.4C 1F 2F 00 00 02 0F CF 08 E2 02 24 E3 E5 FF 00 02 18 06 (00)

 

Thu 03/27/2014 02:01:43 PM : [1C 48 4C 1 ] Link 6 : 0FC8 [E20224E3E5FF0002] *Failed Writing [E20224E3E5FF0002]

 

Thu 03/27/2014 02:01:43 PM : [ 1C 48 4C 1] ERR 1

 

Thu 03/27/2014 02:01:43 PM : [1C 57 C7 1 ] Link 1 : 0FF0 [620123F26EFF0001] Writing [620123F26EFF0001]

 

Thu 03/27/2014 02:01:43 PM : [iNST-TX-I2CS] 02 62 1C 57 C7 1F 2F 00 00 02 0F F7 08 62 01 23 F2 6E FF 00 01 DB

 

Thu 03/27/2014 02:01:43 PM : [iNST-ACK ] 02 62 1C.57.C7 1F 2F 00 00 02 0F F7 08 62 01 23 F2 6E FF 00 01 DB 06 (00)

 

Thu 03/27/2014 02:01:52 PM : [iNST-TX-I2CS] 02 62 1C 57 C7 1F 2F 00 00 02 0F F7 08 62 01 23 F2 6E FF 00 01 DB

 

Thu 03/27/2014 02:01:52 PM : [iNST-ACK ] 02 62 1C.57.C7 1F 2F 00 00 02 0F F7 08 62 01 23 F2 6E FF 00 01 DB 06 (00)

 

Thu 03/27/2014 02:02:01 PM : [iNST-TX-I2CS] 02 62 1C 57 C7 1F 2F 00 00 02 0F F7 08 62 01 23 F2 6E FF 00 01 DB

 

Thu 03/27/2014 02:02:01 PM : [iNST-ACK ] 02 62 1C.57.C7 1F 2F 00 00 02 0F F7 08 62 01 23 F2 6E FF 00 01 DB 06 (00)

 

Thu 03/27/2014 02:02:05 PM : [1C 57 C7 1 ] Link 1 : 0FF0 [620123F26EFF0001] *Failed Writing [620123F26EFF0001]

 

Thu 03/27/2014 02:02:05 PM : [ 1C 57 C7 1] ERR 1

 

Thu 03/27/2014 02:07:28 PM : Setting Time From NTP

 

Thu 03/27/2014 02:12:03 PM : [ Time] 14:12:03 9(0)

Link to comment

----- Front House-Garage Test Results -----

[Failed] Garage Outdoor Lights (23 F2 6E 1)

[Failed] MB C - Front House (24 16 3B 5)

[succeeded] Hallway A - Front House (22 CB 5B 3)

[Failed] Front House Lights (23 F2 B0 1)

----- Front House-Garage Test Results -----

 

This was the scene test, and you had 3 out 4 devices fail. You appear to be having comm issues.

Link to comment

Try unscrewing the CFL's and run the test again. If it passes, that would indicate that the CFL's are causing issues.

 

-Xathros

Link to comment

First of all, thank you all again for your assistance.

In checking the log I noticed the Program to shutoff the lights at Sunset + 4 hours was NOT triggered.

 

I ran various scene tests again and the results seem to vary from succesfull to failed and during this testing no other factors would have skewed the results (i.e. appliance being turned on)

 

 

I have noticed that during the testing the end devices actually come on and then off as part of the scene test yet the test shows failed.

Below is an example where I have added a Table Lamp to the scene and the table lamp being located right beside me where I can see it come on and off as a result of the scene test, yet the scene test states it has failed.

 

Just curious what does "Failed" mean when the device actually responds? Also, is there documentation and I'm sure there is, on I can decipher the communication logs?

 

By the way, I have about 20 CFL's that make up my Garage and Front house lighting which would make any CFL troubleshooting pain staking. I live in Ontario, Canada where incandescent bulbs are no longer being sold.

 

Fri 03/28/2014 06:46:08 PM : [GRP-RX ] 02 61 19 13 00 06

Fri 03/28/2014 06:46:08 PM : [iNST-SRX ] 02 50 22.CB.5B 24.1B.E3 61 13 19 LTOFFRR(19)

Fri 03/28/2014 06:46:08 PM : [std-Cleanup Ack] 22.CB.5B-->ISY/PLM Group=0, Max Hops=1, Hops Left=0

----- Front House-Garage Test Results -----

[Failed] Garage Outdoor Lights (23 F2 6E 1)

[Failed] Den Table Lamp (29 9E C1 1)

[Failed] MB C - Front House (24 16 3B 5)

[succeeded] Hallway A - Front House (22 CB 5B 3)

[Failed] Front House Lights (23 F2 B0 1)

----- Front House-Garage Test Results -----

Fri 03/28/2014 06:46:16 PM : [iNST-ACK ] 02 62 00.00.19 CF 13 00 06 LTOFFRR(00)

Fri 03/28/2014 06:46:16 PM : [Ext MH ] Unexpected Ack imCmd=62 cmd1=LTOFFRR 0x13

Fri 03/28/2014 06:46:17 PM : [iNST-TX-I2CS] 02 62 1C 57 C7 1F 2F 00 00 02 0F F7 08 62 01 23 F2 6E FF 00 01 DB

Fri 03/28/2014 06:46:17 PM : [iNST-ACK ] 02 62 1C.57.C7 1F 2F 00 00 02 0F F7 08 62 01 23 F2 6E FF 00 01 DB 06 (00)

Fri 03/28/2014 06:46:26 PM : [iNST-TX-I2CS] 02 62 1C 57 C7 1F 2F 00 00 02 0F F7 08 62 01 23 F2 6E FF 00 01 DB

Fri 03/28/2014 06:46:26 PM : [iNST-ACK ] 02 62 1C.57.C7 1F 2F 00 00 02 0F F7 08 62 01 23 F2 6E FF 00 01 DB 06 (00)

Fri 03/28/2014 06:46:30 PM : [1C 57 C7 1 ] Link 1 : 0FF0 [620123F26EFF0001] *Failed Writing [620123F26EFF0001]

Fri 03/28/2014 06:46:30 PM : [ 1C 57 C7 1] ERR 1

 

Thanks again !!

Link to comment

The Failed status is the result of not seeing an ACK from a given device. Note the line in Red from 22.CB.5B and this device is marked Succeeded. The remaining devices do not send an ACK or the PLM does not process it. This could be caused by missing Responder link records in the PLM. Could also be caused by one or more CFLs that are noisy when turned On.

 

 

Thu 03/27/2014 02:01:20 PM : [GRP-RX ] 02 61 19 13 00 06

 

Thu 03/27/2014 02:01:20 PM : [iNST-SRX ] 02 50 22.CB.5B 24.1B.E3 61 13 19 LTOFFRR(19)

 

Thu 03/27/2014 02:01:20 PM : [std-Cleanup Ack] 22.CB.5B-->ISY/PLM Group=0, Max Hops=1, Hops Left=0

 

----- Front House-Garage Test Results -----

[Failed] Garage Outdoor Lights (23 F2 6E 1)

[Failed] MB C - Front House (24 16 3B 5)

[succeeded] Hallway A - Front House (22 CB 5B 3)

[Failed] Front House Lights (23 F2 B0 1)

----- Front House-Garage Test Results -----

Thu 03/27/2014 02:01:29 PM : [iNST-ACK ] 02 62 00.00.19 CF 13 00 06 LTOFFRR(00)

Link to comment

Archived

This topic is now archived and is closed to further replies.


  • Recently Browsing

    • No registered users viewing this page.
  • Who's Online (See full list)

  • Forum Statistics

    • Total Topics
      36.9k
    • Total Posts
      370.3k
×
×
  • Create New...