I quite agree that one can always come up with new tests. But the pertinent question is whether in this case Nests's QA would have anticipated, yet not tested for, this particular error condition.
I believe that on balance the answer is yes, probably they did. A question which follows then is, assuming I am right, what is a reasonable amount of blame for failing to test prior to release?