TCPLighting

This plugin integrates a ​Connected By TCP LED lighting gateway with a Vera controller. Once a device for the gateway is created, the plugin in turn creates child devices (of type Dimming or SwitchPower, as appropriate) for each connected bulb. Since the bulbs are created as standard devices, they are available for control via scenes, mobile apps, etc.

Important: In the 3.0.74 TCP gateway firmware update, TCPi disabled the API that version 1.x of this plugin used. This is an automatically pushed update, that not everyone received at the same time. Version 2.0 of this plugin, which uses a secure local API seems to correct this problem. However, the 2.0 plugin will not work with prior gateway firmware version. If for whatever reason, your gateway is running a earlier firmware version, you can try manually installing the v1.x plugin, which is attached below.

Pre-Installation

Set up your Connected By TCP LED gateway and bulbs as per the instructions provided with the devices. Ensure that everything is working (i.e. lights can be controlled using the smartphone apps or gateway web interface) prior to installing the plugin. The Vera and TCP gateway Ethernet cables should be plugged into the same router/access point/hub, so as to ensure that the Vera can reach the TCP hub from a TCP/IP connectivity perspective.

Installation (Marketplace/UI5)

Note: The v2.0 plugin that supports TCP gateway version 3.0.74 and later is pending approval for release on the ​MiOS app marketplace. In the meantime, please follow the manual installation instructions in the next section.

1. Install the ​TCPLighting app from the MiOS App Marketplace (i.e. the Apps / Install Apps page).

2. Wait for the Luup restart to complete.

3. Go into the TCPLighting device configuration UI (wrench icon). You should see a "Pair" button - but don't click it yet ;-)

4. If you are lucky, the auto-discovery feature will have detected the Connected By TCP gateway and configured its IP address.

5. If the auto-discovery failed, you will see the message No gateway IP address specified, autodiscovery failed in the gateway device UI. Some of the reasons why this might happen, and how to manually configure the gateway IP address, are outlined in the Auto-Discovery section below.

6. Press the green sync button on your Connected by TCP gateway.

7. Click the "Pair" button on the TCP Lighting config UI. Wait a few seconds. If the pairing is successful, the plugin will then poll the gateway and create child devices for each bulb. If a bulb's room name matches that of a Vera room, it will be automatically added to the room.

Manual Installation of Version 2.0 (UI5)

Note: Only use this version if your Connected By TCP gateway is running firmware version 3.0.74 or later.

1. Download the TCPLighting Plugin 2.0 zip file attached below.

2. Upload all of the plugin XML, JSON and LUA files using the Apps / Develop Apps / Luup files page. Make sure to click the "Restart Luup after upload" checkbox

3. Wait for the Luup restart to complete.

4. Go into the TCPLighting device configuration UI (wrench icon). You should see a "Pair" button - but don't click it yet ;-)

5. If you are lucky, the auto-discovery feature will have detected the Connected By TCP gateway and configured its IP address.

6. If the auto-discovery failed, you will see the message No gateway IP address specified, autodiscovery failed in the gateway device UI. Some of the reasons why this might happen, and how to manually configure the gateway IP address, are outlined in the Auto-Discovery section below.

7. Press the green sync button on your Connected by TCP gateway.

8. Click the "Pair" button on the TCP Lighting config UI. Wait a few seconds. If the pairing is successful, the plugin will then poll the gateway and create child devices for each bulb. If a bulb's room name matches that of a Vera room, it will be automatically added to the room.

Manual Installation of Version 1.0.1 (UI5)

Note: Only use this version if your Connected By TCP gateway is running a firmware version prior to 3.0.74.

1. Download the TCPLighting Plugin 1.0.1 zip file attached below.

2. Upload all of the plugin XML, JSON and LUA files using the Apps / Develop Apps / Luup files page. Make sure to click the "Restart Luup after upload" checkbox

3. Wait for the Luup restart to complete.

4. If you are lucky, the auto-discovery feature will have detected the Connected By TCP gateway and configured its IP address.

5. If the auto-discovery failed, you will see the message No gateway IP address specified, autodiscovery failed in the gateway device UI. Some of the reasons why this might happen, and how to manually configure the gateway IP address, are outlined in the Auto-Discovery section below.

Auto-Discovery

The Connected By TCP LED gateway supports a subset of the ​Simple Service Discovery Protocol (SSDP) which is part of the ​Universal Plug and Play (UPnP) architecture. In theory, this should allow this plugin to automatically determine the IP address of the gateway without user intervention. However, there are several reasons why this may not work in practice:

1. SSDP uses IP multicasts to search for devices providing UPnP services. Depending on how your Vera and local network are configured, the multicast requests may not reach the gateway. For example, your router may not be configured to forward multicasts from the wired to the wireless segments of your network. This is also discussed in the documentation for ​futzle's ​Wemo Plugin.

2. VeraLite controllers have a slightly odd network interface configuration which results in situations where the multicast responses may not come back on the expected interface. This is described ​here. A workaround is described ​here, but this pretty well defeats the benefits of auto-discovery, given the steps involved.

If auto-discovery doesn't work for you, then you can manually specify an IP address by updating the advanced properties of main TCP Lighting gateway device (click the wrench icon, go to the Advanced tab, and enter the gateway's IP address in the IP field). You may need to check the DHCP client table of your home router to find the IP address of the gateway. Another way of getting the IP address is to open a command window on a PC that is on the same network as the lighting gateway, enter the command ping lighting and note the IP address that the lighting host name resolves to.

If you still can't connect, try enabling remote access via the Connected By TCP / Greenwave mobile app. One user has reported that this seemed to make things work.

v1.0 Release Notes:

• First version available in the MiOS app Marketplace.
• Functionally the same as v0.4, except that it will now auto-update by virtue of being in the app marketplace.

v0.4 Release Notes:

• New approach to flagging offline bulbs. Instead of being rendered invisible, the name off offline bulbs are now prefixed with "[Offline]". The offline labeling can be modified through the OfflineDeviceNameFormat state variable. The format string is as per that used by the Lua ​string.format function, where the %s placeholder is replaced with the device name. For example, if the bulb named "Front Entry Light" goes offline, the default format string of [Offline] %s will cause the device name to be displayed as "[Offline] Front Entry Light" if the status of the bulb cannot be retrieved. Changing the value of the OfflineDeviceNameFormat state variable to %s is unavailable would result in a display name of "Front Entry Light is unavailable". A prefix was chosen as the default format string, simply because the Vera UI truncates longer names, thus a suffix would not be displayed in some cases.
• The auto-discovery feature has been made more robust through retry logic. When polling the gateway with a previously auto-discovered gateway IP fails, the IP address is cleared, which will trigger a new auto-discovery attempt at the next polling interval. See the notes on Auto-Discovery if you are having trouble getting this feature to work.

v0.3 Release Notes:

• Better handling of unknown room names, i.e room names from the Connected By TCP Gateway that do not match Vera room names. The plugin will now only update the room name if a match is found. Previous versions erroneously set the room number to zero in such a case.

v0.2 Release Notes:

• Includes more robust handling of devices and gateways going offline and coming back online. Device numbers should now be retained so that scenes, etc. are not broken. Polling continues after a failed HTTP request to the gateway.
• Experimental and partial implementation of gateway SSDP auto-discovery.
• Gateway device will now get a default name assigned.
• Bulbs will have manufacturer and model attributes set.
• Logging is a little less verbose.

v0.1 Release Notes:

• This is my first attempt at a Vera plugin, so please do not hesitate to provide constructive criticism.
• This is an unsupported hobbyist project. I am in no way connected with ​TCPi (the makers of the Connected By TCP gateway and bulbs) or ​Vera Control, Ltd. Please do not ask them for support with this plugin.
• Code is based on an undocumented HTTP API.
• Only tested on a Veralite with UI5.
• Only tested with A19 dimmable bulbs.
• Default polling interval is 60 seconds. Therefore, any changes made outside of the Vera environment (using a remote or the Connected By TCP / Greenwave Reality apps) may take up to 60 seconds to be reflected in the Vera UI. Ditto for new bulbs.

To-Do:

• Store code in code.mios.com SVN repository. [Done]
• Gateway auto-discovery via SSDP. [Done]
• Additional gateway and light variables settings. [Done]
• Testing with multiple gateways.
• Energy metering (maybe).

Acknowledgements

Many thanks to:

• ​ctguess for ​the forum posting that describes how to control these bulbs.
• ​futzle for the clear and concise description of the ​multicast forwarding issue.
• ​migi and ​futzle for their comments on the ​multiple IPs assigned to the VeraLite Ethernet port.
• ​macfly92 for figuring out ​how modify the firewall rules for a VeraLite to fix the multicast problem.
• ​RichardTSchaefer for clarifying the behavior of luup.set_failure (and helping me avoid going down a dead-end.).
• ​ecsherwo for the insight regarding enabling remote access.
• ​jpope42 for helping identify the importance of having the Vera and TCP gateway plugged into the same device.