Everything's good, except the Link Bulbs. Not paired.Are anyone's GE Link bulbs working after restoring firmware on the hub?
My Link bulbs seem fine but 2 of my trippers don't seem to be reporting. I'll have to bring them closer to the hub and see if they need to be re-paired. I really think I need a Zigbee device between the, and the hub.
I am shocked. This was a tricky, messy, bad situation, BUT.... Ben and the Wink team has come to the rescue. This was very unfortunate to have happened, but the quick response from Wink is something I never expected. The DNS fix has me up and running, and shockingly everything worked immediately after the update. I realize everyone is frustrated with Wink, but I can't think of anyone else who would have worked this hard to try and make the situation right. Good job Wink!
Yep, basically, that's it. My suspicion is that they staged a temporary update server which doesn't have all of the certificate authentication enabled so that you can get the update which fixes the issue and then you can point back to your own DNS servers, which will resolve to the "regular" update servers.
From the Facebook group, the DNS fix hijacks pool.ntp.org (the timeservers) and does a TimeWarp (A jump to the left and a step to the right) back to August. With that, the Hub thinks the old cert is still valid and happily connects to Amazon and pulls down the new firmware. That fixes the problem.
Just remember to switch your DNS back afterwards especially if you use NTP services with pool.ntp.org.
The instructions specifically said to restore your DNS settings. . . so if you might have gone halfway through the instructions and didn't proceed, you're on your own!
From the Facebook group, the DNS fix hijacks pool.ntp.org (the timeservers) and does a TimeWarp (A jump to the left and a step to the right) back to August. With that, the Hub thinks the old cert is still valid and happily connects to Amazon and pulls down the new firmware. That fixes the problem.
Just remember to switch your DNS back afterwards especially if you use NTP services with pool.ntp.org.
I'd suggest grabbing a Cree bulb and putting it somewhere in between. A powered Zigbee device should work.
That said, I'm not sure my trippers (which are surrounded by Cree and GE bulbs) is yet back on track yet. Things are still a bit off after "the incident". Since I'll be re-pairing everything to the ST hub tomorrow though, I'm just letting it go.
I am not saying the fix was my idea but....
From the Facebook group, the DNS fix hijacks pool.ntp.org (the timeservers) and does a TimeWarp (A jump to the left and a step to the right) back to August. With that, the Hub thinks the old cert is still valid and happily connects to Amazon and pulls down the new firmware. That fixes the problem.
Just remember to switch your DNS back afterwards especially if you use NTP services with pool.ntp.org.
My favorite part was you throwing Anandtech under the bus when someone asked you why you posted the fix on your site. "But it is already posted at Anandtech!" Really?
Yeah really, it was already posted here, that was a statement of fact. I also was never asked not to post it, and removed it when originally asked.
And who was throwing anyone under the bus so to speak? You think they didn't already know it was posted here?
Seriously?
1. Go into router admin settings to change DNS, according to your router type: https://support.opendns.com/forums/21618374
2. Take note of your current DNS settings, we will use them later
3. Update router DNS address 1 to point at 52.4.183.25. Update router DNS address 2 to point at 52.0.103.131 (if applicable)
4. RESTART YOUR ROUTER after you save your settings. Internet will go down while router updates. Wait until it comes back up
5. Reboot the Wink hub, make sure the light goes blue
The hub should immediately start updating if it is on production (if not, it will need to be manually updated)
6. Confirm when the update is over that hub firmware is on 00.86
7. MOST IMPORTANT PART: Reset your DNS to the way it was before you changed it in step 3
Holy what. This worked. A note from above - my software version is not 00.86, it's 1.4.0.
The hub firmware version should be 0.86, not the software version.
Holy what. This worked. A note from above - my software version is not 00.86, it's 1.4.0.
So after about two hours fighting with my modem (ISP-provided; could not change DNS. Sons of bitches.).... When it worked and I almost cried like a big baby!
"Baby! BABY LOOK!!! (***dims lights!!!***)" I got some eye rolls, but I couldn't be happier.
Say what you will about Wink, but as another user pointed out, last night the CEO wandered willingly into the Lion's den and kept everyone updated and tried to keep everyone calm. I thought that was big of them. And transparent. And even in the face of one of the worst snafus a tech company could face, they are doing their very best to fix it.
And (minus my non-Wink-related two hour fiasco) the fix was suuuuuper easy. Only takes a few minutes, if that.
I agree. The Captain kicked everybody else off the bridge and took the helm of the foundering ship. Lord knows it couldn't have been easy for him, but he stayed there and took it.