From 3e3f1cfa299bc54475e8b0fbcf715f83275ab520 Mon Sep 17 00:00:00 2001 From: Ian Date: Tue, 19 Sep 2023 08:11:11 -0700 Subject: [PATCH] Update nextbus docs for config flow (#27198) --- source/_integrations/nextbus.markdown | 40 ++------------------------- 1 file changed, 2 insertions(+), 38 deletions(-) diff --git a/source/_integrations/nextbus.markdown b/source/_integrations/nextbus.markdown index 641bbd01467..105671d6b92 100644 --- a/source/_integrations/nextbus.markdown +++ b/source/_integrations/nextbus.markdown @@ -6,6 +6,7 @@ ha_category: - Transport ha_iot_class: Cloud Polling ha_release: 0.93 +ha_config_flow: true ha_codeowners: - '@vividboarder' ha_domain: nextbus @@ -16,41 +17,4 @@ ha_integration_type: integration The `nextbus` sensor will give you the next departure time and associated data from your public transit station/stop. The data comes from [NextBus](https://www.nextbus.com), which provides real time transit data for a number of transit authorities. -It is possible to get the tag information from the NextBus website. - - 1. Visit https://www.nextbus.com/ - 2. Use the drop downs to select the transit system, route, direction, and stop - 3. Extract the tags from the URL. It is constructed with the following pattern: - - https://www.nextbus.com/#!//// - -If tags are incorrect, valid ones will be displayed in the logs as a convenience. Note that the `` tag is not used in this integration. - -```yaml -# 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: string -name: - description: Name to use in the frontend. - required: false - default: - - type: string -{% endconfiguration %} +{% include integrations/config_flow.md %} \ No newline at end of file