Your memory is a toddler? 
I get what you mean. I’ve seen that, too, and it’s cool that it’s there to enable Vacation Mode for devices that have that feature, but the operation of the feature itself is still broken and doesn’t respect the time windows when it’s supposed to be operating—at least not in my experience.
Right, as I understand it you can’t have one Automation be an “Action” of another Automation. That would be a cool idea, though. I was going to suggest that you request this in the Wishlist, but I see that it’s already there:
You can already do this by writing your own Automations. You can create Schedules and use the “Turn on vacation mode” and “Turn off vacation mode” Actions for devices that support it, but you’d have to do this for each device instead of just calling the existing Shortcut. Basically you’d recreate what the Shortcut does in a separate Automation but just make it a Schedule type.
That still doesn’t fix the problem, though. If I set one Schedule to turn on Vacation Mode for my lights starting at 6:00 p.m. and another to turn off Vacation Mode at 11:00 p.m. but that same Vacation Mode doesn’t activate the lights within those times (which are already the times for one of the stated windows, according to Wyze’s documentation), then I haven’t really accomplished anything. If Vacation Mode wants to turn on lights at 3:00 a.m. when it’s turned on but I’m using a Schedule to keep it off at that time, then I get that the lights won’t be turning on overnight when I don’t want them to, but I’m still not getting the lights to turn on when I do want them to.
I think what you’re suggesting is a partial work-around, and I can see how that might help with the overnight hours, but it doesn’t fix the issue where Vacation Mode already is not turning on lights when it should during the morning and evening hours, as it’s supposed to do.
I’m glad you replied, because it made me think through this a little more, and I see what you’re saying. It’s just not a complete solution and doesn’t fix Wyze’s issues with time-based features. (There are currently active topics about users seeing calendar days not matching with days of the week and users in time zones with 30-minute offsets having their cameras misbehave because Wyze hasn’t correctly addressed time.)
Not officially, no, at least not as I understand it. This is primarily a user-to-user support community, though some Wyze Team members do occasionally comment in various topics. I think primarily they track the Wyze News, Beta, and Wishlist categories; others are hit-or-miss.
To keep this on their radar, I’d probably start with reproducing the issue, submitting a log, and then opening a ticket that references the Log ID. That’s what I did last year. Support will tell you that they can’t access the logs, but those are supposed to go to the engineers, and I try to drive home the point with Support that I want the information in the ticket linked to whatever logs I’ve submitted (using the Log ID) so that the developers have a full description of the problem.
I’m also hopeful that fix-it-friday will return at some point, because this is an issue I’d like to see get more attention and a full resolution.