I am also am receiving the error on my android (Note 4 v5.1.1). In fact, I cannot create new rules, triggers or actions. RM works fine on my iPhone.
Will contact support.
How about dreams within the scope of your ability to influence or effect? What ST does in the future shouldn’t be part of anyone’s dreams. I dream of an HA system that is programmable and reliable; I suspect that means it won’t be SmartThings.
They have posted “degraded performance for Android” in the system status.
1 Like
Agreed - I’ve seen things change at companies to fix things - not saying it will here. However, I know I speak for a lot of us here that we’re just grateful that your work has given us something that begins to approach a workable system.
That’s not to be overlooked or overstated. Thank you!
1 Like
Hah. I think you keep thinking that I’m in the UK… I’m not 
1 Like
I understand… but it’s not broken for me. I can go into existing rules, and even go into the actions/conditions/etc without issue. Go figure.
My bad… Now I remember, we’ve had this conversation before… HaHa 
I was just able to create a a trigger to test with no issues on my Android…hopefully it’ll hit everyone soon.
Cool! Thanks. 
No, I had no idea.
However, in my case, it’s not just the older versions that I want. What I want is exactly whatever it is that’s in the ‘Code’ field on my end at the time of updating.
Regardless of how many ways somebody figures out to tell me it’s just an OCD thing and completely unnecessary, I’m still gonna keep doing it.
Why? …it is indeed (at least partially) an OCD thing lol
from the status page… “some Android users are experiencing problems configuring certain SmartApps. We are investigating and will continue to provide updates.”
For me, rules are not functioning at all. I have a temperature sensor to control a frost protection device, and today it is not firing…and of course the android problem means I cannot go in and see why.
I have adopted the precaution of always having multiple controls on anything important, and my virtual thermostat app kicked in as a backup.
Aye, and there’s the rub. 
hey chick @bravenel has built one hell of an app for us. ST would be next to useless for me without it and the best part HE DOES IT FOR FREE!!! If he gives us something that occasional has a bug here or there you cant complain because he is one man and its not like you are even paying for it. If you figure in how unstable the ST platform itself is I think his Rule Machine is about one of the best things we could ask to have.
6 Likes
AYFK?! Do you think I don’t know that? And do you really think he’s one man? Do you think I haven’t contributed to the development of the app by finding and helping @bravenel resolve issues with the app? Are you suggesting that the time that I’ve spent doing that is valueless? Do you think that the time that others have put in to debug this is, as well?
I get the whole open source/community development thing. I get that. And I love RM. Really, I do. And I’m quite familiar with agile development. I also believe that, as this functionality becomes more a central part of a more and more people’s implementations of the platform, stability, in addition to new features, becomes a key aspect of its usability/attractiveness. I was simply suggesting that perhaps it’s time for this app to adopt a bit more of a “structured” development model, so that every update doesn’t open us up to a new bugs.
Yep! Must be that new math! 
2 Likes
Is anyone getting the red banner when attempting to open a rule? Seems like the Rule is the only app…(update: Smart Lighting suffers from the same red banner disease)
I see that it’s been going on for a few hours:
From Platform Status:
Update - Issues loading Smart Home Monitor on Android should be resolved. However, some Android users are experiencing problems configuring certain SmartApps. We are investigating and will continue to provide updates.
Nice.
At least the all mighty cloud is not biased ‘certain apps’ includes the home grown local processing app!!!
Doesn’t that basically say, “hey, we know it’s broke, but we fixed it, unless it’s still broke”?
To those complaining about needing a more stable development life cycle for RM, stop updating with every single thing he commits. Agile development does not mean CI to prod.
It’s very simple, if what you have is working, and you don’t need a new feature, don’t update.
The allure to keep grabbing the latest is something I can understand. Sure, my stuff works now, but maybe it can work even better. The reality is that although this is technically the master branch, it’s develop. If you treat it like continuous integration (sans any unit tests) you run the risk of breaking things. Why don’t you just hang back and let someone else report that it’s broken?
If you have a problem, then update and re-test it. Presumably one of Bruce’s first questions is going to be the equivalent of “are you running the latest?” If it fails on the latest that’s a helpful data point. Bitching about him breaking random things with each commit is pointless. RM is what makes ST useful. Period. The fact that he does rapid development is absolutely fantastic. For those of us that understand the risk, it’s the price of the game.
Report your issues, add to the discussion and help RM get even better. It’s easy to roll back in github so just pick a point where your important stuff works. Play with the latest, roll back if you need to. The last thing you want is Bruce to bail over whining about his free efforts screwing up your setup. Maintaining a proper master and develop branch setup is overhead for him. It’s just not needed when you can create your own personal master by forking and or not updating.
/rant
3 Likes