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…
Hey, bi-weekly has the word weekly in it, which is better than biannual, which only recently replaced annual. But the reality is, that there shouldn’t be any updates if things would roll like they are supposed to. We don’t need updates on f-ups, we just need no f-ups.
tgauchat
(ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)
272
I don’t understand the question…? Don’t you think SmartThings is trying to avoid outages? Do you think they have a crystal ball to know exactly when a specific target level of reliability will be reached?
Complex systems inherently have reliability issues. Except for “anomalies” or specific explained reasons for steps-backwards, the best way to predict when a particular level of reliability will be reached is by extrapolating from a trend-line of what should be a steadily increasing “average time between outages” (MTBF), or “Maintenance Free Operating Period” (MFOP) as suggested by @JDRoberts.
I’m come from a enterprise background and we absolutely have specific target level of reliability set to specific dates. This is especially true for any revenue impacting services where five nines are a minimum.
Your point is taken and I agree with you. It’s my fault for trying to apply enterprise level expectation to a consumer level service like SmartThing but I was shocked to see that there’s NEVER been a single trouble free month in recent history.
1 Like
bamarayne
(Jason "The Enabler" as deemed so by @Smart)
279
So… today is over… yesterday is gone… pretty sure early tomorrow happened already…
You may be waiting on it, but I know you didn’t expect it.
Honestly, I am hoping we stop reminding ST about all the missed commitments on the weeklys and information commits like this… just let them slide by for weeks/months, etc and then compile the list of failures.