Skip to content
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

Uber: Optional parameters are mandatory #3971

Closed
jabesq opened this issue Oct 21, 2016 · 7 comments · Fixed by #8429
Closed

Uber: Optional parameters are mandatory #3971

jabesq opened this issue Oct 21, 2016 · 7 comments · Fixed by #8429

Comments

@jabesq
Copy link
Contributor

jabesq commented Oct 21, 2016

Home Assistant release (hass --version):
0.30.2

Python release (python3 --version):
2.7.9

Component/platform:
uber

Description of problem:
According to documentation, the following parameters are optionnal: end_latitude, end_longitude and product_ids. But if they are not set then no uber sensor is created. So either update the documentation in home-assistant.io if this is a new API limitation or fix this issue.

Expected:
A uber sensor should be created with the minimal option set

Problem-relevant configuration.yaml entries and steps to reproduce:

sensor:
  - platform: uber
    server_token: 'BeAPPTDsWZSHLf7fd9OWjZkIezweRw18Q8NltY27'
    start_latitude: 37.8116380
    start_longitude: -122.2648050

Additional info:
If this sensor could handle device tracker and zone in order to automatically set latitude and longitude, this would a big improvement

product_ids can be found manually with the following command:
curl -H 'Authorization: Token '
'https://api.uber.com/v1/products?latitude=&longitude='

@jabesq jabesq changed the title Uber: Optionnal parameters are now mandatory Uber: Optionnal parameters are mandatory Oct 21, 2016
@fabaff fabaff changed the title Uber: Optionnal parameters are mandatory Uber: Optional parameters are mandatory Oct 21, 2016
@robbiet480
Copy link
Member

A time sensor should be created but not a price sensor since we can't get a price without having a final destination. Can you test to make sure that you are seeing 1/2 sensors and not 0/2?

@jabesq
Copy link
Contributor Author

jabesq commented Nov 2, 2016

I am not seeing any sensor added with just the following data:

sensor:
  - platform: uber
    server_token: 'BeAPPTDsWZSHLf7fd9OWjZkIezweRw18Q8NltY27'
    start_latitude: 37.8116380
    start_longitude: -122.2648050

(but no problem if I add end_latitude and end_longitude)

@Spartan-II-117
Copy link
Contributor

Has this been fixed?

@jabesq
Copy link
Contributor Author

jabesq commented Mar 15, 2017

No, the issue is still here with hass 0.40

@balloobbot
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

@jabesq
Copy link
Contributor Author

jabesq commented May 19, 2017

Still not working

@fabaff
Copy link
Member

fabaff commented Jul 10, 2017

The configuration sample you provided works fine.

sensor:
  - platform: uber
    server_token: !secret uber_api
    start_latitude: 37.8116380
    start_longitude: -122.2648050

screenshot from 2017-07-10 19-17-02

@balloob balloob mentioned this issue Jul 13, 2017
dethpickle pushed a commit to dethpickle/home-assistant that referenced this issue Aug 18, 2017
@home-assistant home-assistant locked and limited conversation to collaborators Oct 20, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants