Zigbee 3.0 button controller $8.88 USD at home Depot, includes cct bulb

PPz · December 10, 2019, 6:33pm

In Canada, they improved with years. 10 years ago, find somebody helpful (and sometimes just find somebody only in the store) was very difficult. Now, at least, they say hello...

Rxich · December 10, 2019, 6:56pm

I'm dying to try, but my HA addiction has me at work, making money to buy more HA stuff.

I'll test later tonight. You guys think my boss would let me go home early if I told him I have some important buttons to press at home?

Navat604 · December 10, 2019, 7:09pm

Of course the boss will let you go. Get him/her addicted to HA as well so you won't even have to ask next time.

Rxich · December 10, 2019, 11:13pm

Here's some messages from the logs. Initially had driver set to Iris 1 button, pressed each remote button once, then changed driver to other button devices . Nothing ever registered in the device events, not parsing since no driver exists, but found this;

Past Logs

dev:39142019-12-10 05:58:27.657 pm debugparse: read attr - raw: 3CE60100010820002020, dni: 3CE6, endpoint: 01, cluster: 0001, size: 08, attrId: 0020, encoding: 20, command: 0A, value: 20

dev:39142019-12-10 05:53:57.206 pm warnconfigure...

dev:39142019-12-10 05:53:52.010 pm warnconfigure...

dev:39142019-12-10 05:53:48.573 pm infoskipped: cluster:0001, [raw:catchall: 0104 0001 01 01 0040 00 3CE6 00 00 0000 07 01 00, profileId:0104, clusterId:0001, clusterInt:1, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3CE6, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00]]

dev:39142019-12-10 05:53:48.571 pm debugparse: catchall: 0104 0001 01 01 0040 00 3CE6 00 00 0000 07 01 00

dev:39142019-12-10 05:53:36.964 pm infoAay remote battery is 100%

dev:39142019-12-10 05:53:36.960 pm debuggetBatteryResult: 32

dev:39142019-12-10 05:53:30.618 pm warnPresence timeout set to: 120 seconds

dev:39142019-12-10 05:53:30.593 pm warndescription logging is: true

dev:39142019-12-10 05:53:30.593 pm warndebug logging is: true

dev:39142019-12-10 05:53:30.592 pm infoupdated...

dev:39142019-12-10 05:53:21.507 pm debugrefresh

dev:39142019-12-10 05:53:21.456 pm warnconfigure...

dev:39142019-12-10 05:52:22.152 pm infoAay remote battery is 100%

dev:39142019-12-10 05:52:22.151 pm debuggetBatteryResult: 32

dev:39142019-12-10 05:52:22.151 pm debuggetBatteryResult

dev:39142019-12-10 05:52:22.150 pm debugparse: [raw:3CE60100010A20002020, dni:3CE6, endpoint:01, cluster:0001, size:0A, attrId:0020, encoding:20, command:01, value:20, clusterInt:1, attrInt:32]

dev:39142019-12-10 05:52:22.141 pm debugmissed: [raw:catchall: 0104 0001 01 01 0040 00 3CE6 00 00 0000 07 01 86000100, profileId:0104, clusterId:0001, clusterInt:1, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3CE6, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[86, 00, 01, 00]]

dev:39142019-12-10 05:52:22.139 pm debugparse: [raw:catchall: 0104 0001 01 01 0040 00 3CE6 00 00 0000 07 01 86000100, profileId:0104, clusterId:0001, clusterInt:1, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3CE6, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[86, 00, 01, 00]]

dev:39142019-12-10 05:52:09.040 pm debugrefresh

dev:39142019-12-10 05:52:09.008 pm warnconfigure...

dev:39142019-12-10 05:52:06.491 pm warndescription logging is: true

dev:39142019-12-10 05:52:06.491 pm warndebug logging is: true

dev:39142019-12-10 05:52:06.490 pm infoupdated...

dev:39142019-12-10 05:52:01.354 pm debugrefresh

dev:39142019-12-10 05:52:01.330 pm warnconfigure...

dev:39142019-12-10 05:51:51.661 pm debugrefresh

dev:39142019-12-10 05:51:51.630 pm warnconfigure...

dev:39142019-12-10 05:51:11.851 pm debugrefresh

dev:39142019-12-10 05:51:11.822 pm warnconfigure...

dev:39142019-12-10 05:50:35.824 pm debugrefresh

dev:39142019-12-10 05:50:35.792 pm warnconfigure...

dev:39142019-12-10 05:48:43.683 pm debugparse: [raw:catchall: 0104 0402 01 01 0040 00 3CE6 00 00 0000 01 01 , profileId:0104, clusterId:0402, clusterInt:1026, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3CE6, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[]]

dev:39142019-12-10 05:48:27.392 pm infoAay remote battery is 100%

dev:39142019-12-10 05:48:27.391 pm debuggetBatteryResult: 31

dev:39142019-12-10 05:48:27.386 pm debugparse: [raw:3CE60100010A2000201F, dni:3CE6, endpoint:01, cluster:0001, size:0A, attrId:0020, encoding:20, command:01, value:1F, clusterInt:1, attrInt:32]

dev:39142019-12-10 05:48:27.347 pm debugparse: [raw:catchall: 0104 0001 01 01 0040 00 3CE6 00 00 0000 07 01 00, profileId:0104, clusterId:0001, clusterInt:1, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3CE6, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00]]

dev:39142019-12-10 05:48:24.165 pm debugparse: [raw:catchall: 0000 8021 00 00 0040 00 3CE6 00 00 0000 00 00 3400, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:3CE6, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[34, 00]]

dev:39142019-12-10 05:48:24.121 pm debugparse: [raw:catchall: 0000 8021 00 00 0040 00 3CE6 00 00 0000 00 00 3200, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:3CE6, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[32, 00]]

dev:39142019-12-10 05:48:24.109 pm debugparse: [raw:catchall: 0000 8021 00 00 0040 00 3CE6 00 00 0000 00 00 3300, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:3CE6, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[33, 00]]

dev:39142019-12-10 05:48:14.533 pm warndescription logging is: true

dev:39142019-12-10 05:48:14.532 pm warndebug logging is: true

dev:39142019-12-10 05:48:14.531 pm infoupdated...

dev:39142019-12-10 05:48:03.546 pm warnconfigure...

oscopeaaron · December 10, 2019, 11:40pm

Bulbs pairs as a RGBW bulb, changed it to Zigbee Color Temperature bulb and it works fine.

The Homeless Despot was in great form. Went to one that said it had 35 waited 20 minutes for them to find it but they never found it. So went to another Homeless Despot and they were there.

flotsam1 · December 11, 2019, 12:11am

I also bought a kit.

The bulb works fine with the "Generic Zigbee CT Bulb (dev)" driver.

The remote does pair, but I could not get any response out of it - having tried most of the Zigbee button controllers.

Having said that, there is another remote that looks exactly like it - the Aurora AOne Smart Remote. That supposedly works with Smartthings UK (see post #156), and the Ecosmart remote is supposed to work with Smartthings here in US.

flotsam1 · December 11, 2019, 12:12am

Now if one of our Hubitat experts can find a ST driver for us that might work, would be helpful!

Rxich · December 11, 2019, 2:17am

Great detective work. I saw the same thing "works with ST" but zero evidence of a driver. It just paired as "thing" to my ST V2 hub.
And worse case, ST puts out a driver and I can use the remote with my ST hub using hubconnect to connect it to HE

mbafford · December 11, 2019, 2:38am

I've got 10 of these - when I bought them right after thanksgiving the 2-pack of bulbs without the remote wasn't available. So far the bulbs are working great. The bulbs are still cheaper by $1.00/each if you buy 2 (bulb+remote) packs, rather than the single 2-pack of bulbs only. sigh yay for e-waste.

I can easily pair the remote to ST, Home Assistant, and Hubitat. However, other than the initial paring (which is quite easy - just hold the reset button inside the battery cover until the LED flashes) and a single battery report message from the remote, I never see any other logs indicating the remote sends any messages at all.

Given I have so many of them, I'd love to be able to use them for something.

oscopeaaron · December 11, 2019, 3:33am

This would probably be the most likely driver to work on Smart things: SmartThingsPublic/zigbee-accessory-dimmer.groovy at 5fb1913fd4077a76a695f88f5c0f62f977fdb91b · SmartThingsCommunity/SmartThingsPublic · GitHub

Doesn't look like they are putting the hub in a group so if Home Depression didn't request something weird then there might be a chance. The two devices in the fingerprint are physically the same in the pictures I could see.

mbafford · December 11, 2019, 3:33am

Based on @flotsam1's response, the device looks like it might be covered by the handler here:

github.com

SmartThingsCommunity/SmartThingsPublic/blob/5fb1913fd4077a76a695f88f5c0f62f977fdb91b/devicetypes/smartthings/zigbee-accessory-dimmer.src/zigbee-accessory-dimmer.groovy

/**
 *  Copyright 2018 SmartThings
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 */

import physicalgraph.zigbee.zcl.DataType

metadata {
	definition (name: "ZigBee Accessory Dimmer", namespace: "smartthings", author: "SmartThings", ocfDeviceType: "x.com.st.d.remotecontroller") {
		capability "Actuator"
		capability "Switch"

This file has been truncated. show original

Similar model names (ZBT-CCTSwitch-D0001 vs. ZBT-DIMController-D0800), and similar fingerprints - but not quite the same.

Using that code as inspiration, I've managed to make a configure method which does some of the work in the above ST device handler, but it looks like SmartThings Zigbee support is much more fleshed out than Hubitat's, so I'm learning as I go and writing raw commands to send. I used this device handler for example Zigbee code.

This configure block gets the remote talking more - but still not sending button presses, just a block of messages in response after I try to configure it.

It's stopping time for me for tonight, so I'll have to revisit later - and if I can confirm the code I've hacked together is actually doing something useful I'll share it here.

flotsam1 · December 11, 2019, 4:02am

Cool! Thanks for looking into this!

flotsam1 · December 11, 2019, 4:43am

Yeah, that first one is what I see as well upon pairing: Model Number: ZBT-CCTSwitch-D0001

mbafford · December 11, 2019, 6:30pm

Just to update everyone - I spent entirely too much time trying to get this to work and I think I'm going to have to back away for now.

It will happily respond with bind success messages to binding requests for all of the clusters it claims to support. It'll send battery information. It'll send error messages if you fill up the binding table. It sends some other messages I can't figure out the meaning of. But I can't get it to send messages when I press a button.

Because it's sleepy (I think), it only responds to requests after you press a button to wake it up, which can be a little misleading if you're trying to debug - but after the queue of messages gets worked through, the remote stops reporting anything when you press a button - except for battery (if enough time has passed since the last report).

This is making me want to get a sniffing capable zigbee dongle just to see what the remote and bulb say to each other during initial pairing.

I'm also wondering if the fact it's a device that supports Touchlink is part of the problem. From what I can tell, Touchlink is poorly (not?) supported by Hubitat? Someone who understands Zigbee better than I do would have to chime in.

I'd share code, but ultimately all I did was execute binding requests - which is pretty standard stuff.

flotsam1 · December 11, 2019, 7:11pm

Understood.

I did some more digging via HD and found the manufacturer - Leedarson. I reached out to them this morning to find out if they have a ST Device Handler for the Remote, since they claim it works with ST. They will get back to me. I assume that if we get a ST driver, then Hubitat should be fairly "straight forward", but I could be very wrong . . .

https://www.leedarson.com/index.php/Product/detail/id/148

Rxich · December 11, 2019, 7:35pm

Thanks, I tried contacting the Aurora company that makes an identical device for their driver, since they advertised ST compatibility, they told to go pound salt(aka ask Samsung)

flotsam1 · December 11, 2019, 9:18pm

Leedarson also came back to me. They stated that - when decoupled - only the bulb will connect (and be usable) with ST, and that the remote will not work with ST. It would seem that we are dead in the water as far as the remote is concerned - until a suitable device handler shows up. Ah well, a $9 CT bulb is not too bad . . .

SmartHomePrimer · December 11, 2019, 9:51pm

It’s kind of sounding like this thing is touch link only, similar to the Lutron connected bulb remote. However, couple of things easy to try still. I’ve seen a lot of hail Mary’s here that actually turned results.

Try pairing the remote a second time to Hubitat. Don’t delete the device, just pair it again, and see if that gives you different results.
Try using this method for those of you that have a Hue bridge. I know, it’s not a Remote that’s talking to the hub, but it at least allows you to control a bulb with a Hue bridge (and Hubitat by way of the integration), and via the remote, without one or the other stealing the pairing.

I still have 6 Lutron connected bulb remotes “authorized” on my hue bridge that I use this way. It’s actually kind of nice. I can’t do the fancy stuff like I can do with the pico, but unlike a pico that won’t work if the hub has a problem, these always work. Keeps the WAF pretty high.

oscopeaaron · December 11, 2019, 10:27pm

I think you could touch link it on Hubitat. I touchlinked the remote to a Tradfri outlet. And it is still on Hubitat.

cpuken · December 12, 2019, 3:42am

Think I'll pick up one tomorrow... and know someone will figure out how to pair bulb and remote.