[RELEASE] TCP Connected bulbs work with SmartThings Again!

ule · February 22, 2017, 3:50am

TCP connected bulbs stopped working with Smartthings since TCP Servers went down

The TCP Gateway allow to send commands to control the lights but use ssl with a self signed cert, and Smartthings do not allow to send request to this type of connections

Until ST change this its no possible to send direct command to the gateway, of course its possible to use a proxy but it requires extra steps and equipment.

The original firmware version of gateway do not use ssl and if you have a gateway with this firmware, you can use direct commands from Smartthings

There is some instructions to downgrade the gateway but I have not use it, if some want to try, the site with the instructions are:

https://github.com/bren1818/TCPFirmwareRestore .

If you have a gateway with firmware ver 2 , you can use this app to control your lights.

You must to block the internet service of your gateway to avoid updates

You must to enter the ip gateway and I suggest you to assign a static ip to gateway, to avoid update the ip each time your router change it

The bulbs are stable and works fine, the gateway does not has a subscription method, then a schedule refresh its needed to update the status if an external action occurs

Your TCP lights must not include custom images, due ST limits, if your lamps have custom images is not possible to get the lamp info.

Try and comment

Device Handler

github.com

SmartThingsUle/TCP-Connectd/blob/master/TCP Bulb.groovy

/** 
 * TCP Bulb
 *
 *
 */

metadata {
	definition (name: "TCP Bulb", namespace: "mujica", author: "Todd Wackford - Ule") {
		capability "Switch"
		capability "Polling"
		capability "Power Meter"
		capability "Refresh"
		capability "Switch Level"

		attribute "stepsize", "string"

		command "levelUp"
		command "levelDown"
		command "on"
		command "off"

This file has been truncated. show original

App connect

github.com

SmartThingsUle/TCP-Connectd/blob/master/Tcp Bulbs Connect.groovy

/**
 *  Copyright 2015 SmartThings
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 */

definition(
	name: "Tcp Bulbs (Connect)",
	namespace: "mujica",
	author: "SmartThings-Ule",
	description: "Connect your TCP bulbs to SmartThings using local integration. You must have a geteway with firmware ver 2",
	category: "SmartThings Labs",

This file has been truncated. show original

If you like this app, please consider supporting its development by making a
donation via PayPal.

vhamcy · February 23, 2017, 2:28am

Awesome. Will try this weekend.

vhamcy · February 24, 2017, 1:52am

I am getting the following message “The TCP Gateway is not responding, please verify the ip address”.
It is not able to discover my bulbs. Can you advise.
I am able to access hub via broswer using local I.P
http://xxx.xxx.xx.xx

Gateway Firmware Version: 2.0.105

ule · February 24, 2017, 2:02am

hi, your ip address must to be xxx.xxx.xxx.xxx without “http://”

ule · February 24, 2017, 2:06am

Remember to block the internet access to your TCP gateway to avoid firmware updates.

Its better if you assign a static ip to your TCP Gateway

celblazer · February 24, 2017, 2:29am

I’m on vaca so being lazy. But I guess this needs to be done in my router?

vhamcy · February 24, 2017, 3:08am

Yes. I restricted restricted internet access and assigned static I.P for TCP Hub.
I did provide I.P without http://. However app is not able to identify devices.

This is what I see in Live log.

 6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:08:13 PM: trace state.loadStatus Loading

6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:08:13 PM: trace state.count 7
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:08:13 PM: trace state.count 6
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:08:07 PM: trace state.loadStatus Loading
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:08:07 PM: trace state.count 6
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:08:07 PM: trace state.count 5
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:08:02 PM: trace state.loadStatus Loading
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:08:02 PM: trace state.count 5
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:08:02 PM: trace state.count 4
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:07:57 PM: trace state.loadStatus Loading
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:07:57 PM: trace state.count 4
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:07:57 PM: trace state.count 3
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:07:51 PM: trace state.loadStatus Loading
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:07:51 PM: trace state.count 3
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:07:51 PM: trace state.count 2
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:07:46 PM: trace state.loadStatus Loading
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:07:46 PM: trace state.count 2
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:07:46 PM: trace state.count 1
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:07:40 PM: trace state.loadStatus Loading
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:07:40 PM: trace state.count 1
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:07:40 PM: trace state.count 0
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:07:40 PM: trace deviceDiscovery()
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:07:40 PM: trace state.loadStatus Loading
6a480f71-3f2a-4dec-a747-d4abbdb24a91 9:07:26 PM: trace state.loadStatus Inactive

vhamcy · February 24, 2017, 7:02am

I think I got it now. I saw this error in Live log.
error org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 65537; XML document structures must start and end within the same entity. @ line 195

i.e bodyXml = new XmlSlurper().parseText(hubResponse.body)

I have added a line above this to write hubResponse.body to log trace. I can see body is starting with < gip> and it has device id etc, but cannot see the end as log trace is truncated. I noticed < image> is too big in the response. I had images attached to all fixtures in TCP app. I removed all bulbs and re-added them without images and now it is working. I will add the rest of the bulbs too and hopefully it would keep working. Thank you . Now I can use Alexa to control TCP bulbs again.

ule · February 24, 2017, 3:35pm

Hi , Thanks for advise , I have verify that TCP Gateway embed the custom image and due ST limits the info is not loaded.

Let me know how works your lights and how many do you have

Thanks

vhamcy · February 25, 2017, 12:54am

Working great. I have 7 bulbs . Hopefully can find more in clearance.

No_Name · March 22, 2017, 1:29pm

Thank you for your effort! JFYI The hub firmware downgrading instruction was released yesterday.
https://github.com/bren1818/TCPFirmwareRestore/blob/master/Instructions.docx

allrak · March 22, 2017, 3:16pm

Worked great! Had to mess around a bit to get it to actually update. Had to hold down the sync button during bootup of the tcp gateway. I downgraded from the 3.x version of firmware.

Brandon_Denney · May 17, 2017, 7:28pm

I got mine downgraded and reconnected last night. Three bulbs are working again so far. Time to dig the rest out of a drawer

Brandon_Denney · May 22, 2017, 2:34pm

@ule @vhamcy @allrak @No_Name Are any of you having an issue where you can’t access the TCP app anymore? Now that I have rolled back the gateway I can’t log into the TCP app to add any other lightbulbs. Is there a way around this?

ule · May 24, 2017, 5:56pm

Hi, I have not problem to access to gateway by the TCP app, I´m using android, after downgrade I must to press the sync button to pair again the gateway

buffaloindierocker · August 15, 2017, 1:13pm

I successfully updated the firmware, but even though I blocked greenwavereality.com and update.greenwavereality.com, the gateway still managed to update to the newest version anyway.

Should I also block the .eu TLDs and try again?

No_Name · August 15, 2017, 1:51pm

Block any internet connection to your TCP gateway by IP. Should work.

ule · August 15, 2017, 7:32pm

Hi, yes you must to block both domains, but its better to block all internet access.

quoguy · September 22, 2017, 2:05pm

anyone got an idiots guide to blocking the internet access using windows 10 PLZ…been trying to sort this out for weeks and just cant get knowhere.
TIA

ule · October 2, 2017, 9:13pm

Still working fine, my lights are very stable, if someone have installed this app, can send me feedback?

Thanks

Topic		Replies	Views
TCP lightbulb not recognised by BT hub Devices & Integrations	2	1347	March 20, 2019
LABS RELEASE: TCP Lightbulbs Connected Things	55	6372	October 24, 2015
Anyone just lose control of their TCP Connected bulbs within the last day or so? Devices & Integrations	18	2748	January 27, 2015
TCP Lighting Integration Issue - 10/27 Devices & Integrations	370	28646	July 3, 2016
Can't re-connect with TCP bulbs Connected Things	21	8660	December 20, 2017

[RELEASE] TCP Connected bulbs work with SmartThings Again!

Related topics