You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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).
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
The text was updated successfully, but these errors were encountered: