So, like many others, I’ve had massive issues with routines not firing, (time and presence, and any really,) reliably. I’ve also had pretty crappy luck with Smart Lighting. In fact, the locally-installed automations were LESS reliable than the cloud-based ones.
I’ve moved almost all my lighting automation to Rule Machine now. I assume the default reaction is “uh–dumb, that’s not local at all.” – and at first I would have agreed with you. Now, when I open my closet door, the light is on before it’s even fully visible. Instantaneous. Everything I have set up using Rule Machine is working just like this. I have also added additional logic, like an “Auto Lights” virtual switch to control each section of my house… as a variable basically. Of course this is not really possible with Smart Lighting, and I do not fault it for that.
I do wonder, how it is that cloud-based, user-provided smartapps are running complex lighting automations more reliably and quicker than the OEM solution that runs natively, locally.
So now, with months and months of issues with my routines not firing properly and playing tag with ST support, I am considering doing the same thing with Routines–and moving them to Rule Machine. My greatest fear is that somehow I will overload the RM framework–or that I will lose these all during an upgrade in the future. I really, really, wish there was a way to backup these automations. Perhaps the smartapp could have an import/export option for google drive, or something. That would be awesome.
Does anyone know if I can add a second version of Rule Machine, and call it “RM Routines,” or something? Not sure how the child smartapps communicate to the parent–if the name matters in this code. I hope this doesn’t sound like pure whining—because I’m not trying to. I just want to use whatever works best. So far, writing this all out using RM is working much, much better than using Smart Lighting, and I’m confused as to why.