Another workaround to try (if you’re using Keen vents with the stock device handler):
The vent updates its status every minute. Use this as a trigger event in Rule Machine, compared to something that will always be true (e.g., temp > 0). Then configure a custom command for your current temp sensor (again, in Rule Machine) to refresh its state (i.e., “refresh()”). Finally, tie it all together by having the action in Rule Machine force a refresh of your temp sensor. Since the trigger will always be true, and the 3 decimal place temp reporting of the stock device handler will almost always (better than 99.5% of the time) result in a temp change at every reporting interval, your existing temp sensor will update it’s status every minute.
I use this exact configuration to force a refresh of an ST temp/humidity sensor that controls a bathroom exhaust fan, so that when the humidity rises more than 2% in 1 minute (like when someone is showering), it turns on the exhaust fan. Without timely updating of the temp/humidity sensor though, it wasn’t much good.