Gl-c-007 Reset

[Chloe Sarnoff]

Ihave 5 of these connected to my LED cabinet lights and they were working well with SmartThings. In my conversion to Hubitat, I reset 1 of them using the "off/on and then 4 more times" sequence. I received the 4 blinks to indicate it was reset. I started pairing with Hubitat and it was found, but within 3 seconds, the light turned off . After finishing entering device name and room, Hubitat shows it as on but it doesn't change the controller. I thought it might be just one, so I did it again with a second one with the same deadly outcome.

Hubitat picked the "Advanced Zigbee RGBW Bulb" for the driver. The contorller shows as a Zigbee device in the devices list. My strip is also white but when it was working with SmartThings, we change the temperature of the strip throughout the day (Daylight -> Warm) and from 80% to 25% after dinner.

I am having a similar issue with the Gledopto controllers. I have 2 of them and neither of them will pair easily. I finally got one to pair with the hubitat but then it wouldn't respond at all. Frustrating, but sounds like I will need to get new controllers (also not Gledopto) any recommendations?

Completely at my wits end! Ray in support was responsive right up until the point I sent him detailed videos. Then all communications ended. I can only assume that their product is faulty and he can see it based on my videos. Therefore he has stopped responding because he would need to say "yup - it is a default in the device, but you will need to buy replacements" and he is afraid to say it. Will I buy replacement GLEDOPTOs? I will give him to the end of the week, but then it is time to spend $$$ on somebody else's products.

Not really. There are several threads, e.g. this one, and also in different languages. Problems may occur with one user, but not with others. Some problems are also only in combination with some apps, mostly apps for Zigbee devices. The main reason for the v5.x firmware is the rewrite of Zigbee.

I have a weird issue with the Gledopto GL-C-009P

I have an Homey Pro (Early 2023) and I am able to add the device or with the official app or with the community version. I had one app installed at the time. But in both cases the device is uncontrollable, it does not respond to on/off or dim. I am however able to interview or ping the device from developers section.

Now the weird part. When I have no Gledopto app installed, the device is added as unknown/generic zigbee device and the controller works fine, I am able to use on/off and dim the led strips (single color 2700K) attached to the controller.

I made a Gledopto support ticket to be sure, although it works fine without the app.

Is your experience that the Gledopto app needs to be uninstalled? I have couple of Gledopto zigbee controllers without the reset button that work fine.

I have a problem with the GL-C-008P (RGB + CCT) with a reset button. I had it added to Homey and I could control the led strip without any issues when I tested it around 2 weeks ago. Recently I noticed that I cannot control the device anymore. I tried the repair process but after showing the device is being added message, it goes back to the screen that tells me to reset the device. I tried removing the device, resetting it and adding it again but that does not work either. I get a message saying that it failed or it goes back to the same screen telling me to reset the device. I have the same issue when using the Gledopto app and when adding the device as a generic zigbee device.

I also have a problem with the GL-C-006P controller with the reset button. I managed to added it to Homey couple of times but I never managed to control it. It always times out.

I am using Homey pro 2023.

When I try to repair the connection, the device leaves the network due to a reset and often I cannot add it anymore. I then try a couple of times, power cycle it, reset it and then in the end I manage to add it to Homey. Then couple of days later the same thing happens.

I have an issue with my GL-C-002P 5in1 mini controller. It is possible to add it. But as soon as it has been added all the commands just give me a timed out message.

I have tried to add it as another RGB+CCT device in the list of available devices with the same issue.

It always shows up as a GL-C-008P when I have a look in the advanced settings.

A: Please check the above Q&A, confirm the wiring is ok, power supply, controller+light or bulb works normally. Then you can close the app ,open it and research within 60s when you switch on the power, or you try switching on/off the light during app searching , once linked, the light or bulb will get darker( earlier version) or get green. If still not found, you can reset the light.

A: You can close the app, open it and research within 60s when you switch on the power, or you try switching on/off the light during app searching , once linked, the light or bulb will get darker( earlier version) or get green.

@Peter_Kawa I will give it a try tonight - currently that LED controller is not powered on. I tested it remotely with another controller, GL-C-008P and got a bit strange results. I can see in the developer tools that it is not online and I get a timeout message when interviewing but at the same time I can still turn the LEDs on and off. How can this be? I connected this controller for the first time yesterday and I have to say that it is misbehaving a bit. When I was changing the brightness or color temperature very quickly, I was sometimes getting a timeout error message - this never happened with any of my other zigbee devices. I would suspect some range issues but I have another zigbee controller just next to it and that one is working perfectly fine.

I also tested it with 2 of my other GL-C-006P controllers, those show up as online and I can interview them.

@hankdroid do you have a GL-C-009P with the reset button or without it? The issues I am having are only with the controllers I purchased a bit more recently and both of them have the reset buttons. Maybe there are some small differences and they are not fully supported yet?

Do you know what the issues with interviewing could be related to? Why could one device almost always fail to be interviewed due to time out but controlling it would work while the other one can be interviewed but cannot be controller? Just incompatibility issues and the developer needs to update the app or could it be something else?

You can switch between the modes using the Opt button on the device. After switching modes Zigbee2MQTT will automatically detect the new mode. Note that during the pairing process the log message identified as: Gledopto Zigbee LED Controller XXX might state model that differs from currently selected one. You should wait for the log message Detected Gledopto device mode change that should follow shortly afterwards meaning that Zigbee2MQTT has recognized the currently selected mode.

New log file whereby I delete the thing, do a factory reset on the device, switch to RBG mode, then Scan for new items, and add it again and wait for a minute. Same result, discovery incomplete.

ZigBee.log (175.7 KB)

You were right @chris. Issue found and solved: Poor reception (4 meters away, blocked by furniture; repeater functionality questionable).

Moved the device closer to ZigBee controller and now discovery and LED control works fine.

"TI recommends connecting Signal Detect pin from the Optical Transceiver to the LED_1

pin and enable it using SD_EN bootstrap pin in 100BASE-FX mode. The LED_1 pin is not

used in design and that, if the electrical link between the fiber module and the DP83822 is

broken, disconnected or otherwise disrupted, the link will recover only by initiating a soft

reset through MDIO/MDC interface."

Also, probably important is that access to strapping pins on the PHY is difficult do to the PCB layout so as much as possible I have tried to change PHY behavior using PHY register values rather than strapping options.

hey. i got Mercedes c300 and get codes B007F13, B007E13. i changed front seatbelts (used from ebay) and nothing changed. i m not sure if this is seatbelt fault or i need reset a module. a maybe rebuild a seats belts?

For just a seatbelt code a reset would not be needed. Either you have a faulty seatbelt, damaged wiring or a faulty module. Your seatbelts should have between 2-3 ohms of resistance at the squibs. If they are not there ship the seatbelts to us for repair. If they are within range, then you have one of the other issues.

1.8 ohms is a little low but 0.001 very bad. We can repair those for you. You can call CS and they will help you with getting it set up or you can visit the website MyAirbag.com an set it up yourself.

The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

The Open Procedure for service "ESENT" in DLL "C:\WINDOWS\system32\esentprf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

The Open Procedure for service "Lsa" in DLL "C:\Windows\System32\Secur32.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

The Open Procedure for service "MSDTC" in DLL "C:\WINDOWS\system32\msdtcuiu.DLL" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

The Open Procedure for service "WmiApRpl" in DLL "C:\WINDOWS\system32\wbem\wmiaprpl.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

I'm having the same problem, I've reset Win10, I've reinstalled PS cc 2017 twice in the last week, checked the framework is updated, have tried a direct install and a cc install. My firewalls are set to allow. I've been trying EVERY suggestion that's been made.

3a8082e126