Gledopto GL-C-008-1ID will not switch OFF

Hi guys,

I’ve got (now) 2 Gledopto GL-C-008’s which will not switch off. They stay dimmed. No clue why. I’ve reset them, no luck. I’ve used other PSU doesn’t resolve issue. I’ve just connected to other piece of LED-strip, no luck. I’ve moved both controllers in close proximity from Z2M coordinator, no luck. In MQTT Explorer and Home Assistant a see proper payload passing by. Z2M-logs ;

info  2020-07-12 18:14:45: MQTT publish: topic 'zigbee2mqtt/light_cove_bedroom', payload '{"state":"ON","brightness":254,"color":{"x":0.177,"y":0.655},"color_temp":148}'
debug 2020-07-12 18:14:47: Received MQTT message on 'zigbee2mqtt/light_cove_bedroom/set' with data '{"state": "ON", "color": {"x": 0.52, "y": 0.224}}'
debug 2020-07-12 18:14:47: Skipping state because of Home Assistant
debug 2020-07-12 18:14:47: Publishing 'set' 'color' to 'light_cove_bedroom'
info  2020-07-12 18:14:47: MQTT publish: topic 'zigbee2mqtt/light_cove_bedroom', payload '{"state":"ON","brightness":254,"color":{"x":0.52,"y":0.224},"color_temp":112}'
debug 2020-07-12 18:14:50: Received MQTT message on 'zigbee2mqtt/light_cove_bedroom/set' with data '{"state": "ON", "color": {"x": 0.545, "y": 0.234}}'
debug 2020-07-12 18:14:50: Skipping state because of Home Assistant
debug 2020-07-12 18:14:50: Publishing 'set' 'color' to 'light_cove_bedroom'
info  2020-07-12 18:14:50: MQTT publish: topic 'zigbee2mqtt/light_cove_bedroom', payload '{"state":"ON","brightness":254,"color":{"x":0.545,"y":0.234},"color_temp":44}'
debug 2020-07-12 18:14:50: Received MQTT message on 'zigbee2mqtt/light_cove_bedroom/set' with data '{"state": "ON", "color": {"x": 0.592, "y": 0.25}}'
debug 2020-07-12 18:14:50: Skipping state because of Home Assistant
debug 2020-07-12 18:14:50: Publishing 'set' 'color' to 'light_cove_bedroom'
info  2020-07-12 18:14:50: MQTT publish: topic 'zigbee2mqtt/light_cove_bedroom', payload '{"state":"ON","brightness":254,"color":{"x":0.592,"y":0.25},"color_temp":37}'
debug 2020-07-12 18:14:53: Received MQTT message on 'zigbee2mqtt/light_cove_bedroom/set' with data '{"state": "ON", "color": {"x": 0.484, "y": 0.481}}'
debug 2020-07-12 18:14:53: Skipping state because of Home Assistant
debug 2020-07-12 18:14:53: Publishing 'set' 'color' to 'light_cove_bedroom'
info  2020-07-12 18:14:54: MQTT publish: topic 'zigbee2mqtt/light_cove_bedroom', payload '{"state":"ON","brightness":254,"color":{"x":0.484,"y":0.481},"color_temp":41667}'
debug 2020-07-12 18:14:56: Received MQTT message on 'zigbee2mqtt/light_cove_bedroom/set' with data '{"state": "ON", "color": {"x": 0.19, "y": 0.64}}'
debug 2020-07-12 18:14:56: Skipping state because of Home Assistant
debug 2020-07-12 18:14:56: Publishing 'set' 'color' to 'light_cove_bedroom'
info  2020-07-12 18:14:56: MQTT publish: topic 'zigbee2mqtt/light_cove_bedroom', payload '{"state":"ON","brightness":254,"color":{"x":0.19,"y":0.64},"color_temp":156}'
debug 2020-07-12 18:14:58: Received MQTT message on 'zigbee2mqtt/light_cove_bedroom/set' with data '{"state": "OFF"}'
debug 2020-07-12 18:14:58: Publishing 'set' 'state' to 'light_cove_bedroom'

They will not switch off. What can cause this problem? I’ve got 41 devices hooked up to CC2530+2591 with Firmware DEFAULT_20190608 running Z2M v1.14.1.

EDIT; because I used default Firmware and already have 41 Zigbee-devices hooked up I’ve moved to the Source Routing Firmware. The link-quality of various devices improved tremendously. Some from low 30’s to 111. But still suffering the same switch off issue though.

Just for the record, I had the same Problem with the Gledopto on deconz. Not tried it with zigbee2mqtt yet.

I’m starting hate the guts these Gledopto pieces of sh4t. Today connected a Gledopto driver on kitchen which had the same problems (other LED driver though). Controller hasn’t been in network for months.

Initially it worked today controlling that thing straight within Home Assistant. So that looked good, let’s add it into flow in Node-RED. The piece of @@#! didn’t want to switch off! One Gledopto driver in same flow works without problem the other don’t. Both are Zigbee LED controller RGB + CCT (1 ID) (GL-C-008-1ID) running on Zigbee2mqtt 1.14.1

When I remove transition: 2 in devices.yaml on device, it will switch off in flow (after calling manual light-services). Then I thought let’s bypass HA. I converted service call into JSON -payload for MQTT-topic with transition-atteribute set in Z2M yaml-file. In a Github Issue about Gledopto GL-B-007Z and GL-B-008Z Koenkk states;

For brightness it is actually supported, send e.g.:

On:

{
  "state": "on",
  "brightness": 255,
  "transition": 3
}
Off

{
  "state": "off",
  "brightness": 0,
  "transition": 3
}

So I did this within a function-node;

const MQTTmessage = {
    "turn_on": {
        "payload": {
            "state": "ON",
            "color": {
                "x": 0.551,
                "y": 0.404
            },
            "color_temp": 356,
            "brightness": 100,
            "transition": 2
        }
    },
    "turn_off": {
        "payload": {
            "state": "OFF",
            "brightness": 0,
            "transition": 2
        }
    }
}

return MQTTmessage[msg.payload.service];

Adding transition will cause Gledopto NOT turning off. Is it a bug?
EDIT: strange thing is the other working Gledopto driver HAS transiition set in yaml-config.