LABS RELEASE: TCP Lightbulbs

They work with the normal switch. But maybe a little different than you’d expect.

  1. if wall switch off and you switch on at wall switch, light goes on to full brightness.
  2. if wall switch on, but you turned off in an app, you must turn wall switch off, then on. Which then goes to full brightness.
    1. Do not put these in a dimmer circuit.

      HTH,
      Twack

That actually sounds like a pretty reasonable way for them to work via the switch. Thanks.

@twack

I never was able to make the TCP light go on based on an event other than IFTTT. Any suggestions?

@beckwith,

Did you pick another switch or light to go on with the event? Did that switch or light come on? If it did, can you see the commands for “on” being sent in your log for both the light or switch and the TCP light?

Let me know,
Twack

Never mind.

I found my problem. It was set to only trigger during “Night” mode. It seems once you select a mode, unchecking it doesn’t get saved. As a workaround, I checked all modes and now it works.

Sorry for the false alarm and thanks for your help.

@beckwith,

So how are you liking the bulbs and the app?

Twack

@twack

Great! I have the two bulb set. Right now I also control them with physical z-wave switches virtualized through the “The Big Switch” app. The lag with this set up is pushing it a bit.

@twack I was wondering if there was a way to get the state of the light if it was turned on manually at the switch. Right now when you turn on the light manually it comes on but in the ST dashboard it is shown as off. It would be nice if it would up date ST state to on. Also if the light switch was set to off and the TCP bulb was not receiving power if in ST Things we could show it was powered off would be cool to. I looked at the TCP app and these states seem to be shown by the native app. Ie. little red circle with x in it when bulb is powered off, and also the app eventually updates the state of the bulb to on if you manually use the switch.

Oh I also noticed if I add new bulbs after initially setting up TCP (Connect) it doesn’t see the new bulbs and I have to remove the smartapp and reinstall the smartapp for all the bulbs to be seen.

Just somethings to consider for future enhancement, but i’m loving that you got this working, its a great way to add lights at a lower cost. Awesome work. Picked up 6 bulbs and TCP for some lamps around my house :slight_smile:

Cheers.

I figured out a pretty cool trick with the TCP bulbs. Basically, you can have individual bulbs and master switches that you create from the TCP gateway (pretty much @twack’s virtual dimmer + dim with me app). The plus to setting it up this way is the bulbs assigned to the “master dimmer” all operate perfectly in sync as they are grouped on the TCP gateway, not SmartThings. The only drawback I’ve noticed is that the bulbs are no longer listed individually in the TCP app, but that’s not a big deal because I don’t use it. I’ll try to explain the process as clear as possible.

After you’ve set up the bulbs (individually) on the TCP side, add them to SmartThings.

Go back to the TCP app and create ‘fixtures’ and group the bulbs you want to control together.

Back in the SmartThings app, you need to app a new TCP connect app, temporarily. DO NOT SELECT NEW GROUPED BULBS YET, you just let SmartThings see them on the network. Once SmartThings sees them on the network, just uninstall the second TCP connect app.

Back in the original TCP connect app, the new grouped bulbs will appear while discovering. You can now select the new groups and keep the individual builds selected as well. All controllable via SmartThings, individually and by groups! Awesome stuff!

1 Like

Thanks for the info!

I picked up the TCP starter kit today.

FYI for anyone else interested. They are listed at $80 on homedepot.com However in store this morning they were $50.

I installed my TCP lights. For some reason my gateway, even though it is plugged into my router, can’t be seen my by ipad (on wifi). But I made an account and if I log in and take the long way around the internet I can still access everything.

One question - my bulbs came grouped in “unknown house” which does show up on ST. Anyone know how to ungroup them? I can’t figure it out on TCP’s utility lighting/.

My bulbs aren’t in the same room.

I just got back from a local Home Depot, and the 2 bulb TCP starter kit was $80 in the store. Maybe you caught the lower price before they changed it in their retail store system. I ordered the 3 bulb starter kit with remote from tigerdirect.com just now, because it’s $70 after rebate 5/9 and 5/10. I’m not a fan of rebates, but it seems worth it to try to get that price.

I have two of the TCP bridges, no bulbs or packaging, that are not in use. They are new and I’ve tested them. If anyone is interested, send me a message!

Yeah I wouldn’t have bought the starter kit at $80 because I don’t have enough fixtures that take regular sized bulbs. Everything seems to be candleabras now. But when I saw it at still at $50 in store I couldn’t resist. Glad I caught it at the lower price. Once I got them integrated to ST they have worked great.

I had mentioned before that I was having a problem with just 2 bulbs and ST. Since then I have purchased 4 additional bulbs. So now I can explain better.

With 3 bulbs being activated within an app, the 3rd normally doesn’t respond or it is just hit and miss. The problem I am having with 2 bulbs is dimming. If I setup an app to dim 2 bulbs, 50 % of the time, they will both come on, but the 2nd in the chain ignores the dimming command. This is what was happening in my hallway with 2 bulbs. Then I followed the example here to create a fixture. Now ST thinks it is just 1 bulb. Works all the time.

But when I purchased the other bulbs and added 1 more into that app (1 fixture, 1 bulb : ST thinks it is just two bulbs) they would both come on but the 2nd would ignore the dimming command most of the time.

Anyhow, I understand that the new hub should take care of this problem. Just wondering if there is going to be any more work on the current hub when it comes to TCP Connected bulbs?

A while ago, you indicated you had a prototype that included wattage. Is that version available yet?

Not available yet. I think we’re waiting on the App roll-out to settle in.

Twack

Cool. Just wanted to make sure it wasn’t forgotten or fallen through the cracks so to speak.

Has anyone installed BR30 TCP Connected as a recessed fixture? Tigerdirect TCP Connected BR30 has $15 off $100 (no sales tax), ordered 4 today and plan to install next week (once delivered)… just wanted to check here first? Thanks!