There is a new HAOS update available. I’ve tested here and the exclusion worked properly for me. Could you please confirm if it worked for you or if you still having an issue?
I want to release a new version of the blueprint soon, with more logs, so I wanna know if will need log around this.
Hi @SilverLeaf, my apologies for my delay in a response.
Could you please give me one more information from Developers tools > States?
I wanna know if you have the entity sensor.backup_state and it’s attributes.
Aha!
I believe this sensor is only available when Google Drive Backup add-on is running, and I was using this in the automation to skip a new backup if another backup was done in the past 2 hours.
Now I know why this isn’t working for you (and probably for other people also).
I haven’t changed this one to not mess up with existing implementations, so if you want to use that new one, create a new automation based on that one and remove your previous automation based on the old blueprint.
Could you please take a look at the sensor sensor.samba_backup and let me know exactly how is the format of name and for the value of the attribute last backup?
You can see this under Developer Tools, selecting tab States and then typing the sensor name at the search field. (Please make sure Attributes is selected, so you can see the attributes)
I don’t have Samba backup, so I need your help to make sure I’m doing right on the part where the automation should wait for the backup to complete before start the updates.
You can use the “first day of the month” input to prevent running it on the beginning at the month. It’s not the same you are asking for, but it might help for now.
I will take a look on how to prevent major releases (selectable via another input) and come back.
By the way, I would suggest you to use this newer Blueprint instead: Scheduled auto-update for Home Assistant as this one is based on Schedule helper (which provides more flexibility to run the updates in the right time windows, and not only a time to trigger per day).
It is interesting… No timezone info on the last backup timestamp…
Do you know if this is UTC or local time? I mean, do you run your backup at around 02:00AM local time?