GLEDOPTO GL-C-002P not acting as Zigbee router

Hi all,

I'm running a Hubitat C-7 (latest platform and Zigbee firmware) and testing a GLEDOPTO GL-C-002P (5-in-1 Mini Ultra Thin LED Controller).

The controller works perfectly as a CCT controller (on/off, dimming and smooth 2000K–6500K colour temperature transitions), but it doesn't seem to function as a Zigbee router.

An IKEA TRÅDFRI LED Driver installed beside it quickly became the parent for many of my battery-powered devices, while the GLEDOPTO never gains any child devices. Get Child Data always returns:

[Unknown, unknown 0, type:null]

The neighbour table shows a good link to the hub, so it doesn't appear to be a signal issue.

Has anyone successfully used the GL-C-002P as a Zigbee router on Hubitat, or is this expected behaviour?

One other oddity: the controller label says GL-C-002P, but Hubitat identifies it as GL-C-008P.

Thanks!

I have had one of these devices for years and it always gets a query for items it is routing but it never has any elements; works fine otherwise.

Little devil is always pink and lonely.

Thanks, that's really interesting. Mine behaves almost identically. It works perfectly as a CCT controller, but Get Child Data is always empty and it never appears to become the parent for any battery devices. Sounds like this may just be how the GLEDOPTO firmware behaves.

really interesting! I hadn’t even looked at the connections on that previously -

My kitchen counter uses this model, and as you can see the 6 nearest endpoints, some 3’ away, none more than 10’… not one of them is connected! And yet that sucker is heavily connected in my mesh to other routers. It’s as if it only connects TO routers.

My theory broke however - I also have the exact unit in the bedroom as an under Bed strip.

It’s nicely centered to the room and should see and hear lots of endpoints.

But one device IS connected to it … so - is it possible it’s the order a device gets connected to the mesh? I rebuild my Mesh occasionally - the old ‘Turn off your HE for 20 minutes and cause the ‘panic’ but I don’t think that causes endpoints to redetermine a parent. It sure is odd!

Then to make matters worse - Gemini says it’s not a router! I thought maybe it was 2.0 router but supposedly it doesn’t do any routing. Yet my discovery shows it in blue, which according the the zigbee map legend IS a router. so wierd! Then another search on is it a router says other user report it is a router… wow. this is a deep hole! I’ve got a Kasa 3.0 in wall switch 3’ away from either unit - I’m just relying on that!

There is nothing to say a device must be a router, even if it is capable. If other devices are better routers, or if this is a weak router, other devices might not like this device and therefore ignore it.

That said, it is weird that it isn't routing. Maybe this device has some firmware bug?