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
Add documentation for new RMV public transport sensor #5947
Conversation
- station: STATION_OR_STOP_ID | ||
``` | ||
|
||
Configuration variables: |
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.
Please use our configuration tag syntax instead to describe the config options.
https://developers.home-assistant.io/docs/en/documentation_create_page.html#configuration
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.
Ok. Thanks for the info. I updated the config options.
Looks like the build failed on an unrelated page. |
# Example configuration.yaml entry | ||
sensor: | ||
- platform: rmvtransport | ||
nextdeparture: |
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.
Isn't this called next_departure
in the merged version? (Which by the way is not consistent with the MVG sensor, where we have nextdeparture
and timeoffset
. Not sure if this should be handled consistently.)
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.
Thank's for pointing it out. I agree with your remark about consistency, but it actually is PEP 8 compliant. So it would rather make sense to change the names of the MVG sensor, no?
This needs to be rebased in order to fix the build. Will take care of that. |
Rebased, awaiting build results before starting a review. |
Looks good to go! 🎉 |
* Initial documentation for the rmvtransport sensor. * Fix name * Fix typo * Added missing variable description for max number of journeys. * Minor wording fix * Fix setting names after code change. * Use configuration tag syntax. * Add logo. * Update logo file name. * Fix liquid syntax error. * Fix config setting name. * ✏️ Markdown tweaks
Description:
This adds documentation for a new public transport sensor for the Rhein-Main area. It is based upon PyRMVtransport which uses public data from opendata.rmv.de.
Pull request in home-assistant (if applicable): home-assistant/core#15814
Checklist:
current
. New documentation for platforms/components and features should go tonext
.