Earlier of two times results in execution at both times

🛎️ Get Help
1

Hi,
I'm using the "earlier of two times" setting in mode manager but it is executing at both times. Specifically I set a mode at the earlier of either 8pm or Sunset+90. This was working as expected for quite a while but has stopped working in the past month or two.
I have tried switching the times in the rule without any impact and I just removed the entire Mode Manager app and installed it again and I am seeing the same issue.

After setting up the Mode Manager app from scratch again I see a "timeHandlerNew2" handler set to run at 10:04pm tonight, which is corresponds to Sunset+90 and is very much not earlier than 8pm.

Thank for your time and attention,
Matt

2

It always schedules both times, not knowing in advance which will be earlier (the app might run for many months). When it runs at 10:04 PM it should determine that it is the later of the two times, and not change the mode.

Are you by chance changing to some other mode in the interim between the two times?

I will spend some time tomorrow checking this again. We are at the very tail end of this release cycle, and it may not be possible to get any changes to this in. However, in the next release, there will be an entirely new version of Mode Manager. We will be certain that it does not have this problem. In the interim, since you know, for now which is the earlier time, perhaps you could just use that until that next release comes out in a couple of months.

3

Ahh, that makes sense. I guess I will need to wait a bit to see if the problem continues this evening.

Yes, I have another change to a different mode at wither 9:30pm or 10:30pm depending on the day. So during the summer the mode with change between the two times that it evaluates.

That makes sense and I understand the reasons.

This also makes sense as a mitigation, but I will admit it is a little frustrating. But I also fully understand not having time/resources to chase a bug in a version that is being replaced.

Thank you for your response! I really appreciate it!

4

We will have a fix for this in the next hot fix release. That should come today or tomorrow.

2 Likes
5

Wow, thank you so much! That's great to hear!

6

I hate to mention this, but I experienced this issue again today, after the update to 2.3.2.132. For the time being I've gone back to a custom written rule to set the mode based on which time is earliest, so this isn't a pressing issue for me. I just figured you might appreciate knowing that it still might be a problem.

I'm happy to help troubleshoot this if you need, but I assume you have other things which are more pressing.
Thanks for all your help,
Matt