Anyone got issues with Alexa controlling stuff under ST?
Keep getting “Smartthings insist responding”?
Also tried rediscovering via Alexa and it fails to find stuff?
However, can still control hue bulbs fine…just not all other types of devices registered with ST via Alexa.
But works fine via ST app.
I got the update yesterday and things were fine…only noticed this prob tonight?
Wonder if others are experiencing the same?
Multiple platform issues right now, and according to some staff at least it’s independent of the firmware update:
So my hub just updated to 17.12, and now Google Home will no longer control my devices. I removed Google assistant from the SmartApps list, and I logged out of SmartThings from Google Home Control. Anyone else having issues with Google Assistant after the update?
ActionTiles is not working now.
Same here. No Google Home control and a 500 error in the Home app.
Currently down.
Yep, separate issue being investigated. Something about Murphy’s Law.
Thanks for the info. Google Assistant worked completely fine with SmartThings until my update today around 4pm… I figured it had to be related.
Just got the update. Is it my imagination or did 17.12 change the zigbee OTA update options? I looked & mine stated only active for non-light items?! I selected option to include Lights as my Osrams were previously updating. I think a lot of people were using that feature & may want to re-activate the option in your IDE Hub utilities menu.
And this is how they get us all to buy an S8 and start using the connect app!!!
https://community.smartthings.com/t/hub-firmware-release-notes-17-12/83722/238?u=tweason
I was just about to come on here and say the exact same thing
I was really dreading the update based on all the negative posts. I figured I would come in and put one in the positive column just to keep the balance.
While I agree that ST REALLY needs a way to back up and the ability to defer for convenience, I read the forums before hand and knew what I was getting into.
I wanted the ability to tweak and play. With that flexibility comes risk.
Anyhow, luckily for me, I did not have to rebuild everything.
Great movie, took my 3 year old to see it last weekend 
My hub updated with no problems today.
I just tried it again, and voice commands are now working with Google Assistant. I did have to go into the Google Home app, click add, then sync SmartThings up.
My Google Home also started working to control SmartThings.
Everytime I mentioned or ask about a backup feature, I’m just ignored. Maybe the fact that I mentioned Vera and the new release of Vera Secure having that capability didn’t win me any points… Something as large as SmartThings has to at the very least have some sort of back up capability on the customer facing side. Just saying!
FYI: My firmware upgrade went smoothly and without a single glitch (app side reported 17.12 without the need for rebooting or reconnecting to cloud. 0 device failures. 3 notifications, hub offline, hub online and arrival sensor arrived at home (that’s another topic that someone posted earlier today on whether or not you have Automations that fire post upgrade automatically disarming your home and opening garages and unlocking doors because the arrival sensor is recognized the way it is during the firmware upgrade. If you aren’t home, lol, that’s not a good thing to have happen.
Anyway thanks guys for not inserting a destructive bug into my firmware for my miles of posts over the last few days. I meant well 
If the arrival sensor is away from home, it shouldn’t make any difference.
The potential problem would be if the arrival sensor is at home at the time that the hub upgrade starts. Unless there’s some magic on the cloud side, the following is likely to happen:
One, the arrival sensor is noted as being at home in the cloud account records
Two) the upgrade starts
The cloud account marks the arrival sensor as being away from home if the upgrade takes too long
the upgrade completes, The arrival sensor checks in again, the cloud account notes the arrival sensor as having “arrived” ( even though it was actually home the whole time)
automations that are triggered on arrival, fire.
But I don’t know for sure if it happens this way. It’s possible that the cloud account is smart enough to ignore “away” conditions that happen during the time of the upgrade.
But in either case, if the presence sensor is in fact away from home, there wouldn’t be anything to trigger an arrival event, so there shouldn’t be a problem.
Hi,
My hub went offline this afternoon for the update (about 3 hours ago) and it has not come back online. What can I do to get back online?
Thanks!
My firmware for 17.12 started and hub went away doing its business. However I had flashing purple LEDs for over 4 hours and no ST control.
I know it says don’t, but I had to pull the power and batteries, and eventually it recovered and was my firmware is 17.12.
Is there anything I can check, do, confirm please?
Hey All, it looks like the vast majority of people have successfully received the updated and migrated. We encourage anyone that has an offline hub to contact support as required to get things sorted. We’ll also be running through the data we have available and reaching out to the relatively small number of users who appear to have had issues with the update.
For users with a blinking magenta LED:
Go ahead and power cycle the device (remove power and batteries if present) and let the device boot again. The hub should go back to blinking magenta again as it downloads the update. If the device is still blinking again after an hour, please contact support. For most users, we expect that this portion will complete in ~10 minutes (but it could be much longer for users with slow/intermittent internet).
For Users With a Blue Blinking LED:
This LED pattern indicates that the hub is not able to get an IP address. The following steps may be taken to attempt to give the device a helping hand. Regardless of whether these steps work, please contact support and provide information on your network setup so we can determine if there are remaining pieces of network eqipment that are not working well with the SmartThings DHCP client/networking stack.
Things that can be attempted:
For Users Still Reporting 16.14
The very newest hubs and select hubs with specific hardware variants may not have received the update yet. We will be doing a final bit of testing to ensure things are ready to go for those hubs and send out emails (for registered hub). If you received an email in the past about the update but your hub is still reporting the old firmware version (but connected to the cloud), you may try the following:
Something Else
For anything else (e.g. Green LED but unable to control devices), please contact support and we will work to get things sorted.
I’m a new SmartThings owner and I’m surprised by how much requires the internet to run. I’ve asked ST Support about it and they said the cloud-based things are more secure than locally processing ones. I’d be sure the opposite is true so I’m not sure why they’d say that…
Anyway, so I asked them to pass on my request for a few device handler types (Z-Wave Plus version of door sensors and motion sensors) to run locally.
