-
Notifications
You must be signed in to change notification settings - Fork 5
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
KIMB-technologies/Radio-API #57
Comments
Hi Sepp, I do not use my Radio via ethernet, however, I can not imagine that using a wired connection instead of a wireless is a problem for Radio-API itself. But I assume that the connection settings to redirect the requests to Radio-API instead of Silicone Frontier's API may need to be changed or redone. |
I have now switched it to wifi but unfortunately it is not working yet. Do you know where else I can look? thanks |
Yes, this is possible. Typically DNS results/ answers have a TTL (time to live). Thus, the radio may only query the DNS server every x time units (for me it is 12 hours for |
Thank you then I'll wait |
Hello The two radios use the same DNS and I only ever get: At the moment I don't know what to do...... PS: 2 Radio sind die gleiche Baureihe und die anderen 2 auch und jeweils von einer jeder Baureihe geht einer und der 2 nicht nur weil sie am LAN waren vermutlich weil bis dato hat es immer perfekt funktioniert nur finde ich den Fehler nicht . Thanks in advance Sepp Translated with DeepL.com (free version) |
It looks like you need to fix your DNS on your radio side. You are trying
to connect to frontier-nuvola not KIMB's software. It looks like
frontier-nuvola disabled access until you reset your password and agree to
their new policies - which is a very good reason to switch to KIMB's
software.
…On Tue, Apr 9, 2024 at 4:50 AM Sepphuber007 ***@***.***> wrote:
Hello
The two radios use the same DNS and I only ever get:
Register http://nuvola.link/sr
Code:xxxxxx
Valid for 10 minutes
Do you happen to know another solution
I use Pihole but have not changed anything except that I have connected
them directly to the LAN. Now they have been connected to the wifi again
for 1 day and I still can't get your reg. favs that are stored on my Rapi,
At the moment I don't know what to do......
Thanks in advance Sepp
Translated with DeepL.com (free version)
—
Reply to this email directly, view it on GitHub
<#57 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJW3VC52DMQBDIFH6IUSA7DY4O2U7AVCNFSM6AAAAABF3N3LHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBUGYYDAOJXHA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Hi, Then, the only possible thing causing the problems are the DNS requests and thus, the redirect of the radios' requests to Radio-API. Especially, because the problems started after changing radios from Wifi to Ethernet.
PS: If it is easier for you, you may also answer in German. |
Danke das ich Deutsch auch schreiben kann. Ich habe den Fehler gefunden hab mir im Pihole den DNS Record gelöscht hama.wifiradiofrontier.com jetzt funktioniert wieder alles danke nochmal für eure Unterstützung. |
Super, dass es jetzt wieder funktioniert! |
Hello
I have 4 wifi radios: all 4 were previously connected to wifi.
Now I have connected 2 to Lan and the broadcast list has disappeared on both (back to the original Frontier broadcast list). Switched the 2 back to wifi and still I can't get their list - what am I doing wrong?
Is it not possible to connect the radio to the Lan to get the broadcast list from them? KIMB-technologies/Radio-API
thx
Sepp
The text was updated successfully, but these errors were encountered: