Radio Browser - Integration not ready yet

Configuration
1

Hi,

First things first: I’m new to HomeAssistant and am at the moment a bit daunted by all the bits I can see in the interface. However I’m keen to learn, although that may be a slow process.

I’ve loaded up HAOS on an old PC and it’s plugged into my network. It’s headless, so I can only access it by the web interface. It appears to be working fine and has found my router, a couple of Shelly devices and a load of Chromecast Audio’s I have. All well and good.

I also have a Raspberry Pi running PiHole on the same network which runs my DHCP server. For the purposes of setting up HA I have stopped PiHole from blocking any traffic, hopefully ensuring that it won’t stop anything essential in HA from working.

The problem is that Radio Browser won’t initialise. All it will tell me is ‘Failed setup, will retry’. Looking at Settings > System > Logs I can see the following:

Logger: homeassistant.config_entries Source: config_entries.py:1248 First occurred: 3:25:38 pm (3 occurrences) Last logged: 4:10:44 pm Config entry 'Radio Browser' for radio_browser integration not ready yet: Could not connect to Radio Browser API; Retrying in background

If I ask HA to save a log file to local disk I can also find the following in that log file repeatedly:

2023-09-13 23:32:17.808 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Radio Browser' for radio_browser integration not ready yet: Could not connect to Radio Browser API; Retrying in background

Google has led me to this thread on this forum which seems to deal with a similar issue:

I have tried nslookup as follows:

ogp@X220:~$ nslookup -q=SRV _api._tcp.radio-browser.info
Server:		127.0.0.53
Address:	127.0.0.53#53

Non-authoritative answer:
_api._tcp.radio-browser.info	service = 1 1 443 at1.api.radio-browser.info.
_api._tcp.radio-browser.info	service = 1 1 443 nl1.api.radio-browser.info.
_api._tcp.radio-browser.info	service = 1 1 443 de1.api.radio-browser.info.

Authoritative answers can be found from:

ogp@X220:~$

(Note: this is typed into the terminal on the machine I am accessing HA from - this isn’t typed into the HA Command Line on the HA machine).

The thread linked about suggests that there may be problems with Virgin ISP not allowing access to the Radio Browser server. I have therefore added 8.8.8.8 as a DNS server into the PiHole but this has made no difference. I have also tried adding 8.8.8.8 as the DNS server in HA (in Settings > System > Network) but this has made no difference.

If it’s relevant, Meteorologisk institutt (Met.no) seems to have the same problem, which may also suggest a connection issue.

In short - what can I do to make Radio Browser work?

Thanks.

2

I have the same issue.

Home Assistant Core

2023-10-05 12:55:36.427 WARNING (MainThread) [homeassistant.config_entries] Config entry ‘Radio Browser’ for radio_browser integration not ready yet: Could not connect to Radio Browser API; Retrying in background

Anybody a suggestion…?

Thanks.

3

LeonBos,

Thanks for your post, sorry I’ve taken a while to come back to this thread.

Can anyone make any suggestions to help us both out?

Thanks in advance.

4

Very late update: I came across a few oddities with my HA installation and google threw up the fact that a HAOS installation created with Balena Etcher can be very problemmatic. Google is your friend but it seems that I wasn’t the only person affected.

The solution is a bit radical but it works; start again, but don’t create your installation using Balena Etcher. I did this and the new installation has worked beautifully right from the start.

So, if anyone else is struggling with Radio Browser and Meteorologisk institutt not working then try starting again from scratch.

5

Sorry as I am new to all this:

I have the same issue since yesterday:
-Radio browser
-Meteorologisk
Stopped working and both write: “Failed setup, will retry”.

The only think I did was to update my HA to the latest version.

I tried to bring back old bavkups but still the same issue.

Do I need to reinstall EVERYTHING? (Raspbian, D9cker & Ha?)

WTH?

6

I still haven’t found what went wrong, BUT I just reinstalled EVERYTHING from scratch (Raspbian, docker, HA) and everything worked again.

First I tried to reinstall my first FULL backup (I made a backup first thing) bit the problem persisted.

No clue what went wrong or why it wasn’t resolved even after a full backup re-installation. I am just leaving a comment here for anyone who might bump onto the same problem and look for an answer.

7

And today again the same issue.

Why when I reinstalled a stable FULL update I still have the same problem? Is this normal?