Ecosmart LED Smart Bulbs

Oh, you only hear the humming noise when you dim the lights through SmartThings?

They typically have a minor hum, but it’s so quiet you shouldn’t notice it.

It’s possible you got a bad batch of bulbs. I’d see about exchanging them. Mine doesn’t hum (at least not noticeable from 5 feet away)

HI,

could you please provide details instructions on how I can hook the Ecosmart bulbs to the Smarthings Hub v2? I need clarification on how others are doing it.

Thanks

anyone get the rgb bulbs working with better color? I have two and so far tried a few different device types but all i can seem to get is white offwhite and purple. and the device type in this thread is a dead link.

also anyone figure out how to group rgb lights so colors will be synced across multiple lights? I found several dim with me apps but nothing for rgb

Hi,

Please …how did you get the Ecosmart light bulb working with the hub?

Thanks

Try resetting it first. It’s the same process as the GE link bulb. To reset. On 3 seconds, off 3 seconds until you see the bulb dimming.
Put put your hub into device discovery and once you see the bulb blinks. It’s pair. You can change it to GE link bulb device type
If not. Try bring it closer to the hub.

You can try @sticks18 Phillips hue device type

I’ve been unable to get the tunable bulbs working with SmartThings V1. I can query the lightbulbs for their state but trying to use any standard profile Zigbee commands results in nothing happening. Using cluster library level I can turn them on/off, but not change the color temperature. They do work fine with Wink though so they may do something… differently… out of spec.

Have you tried the stock ST ZigBee White Color Temperature Bulb device type? I am using this for a couple of ecosmart GUI10 bulbs.

I’ve used anything and everything remotely conceivable as being a sane device type. I’ve also read the specification and played with it directly using a template type. The thing just likes to ignore anything I tell it to do.

That’s strange. I have at least 10 of these GUI10 ecosmart bulbs and both GE link and the ST ZigBee White Color Temperature Bulb worked. You are not talking about the color bulb are you? Maybe remove the bulb and add it again.

I’m using the tunable color lightbulb, not the color changing one. I’ve tried removing/adding a few different ones.

Not really sure what else to say other than a bad bulb maybe?

I’ve got 5 of them, they all work fine with Wink. It’s bizarre.

All 4 bulbs I have 2rgb, 2 white. I had to start searching for new devices in the app, turn on the light, after a minute or two cancel the device search close the app start it again and they were there as non configured devices. Never did I get it to pop up and say device found.

Hope this helps

Hi Josh, can you try going into the IDE, My Devices and clicking into one of these bulbs and see what the line Raw Description says?

If it’s not populated, could you reset one of the bulbs, start Live Logging then pair it back to ST and paste the logs here?

There seems to be an issue with non-official zigbee bulbs where ST doesn’t pull the correct endpointId, so any devicetypes using ${endpointId} or the newer zigbee framework commands that don’t specify the endpoint don’t work because the commands aren’t addressed properly. The two questions above are targeted at seeing what endpoint the primary on/off, dim and color clusters are attached to. @Navat604 if you can see the raw description for one of your bulbs, it is likely the same for all of these Ecosmart line.

Raw description is:

01 0104 0102 00 09 0000 0003 0004 0005 0006 0008 0300 0B04 FC0F 01 0019

Data is:

application: 0f
endpointId: 01
manufacturer: EcoSmart
model: zhaTunW

It looks like ST knows the endpoint. Are you comfortable modifying devicetypes?

Can you try copying the official Osram Lightify Led Tunable White devicetype and add a simple
log.debug "ST is using endpoint ${endpointId}" inside the on() command? Then press “on” in the app while running Live Logging. That should confirm whether ST is using the right endpoint.

ST is using endpoint null

How… unexpected.

${device.endpointId} returns 01 though.

Not sure if you want this but here’s the raw data and log for a working bulb. Looks identical to yours.

Raw Description
01 0104 0102 00 09 0000 0003 0004 0005 0006 0008 0300 0B04 FC0F 01 0019

On and off commands

21ae1f58-1a72-42d3-ae02-3a9316df7bbe 8:29:34 AM: info [name:level, value:100, type:level]
21ae1f58-1a72-42d3-ae02-3a9316df7bbe 8:29:34 AM: debug description is read attr - raw: AEA901000808000020FE, dni: AEA9, endpoint: 01, cluster: 0008, size: 08, attrId: 0000, encoding: 20, value: fe
21ae1f58-1a72-42d3-ae02-3a9316df7bbe 8:29:34 AM: info [name:level, value:0, type:level]
21ae1f58-1a72-42d3-ae02-3a9316df7bbe 8:29:34 AM: debug description is read attr - raw: AEA90100080800002000, dni: AEA9, endpoint: 01, cluster: 0008, size: 08, attrId: 0000, encoding: 20, value: 00
21ae1f58-1a72-42d3-ae02-3a9316df7bbe 8:29:34 AM: info [name:switch, value:off, type:switch]
21ae1f58-1a72-42d3-ae02-3a9316df7bbe 8:29:33 AM: debug description is catchall: 0104 0006 01 01 0000 00 AEA9 00 00 0000 0B 01 0000
21ae1f58-1a72-42d3-ae02-3a9316df7bbe 8:29:33 AM: info [type:switch, name:switch, value:off]
21ae1f58-1a72-42d3-ae02-3a9316df7bbe 8:29:33 AM: debug description is on/off: 0
21ae1f58-1a72-42d3-ae02-3a9316df7bbe 8:29:28 AM: info [name:level, value:100, type:level]
21ae1f58-1a72-42d3-ae02-3a9316df7bbe 8:29:28 AM: debug description is read attr - raw: AEA901000808000020FE, dni: AEA9, endpoint: 01, cluster: 0008, size: 08, attrId: 0000, encoding: 20, value: fe
21ae1f58-1a72-42d3-ae02-3a9316df7bbe 8:29:27 AM: info [type:switch, name:switch, value:on]
21ae1f58-1a72-42d3-ae02-3a9316df7bbe 8:29:27 AM: debug description is on/off: 1
21ae1f58-1a72-42d3-ae02-3a9316df7bbe 8:29:27 AM: info [name:level, value:0, type:level]
21ae1f58-1a72-42d3-ae02-3a9316df7bbe 8:29:27 AM: debug description is read attr - raw: AEA90100080800002000, dni: AEA9, endpoint: 01, cluster: 0008, size: 08, attrId: 0000, encoding: 20, value: 00
21ae1f58-1a72-42d3-ae02-3a9316df7bbe 8:29:27 AM: info [name:switch, value:on, type:switch]
21ae1f58-1a72-42d3-ae02-3a9316df7bbe 8:29:27 AM: debug description is catchall: 0104 0006 01 01 0000 00 AEA9 00 00 0000 0B 01 0100

That’s interesting and strange. Is groovy case sensitive for variable names? What if you change it to ${EndpointId}?

The private get() method uses a capital E. Either that or the BigInteger()toString() combo isn’t working correctly. Either way, if you change all the ${endpointId} to 0x${device.endpointId} I think it will work.

(Thanks Ray. I think we’re on the right track.)