Skip to content

modify index.json snzb-01m_v1.0.5.ota add telinkEncrypted#1078

Open
Oniums wants to merge 1 commit intoKoenkk:masterfrom
Oniums:patch-1
Open

modify index.json snzb-01m_v1.0.5.ota add telinkEncrypted#1078
Oniums wants to merge 1 commit intoKoenkk:masterfrom
Oniums:patch-1

Conversation

@Oniums
Copy link
Contributor

@Oniums Oniums commented Feb 28, 2026

modify index.json snzb-01m_v1.0.5.ota add telinkEncrypted

modify index.json snzb-01m_v1.0.5.ota add telinkEncrypted
@Oniums
Copy link
Contributor Author

Oniums commented Feb 28, 2026

I’m not sure whether this change is correct. When I previously submitted the SNZB-01M OTA image, I had included telinkEncrypted, but it seems it was removed later.

However, when I tested OTA in my own Zigbee2MQTT environment using a lower-version SNZB-01M device image, I saw the same error in the logs as mentioned earlier about failing to parse Telink-encrypted OTA.

image

So I added the following field in my Zigbee2MQTT configuration.yaml and used a local my_index.json to test OTA.

image

In my_index.json, I used the same configuration as in this repository, but added telinkEncrypted.:

image

After restarting Zigbee2MQTT, OTA worked normally.

@Oniums
Copy link
Contributor Author

Oniums commented Feb 28, 2026

This started because some users reported that SNZB-01M could not complete OTA normally in Zigbee2MQTT, so I ran the tests and steps above.

When you have time, could you please take a look and let me know whether this is the right way to handle it, or if there is a better approach?Thank you!

@andrei-lazarov
Copy link
Contributor

Hi. What is your Z2M version?
(I think telinkEncrypted is not needed on the latest version)

@Oniums
Copy link
Contributor Author

Oniums commented Feb 28, 2026

zigbee2mqtt-2.6.3

image

@andrei-lazarov
Copy link
Contributor

Well, please update Z2M and check again.
Latest is 2.8.0, very soon 2.9.0.

@Oniums
Copy link
Contributor Author

Oniums commented Mar 2, 2026

I tried again later with Z2M version 2.8.0 and attempted to OTA the SNZB-01M directly, it still failed.But this time the failure reason seems different.
image
[2026/3/2 13:40:15] z2m: OTA updating '0xa4c1382e1c9f24cd' to latest firmware
[2026/3/2 13:40:21] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0xa4c1382e1c9f24cd', payload '{"action":"single_button_4","battery":100,"linkquality":255,"update":{"installed_version":4100,"latest_release_notes":null,"latest_source":"https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/images/Sonoff/snzb-01m_v1.0.5.ota","latest_version":4101,"state":"idle"}}'
[2026/3/2 13:40:41] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0xa4c1382e1c9f24cd', payload '{"battery":100,"linkquality":255,"update":{"installed_version":4100,"latest_release_notes":null,"latest_source":"https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/images/Sonoff/snzb-01m_v1.0.5.ota","latest_version":4101,"state":"available"}}'
[2026/3/2 13:40:41] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/update', payload '{"data":{},"error":"OTA update of '0xa4c1382e1c9f24cd' failed (fetch failed)","status":"error","transaction":"jh3om-2"}'
[2026/3/2 13:40:41] z2m: OTA update of '0xa4c1382e1c9f24cd' failed (fetch failed)

Z2M Frontend Setting:
image

@andrei-lazarov
Copy link
Contributor

fetch failed

Normally you get this error when there is no internet access.

Can you access these links from the same computer where Z2M is running?

https://raw.githubusercontent.com/Koenkk/zigbee-OTA/refs/heads/master/index.json

https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/images/Sonoff/snzb-01m_v1.0.5.ota

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.

2 participants