Local interaction with the bulbs is clearly still possible because you can control the bulbs locally through the TCP app. What was disabled was the local web interface for the hub itself and the interface that ST was using to control the bulbs locally. I am sure there is a way for TCP to allow local control from SmartThings, but the current SmartApp does not have this and it is purely a cloud to cloud setup at this point. @twack might be able to explain in better detail why there is no longer any local access to the TCP hub.
Just dropping in to say Iām still having this issue.
are you still having it Jody?
1 Like
Yes. It seems to be about 72 hours before the token needs refreshing and the SmartApp loses access to the TCP servers.
I canāt seem to find anything consistent about it other than:
- it keeps happening
- it seems to happen in the late evening/overnight hours. I always discover the connection is broken in the morning because my lights are still on. I donāt think Iāve seem them not come on when they are supposed to at sunset (unless I didnāt reauthorize through connect from the night before)
1 Like
I could not find a consistent problem with my gateway. I bought some GE bulbs and have put my TCP kit up for sale.
1 Like
Just wanted to drop an update in here that my TCPās have been great for at least 2 weeks. I have not had to reauthorize them and I have had solid performances scheduling them with ST.
I just noticed this last night as well. I was going to try and use them again with my Harmony remote! Thanks to whoever fixed it.
Thinking about just moving on to GE links. Sounds like they pair with ST Hubs better and work more consistently. May give a try and see about reliability.
Iāve just started using the TCP app or website by itself and the reliability issues appear to be resolved.
Iād love to use the ST integration, but things are finicky most of the time, so rather than rely on routines or trigger lights based on time of day (which hardly works), I just pop into the TCP app and control them that way.
I clearly spoke too soon. Iām having issues all over again with having to reauthorize the app.
It just isnāt worth the trouble anymore. I will be uninstalling my TCPās and just putting in a smart switch in the near future.
I canāt even go a full day without having to reauthorize. This is an absolute mess. Is anyone even attempting to look into making this integration actually stable?
Something is already saving my credentials, I donāt understand why it canāt just reauthorize and get a new tokenā¦
And, sometimes, even reauthorizing the SmartApp doesnāt even cause the integration to work!
Yes, I am also experiencing error code 400 disconnects with the gateway. Does anyone know if there was another TCP Gateway firmware update that broke integration, or is this a bug in SmartThings?
Yep, definitely broke again. I give up trying to make it work. As soon as I get some extra cash laying around Iāll replace the TCPās with something else.
Yeah but the question isā¦ are you just going to get into another mess because the issue is with ST and not the other product?
Iāve had TCP bulbs for ages now and they work fine by themselves. I can use their app and even their website and control things with no problems. My issues come from trying to use ST to control them.
I have similar issues with the Osram Gardenspot that works just fineā¦ but ST decides every now and then that it canāt talk to the thing. Same with my ecoBee thermostat, and my garage door openers, etc.
So, while it would be nice to have an all-encompassing platform that controls everything, and has the extensibility of smart apps and all that good stuff, Iāve already relegated myself to the fact that ST is just not ready for that role. Maybe as time passes this will change and I can start relying on it to manage third party devices like TCP bulbs, but for the time being Iāll just accept the fact that I have to use an app / website for my bulbs and ST for other things.
I think you are right that the issue is in the ST TCP connect app and having to reauthorize. However Iām pretty deep in the HA rabbit hole and I really donāt have a place in my house to use stand alone TCP lights without the advantages of all the other automations I could do with those same lights properly working in ST.
Iāll just move to a smart switch and the only issue I should have are platform wide issues, which seem to be much better lately.
1 Like
This is what I did in my previous place, but havenāt had the chance to do after I moved.
Of course the downside is that you can use (some) TCP / Osram / Hue bulbs that have additional features like color rather than just intensity, and that wouldnāt be available with a dumb bulb connected to a smart switch.
My emails with SmartThings support resulted in SmartThings saying theyāre looking into the issue (with no ETAs of when it will be fixed). One of the supervisors suggested assigning a static IP to the TCP gateway as well as the SmartThings hub. Not sure if anyone tried this yet as a temporary fix.
I have a mac address reservation for my TCP and have had it for a long time. Didnāt fix the issue for me. But I will say I havenāt reauthorized in maybe a week. I have a dimmer switch sitting here waiting to be installed the next time I have to reauthorize.