Hmm. So, I rolled back to .132 and my rules looked intact again (at least when I examined them all after the rollback).
Do I need to be going back before that (i.e., to .129)? And, do I need to restore the entire DB? Or, should I be safe with just the platform rollback to .132? And not touching anything for now?
Then may I respectfully suggest that, until a fixed platform version is released, one of the staff magicians make the “Download latest version” button in Diag Tools cause 2.3.1.129 (version before the issue was introduced) to be downloaded?
With all due respect, it's Friday night. I can't promise that anything can be done before Monday, and the most likely thing to happen is a hot fix. Something might happen prior, but that's not known at this time.
Was on 132, noticed no "Broken Actions" but found errors running a rule setting a local variable to a device attribute (sensor value). Rolled back to 129 (with current database), now the rule showed "Broken Action", threw an error and needed to be manually fixed. YMMV
As usual, HE staff goes above and beyond on dealing with issues that arise. Companies I've worked at/with in the past would not even be aware/looking at this until mid-day on Monday at best, maybe a fix by the end of the week. Just another reason why HE is the best, IMHO.
LOL...I have, lovely state, but tons of sun. I did forget to mention the incredible amount of ice cubes required to maintain a livable temperature inside the dome.