Bricked CGDK2 / Qingping Temp RH Lite #27
Comments
|
|
Back to BLE
|
|
I am also experiencing the same issue. After flashing with firmware 4.5, the sensor displays a temperature of -3.9c and 10.0% humidity. The flashing log was as follows; After a few attempts, I did get it to pair with Zigbee2MQTT. However, as the device is unsupported I took the definition from here for the LYWSD093MMC and adapted it to the CGDK2; Zigbee2MQTT is now able to read it, but the values are also wrong; 
I wanted to try @pvvx 's instructions in the previous comment to flash it back to BLE but the OTA for this is not yet in Zigbee2MQTT. Therefore, following the instructions here I created a custom OTA firmware index with the following contents; I downloaded the firmware file and placed it in to an After restarting Zigbee2MQTT I went to the OTA screen and checked for updates for the device. It found one, and I then started the flash process. It takes about 15 minutes. However, once complete the display showed the correct temperature and humidity again, and I was able to reconnect to it over Bluetooth using the flashing tool; @SkyRaax If you are able to get it paired to your Zigbee system, then hopefully you'll be able to get it back on the BLE custom firmware again. It's a little bit more complex for Zigbee2MQTT compared to @pvvx's ZHA instructions but I figured it out eventually! If you're having trouble getting it paired, put it in to pairing mode and place it close to your coordinator - although the screen might go back to the -3.9c display it does eventually seem to pair. After getting it back on the BLE firmware, I did then try flashing back to the Zigbee firmware, in case I wasn't supposed to have flashed the Zigbee firmware without first flashing the custom BLE firmware. Unfortunately, this produced the same results as before - the sensor displays a temperature of -3.9c and 10.0% humidity. I'm going to try and get it connected back to Zigbee2MQTT again so I can flash the BLE firmware again. @pvvx Is there anything I can do to help diagnose why the Zigbee firmware doesn't work? |
|
Yeah that's exactly what happened to me, but thank you for the tip that I can still connect the thing to ZigBee. Will try this! And as it seems I think maybe the manufacturer changed something so that this firmware doesn't work anymore. |
|
This means that in these СGDK2 models a different temperature and humidity sensor is installed. Some information on the sensor can only be obtained in BLE firmware. Requires firmware version 4.6
02 - Get address devises Need response log: |
|
I got it back on to the BLE firmware (v4.6) again and sent those commands; |
|
Thanks for the info. |
|
The source code has been modified ( v 0.1.1.5 + ). Requires CGDK2 test with non-standard sensor. |
|
Hello pvvx, I managed to brick the CGDK2 after trying OTA several times, apparently my model also uses a substandard sensor. Can you tell me how to wire the CGDK2 properly? I'm having trouble understanding which wire goes where and which flasher to use. Will this work? Can you give/write a simple guide? Thank your for your help. |
This operation does not require programming via wires. Programming by wire is used only in case of uploading incompatible code or having global errors.
|
|
I understand, but the device is unable to pair to 2 different coordinators and networks when the Zigbee firmware is flashed. So according to your links, i should attach: CGDK2 ---- USB Adapter Which I've already done, But I cannot seem to activate the device for flashing (does not pass activation phase) Thanks |
|
The process finishes, yet the CGDK2 remains in a bricked state:
|
|
Your adapter does not have an RTC or DCR output. In Zigbee firmware, the processor “wakes up” at intervals of 10 seconds. "Atime" must be greater than this period in order to get to the moment when the chip "wakes up". Therefore, it is necessary to connect TX and +3.3V simultaneously during “activation”. And take a smaller firmware file - it is more likely to flash correctly, since the programmer does not have feedback and there is no way to check what was written or what was connected at all. It is possible to use "Erase all Flash". This is a short command and has more reception. After it, if you turn off and turn on the power, there will be no indication. But the chip will be in active mode all the time and will accept the programmer’s command. |
|
TX terminal on the adapter or TX (TP1) terminal on the CGDK2? Thank you for your patience |
|
Okay, I erased flash successfully, unplugged and plugged again. At this point, there was nothing on the screen but I was able to connect to COM port. I flashed the smallest firmware successfully (appears so) but then again it shows -3.8C and 10% humidity. |
|
What firmware did You flash? |
|
This means that this CGDK2 uses some new sensor? Please post the log from the description in: |
|
I think I'm either failing miserably at flashing (missing something obvious) or this adapter is total trash. Thank you very much for your help so far Victor P.S. There are no BLE advertisements, so the flash was a fail most likely |
|
I flashed CGDK2_v46.bin into a bare TLSR8253:
https://pvvx.github.io/ATC_MiThermometer/TelinkMiFlasher.html Vbat: 3324 mV , Temp: 0.00°C, Humi: 0.00%, ID: 0, Reed switch counter: 0, flg: 0x00:r0/t0
BLE or Zigbee firmware for CGDK works with any sensor and screen. And without them. There will be no indication or readings from the sensor, but everything else will work. |
|
I managed to flash it using ATCtelink.py and still getting the -3.8C and 10% hum. Is it possible it uses some other non standard sensor? Cant pair to any Zigbee network, doesn't broadcast BLE advertisments. |
|
You can also flash ATC_v46.bin, MHO_C401N_v46.bin, MHO_C122_v46.bin, ... BLE and OTA will still work. https://github.com/pvvx/TLSR825x_OTA_Flash_Hacker - does not request any sensors and does not use chip pins. But BLE and OTA will work. Interrupting OTA at any time will not ruin anything except waste your battery. All this is done for those who confuse the firmware, so as not to open the device and not use reprogramming by wire. |
|
BIG shoutout to @KingJ! Only because of your pretty well documented process of recovering the device I was able to get it back to BLE myself. Another thing:
@pvvx I tried to flash it again with the flasher itself and I get the same "error" so somehow the sensor isn't still right. In the log you can see I used "ZCGDK2_v0117.bin" this should be the updated version right? So maybe this information helps you, if you need more, let me know! |
|
For confirmation here is the output of the Commands 02 and 05: |
|
I couldn't find any of these CGDK2s for sale (Sensor: I2C addres 0x70, Sensor ID: 00000000). In particular, I was not able to find Xiaomi LYWSD03MMC versions B1.5 and B1.6. |
|
Just wanted to share my findings. I managed to restore to original BLE by flashing CGDK2_v26.bin with https://pvvx.github.io/ATC_MiThermometer/USBCOMFlashTx.html Than I flashed the latest Zigbee firmware ZCGDK2_v0117.bin with https://pvvx.github.io/ATC_MiThermometer/TelinkMiFlasher.html The device pairs fine, BUT it it still showing -3.9°C and 10% humidity. Which means it does use some other, substandard sensor. Let me know what I can do to provide support for this particular sensor. Thank you PVVX for the patience and support. |
|
I had the same issue with the -3.9C/10% result. I am not sure if it will help, but this is the same device that had issues with the ATC_MiThermometer firmware where the sensor was SHTV3 (but was eventually fixed by pvvx). |
|
In the Zigbee version, the previous method does not work. The reasons are unknown to me - I don’t have a CGDK2 with such a sensor for tests and checks. |
|
I have the same issue. I got mine from here, if that helps: I tried to return to the BLE firmware, but this does not seem to work. I added the firmware file to the OTA folder and installed the ZHA toolkit. On the first CGDK2 where I tried this, I got a positive return message:zha_toolkit_version: v1.1.8
zigpy_version: 0.60.1
zigpy_rf_version: 0.22.2
ieee_org: sensor.qingping_cgdk2_battery_2
ieee: 58:f6:3d:81:34:2d:58:5a
command: ota_notify
command_data: null
start_time: "2023-12-23T09:34:45.157909+00:00"
errors: []
params:
dir: 0
tries: 1
expect_reply: true
args: []
read_before_write: true
read_after_write: true
PAR:
cmd_id: null
endpoint_id: null
dst_endpoint_id: null
cluster_id: null
attr_id: null
attr_type: null
attr_val: null
code: null
min_interval: null
max_interval: null
reportable_change: null
dir: 0
manf: null
tries: 1
expect_reply: true
args: []
state_id: null
state_attr: null
state_value_template: null
force_update: false
allow_create: false
event_success: null
event_fail: null
event_done: null
fail_exception: false
read_before_write: true
read_after_write: true
write_if_equal: false
csvfile: null
csvlabel: null
download: null
path: null
use_cache: false
result: null
success: trueBut afterwards I can't find the device within the bluetooth list of the flasher. Do I need to press the button in any way? On the second one I get this errorzha_toolkit_version: v1.1.8
zigpy_version: 0.60.1
zigpy_rf_version: 0.22.2
ieee_org: sensor.qingping_cgdk2_battery
ieee: 58:aa:39:81:34:2d:58:5a
command: ota_notify
command_data: null
start_time: "2023-12-23T09:40:56.964415+00:00"
errors:
- >-
DeliveryError('Failed to deliver packet:
<TXStatus.NWK_ROUTE_DISCOVERY_FAILED: 208>')
params:
dir: 0
tries: 1
expect_reply: true
args: []
read_before_write: true
read_after_write: true
PAR:
cmd_id: null
endpoint_id: null
dst_endpoint_id: null
cluster_id: null
attr_id: null
attr_type: null
attr_val: null
code: null
min_interval: null
max_interval: null
reportable_change: null
dir: 0
manf: null
tries: 1
expect_reply: true
args: []
state_id: null
state_attr: null
state_value_template: null
force_update: false
allow_create: false
event_success: null
event_fail: null
event_done: null
fail_exception: false
read_before_write: true
read_after_write: true
write_if_equal: false
csvfile: null
csvlabel: null
download: null
path: null
use_cache: false
success: falseIs the only way to fix this by manually flashing them again? Or is there anything I need to do differently? |
|
You must proceed as described in "OTA update in ZHA"
The command needs to be repeated. |
|
Thanks for the hints! What solved my problem was changing the path from zha:
zigpy_config:
ota:
- otau_directory: /homeassistant/pvvx/zigpy_ota
+ otau_directory: ./pvvx/zigpy_otaI'm running HA OS and this seems to be the issue. Now both my devices are back to the BT firmware. Anything I can do to help you debug the issue with this new sensor? |
I now tried 2x Qingping Temp RH Lite to flash them with the ZigBee Firmware and both sensors just show this screen after flashing:
I don't have any chance to get this thing working properly. So restarting or resetting don't work.
Also I don't get it in the Zigbee network.
Also the thing don't create any Bluetooth so I can't recover it with the flasher site...
Is there I did wrong or did the manufacturer change something?
The text was updated successfully, but these errors were encountered: