-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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 ride will fail to setup if no product id is set #8401
Labels
Comments
related to #7241 |
Can not be reproduced without configuration as not all products are available everywhere. |
Hey @fabaff this was made in SF so the following config should make this error pop up sensor:
- platform: uber
server_token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
start_longitude: -122.420443
start_latitude: 37.780248
end_longitude: -122.393289
end_latitude: 37.795833 I'm not sure if this helps but the TAXI product id is: d4abaae7-f4d6-4152-91cc-77523e8165a4 Let me know if there's any other info I can give you. |
fabaff
added a commit
that referenced
this issue
Jul 11, 2017
Thanks for your support, @enriquegh. |
pvizeli
pushed a commit
that referenced
this issue
Jul 11, 2017
Merged
dethpickle
pushed a commit
to dethpickle/home-assistant
that referenced
this issue
Aug 18, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (
hass --version
):0.48.1
Python release (
python3 --version
):3.4.2
Component/platform:
sensor.uber
Description of problem:
When using the uber sensor and not specifying any product ids (get all products), the sensor will throw an error and not work.
Expected:
Problem-relevant
configuration.yaml
entries and steps to reproduce:Traceback (if applicable):
Additional info:
Avoiding the TAXI product which has a "low_estimate" value of None seems to fix this but you can't know this without digging deep into the responses received from Uber
The text was updated successfully, but these errors were encountered: