Well it’s not across the board, my whole system is working right now, apps, devices, integrations and all.
Looks like things are slowly making their way back online. IDE came back first, Android app still chunking through some things…
Maybe we’ll get lucky and this will have been an outage to beef things up? Nah… doubtful - no warning on status.smarthings.com…
Nope. My mode change still isnt working from night to home. That really is the only thing Ive been having issues with since last week…a couple days after the update on the 22nd.
I think that’s the key - I never understood why RM locked you in to whichever of the three sub-types you started with. Just make everything a Conditional Trigger, and if the user doesn’t specify one or the other when they set it up, don’t lock them out from changing that later.
The important difference between Rules and Triggers is that rules are activated on any state change of whatever it is the rule is evaluating. A conditional trigger could be activated by one thing changing state, but the conditions can evaluate entirely different things. Those things changing don’t cause the condition to be evaluated, only the trigger event does that. It would be fine to make all rules be what RM called Conditional Triggers, and just make clear to the user that if they don’t specify a Trigger, the rule is evaluated whenever anything in the Condition statement changes state.
I think you’re all over thinking it.
RM filled a hole that ST had no intention of filling.
It allows the full potential of the system. And now it’s a dying animal.
1 Like
So, nothing on status.smarthings.com - but this morning has been a nightmare of backend Cloud weirdness - lights turning on randomly, and a ‘battery pull’ reset of 6 of my Aeon Multisensor 6s (which are back to using the standard ST-provided device handler) due to no communication with the Cloud.
The sensors clearly are registering locally (when I walk in front of one, the green light denoting motion detected goes on, but doesn’t register with the ST Cloud at all). Pulling the batteries is the only thing that gets them back, and even then it may only work for a short time before it’s needed again.
Hub reboots have no effect on solving this - it’s got to be related to last night’s hiccups.
@slagle - nothing came up on the status site - are there known issues that aren’t disclosed yet?
Plus, we can’t remake the app the exact same way. But fortunately, the code is not proprietary, only the app.
This can either be broken down into multiple very specialized apps that are extremely powerful. Or, it can be redesigned and changed enough to not be the sane puritan.
Personally, I kind of like the idea of breaking it down. But then again, I like the ability of not having to worry about one app not talking to another.
It is a dilemma.
But, in my case. I have the latest code of the full version. I intend to use it until I can’t make it work or something better comes along.
Though, I am happy to help with a new project that will work great for new post-RM users.
3 Likes
Folks, you are seriously going to confuse new people trying to figure out what rule machine is/was if you keep putting trouble reports for the general platform in this thread. Please take them to one of the trouble report threads instead. Thanks!
Here’s one option:
10 Likes
Good point - my bad… I’ll take future things to another of those threads.
In general, the problem was that general platform things as they popped up were usually faced by those of us using more advanced things like Rule Machine.
Thanks.
1 Like
Hi,
For a quite long time I didn’t need to create a new rule on rule machine. But today I had to create a new rule.
And then when I press “Create new rule…” I get to an error:
“You are not authorized to perform the requested operation”
Is this a generic problem ? What can I do to troubleshoot it ?
I have Rule Version 1.7.0d
and Rule Machine Version 1.6.6
Thanks.
##Definitely NOT…
3 Likes
I’m also having the same issue. I’m getting the famous “You are not authorized to perform the requested operation” when trying to create a new rule.
I’m currently on version 1.7.3/1.7.11c
Could someone please share the latest version with me?
Thanks,
Ryan
Thanks, guess I can only pray that maybe one day he will come back and release new versions 
1 Like
new version does not solve the issue. I’ve tried it.
I don’t understand why it does not affect everyone if it is a platform generic issue.
btw, I also have issues with my Minimote (range is severly decreased)
it all began after my hub was updated.
This is really bad.
Because there are dynamics that are not fully understood by us as end users.
For example, the cloud based backend infrastructure. You maybe connecting to a different stack than I. Your stack maybe more healthy or less healthy than mine. Therefore we may get different results.
This is but one example. There are many such potential dynamics that are unknown to us and are unknowable unless ST were to document and disclose to end users. I don’t think that’s likely to happen or even a reasonable ask. All we really want is stability.
There have been many attempts to try to discern why one’s deployment is more stable than others - often trying to correlate it to things or dynamics known to the end user and within their control. These often come with hubris and confidence that one has it figured out. Only to be hit by dynamics later on they can’t explain that shake their stability, etc.
2 Likes
FWIW, when I was getting the you are not authorized… error, I contact support and they claim to have done something, in the end, the error went away
Good luck
Rick
Has anyone ever asked what it would cost to buy the code to open source it - I guess the community would contribute to get a legal hand on the advanced code …
Bruce isn’t motivated by financial incentives any of us can afford…
10 Likes
Ok but actually nothing hinders anyone to modify the code and publish the changes for people to implement
Everyone could easily publish search/replace instructions to advance the code without breaching the license included in the latest code - just not the conplete code - at least thats what the included copyright and license state