I thought the name change is enough to update it?
Depends on how optimized it is, if itās just a name change I would not re-evaluate all the actions to see if they are cloud or local since the actions do not change.
Iām curios as to what they say. I was under the impression that the name change was enough (and they asked me to do that for the routine to test it). If not, Iāll make a more substantive change and see if that does the trick.
8 days ago they asked you to change the name, yesterday they asked you to modify the scene thatās included in the routine. Seems like a different request.
correct. I changed the routine name last week and today I changed the scene name. Same approach but for two different parts of the puzzle.
Hi @homeagain
Just to clarify, your scene is already set to run locally, which is great.
However, the routine that triggers this scene is still set to run in the cloud.
SmartThings doesnāt automatically re-evaluate whether a routine can run locally when changes are made inside it (like updating the scene or devices it includes). Thatās why the team recommends the following:
Could you please edit the routine again? Just updating the name is enough. This will trigger the system to re-check whether it can now run locally.
Since the scene is already local, once the routine is updated, it should be able to run locally as well.
Let us know once youāve done that so we can confirm. Thanks again!
That worked! So to confirm, for older setups, I need to change the name (or something more significant) of both the routine and the scene (manual routine) to get them to update to being local?
Thanks for confirming it worked!
To answer your question, yes, changing the name is enough to trigger a re-evaluation on SmartThingsā side.
If you have routines that include older scenes you believe are eligible to run locally, hereās what you should do:
- Update the scene first (even just changing the name). This will move it to local if possible.
- Then, update the routine (again, a small change like renaming is enough). This triggers a re-evaluation, and if it now qualifies, the routine will also move to local execution.
Thanks- I did this on about 15 different routine/scenes and they are mostly local now!