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

These are in sale again but now for 4.88

https://www.homedepot.com/p/EcoSmart-60-Watt-Equivalent-A19-SMART-LED-Light-Bulb-Tunable-White-Starter-Kit-1-Bulb-A9A19A60WESDZR1/310288335?irgwc=1&cm_mmc=afl-ir-10451-483420-&clickid=yhcW%3A92aCxyOU6xwUx0Mo3cmUknRjVSIixZF2w0

Be nice if the remotes work but even if not, hard to beat the bulb price

Must be only your local HD. Mine still says no stock and no option for delivery,.

I noticed a strange behavior. Once a bulb and remote is added to Hubitat and paired with each other, any additional remote added to hubitat will control the same bulb without having to pair directly to the bulb.

These remotes do exhibit very odd behvaior. They are definitely not strictly TouchLink remotes. They act very differently.

That's definitely the case that many of us have found with HE and the same thing is happening for those pairing it with ST. Until I got some Pico remotes for Xmas, I was happy just controlling one set of bulbs and the other 6 remotes went to the closet. Now there are 7 remotes in the closet. Fortunately, the bulbs are individually controllable from the HE hub regardless.

An ST engineer has written a Device Type Handler for these remotes and allows the remotes to work independently but it hasn't been released yet.

They are taking their sweet time releasing one, I can tell you that.

Come on, we just got thru Christmas and New Years. Give them a break. I know I haven't gotten much work done the past 2 weeks. :grin:

But he posted he had one ready like a month ago. Just hasn't released it yet. Looks like we might be close though...

A small update on bulbs - the response time using the zigbee CT generic driver in HE is less than optimal, I have paired all my bulbs to Hue and getting much better performance.

I used the generic rgbw driver and get instant response, in the basement with my HE on the first floor. I do have a good number of repeaters, including an xbee 3 nearby tho. Never had any slow response so far...

They get 2 :+1: up from me but these are 1st CT bulbs I have used. They work fast enough for wife so they work fast enough for me.

Engineer posted an update:

DTH has been finished for a little bit now, but as others have guessed it is going through a review/approval process. I’d guess early next week it should be available :wink:

When it is released there... how long to 'port to' Hubitat and how to install this new code/app?

Installing custom driver code is detailed in this article in Hubitat docs.

https://docs.hubitat.com/index.php?title=Drivers_Code

As far as "porting" it, someone would have to volunteer to port it over and then do the change over. There are many differences between Hubitat and SmartThings when you get down to that level of detail in the driver code, especially when it comes to Zigbee binding. It could be an hour or it could be days.

To clarify, there is no app. This is a driver.

1 Like

I don't believe it would do any good to port to HE. From what I have read in this thread, the remote uses group multicast/broadcast messaging and the HE does not support that. The only way to use in HE is if you have remotes paired to an ST hub (V2 or later) connected using HubConnect or similar.

I could very well be wrong because I don't know what "group multicast/broadcast messaging" is.

You aren't. This device isn't going to work with Hubitat. This has already been addressed earlier in this thread.

I thought you said that zigbee 3.0 devices will switch to unicast when connected to a coordinator that doesn't support multicast?

Never said nor implied this.

That is what you said. So, if that is not what that means, then can you please explain what you do mean? Because I don't understand it then.

The endpoint device isnt cable if determining if the hub is capable of accepting multicast group messaging or not.
What i have observed is that many touchlink devices when joined to a hub, and said hub binds to the devices output clusters that these devices will switch from multicast to unicast messaging.
The device it self doesn't ask the hub anything in regards to it's multicast support...

Well, the device doesn't ask..but in essence the hub is telling the device what it wants by binding to specific clusters? In the end though, the device switches from Multicast to Unicast, right? So, why would multicast be the problem here? Has it been determined that this remote does not do that?

1 Like