We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
That way we will be able to live update the status in the cloud panel and people can automate against it.
When fixed, also add to docs on website under configuration/remote/automation
The text was updated successfully, but these errors were encountered:
When user is not logged in, don't add sensor. When remote is being prepared, set it to "unavailable"
Sorry, something went wrong.
I don't want to add this to the website because we have our own reconnect handler and don't want that user does automate that self.
home-assistant/core#22076
We should put timeouts and guards in place if we want to. Not documenting something is not a protection 😉
pvizeli
No branches or pull requests
That way we will be able to live update the status in the cloud panel and people can automate against it.
When fixed, also add to docs on website under configuration/remote/automation
The text was updated successfully, but these errors were encountered: