core: opensky with Update Error
Hi all,
The problem
all the time i have a Warning: with opensky Plugin. Github opensky
Environment
i use the last HA Version. core-2021.1.5
Problem-relevant configuration.yaml
# OpenSky https://www.home-assistant.io/integrations/opensky/
- platform: opensky
name: opensky
latitude: !secret homeassistant_latitude
longitude: !secret homeassistant_longitude
radius: 20
SCAN_INTERVAL = timedelta(seconds=12) # opensky public limit is 10 seconds
Traceback/Error logs
WARNING (MainThread) [homeassistant.components.sensor] Updating opensky sensor took longer than the scheduled update interval 0:00:12
my Log is full with opensky Warnings đ
Additional information
Thanks all for help!
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 3
- Comments: 60 (27 by maintainers)
Registered users can get 1000 calls per day. The script would have to be altered to include code to authenticate at appropriate intervals. If using 95 second (or so) intervals then you could get a full 24 hours of coverage, but many flights would be completely missed. So seems that this integration may be dead?
Next steps will be adding config flow, so it can be set up via UI. Then we can look into adding authentication. Then I would like to have someone who is a contributing user to OpenSky (like you have these sensors hooked up at your home) and check if thereâs a way we can detect if someone is a contributing user (that grants free access to own states and gives you 8000 credits) and add sensors for that
Next release you can authenticate yourself with Opensky đ
ThanksâŚthen similarly as you âŚwill steer away as this is not my skillset. I already forked yours and will test later this week when back home. Another thing I want to add is that the discovered airplanes end up in a separate sensor as attributes, so they can be further used in HA, e.g. use their position to show on a map card if they fulfill conditions. I already created something similar with floghtaware but this is not a free service
Ultimately someone has to rewrite this so that it meets the requirements to allow authentication and then you can get it to be useful again. I canât see anyone finding this useful if they only get an update every 15 minutesâŚhappy to be wrong though!
Edit: Great job with your work so far! I donât have the skills to get this any further than what I have done.
This integration should be removed since itâs no longer maintained and doesnât work due to credentials.
The are a bunch of design decisions that are rules for devs to follow. @joostlek is improving the current integration. If you want authentication now then you can do your own or use my fork (link further up) as a custom component
Hi, I was almost on the way to add the user/pwd myself as a PR but then noticed this one. Above you mention ânew standardsâ As I can hack a bit but not embedded into the HA dev cycle, what does this mean to the existing sensor which (as I may say) looks pretty straightforwardâŚso why new standards ?
Let me have a look and see if I can add the authorisation requirement
Is there any chance of this integration getting updated to allow user credentials to be added?
Indeed the rate limit must have gotten axed badly,
Header from curl call:
X-Rate-Limit-Retry-After-Seconds: 38715Yet another API killed by homeassistant usage ⌠đ¤Ł
Basically this is integration is useless for its intended purpose, without registering an account.
okay, i updated the issue đ
Hi there,
Thanks for opening up an issue. When creating an issue, an issue template is presented. It looks like youâve (partly) removed it. This causes your issue report to be incomplete.
Please edit your issue to have the full issue template back again and provide as much of the requested data as possible. Without it, we wonât be able to help you.
Thanks already! đ