There may be a more straight forward way to do it now, but the traditional way is to add a condition to the automation based on the automation's (or maybe the light or motion detector) last_triggered property. You need, AFAIK, to use a template for this.

A condition with something like this should make it so it can't fire more than once every hour (60 seconds times 60 minutes): {{ (as_timestamp(now()) - as_timestamp(state_attr('automation.driveway','last_triggered'))) > 60 * 60 }}

You could use mode: single, and then add a 10 minute delay onto the end of the actions.

I'm using the timer helper for this sort of thing. You can have a condition in your automation for not triggering if the cool down timer is active.

A quick and dirty solution would be using a date input helper, that get's updated with every run and is used in a condition. But there is probably a smarter way

To me this automation seems much better suited to using the Node-RED addon. There is a built in “delay” node that can be used for rate limiting. You would set the delay node to once per hour and put it between the node watching your motion sensor, and the node flipping the light switch. Easy stuff. You could do the same with one or two more nodes to get and check the current wind speed and put that inline as well.

Keep in mind though, any kind of rate limiting/cool down makes it more likely that the lights won’t turn on when you actually want them to. For example, if you leave the house and come back after the lights have turned off, but before the cool down period expires you won’t have lights.

Add a door sensor to your setup? Have it trip, the lights then wait for the door to open and close before it trips again.

I mean let's face it, if someone keeps coming into your garden and doesn't knock on your doorz at nightz you don't want them to be able to see where they're going.

Just a thought.