Zigbee LED inline dimmer

Hi Guys,

Here we go, a new user here ( please be gentle ) :slight_smile:

I've installed an inline zigbee 3.0 dimmer switch:
https://www.amazon.co.uk/gp/product/B09F6Y7KKQ/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1

I've used the generic zigbee dimmer driver, but have a few issues:

  1. How do I actually control the light? All I have at the moment is this:

  2. When pressing the on /off switch from the above screenshot the light takes approx 2s to respond - is tis normal? With it being zigbee, I expected almost instant response?

  3. How can I dim the lights for example? ( they are dimmable )

  4. Should I be using a different driver?

Thank you all :slight_smile:

What I forgot to mention that the LED strip I am using is single colour ( warm white ).

I thought I'd give you a bit of an idea what I am trying to achieve...

  1. Lights to be always on between 17.00 - 01.00
  2. During this time at would like them to be on at "X"%, and only increase to "XX"% when motion detector ( in the same room ) detects, well... motion :slight_smile:
  3. I'd like the light to stay at the increased brightness for "X" minutes after there is no motion and return to the original brightness level

I have a sonoff motion detector which seems to be working well and will be used for this purpose.

I know this is soooo simple, but it is also my very first time with Hubitat and feel I needs some gentle guidance please!

Hi,

This MiBoxer FUT036Z is actually a Tuya device, that is trying at the same time to emulate some Philips Hue dimmers commands.... with rather questionable success. So you may expect any kind of oddities.

You can search this forum for TS0501B , several HE users say it works much better in HE with the inbuilt “Advanced Zigbee Bulb driver”.

1 Like

Follow @kkossev 's advice...

For the control. You can control via rules(automation) or if you create a dashboard and add the light switch to the dash board...

Hi all,
Thanks for the input!

So I've (kind of) managed to get it to work with a Generic Zigbee Bulb driver.

I've also had a go at the automations and based on the idea I described above, I created the following 2 simple rules:

  1. Lights on at 17.00 @ 25% brightness and turn off at 01.00:

  2. Increase brightness to 50% when motion is detected and turn off after 3 minutes:

Rule 1 doesn't turn the light on at all, but rule 2 works perfectly.
If I delete / pause rule 1, the rule 2 stops working too.

I've think the problem is that the "motion off after 3 minutes" is forcing the rule 1 to turn off, but have no idea how to fix it?

EDIT:
The Advanced Bulb Driver didn't work for me - to the point where it wouldn't the light on at all.

Thanks for any help!

1 Like

Hello,
Know this has been inactive for a bit but just setup the same Miboxer FUT035Z Dual White CCT Zigbee LED Dimmer 24V and thought would share my experience so far. Do you happen to be using Philips Hue? I've had very good success so far with this integration:

  • Miboxer FUT035Z joined to Philips Hue as a Color Temperature Light
  • Joined the Philips Hue Color Temperature Light to Hubitat using CoCoHue
  • Set the light device driver as CoCoHue CT Bulb
    • I've been using CoCoHue for a long time with quite a few lights so can't speak to the Hubitat Philips Hue App but when I was using previously it worked great. I only changed due to the extra ability CoCoHue gave at the time and have not wanted to go through reintegration of 29 lights and updating all the rules. It has also been a great app thus far.
  • Bulb Device joined to Amaon Echo Skill
  • Hubitat Button Controller App used with Aeotec Wallmote & Phillips Hue Dimmer joined directly to Hubitat
  • Hubitat Rules Machine for motion lighting rules with a Fibaro multisensor, Aeotec multi sensor 6, and Philips Hue motion sensor joined directly to Hubitat
  • Hubitat Dashboard

So far the setup has worked great for my purposes as under cabinet lighting. The lights are turned on via Alexa, the button controllers, and motion rules. The CocoHue driver allows for several presets including Transition Time and "Start level change" rate which may resolve the response delay you are having.

The one thing I noticed is you are using a Dual White Controller with a single color LED Strip. Don't know if that would be causing you any issue. The MiBoxer FUT036Z Zigbee Dimmer looks to be made for single colour strip control.
Miboxer FUT036Z: MiBoxer FUT036Z Zigbee Dimmer 12V

Controller: Miboxer FUT035Z Dual White CCT Zigbee LED Dimmer 24V
LED Strip (JOYLIT 24V UL Tunable LED Strip Lights 2800-6500K White Adjustable 16.4ft 610lm/ft Ultra Bright CRI 90+ IP67 Waterproof, Premium SMD 2835 1120LEDs High Density Warm to Daylight CCT Dimmable Tape Light): https://www.amazon.com/gp/product/B092S2HG4Q/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&th=1
Power Supply (JOYLIT DC 24V 5A 120W Power Supply Adapter, AC 110V / 220V to DC 24V 5amp): https://www.amazon.com/gp/product/B07Q57B6D1/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&th=1

2 Likes

Hi, I’m hoping that reviving this thread for Zigbee In-line Dimmers, in the off chance that a tweak can be made to an existing driver.
I’ve tried to find a single colour dimmer driver for what is called a ‘Zigbee 3.0 Dimmer’
Using one of @kkossev drivers I get ……….

dev:40772024-10-27 01:12:49.103 PMinfoscheduling health check every 10 minutes

dev:40772024-10-27 01:12:49.100 PMinfoInitializeVars( fullInit = false )...

dev:40772024-10-27 01:12:49.091 PMerrorgroovy.lang.GroovyRuntimeException: Ambiguous method overloading for method com.hubitat.app.DeviceWrapper#updateSetting. Cannot resolve which method to invoke for [class java.lang.String, null] due to overlapping prototypes between: [class java.lang.String, interface java.util.List] [class java.lang.String, interface java.util.Map] on line 743 (method initialize)

dev:40772024-10-27 01:12:49.046 PMinfoscheduling health check every 10 minutes

dev:40772024-10-27 01:12:48.962 PMinfoInitializeVars( fullInit = true )...

dev:40772024-10-27 01:12:48.944 PMdebugdeleting lightType

dev:40772024-10-27 01:12:48.941 PMdebugdeleting level

dev:40772024-10-27 01:12:48.937 PMdebugdeleting checkInterval

dev:40772024-10-27 01:12:48.934 PMdebugdeleting ledMode

dev:40772024-10-27 01:12:48.929 PMdebugdeleting switch

dev:40772024-10-27 01:12:48.926 PMdebugdeleting rtt

dev:40772024-10-27 01:12:48.923 PMdebugdeleting powerOnMode

dev:40772024-10-27 01:12:48.919 PMdebugdeleting healthStatus

dev:40772024-10-27 01:12:48.905 PMdebugdeleting switch

dev:40772024-10-27 01:12:48.898 PMdebugdeleting maxLevel

dev:40772024-10-27 01:12:48.895 PMdebugdeleting minLevel

dev:40772024-10-27 01:12:48.893 PMdebugdeleting traceEnable

dev:40772024-10-27 01:12:48.890 PMdebugdeleting txtEnable

dev:40772024-10-27 01:12:48.887 PMdebugdeleting logEnable

dev:40772024-10-27 01:12:48.884 PMdebugdeleting powerRestore

dev:40772024-10-27 01:12:48.882 PMdebugdeleting minimumLevel

dev:40772024-10-27 01:12:48.879 PMdebugdeleting offTransitionTime

dev:40772024-10-27 01:12:48.875 PMdebugdeleting onTransitionTime

dev:40772024-10-27 01:12:48.872 PMdebugdeleting startLevelChangeRate

dev:40772024-10-27 01:12:48.869 PMdebugdeleting transitionTime

dev:40772024-10-27 01:12:48.866 PMdebugdeleting healthCheckInterval

dev:40772024-10-27 01:12:48.864 PMdebugdeleting enableReporting

dev:40772024-10-27 01:12:48.861 PMdebugdeleting groupbinding3

dev:40772024-10-27 01:12:48.858 PMdebugdeleting groupbinding2

dev:40772024-10-27 01:12:48.855 PMdebugdeleting groupbinding1

dev:40772024-10-27 01:12:48.853 PMdebugdeleting doNotDisturb

dev:40772024-10-27 01:12:48.850 PMdebugdeleting flashEffect

dev:40772024-10-27 01:12:48.847 PMdebugdeleting offCommandMode

dev:40772024-10-27 01:12:48.844 PMdebugdeleting levelChangeRate

dev:40772024-10-27 01:12:48.841 PMdebugdeleting colorTransitionTime

dev:40772024-10-27 01:12:48.838 PMdebugdeleting levelDownTransition

dev:40772024-10-27 01:12:48.834 PMdebugdeleting levelUpTransition

dev:40772024-10-27 01:12:48.832 PMinfoinitialize() ... model=TS0501B manufacturer=_TZ3210_4zinq6io destinationEP=UNKNOWN deviceProfile=UNKNOWN

dev:40772024-10-27 01:12:36.449 PMerrorgroovy.lang.GroovyRuntimeException: Ambiguous method overloading for method com.hubitat.app.DeviceWrapper#updateSetting. Cannot resolve which method to invoke for [class java.lang.String, null] due to overlapping prototypes between: [class java.lang.String, interface java.util.List] [class java.lang.String, interface java.util.Map] on line 741 (method configure)

dev:40772024-10-27 01:12:36.383 PMinfoscheduling health check every 10 minutes

dev:40772024-10-27 01:12:36.330 PMinfoscheduling health check every 10 minutes

dev:40772024-10-27 01:12:36.305 PMinfoInitializeVars( fullInit = false )...

dev:40772024-10-27 01:11:58.707 PMinfofingerprint profileId:"0104", endpointId:"01", inClusters:"0003,0004,0005,0006,1000,0008,0300,EF00,0000", outClusters:"0019,000A", model:"TS0501B", manufacturer:"_TZ3210_4zinq6io", controllerType: "ZGB"

dev:40772024-10-27 01:11:58.663 PMtraceZCL version:03

dev:40772024-10-27 01:11:58.660 PMtraceSoftware Build Id:unknown

dev:40772024-10-27 01:11:58.658 PMtraceModel:TS0501B

dev:40772024-10-27 01:11:58.657 PMtraceManufacturer:_TZ3210_4zinq6io

dev:40772024-10-27 01:11:58.589 PMdebuggetting info for unknown Zigbee device

Guessing, I’d say that perhaps some sort of “profile” needs to be added to the driver code, but I’m already out of my depth :stuck_out_tongue_winking_eye:

Tuya TS0501B _TZ3210_4zinq6io is a LED controller, I suppose the logs above are from using this driver?

Yes. That's correct.

Please check whether you are using the latest driver version 1.1.1. I must first fix the bug that throws the exception error in the logs. However, the line number logged does not make sense, maybe you were using and older driver version?

Krassimir, many thanks for replying.
I took a break from testing many driver files and having come back to it after some sleep etc, I am now thinking that the actual hardware is not working.
I started from scratch and removed the inline dimmer from Hubitat and re-discovered it.
I loaded your driver v1.1.1 and retested, with the result being the same non-operational result. However, also without the error in the logs.
Log output, after pressing 'Configure' is ...

Pressing ON, OFF, Toggle etc show as Log entries but no change at the Dimmer.
Dimmer is always ON (100% I think)

EDIT:
I've also paired the dimmer to a Hue Hub and get the same results. The device is detected and configured but nothing happens at the LED side.
I've contacted the seller to see about getting a refund or replacement.

1 Like

Update:
I received a new Dimmer (this one looks incredibly similar BUT came with instructions) and it paired and is operational, as expected.
re-tried the original dimmer and it's still a No Go.

FYI: This new Dimmer also works with Hubitat's "Advanced Zigbee Bulb" driver.

2 Likes