What happened
Smart lock maker Lockstate pushed an automatic over-the-air update to its 6000i locks in August 2017 that left their keypads unusable. The company said firmware meant for its more advanced 7i model had been sent to some 6000i owners by mistake. In an email to customers, it said the lock “failed to reconnect to our web service making a remote fix impossible.” At least 500 owners, many of them Airbnb hosts, were affected. They could take the lock off the door and post it back for a manual fix, taking five to seven working days, or wait 14 to 18 days for a replacement.
- Lockstate cloudSends an automatic update
- Wrong firmwareMeant for the 7i model
- 6000i lockKeypad dead, can't reconnect, so no remote fix
- Posted backFor a manual fix
One update. At least 500 locks off the network.
August 2017: 5 to 7 working days for a fix, or 14 to 18 days for a replacement
Sources: The Register, August 2017; TechSpot, August 2017; Threatpost, August 2017

What I look for
Antony HainesConsulting technical executive
This is why I keep firmware updates to a minimum: every one carries the risk of leaving a device stranded. Every update should check it's the right image for the right device before it installs, keep the old firmware so the device can fall back to it, and go to a small batch first. If a device can't get back online after an update, a software problem has become a postal one.
Products and systems, end to endA system built to run unattendedOperators and buyers: what you can ask for