Gledopto GL-S-014P MR16 Bulb Issues

🛎️ Get Help Devices
,
1

I recently bought several of the Gledopto MR16 Zigbee bulbs. for my landscape lights but I'm having issues with them working correctly. I am able to pair them and initially I can turn them on and off but after a couple minutes they stop responding. I've tried two with the same results and one of them I factory reset (and removed as a device in Hubitat), reconnected and still same results.

It's defaulting to the Advanced Zigbee RGBW Driver which I believe is the one I want to use. Two things I noticed during my investigation. I think that Hubitat automatically triggers the configure command once it's established and it seems like maybe this is part of the problem? Once the configure command is done seems to be when it stops responding. As far as I can tell I have no way to supress that from happening to test and validate that is part of the problem. The second thing I noticed is for the bulb I connected, reset and then reconnected the second time it connected I got a log item noting that the device id had changed which is not something I've seen before for zigbee devices.

So at this point I'm kind of at a loss for what to do next. Any help would be appreciated.

2

Have you tried Generic RGBW Bulb instead? Run a "Configure" after changing drivers. That command does run on pairing, if that is what you're also asking, but it's supposed to help, not cause problems. Not all bulbs work with the "Advanced" drivers; maybe this is one.

Since these are outdoor lights and it sounds like they might be far away from the hub, I'd also see if you're dealing with a range/mesh issue and if bringing them closer to the hub changes anything.

3

I did try switching to the generic RGBW and running configure and it unfortunately did not do anything.

I have multiple zigbee switches about 10 to 15 feet away from the bulbs, but I've also added a MHCOZY zigbee relay to the transformer (different run than what these bulbs are on) that is just a few feet away. That relay is working just fine and is mains powered so should also be able to act as a repeater if needed.

Getting an MR16 socket setup near the hub is going to take some work. It doesn't feel like distance is the issue here but I'll work to figure out how I can rule that out.

4

So I did some more testing. Kept the device in Hubitat and reset the bulb to pair it again with the existing device. I did this to see if the configure command still runs on a re-paired device (it does) and to try a re-pair to hubitat with the Generic Zigbee RGBW Light driver set instead of the default Advanced driver.

Still had the same problems, it stops responding after a few minutes but I noticed something else odd. The configure command is running 3 times. For the second and third time the device address changes. I myself am not hitting the configure command. Only thing I am doing to check responses is turning the bulb on and off. This happens with either of the zigbee rgbw drivers.

The bulb stops responding after the third configure command runs.

image
image1680×1688 248 KB

5

This is very strange, configure is only called either manually via the driver UI, or when the device initially joins the zigbee network.
Can you click the update firmware button in the driver and post the live log results?
I uploaded a firmware image for a Gledopto device recently, but not sure of the exact device it was for, the live logs will indicate which firmware version this device is using...

1 Like
6

Update Firmware seems to do nothing. Nothing showed up in the logs when I clicked it. I've got it set to the Advanced Zigbee RGBW Bulb driver if that matters. And I have debug enabled.

This is the device details

image
image1182×378 23 KB

7

Is the device even working?
At the very least you should something similar to this:

image
image2132×1038 190 KB

8

I think that is the point or trouble I am having. It pairs and works for a few minutes (I know because I can turn it off and on from the hub after it first pairs) but then seems to stop responding altogether after a few minutes. I tried this with multiple bulbs and got the same results.

I also tried powering down the bulb for a while and plugging it back in and that seems to do nothing either.

9

Are all of your other Zigbee devices working without issue?

10

Yup. I've got 96 Inovelli VZM31-SN Blue Series Switches, 166 Sengled bulbs, 20 blinds and a couple dozen other Zigbee devices all connected and working just fine.

1 Like
11

Do you have a link to this device for purchase?, perhaps I can fetch one and see what's up with it...

12

I got mine from Aliexpress but you can also get them off Amazon

13

So I did some experimenting and I do seem to have found a way to get them paired and working correctly but it's an odd process.

I installed the RGBW CT Bulbs - Zigbee to try a driver other than the built in drivers and see if I got the same result. Keeping the existing device and reseting/re-pairing the device I think it was having the same/similar problem. I'd get the following multiple time in the log files with that driver in place.

Landscape bulb test : MAP: [raw:catchall: 0000 0013 00 00 0040 00 17CB 00 00 0000 00 00 00CB17A5D7D3BC1238C1A48E, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:17CB, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, CB, 17, A5, D7, D3, BC, 12, 38, C1, A4, 8E]]
Landscape bulb test : 0013 Multistate event (Rejoining) data:[00, CB, 17, A5, D7, D3, BC, 12, 38, C1, A4, 8E]

I'm beginning to think that maybe the configure/rejoining is being initiated by the bulb, not the hub. I also realized that the bulb instructions say the bulb should go green once it's done and mine was not.

I removed the device, reset it and paired it again. First, I noticed that Hubitat is defaulting to the custom driver instead of the default built in. Second I didn't get multiple configs and the bulb went green. I found now that the bulb continued to respond, I could change the driver to the default advanced driver, run the configure command the bulb works as expected.

I did this same thing with the other bulb I was testing and got the same thing. I now had both my test bulbs connected and working.

I paired a third bulb and at first had the same problem but when I removed it and reset it and re-paired it was able to finish configuring itself (lit green) and it stayed linked.

I have a total of 12 bulbs to pair so I'll see how the others go.

14

Yes, as mentioned previously...

user drivers always take precedence over inbuilt, this can be changed by deleting the user driver or simply commenting out the fingerprint.

Once my sample comes in I'll test and add the fingerprint to the appropriate driver, likely the advanced one assuming the device works as expected.

1 Like
15

So after pairing several more bulbs I think I pinpointed what the problem was. I don't think the driver had anything to do with it.

What was happening was the bulb was not finishing its own pairing but the hub was no longer in pairing mode. Either because it found the device and stopped (first time) or it timed out.

If I keep putting Hubitat into pairing mode it eventually finishes and goes green. There have been a few where I had to factory reset and start the pairing again but they do eventually connect.