Medion Radio - Network Timeout about radio-api HOT 7 CLOSED

Hi,
so you have a working installation for three other radios and the Medion Radio does not work.

Thus, the general installation should be fine and I assume some issues in the interaction of Medion and Radio-API.
Do you have any „uncommon“ requests in CONF_LOG_DIR/requests.log? (It will only show uncommon requests.)
Do you see the request of the radio in the Docker/ Server logs (docker-compose logs)?

from radio-api.

Hi, thanks for the quick answer.

I have to try tomorrow.

I didn't find any logs at the moment.
For that I have to add CONF_LOG_DIR to docker-compose.yml?

(these are my first docker containers)

from radio-api.

Hi,
CONF_LOG_DIR defaults to ./data/ and if you use the provided docker-compose file, this is the folder ./data/ beneath the file.

So you just have to check this folder for the logfile.

from radio-api.

In data Dir I found on new gui-ID for N° 5 in table.json but no radios_5.json file. Seems that a GUI-ID was generated for the Medion-Radio

I can check tomorrow again.

from radio-api.

Oh, that is good to know! Then the radio connects correctly to Radio-API and fails afterwards.

Please try to access the GUI with the new GUI Code and check if the GUI and preview works fine.
If you encounter errors, set „DEV=dev“ via docker-compose environment and try again. It should then show PHP error messages.

from radio-api.

Ok, I cleaned "redis"-Dir then I got finally a connection.
There was maybe something in cache.... I don't know.

Thanks for assist an good ideas. Finally I learned a bit about docker etc...

from radio-api.

Hi,
glad that it works now!

When a new radio connects for the first time, normally the details about all radios in Redis are updated. But it seems as something went wrong. I will consider to optimize the update mechanism.

from radio-api.