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

Adress resolution will get unavailable if running multiple foodsharing sensors #6

Open
FaserF opened this issue Oct 1, 2022 · 0 comments

Comments

@FaserF
Copy link
Owner

FaserF commented Oct 1, 2022

The problem

The first (sensor with lower number) sensor will sucessfully resolve the human readable adress. But all others will fail, as the scanning is too fast and the openmap api doesnt allow too many requests in short times.

What version of Home Assistant Core has the issue?

2022.8.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2022-10-01 12:16:40.265 DEBUG (MainThread) [custom_components.foodsharing.sensor] Nominatim Request: '(('lat', 44.123456), ('lon', 12.123456), ('format', 'geojson'))' '200' <bound method ClientResponse.text of <ClientResponse(https://nominatim.openstreetmap.org/reverse?lat=48.088306&lon=11.827146&format=geojson) [200 OK]>
2022-10-01 12:16:40.265 DEBUG (MainThread) [custom_components.foodsharing.sensor] Error on recieving human readable address via OpenMap API for 44.123456, 12.123456.
2022-10-01 12:16:40.265 DEBUG (MainThread) [custom_components.foodsharing.sensor] Error 'city'.

Additional information

No response

FaserF pushed a commit that referenced this issue Oct 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant