mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-14 12:56:54 +00:00

* Add initial NextBus documentation * Update nextbus docs to meet standards * Update ha_releaes Setting it to the next relese * Update nextbus docs to describe how to get config values * Add sensor to ha_category Co-Authored-By: ViViDboarder <ViViDboarder@gmail.com> * ✏️ Tweak After this we will merge it * ✏️ Change file name
1.5 KiB
1.5 KiB
layout, title, description, date, sidebar, comments, sharing, footer, logo, ha_category, ha_iot_class, ha_release
layout | title | description | date | sidebar | comments | sharing | footer | logo | ha_category | ha_iot_class | ha_release | ||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
page | Public Transit (Nextbus) | Instructions on how to use public transit data from Nextbus in Home Assistant. | 2019-02-20 00:00 | true | false | true | true | train.png |
|
Local Polling | 0.93 |
The nextbus
sensor will give you the next departure time and associated data from your public transit station/stop. The data comes from NextBus, which provides real time transit data for a number of transit authorities.
It is possible to get the tag information from the NextBus website.
- Visit https://www.nextbus.com/
- Use the drop downs to select the transit system, route, direction, and stop
- Extract the tags from the URL. It is constructed with the following pattern:
https://www.nextbus.com/#!/<agency>/<route>/<direction>/<stop>
If tags are incorrect, valid ones will be displayed in the logs as a convenience.
# Example configuration.yaml entry
sensor:
- platform: nextbus
agency: AGENCY_TAG
route: ROUTE_TAG
stop: STOP_TAG
{% configuration %} agency: description: The agency tag from NextBus. required: true type: string route: description: The route tag from NextBus. required: true type: string stop: description: The stop tag from NextBus. required: true type: integer name: description: Name to use in the frontend. required: false default: - type: string {% endconfiguration %}