Hi Mariano! This bulb had been working properly in the Light Multifunction Mc (Old) driver and I am able to control the color. However, when I switched it to the Light Multifunction Mc driver, I am no longer able to set the color (there is a spinner every time I change color/temp and it times out with a network error)
I have a similar bulb, the GL-B-007P which is working fine in the latest Light Multifunction Mc driver.
Thanks again in advance, keep up the great work!
βglen
It should work fine with this driver as well.
Did you try to change the driver (OLD) again to see if it works and return to the Mc?
The driver takes longer to install and configure the device than it appears in the app.
Do not handle the device in app until installation and setup is complete, up to 1 minute.
I have observed the process in the CLI many times and it is appreciated that the beginning of the driver change process is accelerated, if once the driver is changed in the app, the device is closed in the app and reopened, but without handle until after about 30 sec.
It has happened to me that, sometimes this error has been solved by uninstalling the device and reinstalling it
The system chose the βOLDβ driver over the latest one. Problem is, when I go to your Channel, I donβt even see βLight Multifunction Mc-(OLD)β listed in order to disable that βoldβ driver.
I see 7 βoldβ drivers on the page, none of which are currently enabled. The only driver I have enabled is Light Multifunction Mc. Somewhere (OLD) must be enabled, but itβs not showing on Available Drivers for this channel.
Still having an issue. As an aside, one thing that seemed unusual just to let you know, in the Drivers under my hub there were 2 versions of the old driver "Light Multifunction Mc-(OLD)β listed, with different version dates: 2022-01-20T17:17:23.115816 and 2021-12-26T11:19:54.175823
I deleted them both, but the problem where I canβt set the color/white temperature still is happening after deleting and re-adding the device. I get βA network or server error occurred. Try again laterβ message after about 15 seconds timeout.
I have 2 Zigbee devices using the Light Multifunction Mc that this is happening on, and 1 that is working properly. All 3 worked fine on the βOLDβ driver.
Note that I can set the bulb to Continuous Color Change, Random β and the driver is able to change the bulb color. Itβs just that none of the controls in the UI work to change the color. They all just timeout.
βββββββββββββββ¬βββββββββββββββββββββββββββββββββββββββ
β Name β Zigbee Light Multifunction Test β
β Version β 2022-03-03T21:00:58.380071 β
βββββββββββββββ΄βββββββββββββββββββββββββββββββββββββββ
OK .. so after rebooting⦠the driver started working.
I started playing a little more between the published driver and the test driver. It seems that the bulb needs to be toggled between ON/OFF/ON or OFF/ON/OFF when you change the driver or else something is getting confused in the app UI and the color change doesnβt work. If you do this toggle, it works.
I now have both GL-B-007P and GL-C-007P working on the latest published driver!
It seems like the (published) driver is keeping some memory of the last light level when you enter the driver. When changing the color after changing the Dimmer level, the bulb reverts to the prior level. Turning the bulb OFF/ON after setting the level seems to cause the driver to recognize the new level, and maintain that when changing color/temperature.
This is happening with all 3 bulbs, and only using the app β if I change it with Alexa, all is well.