Skip to content
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 esp Matter:Received QueryImage failure (CON-360) #277

Closed
HKSIWAR opened this issue Mar 16, 2023 · 7 comments
Closed

OTA esp Matter:Received QueryImage failure (CON-360) #277

HKSIWAR opened this issue Mar 16, 2023 · 7 comments

Comments

@HKSIWAR
Copy link

HKSIWAR commented Mar 16, 2023

Hello,
I have two esp32, the first one is provider and flashed by the ota-provider example, the second one is requestor and flashed by the ota-requestor example.
ota-requestor. then, i put both devices in the same network. finally, i run the AnnounceOTAProvider command:
out/chip-tool otasoftwareupdaterequestor announce-otaprovider 0xDEADBEEF 0 0 0x1234567890 0.
The following figure shows the error message:
1

@github-actions github-actions bot changed the title OTA esp Matter:Received QueryImage failure OTA esp Matter:Received QueryImage failure (CON-360) Mar 16, 2023
@dhrishi
Copy link
Collaborator

dhrishi commented Mar 16, 2023

@HKSIWAR Are you directly using the upstream connectedhomeip ota-requestor-app and ota-provider-app and not the esp-matter examples? Please provide details about the examples used and branch/tag/commit you are using.

If you are using v1.0.0.2 connectedhomeip tag, have you followed the instructions here: https://github.com/project-chip/connectedhomeip/tree/v1.0.0.2/examples/ota-requestor-app/esp32#prerequisite ? If you face the issue even after following the documentation, then please upload (and not paste) the entire logs on OTA provider, requestor and the chip-tool

@HkiriSiwar
Copy link

HkiriSiwar commented Mar 16, 2023

@dhrishi the following paths that i used are :

the steps are :

  • comissioning provider : I use the following command "sudo out/debug/chip-tool pairing ble-wifi 12345 Orange-710D qtFAgq2N2h8 20202021 3840"
  • comissioning requestor : I use the following command "sudo out/debug/chip-tool pairing ble-wifi 1234 Orange-710D qtFAgq2N2h8 20202021 3840"
  • update image: I use the following command "sudo ./out/debug/chip-tool otasoftwareupdaterequestor announce-ota-provider 12345 0 0 0 1234 0"
    I use the version 1.0.0.2 and the logs output are :
    - Log output ota-requestor :
    log_requestor.log
    - Log output ota-provider :
    log_provider.log
    - Log chip-tools :
    log_chip_tool.log

@jadhavrohit924
Copy link
Contributor

Hi @HkiriSiwar,
From the logs, looks like you have missed one step of Writing into Access Control List.
Please check the steps here

@dhrishi
Copy link
Collaborator

dhrishi commented Apr 6, 2023

@HKSIWAR This issue has been fixed in the upstream codebase project-chip/connectedhomeip#25859

This will be addressed in the esp-matter repository once the connectedhomeip submodule is updated, having this commit. For now, you can try this on your side by applying the fix in esp-matter/connectedhomeip/connectedhomeip

@jadhavrohit924
Copy link
Contributor

@HkiriSiwar I could able to perform OTA on lateste esp matter.
From your logs, looks like the problem is in your OTA image. Can you verify you have OTA image with updated software version ( i.e OTA image software version > current image software version )?

@dhrishi
Copy link
Collaborator

dhrishi commented Apr 12, 2023

@HkiriSiwar Is your issue resolved? Please close this if it was.

@dhrishi
Copy link
Collaborator

dhrishi commented Apr 27, 2023

I will close this now. Please reopen in case of anything

@dhrishi dhrishi closed this as completed Apr 27, 2023
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

No branches or pull requests

4 participants