-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
Updated VOC documentation #2215
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
Conversation
@molobrakos, thanks for your PR! By analyzing the history of the files in this pull request, we identified @fabaff and @lamiskin to be potential reviewers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good with some minor feedback.
|
||
To use Volvo On Call in your installation, add the following to your `configuration.yaml` file: | ||
|
||
```yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good but I suggest you have a minimal example and this one as a advanced example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, I'll fix. Am I supposed to add sensor.volvooncall, switch.volvooncall etc as well? (currently they can only instantiated indirectly by the component, not by the user)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated.
Hello! Thank you! |
@tomoqv Please keep support to the forums or gitter chat. |
Description:
The Volvo on call device tracker was transformed into its own component.
Pull request in home-assistant (if applicable): home-assistant/home-assistant#