Thank you, Mr. Lucky, for that update. FWIW, I have the new Samsung Hub (i.e., SmartThings 2.0) and plan to drop & then reinstall everything when I move over to it (soon), but I’d hate to have to reinstall everything repeatedly like you’ve had to try. I was hoping to wait long enough for its new-product bugs to be worked out before I stuck my neck out. I’m hoping it’ll be more reliable at least for local things (e.g., turn on/off lights/outlets at a specific time rather than at an offset to sunset, etc.).
Putting in tickets now on the individual issues is really important, because judging by volume (not very scientifically), it seems that most things are fixed.
I still haven’t had to reboot my hub once, I did reset a number of apps/routines, and I’ve had no more problems. I’m only one case as each of us is, so now it’s important to get ST more data to stamp out current issues. This self-healing is new, and is only as good as it’s programmed to be, so more data will help.
My 0.33 cents.
1 Like
I dont seem to get results on my tickets. I went back and checked, and my last two that I actually got a follow-up on, the tech said they would do work/research and get back to me, and I never heard anything back.
Someone yesterday mentioned to use the in-app chat. Every time I initiate that my app crashes. Latest version on iOS 9.1.
1 Like
Ask them nicely for status. They are pretty good tech support when I compare/contrast, but they are also overwhelmed and understaffed right now.
Sometimes you just can’t get what you want when you want, but you can’t stop trying. Tickets are so easy to create, and do help even if one or two are not handled properly, I believe most are…
One thing is worth mentioning, we need to NOT take workarounds as solutions for our tickets. I’ve been very adamant not to accept “solutions” where I cannot confirm that the issue reported has been fixed. I’ve had several tickets where a workaround was provided and the ticket was subsequently closed. I used to accept that but is not the best solution if we really want things to get better.
Checking the status of your tickets is easy by following this link:
A reply to a closed ticket reopens a new ticket (the same ticket is reopened IF the "unsatisfied: flag is tagged). I now have a standard response for tickets closed without addressing the real issue:
Thanks for your suggestion. I am using a different app to address this issue. However, this is just a temporary solution. Can we please keep this ticket open until the fix is implemented?
I know this may seem harsh, but to me, closing tickets without actually resolving the issues, makes it look like the issue doesn’t exist anymore…
5 Likes
I have an event that is stuck 4 days in the past. Yes, I know I can get it un-stuck by re-initializing it, but should I have to? They know about the problem, and said they’ve fixed it and put in measures to keep it from happening. They should be able to find out really quickly how many events are stuck in the past to see if their “fix” worked.
What about users that aren’t active in the forums or into the developer API?
I want to see how long it will take to heal itself again.
1 Like
Can you tell me how to find that view that posted in that screenshot? For some reason I cannot find it in my dev portal.
My Locations > Installed SmartApps, then select the desired Routine or Smartapp.
Awesome, thanks. That helps a lot.
I feel like the community users can (edit) help ST with the self healing so that people who don’t come here have their hubs magically work. It’s a natural arrangement in the technical world, the community users tend to drive closer to the edge…
So I think it’s perfectly valuable for you to test/measure the healing of a routine as long as it doesn’t make you unhappy, and you report your findings pretty accurately to ST on a ticket and here (for our endless opinions and ST poking, all constructive of course…)
1 Like
Just wanted to mention from another topic, that if you had scheduled events go bonkers, you may have to restart the schedule for Hue polling as well.
@slagle May want to check and see if this is being added to the automatic schedule healer logic
1 Like
My goodnight continues to fail despite modifying the time and re-saving it. Is deleting the routine and adding it back working for everyone?
Deleting and recreating didn’t work for me, but removing the ‘set dimmers to this level’ did. If you are using that feature, you need to remove it for now, if you want your routine to run.
2 Likes
Routines that use “set level,” whether for dimmers or thermostats, appear to be failing. This is new over the last few days.
https://community.smartthings.com/t/trouble-with-modes-routines/28641/9My goodnight did not run correctly last night. It did not lock the door. It ran fine when I ran it manually. It does turn off lights but no set level.
Good morn ran fine this morn
My time based routines have been failing as well… And all they do is change the mode… All my lighting is based off of mode changes…
It seems to be back and the self healing doesn’t appear to be working either. I have one event stuck 5 days in the past.
Hmm… Most of my scheduling seems to be working reliably except for one of my Custom Device types.
It’s odd how some people have issues and not others. Even the smartapp is displaying the correct mode for me now 
1 Like
What happens when you manually reboot the schedule? Official app or custom?
There are at least three other threads besides this one, all describing bits and pieces of similar problems:
As if this weren’t bad enough, there is little to no involvement by ST in any of the threads, and Support (when they finally get around to responding) seems to be operating in a vacuum. I’ve read in these various threads of people with the same or similar issues that are actively involved with Support in troubleshooting, yet the person I’m dealing with is still in the discovery mode. Not faulting him, but honestly… there seems to be no communication at ST – either externally to suffering customers, or internally amongst themselves. Multiple people working on similar issues, seemingly unaware of what the other is doing. This is insane!
Okay, I feel better now. 
Just to end on semi high note, and for the benefit of people who are looking for something to try, here what works (temporarily) for me.
- Delete all Routines that involve the failing mode
- Remove all reference to the failing mode in configured smartapps
- Delete the failing mode
- Recreate the mode you just deleted
- Add back Routines and smartapp references in the same order you removed them (not sure if the order actually matters, but it works).
This is specifically for modes that fail to change as a result of a time-scheduled Routine. In my case, other actions that are part of the Routine execute… only the Mode change fails. Of course, things scheduled to happen as a result of the Mode change will also fail.
NOTE Re #3, above: Yesterday I encountered a situation where I could not delete the mode within the IDE. It produced this error:
However, I was able to delete it from the mobile app.
My open ticket is #154180. If you have a similar issue, please reference the number to Support, so that we may possibly get the same people involved working on them.