-
Notifications
You must be signed in to change notification settings - Fork 0
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
Support FIP #1
Comments
Note: I've sent an email to the radio france api support to see if they have advice. |
Hey |
Me, again! |
This is what is supposed to exist. There are two entities exposed by the integration:
You probably forget that this integration also runs when you don't listen to your radio.
|
Is it possible to half solve this issue with a button? |
It should be technically possible but I would prefer to find an automated solution (I'm waiting for radio france support to get their opinion on what we should do to support this use case). |
But we could push this button automatically only when we play a radio station on a media player |
Support in https://github.com/kamaradclimber/radio-france-home-assistant/releases/tag/0.3.0 is much better for FIP and its substations: refresh for FIP is done every 2 minutes which means there is a reasonable chance to have up to date info (while keeping the api key usage under the daily limit). Next improvement will be when the api will publish data in advance, if it happens. |
Hey |
Hi there I think @Nikohomeassistant has a good point in an earlier reply. If we'd only call the API when we're actually listening to a station, we'd lower the overall inefficiency of pulling information 24/7. Even better, we'd increase the accuracy for FIP when the API load is lower; 60s or even lower would be a option I think. Conditions I could check to make this work is the combination of:
In the setup of the integration it would be required to add mediaplayers and the url used to stream FIP. |
This is a very valid suggestion, thanks! I think it corresponds well to a use case specific to FIP: display information when listening to the radio. I’ll see what I can do |
Got it, thanks either way!! You could make the 'use api based only under these x conditions' optional (default = always on). Users can create their own boolean helper in such a case. And even allow users to tweak the refresh rate. With the caveat that a max of 1000 requests is in place. |
FIP is a special case because it contains "tracks" only AND does not publish the program in advance.
It leads to errors to find the current program and out-dated data until the next refresh against the api.
In practice what happens:
Solutions:
The text was updated successfully, but these errors were encountered: