EasyTrigger schedule misbehaving occasionally

[danielross]

Hi, I have been a long time registered user of EasyTrigger in HS3 and have been very happy with complex events working absolutely perfectly for years. Recently I decided to move to HS4 - I did a fresh install of HS4 and recreated my devices and events, basically a fresh start (as upgrading didnt work on my computer for some obscure reason).

While easytrigger mostly works as expected, I have a strange issue I cant troubleshoot.

I have an event (event A) that turns on a humidifier in my kids room based on humidity levels, and immediately fires another event (call it event B - see attached). Event B's purpose is to speak an announcement, but ONLY between 8AM-9PM daily AND only if a 'voice announcement control' virtual device is set by me to ON (I have it always on, I only switch it off when I have guests).

Here's where the trouble starts. When event A fires, most of the time event B is triggered as per the stated conditions above. However occasionally, event B fires and speaks the announcement well past 9PM in violation of my easytrigger 'Announcements' schedule. At first I thought I was dreaming because it happened in the middle of the night but then the next day I do see the event record in the logs. It seems to happen every 3-4 days at random times in the night. Attaching one such example.

So what's wrong? Is it the way I have things set up? Why does event B sometimes successfully fire and execute the speak action ignoring the EasyTrigger schedule?

HS4 version: V4.1.17.0
EasyTrigger version: 3.0.0.73

Thanks for any help in advance!

[ewkearns]

You might also want to check and see if "B" did NOT fire at times that it was expected, but fired later. There are reports of this: Here.

[danielross]

Thanks for the tip.... so far I haven't noticed any other events misbehaving or running late. Will keep an eye out.

Incidentally I have been trying out Home Assistant because it has a decent integration for Xiaomi Mi Air Purifiers. Going down the rabbit hole of HA, MQTT, Node-Red, mcsMQTT, ESP chips running ESPEasy firmware - everything's working absolutely fine EXCEPT this irritating voice announcement in the middle of the night. I have briefly thought of ditching HS4 and going back to HS3 or HA if this issue persists.

[Wade]

Might you have overlooked checking "run only if conditions are met" in the event that calls this one?

[danielross]

Might you have overlooked checking "run only if conditions are met" in the event that calls this one?

Wow how have I never noticed this before??? I think me overlooking this option could be the root cause of the misbehaving event/schedule. I have ticked the box now and will report back!