Thanks for linking the other post @JDRoberts, I hadn’t seen this thread earlier. I’ll advocate for hotfixing this issue and may reach out to some of the posters here to potentially receive an early firmware update to aid in confirming that we have the right root cause analysis and fix for the issue.
Based on what we’ve seen, we believe that the portions of local smart lighting automations that are not working or which may work only after a period of time are those that trigger based on a time condition rather than a direct device event. This appears to be a bug in the hub software missed during our testing – in setups with devices triggering events on a frequent basis as is the case in many of our test setups, internal beta, and external beta populations the problem is less obvious or not present due to a number of factors and depending on the automation.
Our product people such as @evanartis are aware of the SmartLighting use and the features it provides that are either not available or less convenient in other parts of the product. Loss of functionality in this release is not intentional.