This worked for all but one bulb that indicates Access Denied when I try to edit it.
You know whatâs awesome? Looking out my front door peephole to see who rang my doorbell only to see complete darkness because SmartThings failed to turn my lights on at sunset.
This is a joke. My coworkers have been persuading me to jump ship and go with the Iris system. Iâm almost to the point of asking if anyone is looking to buy a SmartThings system⌠but I probably couldnât pay someone to take it off my hands.
I currently moving away from iris. Trust me you donât want jump to that system. Support is top notch compared to them. Now that support is a joke. And very limited on devices I have devices that are paper weights after the v2 upgrade. I only gain use of them again when I migrated over to smartthings.
1 Like
Lost connection to TCP again this morning. Reauthenticating/reconnecting to TCP from the SmartThings App worked.
I see multiple notifications like this:
TCP lighting is having Communication Errors. Error code = 400. Check that TCP Gateway is online.
A few days ago I was getting a similar error, but reauthenticating did not fix it. Neither did rebooting both hubs. It eventually fixed itself for some hours, then came back, then fixed itself again. The error was:
TCP lighting is having Communication Errors. Error code = 500. Check that TCP Gateway is online.
Can anyone tell me the difference between error codes 400 and 500?
Also, if I can reauthenticate manually, why canât SmartThings reauthenticate automatically, when an error is detected?
Thanks.
If itâs using HTTP status codes (I suspect it is).
400 is Bad Request - Usually means that the request was malformed or sometimes that a required parameter was missing.
500 is Internal Server Error - meaning that something went wrong on the server that the request was sent to.
Without it giving any further detail itâs hard to say what the issue is.
Re-authentication would require storing your TCP login details which is a security risk as there arenât really any secure ways of storing such data within a SmartApp or device handler as far as Iâm aware.
EDIT
Just looked at the TCP (Connect) SmartApp and it is supposed to refresh the token when it receives a 401 (Unauthorized) status code and it also stores your username and password so that it can do this. However, a 400 and 500 status code donât cause the token refresh. Itâs possible that TCP have done something that causes the wrong status codes to be returned. It wouldnât be that hard to modify the SmartApp to attempt a token refresh when these status codes are returned but itâs not really how itâs supposed to work.
With the new hub firmware update, I had to reauthorize my TCP lights twice within 2 or 3 hours. This whole thing is verging on worthless and Iâm contemplating just getting rid of the whole deal.
I just replaced my TCP bulbs last night with some GE Links. They were not my first choice, but they were on closeout/clearance at Home Depot for $6.33 a piece. I couldnât pass that up. I connected them to my Hue Hub and they are working great so far!
The GE Links need a hub to work? I thought they can work standalone.
They can work standalone, but are a lot more reliable when connected to the Hue hub. Iâm told that when paired directly to SmartThings, there have been issues with them âdropping offâ or losing connectivity.
1 Like
Hi everyone,
I got so sick of TCP bulbs not working correctly I dove into the source and fixed some things. Iâm submitting to official SmartThings repo but if you donât want to wait you can use my code today. Just go to https://github.com/mmacaula/tcp-bulbs and follow the instructions there. Itâs basically just a couple of changes from the original. Iâve been using it for the past several days and not once have I had to re-install my bulbs!
Mike
1 Like
Apparently TCP has decided to turn off the cloud service because no one has had it working well. They are also dropping support for their mobile app. I believe this will break the integration with SmartThings, wink, and anyone else using cloud to cloud.
Stallman was right all along.
So TCP bulbs are now going to end up being expensive LEDs? Will they be able to link and work directly through smartthings or does smartthings need their cloud for them to work?
Originally there was a direct connection possible but TCP shut that down about a year ago. The current ST integration is cloud to cloud, so that will go away when TCPâs cloud service goes away.
ShootâŚIâm wondering if tcp will open that direct connection back up considering the circumstancesâŚ
Nope. Theyâve already been asked and answered.
I have two guesses about whatâs going on.
One) they found that customer support for anything cloud connected was just too expensive.
Or
Two) they want to go for HomeKit compatibility, and their current cloud structure didnât meet its security requirements.
You see both things going on in the marketplace right now. (Schlage just withdrew some cloud functionality back in March because it violated HomeKit terms )
So I wouldnât put a bet down as to which of the two it was. But in either case, they arenât likely to open up local access at the same time that theyâre dropping cloud access.
What a jokeâŚthey sell expensive bulbs that are now essentially useless. Iâm glad I didnât buy them but I was considering getting a few when they go lower on clearance or I was going to talk to the manager I usually deal with and ask him to mark them down considering the fact they are uselessâŚeither way, I wouldnât buy a TCP product going forwardâŚ
Yep. Gotta think twice before buying smart home items on clearance. They most likely to become expensive paperweights in a short while.
1 Like
Looks like we are losing access to our TCP connected bulbs.
http://go.tcpi.com/ConnectedSupport
We regret to inform you that we are making changes to our support model and will be discontinuing the following services associated with the Connected by TCP system effective June 30, 2016:
Access via the internet and connectivity through cloud services
Updates of the TCP Lighting App
Importantly, the following functionality will be unaffected by these changes in services:
Lighting controls through a local (Wifi) connection
General Illumination with Connected by TCP bulbs
Thatâs a shame, still sounds like local network support could be possible but I doubt TCP have released any documentation for it.