Update of Sonoff ZBMINIL2 fails with baffling error code

[PedroKTFC]

The problem

ZHA reports that a firmware update from 0x0000100a to 0x0000100e is available. However, when install is clicked there's a pause, the following error appears in the log - Status.FAILURE: 1 - and the device firmware is unchanged.

What version of Home Assistant Core has the issue?

core-2024.2.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ZHA

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zha

Diagnostics information

home-assistant_zha_2024-02-11T13-04-19.382Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

See file attached (I hope!)

Additional information

No response

[home-assistant]

Hey there @dmulcahey, @Adminiuga, @puddly, @TheJulianJES, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zha can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zha Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

zha documentation
zha source
_{^{(message by IssueLinks)}}

[puddly]

Can you enable ZHA debug logging and retry the update? Your error log unfortunately contains no context for the error. Thanks!

[PedroKTFC]

Can you explain what you need in a bit more detail please? My log was obtained with ZHA debugging enabled. What context do you need?

[puddly]

The log doesn't contain any debug logging lines for ZHA itself. How did you enable it?

[PedroKTFC]

home-assistant_zha_2024-02-11T22-32-47.804Z.log
I've uploaded another one in case I cocked it up last time. I got it by going to the ZHA automation page and clicking on "Enable debug logging", then trying the update and, after it fails, disabling debug logging and saving the file that produces. Should I be doing something different?

[Netpoet]

In case I can help somehow (still quite unexperienced with logging and debugging here):
I seem to have the same type of error message.

Situation here:
I have HAOS 2024.2.1 x86_64 (6.1.74-haos) with 7 SONOFF ZBMINIL2s running, of which some are the "extreme" model, some are not. A few days back, HA started offering firmware updates from 0x0000100a to 0x0000100e for them, rather one after another than all at the same time. The updates take approx. 10 minutes each if they work, and 3 of the 7 offered updates have worked, the others have not.

The update notification looks like this:

For those where the update has not worked, the error message is this:
"Fehler beim Aufrufen des Diensts update/install. Update was not successful - result: <Status.FAILURE: 1>"
("Error loading the service" […])

What do you think I should do to locate (and ideally fix) the error?

[PedroKTFC]

The log doesn't contain any debug logging lines for ZHA itself. How did you enable it?

Did my follow up help?

[PedroKTFC]

@puddly Just nudging you in case you missed my reply. Is there anything more I can do to help diagnose this?

[kimhartlev]

I have exactly the same problem. In fact I have not been able to update a single one of my ~15 ZBMINIL2s. The updates fails when it is around 60-70% complete. The process is incredibly slow (while testing right now it has taken 26 mins to get to 47%)

[puddly]

@kimhartlev Enable ZHA debug logging before you start an OTA update and disable it after one fails to generate a debug log.

[PedroKTFC]

Wow! I didn't know you got an Installing (x%) display!! Mine never gets that far, hence I've never seen it!

[PedroKTFC]

That's what I did to get my logs. Were they not useful?

[kimhartlev]

This time it got stuck at 99%...

home-assistant_zha_2024-02-29T09-55-20.038Z.log.zip

[WillyW72]

Did you already tried to a powercycle. After that I was able to update the device.

[puddly]

Please try the beta. OTA has had many improvements in it.

[PedroKTFC]

Do you mean the beta of HA core? Or is there a way of just trying a beta of ZHA (if so how)?

[puddly]

Yes, the HA Core beta.

[PedroKTFC]

Ah! Unfortunately I don't install beta releases nor the first and sometimes second release of core as my HA runs my house in some detail and I want to minimise the risk of failure. I don't have a test system I can try things out on. Perhaps I should!

I'll have to wait until 2024.3

[PedroKTFC]

I've updated HA to 2024.3.0 and after an initial failure, the firmware update has worked. Many thanks for your work.

[PedroKTFC]

I have another of these devices in a different house and this one isn't updating however many times I try. It usually starts ok but then fails anywhere from 3% up to around 70%. I've attached a debug log. I suspect the update needs to be able to retry more. This device is located in the UK where there's a smart electricity meter. I believe these meters use ZigBee although very locked down. I wonder therefore if it's a "noisy" environment so the probability of failure in transmitting a packet is higher?
home-assistant_zha_2024-03-20T10-17-39.477Z.log

[Netpoet]

This might not solve your problem(s), but it solved mine.
My problem was that some ZHA devices (in my case, Sonoff ZBMINIL2, didn't update, no matter how often I tried, how one-after-another I tried, or how much time I gave the update.
My solution was that I replaced my SkyConnect stick (that I used for ZHA) with a Zigstar UZG (https://uzg.zig-star.com/product/) and moved all devices to Z2M. In Z2M I have been able to update every single one of the devices, slowly but steadily.
Yes, this required me to basically rebuild my entire Zigbee network, in Z2M instead of ZHA. It took some time but I am much happier with the situation now. No more odd dropouts of devices, and the Z2M overview of devices is -- IMHO -- much more comprehensive.

[PedroKTFC]

Thanks for the suggestion. I have thought about Z2M but I'm loath to change. I have quite a few devices and the pain of changing isn't yet worth it. In the longer term I'll probably introduce matter and see how that goes. Only if my ZigBee estate becomes really poor will I make the change. So far it runs ok.

[Rudo1111]

It behaves the same way for me, 3 times the device updates OK and 1 time it doesn't update continuously, it ends at 75% or 85%. I do not understand.

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.