time.wifiradiofrontier.com about radio-api HOT 2 CLOSED

Thank you for the quick reply.

Maybe this is interessting for other people with pihole.

This redirect has to be done in: /etc/dnsmasq.d/05-custom.conf
After the change is done the dns has to be restarted with the command: pihole restartdns

I deleted the redirect for time.wifiradiofrontier.com

As a result the command: nslookup time.wifiradiofrontier.com now shows
Name: eps-loadmaster-hap.nuvolaservices.io
Address: 185.128.204.56

I think this has solved the time sync issue.

Thanks,
Stoneubi

from radio-api.

Hi,

in fact there is an issue in the documentation/ installation guide. The radio expects an NTP server at the IP of time.wifiradiofrontier.com. My Radio-DNS image redirects all request except time.wifiradiofrontier.com to Radio-API, while time.wifi... gets redirected to an NTP-server (this may be time.wifiradiofrontier.com or any other, e.g., for Radio-DNS I use ntp0.fau.de).

Thus, your radio's time sync should work if you change the pi-hole to allow time.wifiradiofrontier.com and redirect all other requests of *.wifiradiofrontier.com to Radio-API.

Thanks for the info regarding the setup guide, I will update it.

Some more info:
As you use a Hama-Radio, it should/ might be sufficient to only redirect hama.wifiradiofrontier.com to Radio-API. This is because for each radio vendor they have a different name as prefix for .wifiradiofrontier.com while the API stays mostly the same (small differences are handled by Radio-API). However these prefixes are somehow strange as aldi (like the German supermarket) is used for radios from Medion. Thus I recommend to redirect all of *.wifiradiofrontier.com.

There is also a server update.wifiradiofrontier.com from which the radio fetches new updates and checks if there is a new software version available. This server is blocked in Radio-DNS and I think it might be good idea to block it: (i) From my experience there are nearly never updates available for the radio. (ii) Silicon Frontier could push an update to all radios which changes the API, blocks third party APIs, or removes features from the radio. Which would then lock us out from our radios or Radio-API.

from radio-api.