2 days ago, I got my notice that it was time to update my Smartthings account to Samsung. Immediately after, all of my CoRE pistons stopped executing. I can see the evaluation change when the criteria is met, but the state itself won’t change unless I simulate. I’ve updated CoRE and tried repairing/ rebuilding all pistons.
If I create a new piston, it will work (for now) but I have a dozens that I would rather not reprogram.
So far, tech support has offered up resetting the Hub and uninstalling / reinstalling the classic app as their suggested fixes.
I don’t have a solution for you, but do local automations still work for you? Even the most basic automations I create in the SmartThings Classic app stopped working a week ago, but Haven’t figured out why.
Also, I highly recommend you start migrating your pistons to webCoRE as CoRE is no longer being updated except for the occasional patch to fix issues. You will find webCoRE easier (once you get use to it) and more powerful than the older CoRE.
If the info above does not resolve your CoRE issue, consider posting on the webCoRE community forum at https://community.webcore.co
My basic automations still work. And I only have one location on my IDE.
CoRE’s pistons are there but the state from true to false won’t change unless I run simulate. Even if I alter the piston. This leads me to beleave that an unseen attribute has been changed on the pistons since any new ones that I create still function.
Yet another example of how Samsung needs to finally implement a backup system.
I’ll start looking into webCoRE when I have some down time.