Sastrugisnow

I also run into this situation. This must be a rather common situation. I'm surprised it doesn't surface more often. I solved it using the node-red-contrib-time-range-switch as suggested but it's...