I doubt that everyone on the team missed the fact that electronics get hot outdoors in the summer. Rather, they probably chose to launch a product that breaks when it gets hot, because it's an easy problem to fix later. Now that
something is out in the field, they can debug their network, satellites, RF hardware, installation instructions, management applications, and figure out what kind of customers want to buy this thing -- all in parallel while some tiny EE team redoes the BOM to use better-spec'd components. Everyone at the company now has a ton of work to do to produce the next version, taking into account real-world feedback as they do it. Would it be worth blocking all those projects another 3 months just so that some guy in Arizona gets more Internet uptime on the hottest day of the year? Probably not. It sucks to invest in an early product and have it break on you, but it's also probably not possible to have a company that releases a totally flawless product on day 1. If you demand perfection, what you are really demanding is for the product to never exist.
(It's also completely possible that the parts simply aren't available. You may have noticed that there's been a pandemic going on for the last year or so, and that's hurt the availability of many electronic components, among other things.)
(It's also completely possible that the parts simply aren't available. You may have noticed that there's been a pandemic going on for the last year or so, and that's hurt the availability of many electronic components, among other things.)