Ugh. Ditto here. it’s one thing after another for SHM this weekend.
I think I posted this to a thread after it was moved here.
Update, it’s also not showing the status of lights and things correctly.
Trevor at support basically told that since I’m using Rule machine which they wont support and Android which doesn’t work well with rule machine they cant help.
SHM is now our daily alarm clock when the alarm goes off because it does not disarm. I am being pressured from the family to get rid of it. Is there a root cause and a timeline on a fix? The entire system is about to go on ebay and looks like I will be signing back up for a good ol’ fashioned security system again and maybe after that 2 year contract is up, I will check back in to see if this or other platforms are stable, its not worth the hassle to have lights magically come on and off. I still have some clappers in a drawer somewhere, at least the kids liked those.
They are just BS you. I am using the default ST routine app, still not working.
It looks like ST is gearing up to last the Android app problems and everything else they can on rule machine.
I’ve been experiencing the “failed to load smartapps” problem on my Android. It works fine on ios.
I was shown the server logs stating that rule machine was exceeding 20 second time out limit. And that it is because of the number of rules I have (75).
The funny thing is, the app is timing out at 10 sec and it works fine on ios
@bravenel, has ST contacted you yet? Are they telling you that there needs to be multiple installs of RM, like I was told?
I predict ST is going to abandon Android and behind ios only.
So I woke up this morning and I checked that my morning Routine successfully disarmed my system, because the app showed disarmed. However, when I opened my back door my siren went off and the lights came on so technically it was still in the Arm (Stay) state even though the app was showing disarmed. What I had to do was tap on Arm (Away) and then back to Disarm and it successfully disarmed my system. This is obviously a very frustrating issue and it is rather amazing that it is taking this long to fix it. You would think Samsung would have techs working on it night and day. I love this system (when it works) and I’m willing to be patient, but my patience is starting to run thin.
@ndavis82 Arming Away and then Disarming worked for me as well. Thanks for the tip. At least there’s some sort of work around other than having it constantly armed.
Who showed you this? 20 seconds applies to each rule not to the collection of rules. Please post here or by PM whatever it is that’s showing the timeouts.
Below is what was sent to me:
I can confirm the error is with rule machine:
smartAppName=Rule, author=Bruce Ravenel and Mike Maxwell, namespace=bravenel, locationId=112e28a0-8488-4f6e-b7d5-088a26126458, locationMode=Late Night, gitRepoId=3771, username=alabamaslammer21@gmail.com, type=onSchedule, method=timeHandler, runTime=22709,
java.util.concurrent.TimeoutException: Execution time exceeded 20 app execution seconds: 25032695149975
I totally agreed with @DeanSmith at
He can confirm that a Rule timed out, which is because of the platform, not because of the Rule (unless you made an infinite loop). Looks like it took longer than the universe is old to run.
Not an infinite loop. I purposely set up my rules to ensure there are no loops, they are unreliable and cause problems.
Would you please shoot me a screenshot of the rule that timed out, by PM.
There was no rule timing out. I was troubleshooting the “failed to load smartapps” error I keep getting when I’m trying to open the smartapps window.
That’s what I was given as a reason for that error.
[quote=“luma, post:45, topic:42157”]
this implementation could not possibly be worse without actively setting my house on fire. [/quote]
Stay tuned - coming in next release!
.
[quote=“U3gRJLfQiF9C, post:80, topic:42157”]
So many problems and so many complains for few days now. Yet http://status.smartthings.com/ is showing everything is “Operational” and “No incidents reported” [/quote]
It’s a Marketing tool - nothing more. You will seldom (if ever) see an issue posted that they don’t already have a solution for. It’s designed to give the impression of a stable system that has occasional glitches, which are quickly fixed. Just look at past incident reports and compare it to your personal experience.
…chiming in to say “me too” - routines are not disarming SHM (but they DO arm it!). Clicking “Disarm” spins, but I can temporarily get around it by clicking Arm, then clicking disarm.
That’s exactly what the error showed, a Rule.
I don’t know what rule. I was trying to open the smartapps page.
I’ve sent several more messages, no response back.