Skip to content

Conversation

@V4n1X
Copy link
Contributor

@V4n1X V4n1X commented Aug 8, 2025

Pay attention to the current sw_build_id of your device, there are 2 (maybe more) version of this device!

GL-C-008P_V11376801_only_for_Vxxx76801.ota
model: GL-C-008P (Vxxx76801)
sw_build_id: 11376801
current_file_version: 22

GL-C-008P_V11576802_only_for_Vxxx76802.ota
model: GL-C-008P (Vxxx76802)
sw_build_id: 11576802
current_file_version: 24

V4n1X added 2 commits August 8, 2025 14:03
GL-C-008P_V11376801_only_for_Vxxx76801.ota
model: GL-C-008P (Vxxx76801)
sw_build_id: 11376801
current_file_version: 22

GL-C-008P_V11576802_only_for_Vxxx76802.ota
model: GL-C-008P (Vxxx76802)
sw_build_id: 11576802
current_file_version: 24
GL-C-008P_V11376801_only_for_Vxxx76801.ota
model: GL-C-008P (Vxxx76801)
sw_build_id: 11376801
current_file_version: 22

GL-C-008P_V11576802_only_for_Vxxx76802.ota
model: GL-C-008P (Vxxx76802)
sw_build_id: 11576802
current_file_version: 24
@github-actions
Copy link
Contributor

github-actions bot commented Aug 8, 2025

Merging this pull request will add these changes in a following commit:

diff --git a/images/Gledopto/GL-C-008P_V11376801_only_for_Vxxx76801.ota b/images/Gledopto/GL-C-008P_V11376801_only_for_Vxxx76801.ota
deleted file mode 100644
index 1893242..0000000
Binary files a/images/Gledopto/GL-C-008P_V11376801_only_for_Vxxx76801.ota and /dev/null differ
diff --git a/index.json b/index.json
index 0b6d130..e672c84 100644
--- a/index.json
+++ b/index.json
@@ -8330,5 +8330,15 @@
     "manufacturerCode": 4678,
     "sha512": "8d536faa3fe43d469fe9ec4f92ea78cce1874872fb82b4401334a76f23158de62ecdfa1af49604726782ba6119c6c60d8363eabc023c2f0dcff3fe06dee2367f",
     "otaHeaderString": "Tue 06/03/2025 V.0020.0020"
+  },
+  {
+    "fileName": "GL-C-008P_V11576802_only_for_Vxxx76802.ota",
+    "fileVersion": 24,
+    "fileSize": 277306,
+    "url": "https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/images/Gledopto/GL-C-008P_V11576802_only_for_Vxxx76802.ota",
+    "imageType": 0,
+    "manufacturerCode": 4687,
+    "sha512": "cef0d4365b82330d6de70146931f055b57ef176e0b51b63d38551d64fda50957b4845b8cfaf899d058ddae7a191824723a92324ef0cdb9bd552587e45c294a7d",
+    "otaHeaderString": "EBL ARGBW_V_0_1"
   }
 ]
\ No newline at end of file
diff --git a/index1.json b/index1.json
index b916b71..2069f58 100644
--- a/index1.json
+++ b/index1.json
@@ -2452,5 +2452,15 @@
     "manufacturerCode": 4678,
     "sha512": "2be3ce5ff9e9b378a447285a7f2f099313a8ec067c5565b0ceb9fcb917ba663d022b05ceaeddd20d0205d9b98b1c2986570699d749031f4b54ffd04d14d593c8",
     "otaHeaderString": "Thu 11/09/2023 V.001C.001C"
+  },
+  {
+    "fileName": "GL-C-008P_V11376801_only_for_Vxxx76801.ota",
+    "fileVersion": 22,
+    "fileSize": 276878,
+    "url": "https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/images1/Gledopto/GL-C-008P_V11376801_only_for_Vxxx76801.ota",
+    "imageType": 0,
+    "manufacturerCode": 4687,
+    "sha512": "d8e682e9179ba9353e4ea7e8494ca440be6f5458772e37b82f99ec6184b0cbeace263e8787af5c69da7ab3275ea14b3cc3c2f318b2c9af72aa8c9b43a6d5344d",
+    "otaHeaderString": "EBL ARGBW_V_0_1"
   }
 ]
\ No newline at end of file

@Koenkk
Copy link
Owner

Koenkk commented Aug 8, 2025

Given Gledopto OTA updates caused a mess before (#827), I'm inclined to not accept any new Gledopto OTAs anymore, because how are we going to guarantee this is not going to break more devices?

@V4n1X
Copy link
Contributor Author

V4n1X commented Aug 9, 2025

Yes you are right, thats only the case if there is ability to check the current installed sw_build_id for the matching hardware revision, and to serve then only the right version, I don't know if that is possible.

Maybe we put the Gledopto Updates into a category for manual updates, with informations about it.

@Koenkk
Copy link
Owner

Koenkk commented Aug 9, 2025

Yes you are right, thats only the case if there is ability to check the current installed sw_build_id

This can be added but the problem is that older z2m instances and ZHA won't check for this so they will feed the wrong OTAs to the device. I propose to keep it manual indeed with some instructions. Maybe we can document it on the device page

@Nerivec
Copy link
Collaborator

Nerivec commented Aug 9, 2025

Not sure what the devices are reporting (i.e. if possible), but looks like this wouldn't work anyway without at least one of these:

    hardwareVersionMin?: number;
    hardwareVersionMax?: number;
    minFileVersion?: number;
    maxFileVersion?: number;

(as can be seen, the detection put one in index1 - detected "older")

@davux
Copy link

davux commented Sep 10, 2025

It looks like there is still a confusion around Gledopto OTAs. See #865 for example.
For example, I'm getting this log in z2m:

zhc:ota: [0xa4c138a7bb787072 | GL-C-008P] Getting latest image, meta: {"fileName":"C-ZB-LC20_V30151203_20250904.ota","fileVersion":838938625,"fileSize":203346,"url":"https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/images/Candeo/C-ZB-LC20_V30151203_20250904.ota","imageType":5145,"manufacturerCode":4687,"sha512":"8effcb4304d10f0af0fa5b3dc40d0724844f23d3cbfbd409bbfff7549c3483cd04c01652c17cb423ffb6ca3ce24e9589290109530fa19e3bc5033476ae3a17ee","otaHeaderString":"Telink OTA Sample Usage"}

So in my example it's a Gledopto GL-C-008P but for some reason it's fetching Candeo/C-ZB-LC20_V30151203_20250904.

@Koenkk
Copy link
Owner

Koenkk commented Sep 10, 2025

@davux this is because Gledopto uses the spec very badly (I fixed this case)

@Anemia7635
Copy link

Just semi-bricked two Gledopto GL-C-008P while OTA flashing via ZHA (not using z2m). They can no longer change mode, are stuck in RGBW, and one is now presenting itself as "C-ZB-LC20v2-RGBCCT by Candeo". Both flash angry red leds when trying to change mode. Naming is not so important to me, but mode is. Will it be possible to reflash/salvage somehow? The one with new name is also stuck in an upgrade loop, running 0x31013001, repeatedly trying to install 0x32013001.

@Ltek
Copy link

Ltek commented Sep 13, 2025

@V4n1X @Koenkk I suspect none of this is Gledopto's fault.

I just posted some enhancement requests that would make OTA easier for users and more failure proof.
... #869

I've been working with the Gledopto firmware dev for over a week now to create a customer FW for me. He's been really great. The FW you are all talking in this thread he told me that was never posted by Gledopto. It is a custom FW that a user posted which was never meant for public release.

The enhancements I hope you put in place would make all these problems easily avoidable and easily reversible... which they are not currently either of those since the user is blind to any real info about the FW that Z2M presents the user. The user must 'trust' that Z2M has proper FW to give, and in the above case, it did not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants