Plugin for Connected By TCP LED Bulbs

KnightLord · February 2, 2015, 1:20pm

It totally works!!! Awesome job!!! Thanks so much for all your efforts to fix this!
BTW, I am on UI5.

krayola · February 3, 2015, 7:43am

For alpha code, it worked great, and didn’t require me to do anything beyond connecting with the gateway.

Suggestions:

I’d rename the button from Login to Connect to Gateway and make the note about the green sync button very obvious.
I’d show that the sync worked visibly on the screen.
I’d make it auto-sync at connect and then update the dialog to say all good to go again.

THANKS!

My wife would have been annoyed if she’d discovered the autolights broken again.

We had a 2.5h power outage, and the UPS powering the non-essential automation gear went down first. Tempted to move the TCP gateway to the UPS after this fiasco.

rEVOLVE · February 3, 2015, 11:29pm

I followed OP instructions in a previous post on adding this alpha code. Unfortunately even after adding the gateway’s IP (and confirming I can ping it from my laptop), the message in the configuration when I try to hit Login is that there is no gateway IP. What am I doing wrong I can’t seem to get the Vera Edge to recognize the IP I’m typing in under “advanced”?

jpope42 · February 4, 2015, 1:57am

Same for me (although I have a VeraLight). Can’t seem to get Vera to find TCP.

pmnb · February 4, 2015, 4:38pm

@rEVOLVE and @jpope42: Can you check the firmware version of your TCP Gateway? Also, are the Vera and TCP units plugged into the same router/access point?

jpope42 · February 4, 2015, 11:35pm

My TCP firmware is version 3.0.7.4 Yep, both devices are plugged in to the sam network

jpope42 · February 4, 2015, 11:45pm

Well, I just tried the procedure again, this time it worked! I must been doing something wrong last night.

Thanks for your help!!

pmnb · February 5, 2015, 2:35am

I’ve found similar behavior sometimes when adding new bulbs via the TCP mobile app - the gateway goes into sync mode, but just doesn’t seem to pick things up, and then eventually succeeds on subsequent attempts.

[quote=“jpope42, post:67, topic:179548”]Well, I just tried the procedure again, this time it worked! I must been doing something wrong last night.

Thanks for your help!![/quote]

rEVOLVE · February 5, 2015, 4:23am

Also at 3.0.74 and moving the TCP control hub to the same switch as my Vera Edge is one of the first things I did.

I either get a message at the top of the Vera UI saying TCP Lighting[32] : Startup LUA failed or one indicating there’s no IP set for the gateway, even though I’ve gone into advanced and entered the proper address. I’ve set my router to reserve this static IP for this “Lighting” device by MAC address.

pmnb · February 5, 2015, 1:52pm

If you could send me any log entries containing the text “TCPLighting”, that would help to dig deeper. If you don’t already have it, the InfoViewer plugin provides a nice way of filtering and accessing logs.

[quote=“rEVOLVE, post:69, topic:179548”]Also at 3.0.74 and moving the TCP control hub to the same switch as my Vera Edge is one of the first things I did.

I either get a message at the top of the Vera UI saying TCP Lighting[32] : Startup LUA failed or one indicating there’s no IP set for the gateway, even though I’ve gone into advanced and entered the proper address. I’ve set my router to reserve this static IP for this “Lighting” device by MAC address.[/quote]

maddingo50 · February 6, 2015, 3:41am

Uploaded the Alpha code and all is good now. Thank you pmnb!

BiGGDaN · February 12, 2015, 7:08pm

Mine is having the same issue but they are still connected with the wink hub.

Dan

pmnb · February 13, 2015, 4:34pm

Hi Dan,

Can you clarify on a few points that will help me sort this out:

[ul][li]What Vera UI version are you using?[/li]
[li]What is the firmware version of your hub?[/li]
[li]Did you try the alpha version of the 2.0 plugin posted above?[/li][/ul]

[quote=“BiGGDaN, post:72, topic:179548”]Mine is having the same issue but they are still connected with the wink hub.

Dan[/quote]

ravls · February 14, 2015, 1:14am

This worked for me on UI7. Thanks!

pmnb · February 16, 2015, 12:27am

I’ve submitted the v2.0 plugin for MiOS marketplace approval.

In the meantime, the v1.0.1 (for TCP gateway firmware prior to 3.0.74) and v2.0 (for firmware 3.0.74+) can be downloaded and manually installed using the instructions posted at [url=http://code.mios.com/trac/mios_tcplighting/wiki]http://code.mios.com/trac/mios_tcplighting/wiki[/url].

pmnb · February 16, 2015, 12:35am

I’ve incorporated some of your suggestions in the 2.0 plugin that I’ve submitted to the marketplace:

[ul][li]The Login button has been changed to Pair[/li]
[li]If pairing is successful, the sync function will be automatically executed.[/li][/ul]

Your suggestion about clearly indicating pair/sync success is a good one, but will require some code rework, so it will have to stay on the “to-do” list for now.

For alpha code, it worked great, and didn’t require me to do anything beyond connecting with the gateway.

Suggestions:

I’d rename the button from Login to Connect to Gateway and make the note about the green sync button very obvious.
I’d show that the sync worked visibly on the screen.
I’d make it auto-sync at connect and then update the dialog to say all good to go again.

THANKS!

My wife would have been annoyed if she’d discovered the autolights broken again.

We had a 2.5h power outage, and the UPS powering the non-essential automation gear went down first. Tempted to move the TCP gateway to the UPS after this fiasco.[/quote]

pmnb · February 18, 2015, 1:53am

The v2.0 plugin is now available on the MiOS marketplace.

justroach · February 18, 2015, 2:46am

Hello! Thanks for all the work on this!

The alpha code was working great for me, but the update triggered while I was away and now it is no longer working with the new 2.0 plugin. I tried completely deleting the device and starting over, but I still get stuck after the Sync bit. I get a “Device not ready” when I try and use the newly created devices that get synced over.

Logs:

50 02/17/15 18:41:16.101 luup_log:122: TCPLighting: synchronize_gateway - start <0x2d54d680>
50 02/17/15 18:41:16.101 luup_log:122: TCPLighting: create_child_devices - gateway is initialized <0x2d54d680>
50 02/17/15 18:41:16.102 luup_log:122: TCPLighting: create_child_devices - creating child with did=360262088736156116, name=Room Lights <0x2d54d680>
50 02/17/15 18:41:16.103 luup_log:122: TCPLighting: create_child_devices - creating child with did=216584995899636507, name=Hallway <0x2d54d680>
50 02/17/15 18:41:18.118 luup_log:122: TCPLighting: schedule_next_poll - timer set LEAK this:-188416 start:1515520 to 0x110c000 <0x2d54d680>
50 02/17/15 18:41:18.118 luup_log:122: TCPLighting: synchronize_gateway - end <0x2d54d680>
6338 root 1672 S grep TCP
6338 root 1672 S grep TCP
6338 root 1672 S grep TCP
09 02/17/15 18:41:30.536 JobHandler_LuaUPnP::Run device 122 TCPLighting room 0 type urn:schemas-pmcode-org:service:TCPLightingGateway:1 id parent 0/0xa12228 upnp: 0 <0x2b084000>
50 02/17/15 18:41:53.324 luup_log:122: TCPLighting: tcplighting_plugin_startup - start <0x2b9b7680>
50 02/17/15 18:41:53.325 luup_log:122: TCPLighting: synchronize_gateway - start <0x2b9b7680>
50 02/17/15 18:41:53.325 luup_log:122: TCPLighting: get_gateway - calling tcplighting_gateway_init, IP=10.19.76.113 <0x2b9b7680>
50 02/17/15 18:41:54.346 luup_log:122: TCPLighting: sync_child_devices for 122 - updating child 123 Spa Lights LEAK this:196608 start:1781760 to 0x109d000 <0x2b9b7680>
50 02/17/15 18:41:54.346 luup_log:122: TCPLighting: update_attr - device_number=123 <0x2b9b7680>
50 02/17/15 18:41:54.347 luup_log:122: TCPLighting: update_attr - attr_name=manufacturer <0x2b9b7680>
01 02/17/15 18:41:54.347 LuImplementation::StartLua running startup code for 122 I_TCPLighting1.xml failed <0x2b9b7680>

Little more:

09 02/17/15 18:55:09.754 JobHandler_LuaUPnP::Run device 122 TCPLighting room 0 type urn:schemas-pmcode-org:service:TCPLightingGateway:1 id parent 0/0xed0210 upnp: 0 <0x2aebd000>
50 02/17/15 18:55:28.387 luup_log:122: TCPLighting: tcplighting_plugin_startup - start <0x2b7f1680>
50 02/17/15 18:55:28.387 luup_log:122: TCPLighting: synchronize_gateway - start <0x2b7f1680>
50 02/17/15 18:55:28.387 luup_log:122: TCPLighting: get_gateway - calling tcplighting_gateway_init, IP=10.19.76.113 <0x2b7f1680>
08 02/17/15 18:55:28.829 JobHandler_LuaUPnP::HandleActionRequest device: 122 service: urn:pmcode-org:serviceId:TCPLightingGateway1 action: Synchronize LEAK this:12288 start:1007616 to 0x149e000 <0x2f293680>
08 02/17/15 18:55:28.829 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:pmcode-org:serviceId:TCPLightingGateway1 <0x2f293680>
02 02/17/15 18:55:28.830 JobHandler_LuaUPnP::RunAction device 122 action urn:pmcode-org:serviceId:TCPLightingGateway1/Synchronize failed with -911/Device not ready <0x2f293680>
50 02/17/15 18:55:29.438 luup_log:122: TCPLighting: sync_child_devices for 122 - updating child 123 Spa Lights LEAK this:-28672 start:1056768 to 0x14aa000 <0x2b7f1680>
50 02/17/15 18:55:29.439 luup_log:122: TCPLighting: update_attr - device_number=123 <0x2b7f1680>
50 02/17/15 18:55:29.439 luup_log:122: TCPLighting: update_attr - attr_name=manufacturer <0x2b7f1680>
01 02/17/15 18:55:29.440 LuaInterface::CallFunction_Startup-1 device 122 function tcplighting_plugin_startup failed [string “…”]:135: attempt to concatenate local ‘new_value’ (a nil value) <0x2b7f1680>
01 02/17/15 18:55:29.440 LuImplementation::StartLua running startup code for 122 I_TCPLighting1.xml failed <0x2b7f1680>

pmnb · February 18, 2015, 3:05am

Eek - Looks like I may have some sloppy logging code. Try uploading the attached file and see if that fixes things.

[quote=“justroach, post:78, topic:179548”]Hello! Thanks for all the work on this!

The alpha code was working great for me, but the update triggered while I was away and now it is no longer working with the new 2.0 plugin. I tried completely deleting the device and starting over, but I still get stuck after the Sync bit. I get a “Device not ready” when I try and use the newly created devices that get synced over.

Logs:

50 02/17/15 18:41:16.101 luup_log:122: TCPLighting: synchronize_gateway - start <0x2d54d680>
50 02/17/15 18:41:16.101 luup_log:122: TCPLighting: create_child_devices - gateway is initialized <0x2d54d680>
50 02/17/15 18:41:16.102 luup_log:122: TCPLighting: create_child_devices - creating child with did=360262088736156116, name=Room Lights <0x2d54d680>
50 02/17/15 18:41:16.103 luup_log:122: TCPLighting: create_child_devices - creating child with did=216584995899636507, name=Hallway <0x2d54d680>
50 02/17/15 18:41:18.118 luup_log:122: TCPLighting: schedule_next_poll - timer set LEAK this:-188416 start:1515520 to 0x110c000 <0x2d54d680>
50 02/17/15 18:41:18.118 luup_log:122: TCPLighting: synchronize_gateway - end <0x2d54d680>
6338 root 1672 S grep TCP
6338 root 1672 S grep TCP
6338 root 1672 S grep TCP
09 02/17/15 18:41:30.536 JobHandler_LuaUPnP::Run device 122 TCPLighting room 0 type urn:schemas-pmcode-org:service:TCPLightingGateway:1 id parent 0/0xa12228 upnp: 0 <0x2b084000>
50 02/17/15 18:41:53.324 luup_log:122: TCPLighting: tcplighting_plugin_startup - start <0x2b9b7680>
50 02/17/15 18:41:53.325 luup_log:122: TCPLighting: synchronize_gateway - start <0x2b9b7680>
50 02/17/15 18:41:53.325 luup_log:122: TCPLighting: get_gateway - calling tcplighting_gateway_init, IP=10.19.76.113 <0x2b9b7680>
50 02/17/15 18:41:54.346 luup_log:122: TCPLighting: sync_child_devices for 122 - updating child 123 Spa Lights LEAK this:196608 start:1781760 to 0x109d000 <0x2b9b7680>
50 02/17/15 18:41:54.346 luup_log:122: TCPLighting: update_attr - device_number=123 <0x2b9b7680>
50 02/17/15 18:41:54.347 luup_log:122: TCPLighting: update_attr - attr_name=manufacturer <0x2b9b7680>
01 02/17/15 18:41:54.347 LuImplementation::StartLua running startup code for 122 I_TCPLighting1.xml failed <0x2b9b7680>

Little more:

09 02/17/15 18:55:09.754 JobHandler_LuaUPnP::Run device 122 TCPLighting room 0 type urn:schemas-pmcode-org:service:TCPLightingGateway:1 id parent 0/0xed0210 upnp: 0 <0x2aebd000>
50 02/17/15 18:55:28.387 luup_log:122: TCPLighting: tcplighting_plugin_startup - start <0x2b7f1680>
50 02/17/15 18:55:28.387 luup_log:122: TCPLighting: synchronize_gateway - start <0x2b7f1680>
50 02/17/15 18:55:28.387 luup_log:122: TCPLighting: get_gateway - calling tcplighting_gateway_init, IP=10.19.76.113 <0x2b7f1680>
08 02/17/15 18:55:28.829 JobHandler_LuaUPnP::HandleActionRequest device: 122 service: urn:pmcode-org:serviceId:TCPLightingGateway1 action: Synchronize LEAK this:12288 start:1007616 to 0x149e000 <0x2f293680>
08 02/17/15 18:55:28.829 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:pmcode-org:serviceId:TCPLightingGateway1 <0x2f293680>
02 02/17/15 18:55:28.830 JobHandler_LuaUPnP::RunAction device 122 action urn:pmcode-org:serviceId:TCPLightingGateway1/Synchronize failed with -911/Device not ready <0x2f293680>
50 02/17/15 18:55:29.438 luup_log:122: TCPLighting: sync_child_devices for 122 - updating child 123 Spa Lights LEAK this:-28672 start:1056768 to 0x14aa000 <0x2b7f1680>
50 02/17/15 18:55:29.439 luup_log:122: TCPLighting: update_attr - device_number=123 <0x2b7f1680>
50 02/17/15 18:55:29.439 luup_log:122: TCPLighting: update_attr - attr_name=manufacturer <0x2b7f1680>
01 02/17/15 18:55:29.440 LuaInterface::CallFunction_Startup-1 device 122 function tcplighting_plugin_startup failed [string “…”]:135: attempt to concatenate local ‘new_value’ (a nil value) <0x2b7f1680>
01 02/17/15 18:55:29.440 LuImplementation::StartLua running startup code for 122 I_TCPLighting1.xml failed <0x2b7f1680>[/quote]

justroach · February 18, 2015, 3:15am

Suhweet!

Worked like a charm! 2.0.1?

You need a BTC donation address…