Never EVER delete an Event Trigger

[drhtmal]

I ran into this bug and thought I was doing something wrong. Nice to know the root cause of the issue. Maybe this will be changed in HS4.

[Uncle Michael]

Would it not be a simple software change for HS engineering to eliminate the "X" in the trigger line???

Probably, but it may, nonetheless, take a while (on a geologic time scale) for your suggestion to be implemented. Much more important to aggressively (and probably repeatedly) publicize the bug.
Can you get your post converted to a sticky?

[randy]

Would it not be a simple software change for HS engineering to eliminate the "X" in the trigger line???

Yes, but there may be a reason to delete a secondary Trigger (Or If). I think the approach would be to remove the X on the primary Trigger, but provide it on the additional triggers with a pop up dialogue “Deleting this Trigger will result in the deletion of its associated Conditions as well. Continue (Y,N)”. Confirmation will delete the entire block. This could be done on the Primary as well, but I cannot see the need to ever delete the Primary Trigger.

[Tillsy]

This product is full of bugs - events in particular are nasty...

For example you have an event that triggers because of x and then:
device 1 on
device 2 on
device 3 on
device 4 on
device 5 on

But let's say you have excluded device 2 from your system? You would expect HomeSeer to now list in that event:
device 1 on
device 3 on
device 4 on
device 5 on

Instead what it does is:
device 1 on
omg omg omg i'm going to die the rest of this event can go boooooooooom errrrRRRrrror maLfunCTIon nEEd iNPut

So then you edit that second item, and add another two, so you correct have:
device 1 on
device 3 on
device 4 on
device 5 on

Which is what you originally expected, but at least you now have right? WRONG... behind the scenes HomeSeer is still pissed off. What you now have is an event that LOOKS perfect in the GUI but in reality:
1. Triggers
2. omg omg omg omg i'm going to die let's get stuck for 10 seconds waaaaaaaaah waaaaaahhhhh omg omg
3. Okay I've calmed down now
4. BOOM, device 1, device 3, device 4, device 5 all instantly now on

Fix is to just delete the whole thing and recreate, then things are instant again.

Your mileage may vary because this isn't always consistent either - seems to be worse the more devices that are affected, or maybe just if HomeSeer decides to just be in a worse mood.

As for deleting the original trigger, I'm actually surprised it doesn't go even worse and maybe damage other events along the way...

[BobSpen]

Would it not be a simple software change for HS engineering to eliminate the "X" in the trigger line???

[donstephens]

Thanks for the head's up.

[randy]

HomeSeer has a bug in Event editing that will allow you to corrupt an Event by creating a non valid Trigger. Here I have built a simple Event with a single Trigger and Condition:



There are three options for deletion in this Event marked by this icon


The first will delete the entire Event, the second will delete the Trigger and the last will delete the Condition. If you delete the Trigger, the Condition below it will become the Event Trigger. Since a Trigger must always be based upon a change or setting of value, this Condition became a non valid Trigger and will never be true.

Do not EVER delete Triggers, just change them if they are incorrect. If you find you need to delete a trigger, FIRST delete all the associated Conditions, THEN delete the Trigger. Otherwise your Event will become incapable of running or will give unexpected results. Here I deleted the Time Trigger from the above Event. You can see that the Condition was moved to be the Trigger and as such can never cause the event to run.