Gledopto GL-C-006P color temperature controls brightness after firmware update

Question

Gledopto GL-C-006P color temperature controls brightness after firmware update

Swampen opened this issue 6 months ago · 48 comments

What happened?

Got the new firmware update available over OTA with z2m and updated it (Version: 10276802, Date: 20210719).
After the update the controller have been acting up and it now controls the brightness when I try to change the color temperature.
Normal brightness control works fine.
I had no issues before the firmware update so perhaps an issue with the firmware?

What did you expect to happen?

Adjusting the color temperature should should control the led temperature and not the brightness

How to reproduce it (minimal and precise)

Update to latest available firmware (Version: 10276802, Date: 20210719)
Control temperature
1. Lowering the color_temp increases brightness
2. Increasing the color_temp decreases the brightness

Zigbee2MQTT version

1.36.0

Adapter firmware version

20230507

Adapter

SONOFF Zigbee 3.0 USB Dongle Plus-P

Setup

Add-on on Home Assistant Yellow

Debug log

log.txt
herdsman_log.txt

Answer 1 · 2024-03-29T19:18:25.000Z

I will try this week with an other device which had been updated

Answer 2 · 2024-03-30T08:04:35.000Z

try to re-pair the Device as complete new Device - some of my Danfoss TRV has some weird behaviour after OTA, after new re-pairing all is good

Answer 3 · 2024-03-31T21:42:08.000Z

try to re-pair the Device as complete new Device - some of my Danfoss TRV has some weird behaviour after OTA, after new re-pairing all is good

Tried that now without any luck. Same behavior.

Answer 4 · 2024-03-31T22:04:30.000Z

I had test this morning the device wich be updated with the last firmware.
The cool led light circuit doesn't work.
The warm one yes.
So I think it's normal for you to think controling temperature color adjust the brightness.
This because colours between cool and warm are just a sum af brigjtness of the two circuit.

So i asked to the manufacturer a new firmware.

Answer 5 · 2024-04-01T09:13:21.000Z

@Loic691 I messaged Gledopto last week and got a new firmware this morning. I will try it later today.

Answer 6 · 2024-04-01T10:53:31.000Z

I messaged too. They advise to not provide firmware on OTA because they said me same device référence can have several hardware version...

Answer 7 · 2024-04-01T10:54:41.000Z

I suggest to wait your test and send me the firmware. I will test on my device

Answer 8 · 2024-04-01T10:56:08.000Z

I think the gledopto are not manage correctly. They should have one firmware for ine reference product. The firmware should manage different hardware version

Answer 9 · 2024-04-01T10:56:46.000Z

So if this exactly ,i will remove the firmware on ota

Answer 10 · 2024-04-01T11:05:36.000Z

I suggest to wait your test and send me the firmware. I will test on my device

Sure. I attached the one I got.
My device have Q.C. sticker date marked as 01/2021
GL-C-006P_10476801_2020401.zip

Answer 11 · 2024-04-01T12:09:11.000Z

Thanks. Let me know about your test

Answer 12 · 2024-04-01T12:14:47.000Z

Thanks. Let me know about your test

Just finished the OTA installation from my fork and the behavior is back to normal again

Answer 13 · 2024-04-01T17:32:03.000Z

Great. I will try yours firmware.

Answer 14 · 2024-04-03T06:23:05.000Z

@Loic691 Did you manage to test the new firmware?

Answer 15 · 2024-04-03T10:34:26.000Z

Not enough time...
I started to gen json update file.
I hope this friday

Answer 16 · 2024-04-05T07:41:26.000Z

Hi @Swampen
I just tried your firmware and it is working now for one of my device.
I will push it on a PR !
And try to update other device with real OTA (not locally)

Answer 17 · 2024-04-05T07:47:46.000Z

@Loic691 I only tested this with OTA from my fork, so I can just create a PR from that 🙂

Answer 18 · 2024-04-05T08:01:29.000Z

So ok i wait for your PR on zigbee-OTA project !

Answer 19 · 2024-04-07T08:20:00.000Z

Hey, yestarday i got a notification for update to 10476801, i did the update but now my controller is broken. I dont have warm colour, only natural and when i try to controll the colour temperature its controlling the brightness. Is there any way to roll back?

Answer 20 · 2024-04-07T18:30:15.000Z

@PskNorz Did it work fine with the previous update I had issue with? Do you have "QC" sticker on the back off your device? Perhaps it is a different hardware revision?

@Loic691 Do your original device work with the new firmware?

Answer 21 · 2024-04-07T18:33:20.000Z

@Swampen Hey, it was first time that i used it, didnt make any update yestarday was the 1st and yes it was working fine. QC sticker is on the back yes.

Answer 22 · 2024-04-07T18:51:07.000Z

@PskNorz What is the date of the year and month on the sticker? Mine has 01/2021

Answer 23 · 2024-04-07T18:56:03.000Z

@PskNorz What is the date of the year and month on the sticker? Mine has 01/2021

Is there any way to get back to the old FW?

Answer 24 · 2024-04-08T10:40:09.000Z

The same issue for GL-C-006P. Got 3 down. Will re-pair them today, but expecting the same trouble. Looks like the OTA should be removed from PR.

Answer 25 · 2024-04-08T11:42:58.000Z

@polsup2 Are the devices offline or is the color temperature the only issue? What is the year/month on your Q.C. stickers?

Answer 26 · 2024-04-08T12:08:35.000Z

For me device is online, temp colour slider control britness, and the only temp colour is natural white

Answer 27 · 2024-04-08T15:18:37.000Z

@polsup2 Are the devices offline or is the color temperature the only issue? What is the year/month on your Q.C. stickers?

Devices became offline. I didn't re-pair them yet. They are installed in electric box , so I need to disassemble something to get the photos of production date. Will provide photos little bit later.

Answer 28 · 2024-04-08T17:54:00.000Z

Will re-pair them today, but expecting the same tro

My expectations were wrong. After physical disconnection of power wire on controllers and re-pairing to network, everything works well: Brightness/wwcw.

I think it would be better to warn people that OTA installation causes need to physically access the controller. In some cases, this action is not easy.

Attaching the photo with production date.

Answer 29 · 2024-04-09T14:47:30.000Z

After a alot of repairs, nothing changes for me.

Answer 30 · 2024-04-11T20:46:55.000Z

@Swampen It is possible to reinstall the zip file that you have here?

And if yes, can you explain me how?

Answer 31 · 2024-04-11T21:18:52.000Z

I think there is a way by using a local index.json file and with the force option on the entry
https://www.zigbee2mqtt.io/guide/usage/ota_updates.html#local-ota-index-and-firmware-files

But I do not think it is likely that it will behave differently after a new update as I suspect you have a different hardware revision inside the controller. I will open mine up tomorrow to check if there is any revision number written on the PCB

Answer 32 · 2024-04-12T07:43:48.000Z

I am experiencing the same issues as well. My devices have a 02/2022 QC sticker on. I performed the update yesterday, repaired the devices, tried every idea that came to mind and read here but the issue remains. The controller turns on only cool white and the color temperature bar controls brightness instead of mireds.
For info, this only happened to devices that i updated to firmware 10476801 (build date 20240401). The devices that i left to the older firmware 10276802 (build date 20210719) work fine. This version appears to have caused the issues to @Swampen but for my case, this is the proper firmware to have and should not upgrade to the latest available.
I would appreciate that firmware version file if available so i can downgrade.

Answer 33 · 2024-04-12T08:38:38.000Z

@Loic691 Did you try to update the device you had tested here to the latest firmware?

I have sent a new email to Gledopto with this new information to see if there is any changes in hardware revision between these QC stickers. Hopefully there is a way to distinguish them.

@monoimoi and @PskNorz If you want to downgrade the firmware, you can do the following:

Add a local index.json file to your z2m config https://www.zigbee2mqtt.io/guide/usage/ota_updates.html#local-ota-index-and-firmware-files
Add the following to your local index.json

[
    {
        "fileVersion": 10,
        "fileSize": 281342,
        "manufacturerCode": 4687,
        "imageType": 0,
        "sha512": "ef83e88563221eeac951f7f6d1769891b7eb9f4df44b0acd2cdd5e473cdd9f2772fd4ec4540b5f852d93fcc14637b28567a2869fb6ea3809fcf76ea5a230572b",
        "modelId": "GL-C-006P",
        "url": "https://github.com/Koenkk/zigbee-OTA/raw/master/images/Gledopto/GL-C-006P_V102.ota",
        "path": "images/Gledopto/GL-C-006P_V102.ota",
        "force": true
    }
]

Update the device

Answer 34 · 2024-04-12T08:58:23.000Z

After upgrading to the newest firmware, color temperature was also broken here.
I fixed the issue by downgrading the firmware with a local OTA index.
[ { "fileVersion": 10, "fileSize": 281342, "manufacturerCode": 4687, "imageType": 0, "sha512": "ef83e88563221eeac951f7f6d1769891b7eb9f4df44b0acd2cdd5e473cdd9f2772fd4ec4540b5f852d93fcc14637b28567a2869fb6ea3809fcf76ea5a230572b", "modelId": "GL-C-006P", "url": "https://github.com/Koenkk/zigbee-OTA/raw/master/images/Gledopto/GL-C-006P_V102.ota", "path": "images/Gledopto/GL-C-006P_V102.ota", "force": true } ]
Details of this firmware:

Firmware build date: 20210719
Firmware version: 10276802
hwVersion: 2

Answer 35 · 2024-04-12T09:31:34.000Z

{
    "color_mode": "color_temp",
    "linkquality": 109,
    "state": "ON",
    "update": {
        "installed_version": 10,
        "latest_version": 12,
        "state": "available"
    },
    "update_available": null,
    "brightness": 125,
    "color_temp": 370
}

QC passed 21/22
FW ; 10276802
FW date : 20210719

OTA update is not working.
Z2MQTT logs :

Info 2024-04-12 11:09:43Updating '0xcc86ecfffe187e3e' to latest firmware
Info 2024-04-12 11:09:47Update of '0xcc86ecfffe187e3e' at 0.00%
Info 2024-04-12 11:09:47MQTT publish: topic 'zigbee2mqtt/0xcc86ecfffe187e3e', payload '{"color_mode":"color_temp","color_temp":370,"linkquality":109,"state":"ON","update":{"installed_version":10,"latest_version":12,"progress":0,"state":"updating"},"update_available":null}'
Info 2024-04-12 11:12:17MQTT publish: topic 'zigbee2mqtt/0xcc86ecfffe187e3e', payload '{"color_mode":"color_temp","color_temp":370,"linkquality":109,"state":"ON","update":{"installed_version":10,"latest_version":12,"state":"available"},"update_available":null}'
Info 2024-04-12 11:12:17MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/update', payload '{"data":{"id":"0xcc86ecfffe187e3e"},"error":"Update of '0xcc86ecfffe187e3e' failed (OTA: Timeout, device did not request any image blocks)","status":"error","transaction":"2mfdd-1"}'
Error 2024-04-12 11:12:17Update of '0xcc86ecfffe187e3e' failed (OTA: Timeout, device did not request any image blocks)Info 2024-04-12 11:09:43Updating '0xcc86ecfffe187e3e' to latest firmware
Info 2024-04-12 11:09:47Update of '0xcc86ecfffe187e3e' at 0.00%
Info 2024-04-12 11:09:47MQTT publish: topic 'zigbee2mqtt/0xcc86ecfffe187e3e', payload '{"color_mode":"color_temp","color_temp":370,"linkquality":109,"state":"ON","update":{"installed_version":10,"latest_version":12,"progress":0,"state":"updating"},"update_available":null}'
Info 2024-04-12 11:12:17MQTT publish: topic 'zigbee2mqtt/0xcc86ecfffe187e3e', payload '{"color_mode":"color_temp","color_temp":370,"linkquality":109,"state":"ON","update":{"installed_version":10,"latest_version":12,"state":"available"},"update_available":null}'
Info 2024-04-12 11:12:17MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/update', payload '{"data":{"id":"0xcc86ecfffe187e3e"},"error":"Update of '0xcc86ecfffe187e3e' failed (OTA: Timeout, device did not request any image blocks)","status":"error","transaction":"2mfdd-1"}'
Error 2024-04-12 11:12:17Update of '0xcc86ecfffe187e3e' failed (OTA: Timeout, device did not request any image blocks)

Then I can't control the device nymore:

2024-04-12 11:14:54Failed to read state of '0xcc86ecfffe187e3e' after reconnect (ZCL command 0xcc86ecfffe187e3e/11 genLevelCtrl.read(["currentLevel"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 51571 - 11 - 30 - 8 - 1 after 10000ms))

Solved with re-pairing the device, but OTA update didn't worked.

Answer 36 · 2024-04-12T09:34:32.000Z

~~@nick-dijkshoorn Interesting with the hwVersion. I looked in my database.db and my device has "hwVersion": 1~~

~~@monoimoi, @Loic691 and @PskNorz Can you check which hwVersion you have?~~

Scratch that. I was looking at the wrong device.. I also have hwVersion 2..

Answer 37 · 2024-04-12T10:24:32.000Z

@Loic691 Did you try to update the device you had tested here to the latest firmware?

Yes localy and it's OK.
I have another device en V1.0.1 which I can't update.
The update fails with this error failed (OTA: Timeout, device did not request any image blocks)
And the device hangs. I have to reboot it and repair again in Z2M.

I think GLEDOPTO have different hardware version with different firmware and there is no issues to check which hardware version we have. I had discussion with GLEDOPTO and they advise to not process update if the device works correctly.

They are easily reachable by email.

Answer 38 · 2024-04-12T10:25:42.000Z

Scratch that. I was looking at the wrong device.. I also have hwVersion 2..

Where we can find hardware version ?

Answer 39 · 2024-04-12T10:36:47.000Z

Sorry I found !
For information, the device I updated locallty is hwVersion 2

The other one I can't update have no hardware version in interview...

Answer 40 · 2024-04-12T10:58:45.000Z

Mine is hardware version 2 :

Read result of 'genBasic': {"hwVersion":2,"appVersion":0,"zclVersion":3,"stackVersion":0,"modelId":"GL-C-006P","appProfileVersion":255,"swBuildId":"10276802","manufacturerName":"GLEDOPTO"}

Answer 41 · 2024-04-12T11:08:08.000Z

Scratch that. I was looking at the wrong device.. I also have hwVersion 2..

Where we can find hardware version ?

Can you tell me how?

Answer 42 · 2024-04-12T13:48:23.000Z

In database.db file of Z2M config directory

Answer 43 · 2024-04-12T13:52:39.000Z

Mine is hardware version 2 :

Read result of 'genBasic': {"hwVersion":2,"appVersion":0,"zclVersion":3,"stackVersion":0,"modelId":"GL-C-006P","appProfileVersion":255,"swBuildId":"10276802","manufacturerName":"GLEDOPTO"}

For mine which is OK for update firmware :
Date du firmware
20240401
Version du firmware
10476801
Constructeur
Gledopto

{"genBasic":{"attributes":{"modelId":"GL-C-006P","manufacturerName":"GLEDOPTO","powerSource":0,"zclVersion":3,"appVersion":0,"stackVersion":0,"hwVersion":2,"dateCode":"20240401","swBuildId":"10476801"}}

For other one which update failed :
Version du firmware
V1.0.1
Constructeur
Gledopto
Modèle
GL-C-006P

{"genBasic":{"attributes":{"appVersion":0,"stackVersion":0,"dateCode":"","modelId":"GL-C-006P","zclVersion":3,"swBuildId":"V1.0.1"}}

Answer 44 · 2024-04-12T15:47:35.000Z

database.db

I got only this.

Answer 45 · 2024-04-12T15:57:43.000Z

@Loic691 Did you try to update the device you had tested here to the latest firmware?

I have sent a new email to Gledopto with this new information to see if there is any changes in hardware revision between these QC stickers. Hopefully there is a way to distinguish them.

@monoimoi and @PskNorz If you want to downgrade the firmware, you can do the following:

Add a local index.json file to your z2m config https://www.zigbee2mqtt.io/guide/usage/ota_updates.html#local-ota-index-and-firmware-files

Add the following to your local index.json
[
    {
        "fileSize": 281342,
        "manufacturerCode": 4687,
        "imageType": 0,
        "sha512": "ef83e88563221eeac951f7f6d1769891b7eb9f4df44b0acd2cdd5e473cdd9f2772fd4ec4540b5f852d93fcc14637b28567a2869fb6ea3809fcf76ea5a230572b",
        "modelId": "GL-C-006P",
        "url": "https://github.com/Koenkk/zigbee-OTA/raw/master/images/Gledopto/GL-C-006P_V102.ota",
        "path": "images/Gledopto/GL-C-006P_V102.ota",
        "force": true
    }
]
Update the device

The update would fail repeatedly until I added "fileVersion": 10 on top of the json file (@nick-dijkshoorn 's example). I have now successfully reverted back to the older firmware and everything works as it used to.
Hardware version 2. Thanks everyone for your input.

Answer 46 · 2024-04-12T16:11:51.000Z

database.db

I got only this.

You can also find hwVersion by using z2m web interface.
Go to devices tab then click the device you want to query.
Click "dev console" tab
Endpoint: "11" -> Cluster "genBasic" -> attributes "hwVersion" and then click read.

Answer 47 · 2024-04-12T16:46:31.000Z

@monoimoi Thank you! I am a newbie and I am trying to learn how Z2M works.

So I think I have found the solution.

My hardware version is Read result of 'genBasic': {"hwVersion":2}
Q.C Sticker 7/22

I sent an email to Gledopto and I told them which Q.C Sticker I have, and they replied to me with an OTA Update file.

GL-C-006P_10576802_20240412.zip

Because I am new to Z2M, I didn't know how to update it, so I switched back to Deconz because I knew how to do it. I updated the device and repaired it back to Z2M.

And it's done! Everything works as it should.

Thanks to everyone. I hope this helps others facing the same problem.