Christmas Tree goes on then off

I have written a rule (see below) that will not allow the Christmas Tree lights to come on if our alarm is set, but as soon as the alarm is turned on they will turn on. OR if they lights are on and we set the alarm, the lights will turn off and when the system is disarmed, they will turn back on. However, I'm getting a weird instance when, not every time, when the system is disarmed one of the trees will turn on then immediately back off. I have also attached the logs. Any direction would be appreciated.

dev:6472022-12-01 08:29:32.560 PMinfoDining Room Decorations is on [digital]
dev:6472022-12-01 08:29:32.558 PMinfoBasicReport value: 255
dev:6472022-12-01 08:29:32.556 PMdebugparse description: zw device: 16, command: 2003, payload: FF , isMulticast: false
dev:6472022-12-01 08:29:32.512 PMinfoDining Room Decorations was turned on [digital]
dev:6472022-12-01 08:29:32.510 PMinfoBasicReport value: 255
dev:6472022-12-01 08:29:32.508 PMdebugparse description: zw device: 16, command: 2003, payload: FF , isMulticast: false
dev:6462022-12-01 08:29:32.253 PMinfoChristmas Tree is off [digital]
dev:6462022-12-01 08:29:32.252 PMinfoBasicReport value: 0
dev:6462022-12-01 08:29:32.250 PMdebugparse description: zw device: 15, command: 2003, payload: 00 , isMulticast: false
dev:6462022-12-01 08:29:31.929 PMinfoChristmas Tree is off [digital]
dev:6462022-12-01 08:29:31.927 PMinfoBasicReport value: 0
dev:6462022-12-01 08:29:31.925 PMdebugparse description: zw device: 15, command: 2003, payload: 00 , isMulticast: false
dev:6462022-12-01 08:29:31.654 PMinfoChristmas Tree is off [digital]
dev:6462022-12-01 08:29:31.653 PMinfoBasicReport value: 0
dev:6462022-12-01 08:29:31.651 PMdebugparse description: zw device: 15, command: 2003, payload: 00 , isMulticast: false
dev:6462022-12-01 08:29:29.765 PMinfoChristmas Tree is off [digital]
dev:6462022-12-01 08:29:29.763 PMinfoBasicReport value: 0
dev:6462022-12-01 08:29:29.761 PMdebugparse description: zw device: 15, command: 2003, payload: 00 , isMulticast: false
dev:6462022-12-01 08:29:29.593 PMinfoChristmas Tree is off [digital]
dev:6462022-12-01 08:29:29.591 PMinfoBasicReport value: 0
dev:6462022-12-01 08:29:29.589 PMdebugparse description: zw device: 15, command: 2003, payload: 00 , isMulticast: false
dev:6462022-12-01 08:29:29.388 PMinfoChristmas Tree is off [digital]
dev:6462022-12-01 08:29:29.386 PMinfoBasicReport value: 0
dev:6462022-12-01 08:29:29.384 PMdebugparse description: zw device: 15, command: 2003, payload: 00 , isMulticast: false
dev:6472022-12-01 08:29:28.637 PMdebugon()
app:9552022-12-01 08:29:28.632 PMinfoDelay Over: On: Dining Room Decorations
app:9552022-12-01 08:29:27.628 PMinfoAction: Off: Christmas Tree, Dining Room Decorations (skipped)
app:9552022-12-01 08:29:27.625 PMinfoAction: ELSE (skipping)
dev:6472022-12-01 08:29:27.618 PMdebugoff()
dev:6462022-12-01 08:29:27.611 PMdebugoff()
app:9552022-12-01 08:29:27.595 PMinfoAction: On: Dining Room Decorations --> delayed: 0:00:01
dev:6462022-12-01 08:29:27.579 PMdebugon()
app:9552022-12-01 08:29:27.573 PMinfoAction: On: Christmas Tree
app:9552022-12-01 08:29:27.570 PMinfoAction: IF (Time between Sunset-30 minutes(4:13 PM) and 10:00 PM(T) AND Armed All contact open(T) AND Alarm Virtual(off) is off(T) [TRUE]) THEN
app:9552022-12-01 08:29:27.459 PMinfoTriggered: Alarm Virtual(off) turns *changed*

Here is the rule:

I can't find anything in your rule logs that suggest the rule is responsible for this. I suggest going to the device detail page for the problematic device, going to "Events," then looking for entries named "command-on" or similar, which will tell you when the "on" command was sent and what app sent it. It's probably not this rule, but it should show you what it is. If there isn't anything there, check that it's not a member of any groups, and maybe given any of the "In use by" apps (scroll down a bit on the page to see it) just in case.

PS - Add an END-IF to the end of your rule for the sake of completeness; not the cause of this (or any, if it's the last line) problem, but a good habit. :slight_smile:

4 Likes

I had another rule similar to this one that I used for morning activation, which, at @bertabcd1234 recommendation to look at, was probably causing a conflict. I wrapped the two rules in to one and I haven't had an issue since.

Thanks for all your help!

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.