Just went to update some of my switches and now I receive the below message:
Failed to check if update available for 'Side Deck' (The device 'VZM31-SN' is not supported for OTA at this time.)
I noticed this starting yesterday after I updated Z2M to 1.28.4-1. I’ll roll back my HA image if necessary but wanted to check if this is a known issue or if I need to adjust a setting somewhere before I restore a backup.
Thanks!
i’m seeing the same issue on Z2M Edge
Info 2022-12-02 09:19:13Checking if update available for 'Attic Light'
Debug 2022-12-02 09:19:13Check if update available for '0x040d84fffe05f387' (VZM31-SN)
Debug 2022-12-02 09:19:13Using endpoint '1'
Debug 2022-12-02 09:19:15Received Zigbee message from 'Attic Light', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":16908808,"imageType":257,"manufacturerCode":4655}' from endpoint 1 with groupID 0
Debug 2022-12-02 09:19:15Got OTA request '{"fieldControl":0,"manufacturerCode":4655,"imageType":257,"fileVersion":16908808}'
Info 2022-12-02 09:19:15MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/check', payload '{"data":{"id":"Attic Light"},"error":"Failed to check if update available for 'Attic Light' (The device 'VZM31-SN' is not supported for OTA at this time.)","status":"error","transaction":"a9o7j-1"}'
Error 2022-12-02 09:19:15Failed to check if update available for 'Attic Light' (The device 'VZM31-SN' is not supported for OTA at this time.)
Debug 2022-12-02 09:19:15Error: The device 'VZM31-SN' is not supported for OTA at this time. at getImageMeta (/app/node_modules/zigbee-herdsman-converters/lib/ota/inovelli.js:11:15) at runMicrotasks (<anonymous>) at processTicksAndRejections (node:internal/process/task_queues:96:5) at isNewImageAvailable (/app/node_modules/zigbee-herdsman-converters/lib/ota/common.js:265:18) at Object.isUpdateAvailable (/app/node_modules/zigbee-herdsman-converters/lib/ota/common.js:256:23) at OTAUpdate.onMQTTMessage (/app/lib/extension/otaUpdate.ts:192:39)
Debug 2022-12-02 09:19:18Received Zigbee message from 'Attic Light', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":16908808,"imageType":257,"manufacturerCode":4655}' from endpoint 1 with groupID 0
Debug 2022-12-02 09:19:18Device 'Attic Light' requested OTA
Same issue for me.
OTA works if you restore 1.28.2.
Cool I’ll roll back to a backup tonight. The only other Zigbee devices I have are Hue bulbs and the OTA check works without error for those so not sure if this is a Z2M thing or an Inovelli thing or a combo thereof.
It is a combination of the Inovelli file server using compression and an issue in a Z2M dependency. I have made a PR to Z2M to work around the issue in the dependency.
Workaround to Address Axios Issue by nathanfiscus · Pull Request #5069 · Koenkk/zigbee-herdsman-converters (github.com)
Do you know I can make a change in nginx to serve the file a different way as a workaround?
My cursory reading of the issues at play is that Z2M got hit with a buggy Axios library version that’s not handling header responses correctly (maybe just ones with brotli? IDK).
I guess you could try switching to gzip instead of brotli and see if that fixes it but hopefully Z2M and/or Axios will push a fix sooner than later.
Thanks. I am doing that now.
Back on Z2M 1.28.2-1, and OTA check succeeds, but it says my devices on 2.06 are up to date. I was expecting to see 2.08 available, according to the firmware change log. Anyone else getting the 2.08 update to show up?
Thank you! Yes, it turns out I am already on 2.08. 
Any other advice here? I cant downgrade Z2M and my blues are stuck on 2.00 (checked w/ genBasic in dev console).
I also am unable to change the doubleTapClearNotifications option in Z2M which i am hoping is fixed with the update to 2.08
I think we are stuck waiting at the moment. Looking at the past Z2M updates, they all published on the first of the month. I’m hoping that will be the case with the next update which I believe has the fix for the OTA problem.
It appears that whatever was wrong on the back end of Z2M has been fixed. The two Blue switches that I had wouldn’t update just got the notification that there was new firmware. They are updating now. I’m still on Z2M 1.28.4-1
Yup, I see it too. Thanks for pointing it out.
And after having updated a bunch of my switches, some of the updated ones still say they have 2.00 and no updates available.
I had that happen with a couple of switches. This post has some info on how to manually pull the correct firmware version so that it will show 2.08 after an update.
Did you find a solution for this?
