Thanks for catching and testing - will resubmit to app store ASAP.
Suhweet!
Worked like a charm! 2.0.1?
You need a BTC donation address…[/quote]
Hey, good point… I would definitely donate a few bucks also! 
The corrected plugin was approved on the app store yesterday for anyone with a similar problem as reported by justroach.
I just wanted to chime in that thanks to PMNB my setup is back to functional again - the way I want it!
It took loading one changed file to the 1.0.1 plugin that he posted today to work with the original out-of-box firmware of a new and never-been-updated TCP hub I bought off the shelf.
I made sure this time to block all WAN access from the TCP bridge in my network router config (router is an ASUS RT-AC66u running aftermarket DD-WRT firmware). Although all access is allowed from my home network for local control, this unit is now blocked from phoning home for updates - the WAN light on the bridge is red all the time and that unit will be “frozen” with its out-of-box firmware of 2.0.105.
Best of both worlds, since now I can control the TCP lighting with web browser, mobile app, AND Vera - just like it worked before TCP decided to lock it all down.
I’ve updated the wiki to contain a download link and instructions for v1.0.2 of the plugin that can be manually installed for those choosing to block out firmware updates. It deals with an incompatibility with the slightly different XML output format returned by RoomGetCarousel HTTP requests to older versions of the firmware.
Anyone with the latest gateway firmware (currently 3.0.74) should stick with the version on the app marketplace.
Thank you rEVOLVE for your help sorting this out, as well as the 5-star rating and kind review in the marketplace.
running TCP GW v3.0.74
vera v 1.7.541
tried the plugin but I get the following error when trying to pair. Have a static IP assigned to the tcp gateway.
No gateway token extracted, pairing failed - HTTPS status=200 - Gateway RC=404
I’m on the road right now, but will look into this when I get home.
In the meantime, can you confirm that you pressed the green sync button on the gateway (and it started blinking) prior to pressing the Pair button on the plugin UI?
[quote=“lesnsit, post:86, topic:179548”]running TCP GW v3.0.74
vera v 1.7.541
tried the plugin but I get the following error when trying to pair. Have a static IP assigned to the tcp gateway.
No gateway token extracted, pairing failed - HTTPS status=200 - Gateway RC=404[/quote]
Yes, I did press the green sync button and waited for the flashing arrows before attempting the sync.
Thanks for the confirmation.
I’ll see if I can duplicate it on my test UI7 unit and get back to you.
I just tested this on a new VeraEdge with the firmware upgraded to 1.7.1018 and it worked (unfortunately or fortunately, depending on how you look at it). That leads me to believe there is something about your setup that I didn’t account for in the plugin.
If you don’t mind spending the time, could you try pairing again and then send me the related log entries? Any log entries from the plugin are prefixed with the text “TCPLighting”.
There are a couple of ways to achieve this:
[ol][li]Logging into your Vera and searching the [font=courier]/var/log/cmh/LuaUPnP.log[/font] file via command line. See http://wiki.micasaverde.com/index.php/Luup_Debugging[/li]
[li]Using the InfoViewer plugin: http://forum.micasaverde.com/index.php/topic,13477.0.html (which must be manually installed)[/li][/ol]
If this doesn’t reveal anything, I may need to get you to try a few other things.
[quote=“pmnb, post:89, topic:179548”]Thanks for the confirmation.
I’ll see if I can duplicate it on my test UI7 unit and get back to you.
I am working with the latest version of the App and a Vera on firmware version 1.7.1707. When I try to pair I am seeing “No gateway IP address specified, pairing failed”. I have opened the Advanced setting and put the IP address of the TCP Connected by hub in the ip field. My Vera and TCP Connected by are plugged into the same router. The logs are the Vera are as follows:
luup_log:7: TCPLighting: pair_with_gateway - IP=nil <0x760ba520>
I see the correct IP address listed in the Advanced tab, even after I refresh my log in. Any ideas on how why the Pair would not be reading the ip addressed and passing it to the pairing call?
Hi,
I’m having a similar issue where the plug in installs, but will not pair with the TCP gateway. I’m running a Vera3 with UI7, latest firmware (1.7.760). The TCP gateway firmware is version 3.0.80. The TCP gateway functions correctly and I can control lights both via the smartphone app as well as control the lights remotely via their website. Version of the TCPLighting plug in is 2.0, installed directly from the Install Apps location. The error I’m receiving from the device installed by the TCPLighting plug in is:
No gateway token extracted, pairing failed - HTTPS status=timeout
I’ve entered in the IP for the TCP gateway in the Advanced settings, clicked the green button on the gateway before trying to pair, have uninstalled/reinstalled the plug-in, etc. Please let me know if there’s any additional info that would help with troubleshooting, or if you have any other ideas that I can try.
Thx!
If you are set up to SSH into you vera, I would be good to see if you can ping that IP from the Vera. It would also be helpful to get any log entries that contain the text “TCPLIghting”.
[quote=“ListerD, post:92, topic:179548”]Hi,
I’m having a similar issue where the plug in installs, but will not pair with the TCP gateway. I’m running a Vera3 with UI7, latest firmware (1.7.760). The TCP gateway firmware is version 3.0.80. The TCP gateway functions correctly and I can control lights both via the smartphone app as well as control the lights remotely via their website. Version of the TCPLighting plug in is 2.0, installed directly from the Install Apps location. The error I’m receiving from the device installed by the TCPLighting plug in is:
No gateway token extracted, pairing failed - HTTPS status=timeout
I’ve entered in the IP for the TCP gateway in the Advanced settings, clicked the green button on the gateway before trying to pair, have uninstalled/reinstalled the plug-in, etc. Please let me know if there’s any additional info that would help with troubleshooting, or if you have any other ideas that I can try.
Thx![/quote]
Not set up to ssh in but will get set up and try to ping. I’ll get the logs as well this weekend and post the relevant entries.
Thx!
below are the log entries for when I’m trying to pair:
50 06/17/16 21:06:40.367 luup_log:58: TCPLighting: pair_with_gateway - Token=nil <0x2eaab680>
50 06/17/16 21:06:40.367 luup_log:58: TCPLighting: pair_with_gateway - error: No gateway token extracted, pairing failed - HTTPS status=timeout <0x2eaab680>
50 06/17/16 21:06:40.368 luup_log:58: TCPLighting: pair_with_gateway - end <0x2eaab680>
01 06/17/16 21:06:40.368 LuaInterface::CallFunction_Job device 58 function STCPLightingGateway1_TCPLightingGateway1_Pair_run took 5 seconds <0x2eaab680>
I am able to ping the IP address when SSH’d into Vera:
:/tmp/log/cmh# ping 192.168.1.28
PING 192.168.1.28 (192.168.1.28): 56 data bytes
64 bytes from 192.168.1.28: seq=0 ttl=64 time=5.539 ms
64 bytes from 192.168.1.28: seq=1 ttl=64 time=0.561 ms
64 bytes from 192.168.1.28: seq=2 ttl=64 time=0.530 ms
I did an uninstall/reinstall of the app and got this despite the fact that I input the IP address on the advanced tab. I also verified that it did save the ip address after I got this error:
08 06/17/16 21:44:32.905 JobHandler_LuaUPnP::HandleActionRequest device: 60 service: urn:pmcode-org:serviceId:TCPLightingGateway1 action: Pair <0x2da4d680>
08 06/17/16 21:44:32.906 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=60 <0x2da4d680>
08 06/17/16 21:44:32.907 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:pmcode-org:serviceId:TCPLightingGateway1 <0x2da4d680>
08 06/17/16 21:44:32.907 JobHandler_LuaUPnP::HandleActionRequest argument action=Pair <0x2da4d680>
50 06/17/16 21:44:32.908 luup_log:60: TCPLighting: pair_with_gateway - start <0x2da4d680>
50 06/17/16 21:44:32.909 luup_log:60: TCPLighting: pair_with_gateway - IP=nil <0x2da4d680>
50 06/17/16 21:44:32.909 luup_log:60: TCPLighting: pair_with_gateway - UUID=4d494342-5342-5645-003c-000001c9e646 <0x2da4d680>
50 06/17/16 21:44:32.910 luup_log:60: TCPLighting: pair_with_gateway - Token=nil <0x2da4d680>
50 06/17/16 21:44:32.910 luup_log:60: TCPLighting: pair_with_gateway - error: No gateway IP address specified, pairing failed <0x2da4d680>
06 06/17/16 21:44:32.911 Device_Variable::m_szValue_set device: 60 service: urn:pmcode-org:serviceId:TCPLightingGateway1 variable: ErrorText was: No gateway token assigned, use device configuration UI to pair first now: No gateway IP address specified, pairing failed #hooks: 0 upnp: 0 skip: 0 v:0x107f658/NONE duplicate:0 <0x2da4d680>
50 06/17/16 21:44:32.911 luup_log:60: TCPLighting: pair_with_gateway - end <0x2da4d680>
It looks like the first ping took a while.
Can you try testing the attached version of the I_TCPLighting1.lua file. I’ve changed the HTTP timeout value to 20 seconds, as opposed to the original 5 secs.
The steps to install the revised file are:
[ol][li]Download the I_TCPLighting1.lua file attached below.[/li]
[li]Upload this file to your Vera using the Apps / Develop Apps / Luup files page. Make sure to click the “Restart Luup after upload” checkbox[/li]
[li]Wait for the Luup restart to complete.[/li][/ol]
[quote=“ListerD, post:95, topic:179548”]I am able to ping the IP address when SSH’d into Vera:
:/tmp/log/cmh# ping 192.168.1.28
PING 192.168.1.28 (192.168.1.28): 56 data bytes
64 bytes from 192.168.1.28: seq=0 ttl=64 time=5.539 ms
64 bytes from 192.168.1.28: seq=1 ttl=64 time=0.561 ms
64 bytes from 192.168.1.28: seq=2 ttl=64 time=0.530 ms[/quote]
Will do. I’ll try this tomorrow evening and report the results. Thx!
That did it! I was able to pair and sync. The two bulbs I was starting with came up in Vera as named in TCP. Well, one came up. then I realized my wife had turned the other one off. a second sync and bulb number two appeared. Thank you so much for the plug in and the help getting it all working. Now I can get the rest of the lamps hooked up. Thanks again. If you ever need help testing, let me know.
Glad it worked. I’ll roll that along with an update promised to another person in a 2.1 update.
I am having the same issue others reported…“No gateway IP address specified, pairing failed” can someone post the estimate of when 2.1 with this fix will be released.
Thanks in advance.