Never EVER delete an Event Trigger

[devanb]

Thank you for responding,

Regarding Sparkman's question, If I remove the trigger condition Day of the Week, Jon00 still reports the event broken.

I've made a simple event asking to lower the temp to 74 on Monday and Wednesday at 4am and it's still broken.





Now I'm getting worried my installation became corrupted somehow.

[randy]

Try collapsing the condition. I think on multiple choices, the condition needs to be collapsed to write it to the DB. It is a best practice to fully collapse an Event after editing.

EDIT: I just confirmed this to be true.

[devanb]

You are a genius!

I wish I knew that you have to collapse conditions in order to effectively save them.

It works now and I've replaced the Wait statements with delayed device actions.

Sorry to hijack this thread.

[randy]

You are a genius!

I wish I knew that you have to collapse conditions in order to effectively save them.

It works now and I've replaced the Wait statements with delayed device actions.

Sorry to hijack this thread.

Not a genius

On most events, when you complete a Trigger, Condition or Action, they will automatically collapse. The days of the week, being multiple choice, give no clear indication you have completed selections, so they do not automatically collapse. I suppose HomeSeer could write changes as you select/deselect boxes, but I could see that giving undesirable delays on slower systems.

[pcburcham]

[*]Do not group a number of devices under one device control Action, instead put each under a separate action

So, instead of setting the "control a device" action and then picking through the dropdown lists and turning on/off a number of devices, it is better to continue with THEN after each device/action for the sake of event integrity, correct? Any drawbacks to that or does HS3 execute the commands just as efficiently one way as the other? I've always stacked my devices under a single action and starting to reconsider that practice after reading this thread.

[Tillsy]

Try collapsing the condition. I think on multiple choices, the condition needs to be collapsed to write it to the DB. It is a best practice to fully collapse an Event after editing.

EDIT: I just confirmed this to be true.

What the %$^&*?!? Wowsers, that's got to be one of the most unobvious things I've heard in my entire life. Guess that explains the occasion frustration I've had with making a few changes here and there, then finding bits and pieces missing/not working. There should at least be a line of text warning of this if it can' be fixed - then again 4761 customers would have to report it to them before that would even be considered

[randy]

What the %$^&*?!? Wowsers, that's got to be one of the most unobvious things I've heard in my entire life. Guess that explains the occasion frustration I've had with making a few changes here and there, then finding bits and pieces missing/not working. There should at least be a line of text warning of this if it can' be fixed - then again 4761 customers would have to report it to them before that would even be considered

I'm only the messenger