App down again (February 11, 2017)

NA01 shard with android working in Western NY.

Do put in support tickets since it hasn’t hit the official status page yet. :disappointed_relieved:

I have added it to the first bug reports page in the community-created wiki, but that’s just for community use, support doesn’t read it.

I’m on na-01 and physically located in SoFlo. Not working, but being patient. Turned off the fan so it can’t be hit by anything, right? :smiley:


Na-01 here as well in Niagara Falls Canada. Automations are hit or miss. Routines tab will not load. Smartapps tab loads but selecting any apps yields “sry but there was an unexpected error”. Choosing a device yields “failed to load device”. Also mode is blank in the hamburger menu and cannot b changed via the ide either.


Same here can’t open app. Submitting ticket

1 Like

So basic pistons work but the app does not and either do routines for me.

1 Like

Yeah, exactly my situation :rage: … and the status line (offline/online) is missing from the hamburger menu, too.

The Minimotes work, though :neutral_face:

… time to make breakfast I guess, while this blows over …

1 Like

Mine were too the only problem is I have one of them set to run a routine to change it from night today but doesn’t work Fortunately I was able to turn off the alarm because I have a piston tied to win the front door is unlocked with code

For those running into issues could you take the time to:

  1. Open a support ticket if you haven’t yet with details
  2. Let me (and support) know if you have contact book enabled with contacts? (if not please DM me your username as well)


1 Like

Im on na-2 andriod
i can open the app fine but there are no routins
and mode is blank

Edit @vlad
yes i have contact book enabled with contacts
Opening ticket now

done…ticket 318364

Yes to contacts… But why would that matter? Everything was working last night and now it’s broken this morning. Unless someone pushed yet another Friday evening update…

"The beloved red network error is back. Can’t load routines or smartapps, just spins and spins. Clicking any device reports a red ‘failed to load device’ message."

agreee it worked at 2:30 AM EST and did not work when the dog got me up at 5:30AM so what changed in that 3 hour window?

1 Like

There was a regression with a deploy that went out on Friday morning. It effected how contact book is loaded from the database. They have a long timeout in the cache because they hardly ever change, as the records ttl’d out of the cache more people started to see the error when hydrating the cache again by reading the record from the database first.

A fix has been rolled out.


Can you guys please please PLEASE stop making changes on Fridays. Especially when you don’t even bother to staff / check for outages after the fact. I’m honestly so frustrated with these Friday / weekend deployments that continue to break MY house. There is a reason no other SaaS / cloud company deploys past Thursdays. Why does ST elect to keep going against best practices that have been well established and adopted in the industry for a reason?!


Couldn’t agree more

And why not update the status page if there’s an issue that affects multiple users and ST staff are obviously aware of it?

This is the exact reason we need a viable option for local execution and no cloud dependency. Really getting fed up.

There are many reasons. Unfortunately ST has never indicated this platform will be anything but primarily cloud based.

1 Like

Different architectures have different pluses and minuses. There are a number of competing systems that run mostly locally, and their customers almost all complain that they don’t have cloud integrations with Alexa and IFTTT and weather services and MyQ and notification services. So in part it’s a matter of deciding what’s most important to you.

That’s not to let anyone off the hook for unreliability. I use Siri and Alexa and Netflix and Vue every day, which are all cloud-based services, and I’m happy with the level of reliability.

So I think there are two separate issues here. The first is whether you really want/need a primarily local system, and the second is the MFOP ( maintenance free operating period) that your household requires.

All of which is to say I’d rather see the focus put on reliability and customer friendly scheduling than just on local operations. Because it’s entirely possible to build an unreliable local system as well. Just sayin’… :wink: