❓ [Question]: Backup fails and location becomes unavailable after updating HomeAssistant to 2026.3.4

[hmayer1980]

Contact details ☎️

No response

What's your question? 🤔

I have yesterday upgraded Homeassistant from 2026.3.1 to 2026.3.1.
Today I was wared that the Backup for pCloud failed. The logs show

I tried to reload the Integration afterwards - then the Backup location also became unavailable.

Now I am not sure how to proceed?
Remove the Backup location / Integration?

Context 🧩

No response

What have you tried? 🛠️

No response

[ghotso]

Thanks for your report! 🙌
I’ve automatically improved the issue title to better reflect the problem you described.
A team member will take a closer look as soon as possible.

[nils1981]

I have the same issue. Also tried to reconfigure the pcloud integration without success.

[ghotso]

Thanks for raising this! I’ll take a look and try to release a fix in the next few days.
It would also help if you could specify which Home Assistant environment you’re using (e.g., Docker, VM).

[nils1981]

Thank you much! I am using a VM on Proxmox.

[hmayer1980]

I am using HAOS. I could resolve the problem by removing the "Hub" / Integration - restarting - and newly adding the integration. To strange.

[nils1981]

That also worked for me. Very strange! .... Thank you very much!

[nils1981]

I updated to 2026.4.0 yesterday and same thing happened again. I applied again same procedure to recover as mentioned above. There seems to be some kind of issue/conflict since 2026.3.4. It's very strange as alls works fine (including restarts) after re-adding it with procedure above.
@ghotso - would you mind to have a look? Thank you very much.

[bkuehnel795]

Hi & good day!
Same here, it started w/ 2026.3.4.
All sensors show a steady response / data, but prior to the first failed attempt, the values become strange...
Like the attached...

Only a re-install helps...

[ghotso]

Hi 👋
Thanks for the additional info - that helps a lot!
And sorry for not providing a fix yet. I’m a bit short on time at the moment, but I’ll try to release a fixed version by Sunday at the latest 🙂