-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OTA Error: NotSupportedError: GATT operation failed for unknown reason. #29
Comments
I had a similar error when I flashed from a computer, try from your phone |
Try to extract and insert the battery. |
Also try a different battery. I've found if the battery is a bit on the low side it may throw random errors like above |
i have a problem with hw B1.7 revision too, brick after first flashing via air (no connect, no screen), then flashed via UART - all worked fine but get another brick after OTA (z2m) on ver 1.0.3 revision 1.7 little shitty)) another device hw B1.4 worked fine |
I have exactly the same symptom hw B1.7 - after uploading the software and rebooting, the sensor screen displays nothing. Battery replaced with new one and reset done. With another hw B1.4 device, the transition to Zigbee was successful. |
I don't have any idea why OTA on B1.7 works incorrectly. Feel free to share your thoughts. #36 |
For B1.7, B1.9, B2.0, the code from ATC1441 used to work with the display controller (BU9792FUV) in the Zigbee firmware is not quite correct. |
Same error with B1.6. Tryed on several devices with PC and phone. Flashing ATC_ota_40000 is OK. After reconnect:
And when trying to flash anithing after ATC_ota_40000.bin (not only z03mmc.bin) I have error "Update error: NotSupportedError: GATT operation failed for unknown reason." I think that is important: all firmwares stops on "Sending block nr: 7 from ..." when flashing
|
@mtdn - Clarification is not possible - there is no source code ATC_ota_40000.bin. There are only guesses - ATC_ota_40000.bin does not clear the Flash area for writing OTA. |
Had the same issue with revision B1.6 several times, on all 4 devices that I bought. Flashing ATC_ota_40000.bin went smoothly after activation, but flashing z03mmc.bin always gave an error after the first battery-out/in and connecting to the ATC_XXXX device. What helped was simply retrying:
I was able to flash all 4 devices after a maximum of 3 tries per device. But I have no idea what the cause for the issue is. As others reported above, it stops at "Sending block nr: 7 from ..." and shows the " NotSupportedError: GATT operation failed for unknown reason." |
z03mmc.bin from devbis is not supported in BLE OTA TelinkMiFlasher.html. TelinkMiFlasher.html supports downloading Zigbee firmware in *.zigbee file format with BLE firmware version from 4.6. When selecting the firmware file in TelinkMiFlasher.html, copy and paste the link If there is a “disconnect” when starting the flashing, reconnect and repeat OTA. The reasons for 'disconnect' may be due to difficulties in preparing Flash to write firmware to another area. Not all BT adapters can maintain a connection at varying intervals. |
I received V1.6 HW sensors and confirm that OTA in transitional firmware is broken. |
everything is ok from step 1-4
but after step 4 , flash firmware ATC_ota_400000
when i reboot device ,reflash website
connect shows:
21:50:33: Reconnect 5 from 5
21:50:33: Hardware Revision String: B1.7
21:50:33: Software Revision String: V4.4
21:50:33: Firmware Revision String: github.com/pvvx
21:50:33: Detected Mi device
21:50:33: NotSupportedError: GATT operation failed for unknown reason.
21:50:33: Something went wrong, too many reconnects
the displayer is still work
The text was updated successfully, but these errors were encountered: