TCP bulbs no longer working with ST

While we wait on the TCP API to be integrated into a device type in SmartThings, has anyone else set up TCP lighting control via Wink like I have? Wink gave me a message the other day that it could do local control and wanted me to press the sync button on the TCP hub, but that seemed to time out. I may try again and move the Wink hub closer to the TCP hub if it is worth the effort?

Just emailed. Let me know if you gotā€¦

yep I just got it - thanks.

However, on page 17 it reiterates that the local gateway needs to be accessed via http: or https: . From what Iā€™m reading above, it looks like we can only connect to the gateway locally via HTTPS, which SmartThings does not support :frowning:

Time to try out local control with the Wink Hubā€¦

Robert - since you have engaged TCP support - can you ask them if we can revert the TCP hubs to an older firmware version that supports local API control over HTTP? If so then we may have a chance with local control via SmartThings.

Iā€™ll email them now and see if they respond. They responded within a day last time.

Email I got from Wink says I wonā€™t be able to control TCP bulbs remotely or use Winkā€™s robots/schedules. Only control them while Iā€™m under same Wifi as TCP. :frowning:

Ugh. It was working this morning and I thought they forgot :slight_smile:

Now thereā€™s a red light on the hub so it looks like their side is definitely done for.

I guess the hope that the other TCP app or IFTTT integration would somehow continue to work was just wishful thinking

After 2 weeksā€¦no sign of a response about HTTP.

Has anyone smarter than me figure what to do with all these bulbs out thereā€¦besides just using them as LED light bulbs.

One community member was able to set up a local server and get things to work:

Iā€™ve created an open source Web interface to control the tcp bulbs. Have a look here: https://github.com/bren1818/TCPLightingWebInterface

Cheers, bren1818