Just ran it now and it ran correctly. The supervisor log shows:
2025-01-08 04:47:49.628 ERROR (MainThread) [supervisor.homeassistant.module] Can't backup Home Assistant Core config folder: [Errno 2] No such file or directory: '/data/homeassistant/nest/event_media/4fe7f1084398ae1e51fc3d8c6fb3b92f/1736294916-camera_motion.jpg'
Does this mean if a file is not found the backup fails?
Looks like the real error showed up in the host log
By the way, I run Acronis to back up all of my folders, custom settings configs, etc. Much, Much easier to restore when I make a mistake or the system doesnât like a custom update.
This is fuss about nothing.
Does haos use encryped file system? I donât think so. There are a zillion ways how to retrieve data from linux fs. So where is the problem?
Dev will fix things and there you go.
I think all should relax a bit, grab a beer, smoke a pot, or whatever.
Is there anyway to get better documentation on the backup. For example, last night the Auto backup failed apparently do to a connection issue ( donât understand why as it is stored locally) . How do I set retry on failure? I have used many commercials backup programs and they all had this.
I didnât ask for my backups to be encrypted, nor do I want them stored in the cloud. Why do you guys keep implementing stuff in a vacuum? We need an unencrypted option immediately.
So that means to me, nothing will happen to restore UI functionality quickly but we still want you to post youâre concerns.
In your earlier post you said that you were weary of the âbombardmentâ. Seems a bit hypocritical?
You managed to remove the add-ons backup from the UI whilst everybody was off site at CES. So again I find that a bit hard to swallow.
Lack of communication and transparency has created your problem. That is the most important issue to adress here!
We have 50 employees at Nabu Casa - some of us are working and doing things as planned, several key people are currently in Las Vegas at an event planned long before this release. Not everyone is required to sit on the forums and answer people. And I will not force my colleagues to read through angry messages when I can be their shield.
I hear that poor communication is the problem, and we have recognized that, but it is unreasonable to continue to ask for responses every day. I will reiterate - even though you donât see us typing, we are watching.
I have to agree with @MissyQ so she knows she is not standing alone in this.
I followed this thread a bit and to me it feels like a âtotal shit stormâ(sorry for the used words) because some people would like to see a feature a bit different.
And no of the devs has actually said actually said not listening to the request. If if read the official responses, all is under consideration and it will take some time.
and I can understand that,
I think this feature is a great contribution to the project,
Too maybe let cooler heads prevail, I think there are 750 comments because of the vacuum that was left. And social media hates a vacuum. Whatâs more is there is a large communication breakdown (which you fully acknowledged, Iâm merely stating, not poking), to the point where two involved moderators canât agree on how they interpret the course forward.
I think, and maybe Iâm wrong in this assumption, but at this point, no one is asking for the feature to be fixed on 2025.1.2 or whatever. But the reasoning behind the feature? Some clarity on the roadmap of the feature? I think those would go a long way to calming the bombardment. And to the best of my knowledge (happy to be wrong), those have not been provided. Just my two cents.
The 750 comments âbombardmentâ is only partially due to badly designed and communication change of existing functionality, itâs due to the initial follow-up. Patronizing and condescending response lecturing people âthatâs now MVP worksâ (no it doesnât) added the major fuel to the fire. âMy way or highwayâ is not something you should ever response with, no matter how right you believe you are
I absolutely do not disagree with you. There were missteps that happened with the communication around this release - we need to fix those, but just as with fixing code making sure the communication lands correctly takes time. Believe me when I say this thread has been the focus for most of us all week.
However, thereâs also a problem in that not everyone is reading all of the posts, or they are reading too much into one thing. Itâs easy to reply to someone 100 comments ago and not read anything else below it.
There are several factors at play here, but seriously - patience is needed. Even when we have taken the time to post something long, itâs not good enough - faster responses will (and already did) make things worse.
*Just to be illustrative*: I was off for 2 weeks, came back to work with the worst head cold I've ever had and a 500 post release thread of very upset people. It's been a hell of a week.
Hey, I didnât say you werenât being âbombardedâ. I said your post was asking for more.
I am merely highlighting some not joined up responses here. And if you construed my comment as being angry then I apologise. (Correct spelling BTW )
I am glad everybody is listening and we are getting some communication.
Thank you for the response. I hope people read it and take to heart that the people on the other end of the computer screens are aware of the thread and the focus given, and that details will be forthcoming
I did misread your tone, thank you for clarifying.