|
| 1 | +--- |
| 2 | +layout: page |
| 3 | +title: "Washington State DOT" |
| 4 | +description: "Instructions on how to integrate WSDOT data into your home." |
| 5 | +date: 2017-01-21 18:00 |
| 6 | +sidebar: true |
| 7 | +comments: false |
| 8 | +sharing: true |
| 9 | +footer: true |
| 10 | +logo: wsdot.png |
| 11 | +ha_category: Transport |
| 12 | +ha_iot_class: "Cloud Polling" |
| 13 | +ha_release: 0.37 |
| 14 | +--- |
| 15 | + |
| 16 | +The `wsdot` sensor will give you travel time information from the [Washington State Department of Transportation](http://wsdot.com/). |
| 17 | + |
| 18 | + |
| 19 | + |
| 20 | +First, you need to get a free Traveler Information `api_key` from the [WSDOT API webpage](http://wsdot.com/traffic/api/). Just enter your email address to instantly get the key. |
| 21 | + |
| 22 | + |
| 23 | +Once you have the code, create `wsdot` sensors by editing your `configuration.yaml` file as follows: |
| 24 | + |
| 25 | +```yaml |
| 26 | +# Example configuration.yaml entry |
| 27 | +sensor: |
| 28 | + - platform: wsdot |
| 29 | + api_key: XXXXXXXXXXXXXXXXXXXXXXX |
| 30 | + travel_time: |
| 31 | + - id: 95 |
| 32 | + name: I-90 Eastbound HOV |
| 33 | +``` |
| 34 | +
|
| 35 | +Configuration variables: |
| 36 | +
|
| 37 | +- **api_key** (*Required*): Your `api_key` from WSDOT. |
| 38 | +- **scan_interval** (*Optional*): How frequently to query for new data. Default: 3 minutes. |
| 39 | +- **travel_time** array (*Required*): List of routes. |
| 40 | + - **id** (*Required*): Name of the route. |
| 41 | + - **name** (*Optional*): Name of the route. Default just uses `id`. |
| 42 | + |
| 43 | +Figuring out which Travel Time ID (`id`) is associated with your routes is a bit of a challenge. If you visit `http://wsdot.com/Traffic/api/TravelTimes/TravelTimesREST.svc/GetTravelTimesAsJson?AccessCode=[your_api_key_here]` substituting your `api_key`, you will get a list of all available routes. Search through it and then find the key `TravelTimeID`. That tells you the number you need. |
| 44 | + |
| 45 | +Some common examples include: |
| 46 | +``` |
| 47 | + 73 Issaquah-Seattle (WB PM) |
| 48 | + 74 Seattle-Issaquah (EB AM) |
| 49 | + 75 HOV Issaquah-Seattle (WB REV) |
| 50 | + 76 Issaquah-Seattle (WB REV) |
| 51 | + 77 HOV Redmond-Seattle (WB PM) |
| 52 | + 78 HOV Seattle-Redmond (EB AM) |
| 53 | + 79 Redmond-Seattle (WB PM) |
| 54 | + 80 Seattle-Redmond (EB AM) |
| 55 | + 81 HOV Redmond-Seattle via I-90 (WB PM) |
| 56 | + 82 HOV Seattle-Redmond via I-90 (EB AM) |
| 57 | + 83 Redmond-Seattle via I-90 (WB PM) |
| 58 | + 84 Seattle-Redmond via I-90 (EB AM) |
| 59 | + 85 HOV Redmond-Seattle via I-90 (WB REV) |
| 60 | + 86 Redmond-Seattle via I-90 (WB REV) |
| 61 | + 89 Bellevue-Seattle via 520 (WB PM) |
| 62 | + 90 HOV Bellevue-Seattle via 520 (WB PM) |
| 63 | + 91 HOV Seattle-Bellevue via 520 (EB AM) |
| 64 | + 92 Seattle-Bellevue via 520 (EB AM) |
| 65 | + 93 Bellevue-Seattle via I-90 (WB PM) |
| 66 | + 94 HOV Bellevue-Seattle via I-90 (WB PM) |
| 67 | + 95 HOV Seattle-Bellevue via I-90 (EB AM) |
| 68 | + 96 Seattle-Bellevue via I-90 (EB AM) |
| 69 | + 97 Bellevue-Seattle via I-90 (WB REV) |
| 70 | + 98 HOV Bellevue-Seattle via I-90 (WB REV) |
| 71 | +``` |
| 72 | + |
| 73 | +<p class='note info'> |
| 74 | +WSDOT does provide information about ferry schedules, mountain passes, tolls, etc. but so far only Travel Time data is available in this component. |
| 75 | +</p> |
| 76 | + |
| 77 | +Here's an example of the sensor in use: |
| 78 | + |
| 79 | +<p class='img'> |
| 80 | + <img src='{{site_root}}/images/screenshots/wsdot_sensor.png' /> |
| 81 | +</p> |
| 82 | + |
0 commit comments