Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google Drive Backup #203

Closed
Opontios opened this issue Jun 2, 2023 · 2 comments
Closed

Google Drive Backup #203

Opontios opened this issue Jun 2, 2023 · 2 comments

Comments

@Opontios
Copy link

Opontios commented Jun 2, 2023

First thanks for the very interesting and helpful project, I've been using it from the very begining. But it's strange to me that nobody mentioned the following issue. If you have the Google Drive Backup add-on installed, it uses 2 additional entities for monitoring the success of the backup creation, 'sensor.backup_state' and 'binary_sensor.backups_stale'. Nobody is using those entities in their dashboard or in an automation, as me? Because if you do, spook finds them unknown at every reboot of the system and ceates a warning, probably because of the fact, that they become available after the full system reboot. Can it be somehow fixed? Thanks
Untitled

@frenck
Copy link
Owner

frenck commented Jun 2, 2023

it uses 2 additional entities for monitoring the success of the backup creation, 'sensor.backup_state' and 'binary_sensor.backups_stale'.

They have been reported before, see #18

The problem is, that those states are directly injected by the add-on into the state machine, without actually having entities (it bypasses / incorrect is using the API to inject states).

The message is therefore correct, those entities do not exist. The states might appear some time (once the Google Drive add-on injected them externally).

There is not much I can do about these. In the next version you can opt to ignore these repairs to (although that is suboptimal, it is the best I can do).

../Frenck

@frenck frenck closed this as not planned Won't fix, can't repro, duplicate, stale Jun 2, 2023
@Opontios
Copy link
Author

Opontios commented Jun 2, 2023

I red those posts. Now it's all clear to me. Thanks for the quick response and keep up the good work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants