Here’s the irony of the supposed “fix” from the SmartThing supervisor. Now that I’ve tried it, SmartThings is giving me “Unexpected error has occured” problems with the notifications, so I can’t tell if my SmartThings is still connected to my TCP while I am away.
Just wanted to chime in that I am having this problem as well. I get the authentication error, which can be fixed by going into the TCP SmartApp and re-authenticating.
Haven’t had to reauthorize in a few weeks. Hoping this post doesn’t jinx me.
Same here, been kind of nice not to have to reconnect multiply times/day.
1 Like
My two ST/TCP systems have been stable. too. I mean I haven’t had to re-authenticate for a while. I did have one TCP hub that needed a reboot, and one Internet outage.
And the response time is barely acceptable, at best–typically 1 second for the motion sensors, plus 1-2 seconds of system delay before the lights come on. Sometimes it takes 5 seconds or more to turn the lights on.
Door sensors don’t have their own delay, just the system delay.
Reauthorized twice in the last 3 days. 
Anybody else having issues reauthenticating? After entering my credentials the next screen is completely blank, other than the banner across the top. If I hit “Done” in the banner, I get an error message. I sent an email to support, but no response yet.
I had a similar or identical problem this morning. I reset my router, ST hub, and TCP hub, as well as trying to reauthenticate. Nothing worked. I was able to control the lights from TCP only.
Same exact experience as Ernie and Glen, starting last night / this morning. Blank screen after trying to authenticate. Wouldn’t even let me remove the TCP integration and re-add. When trying to remove, it throws an error message. TCP controls still work, so it’s definitely the TCP/ST integration.
ST team, did something significant change in the latest Android SW update?
From support:
“This looks like a known issue and other customers are experiencing problems with it. We are aware of the bug and are working on a resolution, but at this time there isn’t a definite timeline for when we can have a fix in place.”
I guess we just wait.
Not too long a wait. I was able to reauthorize. My TCP’s are back up and running.
Last night I encountered the same issue, where no tcp bulbs are accepting the instruction from hub, so tried to reauthorize and after authorization I see blank screen after that.
I am now controlling TCP bulb only through TCP app or manual switch on / off.
Do we have any update from the support team.
Thanks.
Hi,
I had the same issue this morning here in the UK, reported to support and then this evening found this thread, just went in and reauthorised and everything is working now. Give it a go!
A big Phew!
@pjmdesigns Thanks a lot, I gave it a try and it is now working.
Did support gave any reason why this is happening. I am planning to buy few more tcp bulbs as its price is now lower in amazon but this issue is freaking me out.
Mine appears to be working now as well. Looks like it was a server-side issue, since they didn’t have to issue an OTA SW update.
My TCP lights have completely disappeared from SmartApps. While I can “re-auth” them, when I go to my devices, the TCP lights I had don’t appear in the list.
I don’t understand who is breaking integration - TCP or Samsung, but it’s really annoying.
Mine are working again but have been moved from their rooms. They show up in the “things” category but I’m unable to put them back into their rooms under add/edit devices in this room. Strange.
I have the same issue but not just with TCP bulbs. My Blink cameras and Bloomsky also have this issue. Please open a ticket with support.
Started a ticket let’s see what happens. You are right my Bloomsky also can’t be added back to my room “outside”.
solution here:
I tested with one bulb, think I’ll wait and see if there is another solution before I do it 25 times.