Thru the hue hub to ST hub… Don’t directly marry it to the ST hub.
geez I 1000 X agree. As an engineer myself, I find the SmartThings engineers pretty good at what they do and the platform in general is satisfactory. But TCP I feel are hacks at what they do. Has anyone actually tried to change their password on the TCP app OR the TCP website? I am glad the Zigbee bulbs have gone down in price where it makes replacing the TCP bulbs not so bad. I have given up on TCP integration and SmartThings should stop dedicating resources to support the shitty platform.
TL/DR I don’t place any blame on SmartThings I think TCP just can’t get their shit together.
My TCP bulbs are not working tonight, GE bulbs are okay. Anyone else having trouble tonight?
Not tonight. About 3 days ago I had to re-install the TCP app. Basically, go thru the settings again in order for them to start working again. A previous reboot of the hub (both TCP and ST) didn’t work. The re-install o re-registration of the app worked for me.
I officially ditched my TCP bulbs with GE Link bulbs. They are SO much better and I’m very happy with the change. I have spent so much time with those TCP bulbs and money, so it really sucked doing it. But in the end, its really nice to have something stable and actually working. I’m just throwing it out there in case anyone is thinking about making the switch.
I couldn’t take the total lack of support being provided by SmartThings and TCP any more. Obivously everyone is still having issues, but no one seems to care. Very frustrating…I hope they get it work eventually for all those people who spend a fortune on these bulbs.
No issues last night. Over the weekend I lost all connectivity with my TCP bulbs, but on the TCP side of things (though, first noticeable when I could not control the devices via SmartThings). I rebooted my TCP hub after some troubleshooting, which resolved my issue (again, TCP issue, not SmartThings).
For what it’s worth, when I’m ready to post something like “TCP bulbs, etc…” I try to check within the native app first.
Interestingly enough, with today’s SmartThings issue, the only devices I could control were my TCP bulbs and my Hue bulbs – anything attached directly to my SmartThings hub was unresponsive. Sometimes a few different connection methods/hubs isnt too bad haha.
TCP bulbs are a little wonky, most things are, but since the last major SmartThings update things have been great.
Tonight I had a bit of weirdness with my TCP bulbs. Some bulbs stopped responding to ST at some point yesterday. Today no bulbs would respond. To restore functionality I rebooted the TCP hub and ST hub. That did not fix it. I checked the TCP connect app and all was normal there. I reset my TCP remote password and re-entered it into ST as the exact same password. Finally after refreshing each bulb they started responding to commands from ST.
Some people were saying in other topics that oauth wasn’t working the last day or so, that might have affected any cloud to cloud connection that uses a sign in. @625alex might know more.
I believe the TCP connect uses digest authentication to talk to the TCP site, and I also just noticed another SmartApp Event message go up on the status page. Either way it would be good to get an update on the TCP status. The remote method of talking to the TCP hub was supposed to be a temporary fix. They have a push button authentication method for local auth that is very similar to that of the Hue hub. I am just wondering if the connect app will ever take advantage of that.
I started having issues with TCP a little while ago. Lights were coming on at sunset correctly, but not turning off at the designated time. I thought perhaps I was having gateway connection issues, but I monitored via the TCP app, did not have connection issues and the lights still did not turn off as scheduled.
As suggested by support I changed my TCP password. Now TCP won’t work at all with ST for me. TCP Works fine via their app. but when I run TCP connect I get this error in the logs
12:05:35 PM EDT: error java.lang.NullPointerException: Cannot invoke method getAt() on null object @ line 201
I have supplied the error to support but thought I would check here. Thoughts or ideas? Thanks.
EDIT - also I cannot uninstall TCP connect. - gives me an error
I could not uninstall TCP connect last night either, but it finally worked really late in the evening.
I now have my TCP gateway and 4 TCP bulbs completely uninstalled, and the GE Links fire in less than a second after I click their icon. Night and day difference in performance and reliability. Very pleased with the move off of TCP.
I feel lucky I didn’t have a huge TCP investment yet.
That’s my experience for any one contemplating options.
Anyone else having TCP/ST trouble tonight?
The native TCP App controls the lights fine.
I don’t see any red ERROR messages in the IDE but I do get this in the ST app:
@thegibertchan ?
Thanks
Update: this morning I can use ST to turn ON my TCP bulbs but not to turn them OFF. Rebooting the hub did not help.
I have had no issues … if ever I have nowaydays I just ‘login’ again via the ‘TCO bulbs connect’ tile and get out again, seems to do the trick (not sure if this is your issue of course).
correction ‘TCP bulbs connect’ tile
Looks like I got my TCP bulbs working again with ST.
I went into ST Labs and opened my TCP Connect app and clicked DONE on each screen and like magic it’s working again!
Thanks
I had my TCP Gateway fail on me and TCP replaced it. I just received it today and reconnected all my TCP Bulbs through the TCP App. When I went into Smartthings, it still had my old bulbs connected and wouldn’t let me remove “TCP Bulbs” from labs. I went in through the web and removed all the old bulbs and reopened the app, and that seemed to work to remove all of my bulbs and “TCP Bulbs” from Labs. Now, when I try to reinstall the bulbs through Smartthings, I get to the credentials screen with the new “TCP Bulbs (Connect)”, but when I hit “Next” after entering my credentials, it takes me to a blank grey screen with the back arrow, the title “TCP Bulbs (Connect)” and a “Done” button at the top. Nothing opens on the page, it just remains grey and blank. If I hit back, it takes me back to the credentials screen, and if I hit “Done”, the Smartthings app crashes. Have tried it several times with the same results.
Does anyone have any suggestions or has anyone faced a similar problem?
Any help at all would be appreciated.
Thanks
I had this exact same problem. First thing I would do is log into TCP through a web browser, or turn wifi off on your phone and log in through TCP app on your phone (prevents the app from seeing the gateway locally). Do you see your lights?
If not, then your lights are not associated with your account. This happened to me because of trying to change my password I somehow actually created a second account for my gateway. I resolved it by calling TCP support - gave them info on my gateway and they then assigned the account to the gateway and deleted the other account. My TCPs work great with ST again.
@CaptainUns what @greg said will solve your problem. I had to replace my gateway once so I emailed them and they associated my new gateway with my account. After they did that all was good!