My window was, “12:00 pm EDT and 4:00 pm EDT” and nothing yet on either hub! Keeping fingers crossed, as we leave next week & won’t be back here 'till November…
Mine did the same think, except it went offline twice. It was still showing the old firmware. I went into the IDE and rebooted the hub, now on 000.017.00012. So it looks like you need to reboot hub if not showing the 17.12 firmware.
I echo a lot of the sentiment communicated here. Smarthings engineering really needs to get their collective feces together. 70% of the time you guys update/reboot my hub I need to troubleshoot new problems. I’m close to the point where I need to find a new home automation hub from a company that takes this MUCH more seriously. I assume you are all working toward the smart home of the future yet you keep making those that have to live with our technology leading philosophy pissed off that their smart home just got dumber !
In case you were not aware. I for one expect that any standard switches, sensors, lights, locks etc… should always work. Period. The more you do that interferes with this simple philosophy, the slower you will make the migration to smart homes. Your Mission Statement should include a line similar to “It just works !”
Now if you’ll excuse me I have to go and troubleshoot my system after you upgraded it and rebooted it without my permission.
1 Like
Now another email says, “Friday, April 7, between 12:00 pm EDT and 6:00 pm EDT.”
Does that mean one hub today & the other tomorrow? Or has today’s update been postponed?
Device health probably (rightly) saw that some devices could not be contacted during the update and marked them offline. They should be marked online again once they perform a regular report after the hub came back online. There is currently no special logic here to attempt to contact the device again when it comes back online, so the device-specific regular reporting period would need to be hit before the device is marked online again.
Future updates will be much shorter than this migration update, so this generally should not be a significant issue moving forward (the device could still miss one report, but would probably not miss 2 which is generally what is required for it to be marked offline).
If you have multiple hubs, it is possible that they are split across days. If a hub was supposed to update today but is still reporting the old version, you may need to disconnect/reboot the hub to get it to report the new version as has been noted elsewhere in this thread.
1 Like
Thanks, Paul! Looks good now…
My hub currently is having a lot of activity under “events” in the IDE. Both my app and IDE state the old firmware but it was supposed to be updated between noon and 4pm today. Devices are also actually unreliable right now. Could an update be happening now? What’s all the event activity listed as Ssdp Term that’s ongoing?
You will see additional SSDP traffic as a result of the LAN SuperConnect features that were launched a few weeks ago. The only LAN related changes on the hub with this release were some minor fixes and increasing the supported number of concurrent LAN connections slightly.
Due to the offline time during the update, some ZigBee devices may have changed routes which could cause increased/decreased stability depending on the devices that end devices end up choosing for parents/routes. Are the problems related to a specific subset of your devices?
Feel free to file a support ticket to help trace down the problem (this thread is pretty chatty).
Thanks Paul. I guess my core question was why the hub didn’t update during the original timeframe of noon to 4p today and if the update was slower to roll out and could still be updated today. My hub is currently online but it did reboot today, but the firmware didn’t update. I’m have smart lighting rule issues, that’s all, it’s not troublesome right now.
We ended up rolling a little past the window as we had to slow things down in order to avoid overloading the cloud. The aforementioned overloading of the cloud resulted in an issue for some hubs (particularly ones connected to the NA01 shard – see FAQ: How to find out what "shard" (cloud slice IDE URL) your Account / Location is on?).
If your hub went offline for a period and is now online but reporting the old version, you are likely updated. You will need to trigger a disconnect or reboot your hub in order to get the data in the cloud up to date.
1 Like
You’re correct, I rebooted my hub (it took longer than normal) but now shows the updated firmware. Thanks for the guidance!
Upgraded and everything seems normal only arrival sensor logged an alert as getting disconnected but reconnected afterwards
I’m in the UK and have two hubs at different locations.
Both went down at about 17.30 BST but only one came back. Of course the one that didn’t is 200 miles away, so no I can’t just press the reset button!
The one that has stopped responding was on 16.14 and the one that is working is reporting 17.12.
Pain in the a**…
my hub is down for more than 10 hours now.
this is really unacceptable service level. Samsung STOP the firmware upgrade if you won’t be able to HANDLE it with CARE !!!
I have rebooted the hub 3 hours ago and it restarted firmware download. Still downloading.
When I check on my router, I see 2 way traffic between my Hub and the Amazon servers.
How big is the firmware itself ?
I’m pretty sure that if the hub has a gender, it is female. And a mean and jealous one at that.
True story: so, the afternoon passed and I kept checking the hub for the imminent update during the afternoon, but nothing happened. TIme passed and my GF came back from work, happy with the workday and very happy to see me as well it seemed, as we ended up in the sofa.
Right about when we were about to get down, the hub decided to fire off flashing lights and presence sensor notifications that triggered the stereo (that was playing smooth R&B) to announce “someone is arriving” 3 times after each other.
Of course we thought my daughter came home early from the stable, and scrambled around to get dressed thereby ruining the moment. I could almost hear the hub snicker from its place downstairs…
I would like to re-iterate my request to have a user preference to not accept automatic updates.
ST: how are you planning to remedy me and this situation? Pardon my French, but techology c*ck blocking is for real! 
Damage control afterwards: I have lost one ST motion sensor and all LIFX lamps had to be turned off/on to register correctly with the hub. Dinner planned for the evening to give my GF the attention she deserves. The hub remains on the shit list for a long time.
8 Likes
I received the hub update yesterday but following the update the Alexa Integration with Lighting stopped working. I rebooted the hub, rebooted the philips hue hub and still not working. I have a couple of Fibaro dimmers and they also stopped working with Alexa commands. Wemo was working with Alexa commands. Weird.
Anyway I tried re-scanning for all devices in alexa app, deleted and re-discovered and still not working.
I then removed and re-added the Smarthings skill in the Alexa app and that seemed to fix it.
Hardly a seamless upgrade from my point of view.
Just posting to help any others who have similar issues after the Hub upgrade.
Cheers.
Brilliant 
1 Like
3 of my sensors have been offline since the update.
Hub reporting 7.12.
Rebooted the hub but they have still not re-connected.
This is coinciding with one of my sensors going crazy for the last few days and waking us up a bunch.
It’s slowly becoming normal in our house for SmartThings to be prefixed with other “ing” words…
finally my hub is back online. It took about 12 hours.
12 hours of DOWNTIME !!!
This is really unacceptable.