How to do OTA? about z03mmc

[Nab0y]

Mine is directly conected to Cordinator.

Yes, it's not my case. You can try to forcefully make the sensor take the firmware from a local folder.

After that, you'll need to restart Z2M since the configuration file has been modified. And once you're done, don't forget to revert everything back to its original state.

[shirou93]

Mine is directly conected to Cordinator.

Yes, it's not my case. You can try to forcefully make the sensor take the firmware from a local folder.

After that, you'll need to restart Z2M since the configuration file has been modified. And once you're done, don't forget to revert everything back to its original state.

Thanks Your solution working :)

[Mostalk]

Use this in "OTA index override"

[
     {
         "fileVersion": 268775425,
         "manufacturerCode": 4417,
         "imageType": 515,
         "url": "https://github.com/devbis/z03mmc/releases/download/1.0.5/1141-0203-10053001-z03mmc.zigbee"
     }
]

[Mostalk]

@kubert96
Hmm, it worked for me. With such an error, it helped me to reset the battery.

In any case, you can just wait until @devbis updates the OTA index repository.

[kubert96]

OK :D

info 2023-10-31 13:05:42MQTT publish: topic 'zigbee2mqtt/Office Aquara Temp', payload '{"battery":90,"humidity":62.36,"linkquality":102,"temperature":24.06,"update":{"installed_version":268709889,"latest_version":268775425,"progress":0,"state":"updating"},"update_available":false,"voltage":2900}'

Finaly working. With Local File. :)

@Nab0y thank you :)

[Nab0y]

Hey Guys , Is there any way to go back to the original firmware or any ATC firmware? Using OTA or another option?

https://github.com/devbis/z03mmc#flashing-firmware-with-usb-to-uart

[Psytoshgen]

Koenkk/zigbee-OTA#386
PR to track

Надо бы это добавить в инструкцию по откату назад. Долго ходил вокруг, да около, пока не наткнулся на это.

тут все просто.... останавливаем z2m залазим в файл state.json и в latest version пишем (например файл на который хотим называется 1141-0208-01143001-ZMHOC401N) в последней версии прописываем 01143001 и после запуска z2m видим приглашение обновиться.... а вот как обновиться с альтернативной, еще не придумал...

[kubert96]

error 2023-10-31 07:19:44Update of 'Office Aquara Temp' failed (Device didn't respond to OTA request)

[kubert96]

info 2023-10-31 08:42:28MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/update', payload '{"data":{"id":"Office Aquara Temp"},"error":"Update of 'Office Aquara Temp' failed (Device didn't respond to OTA request)","status":"error","transaction":"6594s-2"}'
error 2023-10-31 08:42:28Update of 'Office Aquara Temp' failed (Device didn't respond to OTA request)

[devbis]

Koenkk/zigbee-OTA#386

PR to track

[Nab0y]

One of my eight sensors also refuses to update via OTA, but it reports a slightly different error.
Info 2023-10-31 14:12:00MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/update', payload '{"data":{"id":"Температура влажность кухня"},"error":"Update of 'Температура влажность кухня' failed (Timeout: device did not request any image blocks)","status":"error","transaction":"j9w29-1"}' Error 2023-10-31 14:12:00Update of 'Температура влажность кухня' failed (Timeout: device did not request any image blocks)
I suspect that it's because this sensor is the only one currently connected not directly to the coordinator but to the nearest router, and the issue might not be with the sensor itself but with the router, which seems to be refusing to pass on the update through itself. Well, that's my theory, at least.

[kubert96]

Mine is directly conected to Cordinator.

[devbis]

device did not request any image blocks

usually means that OTA image and fw version is the same. But if it is not, you may replug the battery and push OTA again

[Nab0y]

device did not request any image blocks

usually means that OTA image and fw version is the same. But if it is not, you may replug the battery and push OTA again

That's what I intend to do, but it will take me a few hours to physically reach the sensor :)

[adorobis]

usually means that OTA image and fw version is the same. But if it is not, you may replug the battery and push OTA again

For me some devices don't show correct fw version information in z2m (not in HA) although they were updated successfully. I have such case for 1 of 3 of the temp sensors but also some other devices (e.g. xiaomi wall switches). Re-inserting batteries and clicking "check for updates" does not help. Example below. The first two were updated OTA today, the last one was flashed straight with the latest version. Anyway it seems a z2m issue as it is not limited to those sensors.

[devbis]

@adorobis You can read newer values for devices using dev console for a device

[adorobis]

I get either timeout or nothing changes. Still shows the old version in z2m.

[fraddygil]

Hey Guys , Is there any way to go back to the original firmware or any ATC firmware?
Using OTA or another option?

[beeline09]

Koenkk/zigbee-OTA#386

PR to track

Надо бы это добавить в инструкцию по откату назад. Долго ходил вокруг, да около, пока не наткнулся на это.

[beeline09]

Koenkk/zigbee-OTA#386
PR to track

Надо бы это добавить в инструкцию по откату назад. Долго ходил вокруг, да около, пока не наткнулся на это.

тут все просто.... останавливаем z2m залазим в файл state.json и в latest version пишем (например файл на который хотим называется 1141-0208-01143001-ZMHOC401N) в последней версии прописываем 01143001 и после запуска z2m видим приглашение обновиться.... а вот как обновиться с альтернативной, еще не придумал...

Да, спасибо, я именно так и сделал) с альтернативной имеется ввиду не вашей?