jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-05-03 17:48:59 +00:00
Code Issues Packages Projects Releases Wiki Activity
home-assistant.io/source/_components/sensor.uber.markdown
Fabian Affolter c72ec348e4 Minimizing of the configuration sample (#1043)
2016-10-02 17:14:35 +02:00

2.7 KiB
Raw Blame History

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 Uber How to integrate Uber in Home Assistant 2016-03-24 23:04 true false true true uber.png Transport Cloud Polling 0.16

The uber sensor will give you time and price estimates for all available Uber products at the given start_latitude and start_longitude.The ATTRIBUTES are used to provide extra information about products, such as estimated trip duration, distance and vehicle capacity. By default, 2 sensors will be created for each product at the given start location, one for pickup time and one for current price. The sensor is powered by the official Uber API.

You must create an application here to obtain a server_token.

To enable this sensor, add the following lines to your configuration.yaml file:

# Example configuration.yaml entry
sensor:
  - platform: uber
    server_token: 'BeAPPTDsWZSHLf7fd9OWjZkIezweRw18Q8NltY27'
    start_latitude: 37.8116380
    start_longitude: -122.2648050

Configuration variables:

  • server_token (Required): A server token obtained from developer.uber.com after creating an app.
  • start_latitude (Required): The starting latitude for a trip.
  • start_longitude (Required): The starting longitude for a trip.
  • end_latitude (Optional): The ending latitude for a trip. While end_latitude is optional, it is strongly recommended to provide an end_latitude/end_longitude when possible as you will get more accurate price and time estimates.
  • end_longitude (Optional): The ending longitude for a trip. While end_longitude is optional, it is strongly recommended to provide an end_latitude/end_longitude when possible as you will get more accurate price and time estimates.
  • product_ids (Options): A list of Uber product UUIDs. If provided, sensors will only be created for the given product IDs. Please note that product IDs are region and some times even more specific geographies based. The easiest way to find a UUID is to click on a sensor in the Home Assistant frontend and look for "Product ID" in the attributes.

A full configuration entry could look like the sample below:

# Example configuration.yaml entry
sensor:
  - platform: uber
    start_latitude: 37.8116380
    start_longitude: -122.2648050
    end_latitude: 37.7768520
    end_longitude: -122.4155500
    server_token: 'BeAPPTDsWZSHLf7fd9OWjZkIezweRw18Q8NltY27'
    product_ids:
      - '04a497f5-380d-47f2-bf1b-ad4cfdcb51f2'