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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to upgrade to custom firmware #16823

Closed
fred-gb opened this issue Feb 26, 2023 · 21 comments
Closed

Unable to upgrade to custom firmware #16823

fred-gb opened this issue Feb 26, 2023 · 21 comments
Labels
problem Something isn't working stale Stale issues

Comments

@fred-gb
Copy link

fred-gb commented Feb 26, 2023

What happened?

Hello, 馃憢馃徎

I have problem with my Zlinky TIC

I would like to upgrade to a special firware version limited.

But I can't...

What did you expect to happen?

Upgrade from UI or anything else.

How to reproduce it (minimal and precise)

I used zigbee-OTA script. to create an index.json, with last entry:

    {
        "fileVersion": 13,
        "fileSize": 245406,
        "manufacturerCode": 4151,
        "imageType": 2,
        "sha512": "dd77b28a3b4664e7ad944fcffaa9eca9f3adb0bbe598e12bdd6eece8070a8cdda6792bed378d173dd5b4532b4cdb88cebda0ef0c432c4c4d6581aa9f2bbba54d",
        "url": "https://github.com/fairecasoimeme/Zlinky_TIC/releases/download/v13.0/ZLinky_router_v13_limited.ota",
        "force": true
    }

I add force configuration.

In configuration.yml I add:

ota:
  zigbee_ota_override_index_location: my_index.json
  ikea_ota_use_test_url: false

I renamed index.json in my_index.json an put in same directory like configuration.yaml.

I restart my docker Zigbee2Mqtt.

And send message: domotique/zigbee2mqtt/bridge/request/device/ota_update/update with ID of device 0x00158d0006a4018c.

But... No update avaiblable when I try in UI.

Update of '0x00158d0006a4018c' failed (No new image available)

Zigbee2MQTT version

1.30.1 commit: eb878d3 (docker)

Adapter firmware version

6.10.3.0 build 297

Adapter

SONOFF ZBDongle-E (EZSP v8)

Debug log

Zigbee2MQTT:debug 2023-02-26 17:09:50: Responded to OTA request of '0x94deb8fffe8a1ec6' with 'NO_IMAGE_AVAILABLE'
@Danit2
Copy link

Danit2 commented Feb 26, 2023

This is beqause of this problem.

#12554

It is not fix at the moment.

You can make a custom converter of this device with the normal ota directory and then the override will work.

@molusk
Copy link

molusk commented Feb 28, 2023

@Danit2 when I look at the lixee converter, I don't see much about OTA : ota: ota.lixee, .

What do you mean we should do with this custom converter ?

On the other hand, I have found the file dedicated to OTA for lixee device : https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/lib/ota/lixee.js
I tried to modify it on my install to point to the right ota (ends with "limited.ota") file but it does not seem to change anything. I don't really know javascript, it does not help 馃槅

@Danit2
Copy link

Danit2 commented Feb 28, 2023

You must replace the ota: ota.lixee with ota: ota.zigbeeOTA then the local ota index is working.

@molusk
Copy link

molusk commented Feb 28, 2023

Thank's a lot, I will test this as soon as possible 馃憦

@molusk
Copy link

molusk commented Feb 28, 2023

If I understand well, the next step would be to modify lixee.js to handle custom index (and/or alternative firmware as we are currently trying to push). Huge step for the JS rookie I am 馃槅

@Danit2
Copy link

Danit2 commented Feb 28, 2023

yes, when you will use the local index you have to write the same function as in this file:
https://github.com/Koenkk/zigbee-herdsman-converters/blob/a3e11ce5ffa9a02f61f296ecf990dc410e2691f0/lib/ota/zigbeeOTA.js#L34

But there i can not help. Sorry.

@github-actions
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Mar 31, 2023
@molusk
Copy link

molusk commented Apr 4, 2023

The issue should be kept open until someone finds a suitable solution.
I don't know JS well and don't have enough time right know to try to solve this issue.

@github-actions github-actions bot removed the stale Stale issues label Apr 5, 2023
@github-actions
Copy link
Contributor

github-actions bot commented May 5, 2023

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label May 5, 2023
@molusk
Copy link

molusk commented May 9, 2023

This issue should be kept open.

@github-actions github-actions bot removed the stale Stale issues label May 10, 2023
@djbiti1
Copy link

djbiti1 commented May 30, 2023

There is a workaround for this issue: #13681 (comment)
Not really a solution, but for a one-time update it is good enough.

@molusk
Copy link

molusk commented Jun 1, 2023

Indeed, but there was a discussion about how the creator of the device should manage the firmware variants to allow an elegant way of managing upgrades. Representatives of various zigbee managers (including z2m) were involved.
Nothing was done for z2m yet.
The workaround works but this issue should be kept open until somebody competent enough and willing to do it passes by :)

@github-actions
Copy link
Contributor

github-actions bot commented Jul 2, 2023

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Jul 2, 2023
@molusk
Copy link

molusk commented Jul 2, 2023

Do not close this issue, please.

@github-actions github-actions bot removed the stale Stale issues label Jul 3, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Aug 3, 2023

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Aug 3, 2023
@molusk
Copy link

molusk commented Aug 4, 2023

Please keep this open.

@github-actions github-actions bot removed the stale Stale issues label Aug 5, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Sep 4, 2023

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Sep 4, 2023
@molusk
Copy link

molusk commented Sep 4, 2023

Please don鈥檛.

@github-actions github-actions bot removed the stale Stale issues label Sep 5, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Oct 5, 2023

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Oct 5, 2023
@molusk
Copy link

molusk commented Oct 9, 2023

Not stale

@github-actions github-actions bot removed the stale Stale issues label Oct 10, 2023
Copy link
Contributor

github-actions bot commented Apr 8, 2024

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working stale Stale issues
Projects
None yet
Development

No branches or pull requests

4 participants