55 but now that I have learned a lot I can redo a bunch of them and make fewer pistons.
Did you sleep at all last night?
I find the more I learn the app the fewer pistons I have. My goal is one.
I call that “The ULTIMATE Piston”.
It finally moved away from theory to now whiteboard.
Pist-One 
waterboard what? Trust me, it won’t work with your hub.
No but connecting a car battery to it’s nether regions might
only slightly only slightly
that is when ST messes me one for the last time
The Pissed-One. Comes with waterboarding features, applies them to the hub at random times, keeps hub running. It turns out, fear does get the job done. All the time.
Don’t hold your breath on getting anything restored. Support just got back to me.
I was waiting to get confirmation back from our engineers to be sure, but if SmartTiles dashboards have been lost there is no way to recover them. I don’t believe Nest Manager has a backup function, but CoRe does have one in place so you can recover your pistons in the event of an incident like Mondays. I’m truly sorry for the inconvenience, but if we can help with anything, please let us know!
Oh good… I can stop holding my breath now! Hahaha
While I can’t say anything with any certainty…
If SmartThings is/was able to restore SmartApp state for their own SmartApps, then they could do the same for SmartTiles. We don’t do anything magical (well, besides being wonderful).
SmartTiles only uses State for Tile order, Custom CSS, and some anonymous tracking. Unfortunately, the loss of the first 2 is quite disappointing to some SmartThings Customers.
Substitute Pinocchio with ST:
Prince Charming: You! You can’t lie! So tell me puppet… where… is… Shrek?
Pinocchio: Uh. Hmm, well, uh, I don’t know where he’s not
Prince Charming: You’re telling me you don’t know where Shrek is?
Pinocchio: It wouldn’t be inaccurate to assume that I couldn’t exactly not say that it is or isn’t almost partially incorrect.
Prince Charming: So you do know where he is!
Pinocchio: On the contrary. I’m possibly more or less not definitely rejecting the idea that in no way with any amount of uncertainty that I undeniably
Prince Charming: Stop it!
Pinocchio: …do or do not know where he shouldn’t probably be, if that indeed wasn’t where he isn’t. Even if he wasn’t at where I knew he was
[Pigs and Gingerbread Man begin singing]
Pinocchio: That’d mean I’d really have to know where he wasn’t.
You left out the part where Pinocchio said that him or Geppetto will provide an update on Shrek yesterday or early in the morning…
“In a few weeks ™…”. 
Agreed. SmartTiles (and Nest Manager and CoRE) provide a functionality that SmartThings hasn’t been able to offer, so I’m not surprised that they pointed to you for backup functionality. I’m looking ahead to V6, so I’m not in a rush to go and fix my CSS.
That being said, @tonesto7 wasn’t sure why Nest Manager Automations* got hit, as they don’t use State. I’m leaving those automations alone as well, and haven’t gotten around to rebuilding CoRE (busy week). Maybe somebody much smarter than myself can piece together what the root cause is.
*EDIT: a word
It appears that some integrations which stored credentials also got hit.
We use atomicState for things like dtStamps or temporary storage, but almost everything is based off settings which were completely blanked out in the child app.
Thanks.
The explanation is over my head, at the moment, but I plan on learning when I have free time, that just hasn’t happened in the last 6 months.
If I have time tonight, I’ll have to dig through my other SmartApps to see if anything more subtle got hit as well though. I know several of them rely on settings for logins and preferences that I don’t see day-to-day. The only obvious indication I had was that my SmartTiles looked wrong, and that sent me down the rabbit hole looking for lost automations.
Coincidence, Nah, I don’t think so. Let’s go through some facts:
- My Netatmo integration with other platforms (VeraPlus, ImperiHome…) did not have any issues and is still working, and they have not released any updates, so it looks like the Netamo API hasn’t changed and it’s working;
- ST Support told me that some users were able to login/connect again using the Netatmo (connect) smart app and that this resolved the issue, and also since this hasn’t affected all ST users that use Netatmo it looks like the Smart App and Child DH codes are still working;
- I’ve reported to ST Support that I’m unable to login/connect to Netatmo because when I try it’s returning and XML page with the message “error=invalid_token”;
- Curiously there is a variable called “accessToken” and it’s stored on the smart app Application State.
Let’s see: does it look like there was an issues with the Application State of this Smart App? Just saying…