3 ms·
You don't have to "revive" the device in order to use it. The problem was: out-of-sync device clock prevented software updates which in turn prevented cloud sy
by JohnKemeny 2mo ago
You don't have to "revive" the device in order to use it.
The problem was: out-of-sync device clock prevented software updates which in turn prevented cloud syncing. You don't need software updates or cloud syncing for the device to work.
The fix is to set the clock and do the software updates.
- nextlevelwizard 2mo agoAnd why is time such a hard thing to handle in 2026?
- 0x6c6f6c 2mo agoTime can be an issue connecting to Wi-Fi. Devices who've lost track of time often can't properly negotiate access to then get NTP updates to their time. Perhaps this could be solved, but it's a common problem for devices left for the batteries to go dry. It is a bit sensationalist to say this is reviving it though, which makes this sound like some wild issue.
- yencabulator 2mo agoFrankly, consumer gadgets where time is >10 minutes off of trusted time service should force-set their time, instead of giving up. Defaults that make sense to servers with dedicated ops don't make sense for consumer products. Don't just run a default-config NTP client in a consumer product.
- fhn 2mo agowhy does the date/time matter? Just update the thing.