Getting "connection to weather data failed #288
Comments
|
That is a good question. I run a few as well but have only seen this if I am working on it and do a constant reboot. They limit the number of calls in a period of time. Maybe increase the time between refresh? |
|
I'm suffering this too, in the UK. I logged into Openweather & noticed they longer showed the city name where I am! I changed it to one 2 miles away & it worked for a short period & then started the error again. I have tried a new API key, refreshing the data at different times, I even reflashed the whole device but have the same issue. If I log onto the web portal screen it shows the weather data fine. If I go into the settings & click on save, it works once only & then back to the error. I can't even disable the weather, or I'd do that! I mostly wanted it for time & temperature but of course the temperature is always wrong. Be very interested if there is a fix to this. |
|
I suspect the answer may be “Use a service other than OpenWeather” –
I did try emailing them and got back a rather generic response that when “interpreted” said, “Our free service is slow, if you want something faster, pay us”.
If I ever get around to it, there’s probably a “timeout” value somewhere in the sketch that could be adjusted – kinda hoping the author is still alive and interested enough to chime in,
From: Anthony ***@***.***>
Sent: Monday, April 29, 2024 5:02 AM
To: Qrome/marquee-scroller ***@***.***>
Cc: n7qnm ***@***.***>; Author ***@***.***>
Subject: Re: [Qrome/marquee-scroller] Getting "connection to weather data failed (Issue #288)
I'm suffering this too, in the UK. I logged into Openweather & noticed they longer showed the city name where I am! I changed it to one 2 miles away & it worked for a short period & then started the error again. I have tried a new API key, refreshing the data at different times, I even reflashed the whole device but have the same issue. If I log onto the web portal screen it shows the weather data fine. If I go into the settings & click on save, it works once only & then back to the error. I can't even disable the weather, or I'd do that! I mostly wanted it for time & temperature but of course the temperature is always wrong. Be very interested if there is a fix to this.
—
Reply to this email directly, view it on GitHub <#288 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGDARKMCMFQZRWEIEEBP2J3Y7YZDBAVCNFSM6AAAAABGTJCZ2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBSGU2DMMZUGA> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AGDARKMFSXOC2BG653DWSJLY7YZDBA5CNFSM6AAAAABGTJCZ2KWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT4EERKI.gif> Message ID: ***@***.*** ***@***.***> >
|
|
I will take a look at it when I get time. |
|
Thank you that would be very much appreciated |
|
I am having a hard time replicating this issue. Would it be possible for you to capture the Serial Monitor Log for the weather request when it fails? I would like to see if we can get the HTTP response code or if it is just a connection issue. If the response code is 400 level -- like 429 -- you might be hitting your request limit. I have 5 running all the time and never hit my limit. I am wondering if they are treating different countries or regions differently. I am in the US. |
|
Thanks! A few updatesI have 4 running, one for each continental US timezone. I had to reset them all this morning, at startup they all complained. I went into each web page and did a “refresh data”. After that, they worked for two minutes and then on the 3rd minute they all started complaining again.Here’s what I got back from OpenWeatherDear customer, Thank you for reaching out. My name is Viacheslav. I will gladly assist with your request. I wanted to share some insights regarding the possible cause of errors you may be experiencing. It's likely that your API calls coincide with peak usage times among other users. For instance, making calls at rounded times such as 11:00, 11:30, or 12:00 often leads to increased automated requests from many users. To optimize your API usage and avoid potential conflicts during these peak times, we recommend adjusting your request timings by a few minutes. For example, instead of 11:00 or 11:30, consider scheduling your requests for 11:03 or 11:33. Another option is to explore our premium subscription plans, which grant access to premium servers with reduced loads, ensuring smoother and more reliable service. If you encounter any difficulties or have further questions, please feel free to reach out to our support team. Best regards, Viacheslav Verbytskyi Technical Support SpecialistOpenWeatherLondon, UKref:!00D3i0tNQc.!500Wj02CYPm:refSent from my iPhoneClay JacksonOn Apr 29, 2024, at 11:27 PM, Qrome ***@***.***> wrote:
I will take a look at it when I get time.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
I’m in eastern Washington state. Will try to capture, but it may take a bit, as I’ll have to move the device to connect it to a PCSent from my iPhoneClay JacksonOn Apr 30, 2024, at 10:06 AM, Qrome ***@***.***> wrote:
I am having a hard time replicating this issue. Would it be possible for you to capture the Serial Monitor Log for the weather request when it fails?
I am wondering if they are treating different countries or regions differently. I am in the US.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
I also am running 5 units and do not see this issue. I am curious what do you have your minutes between refresh set to? It defaults to 15 minutes? Maybe you should try reducing that if you have changed it. |
|
15 minutes on all
From: Qrome ***@***.***>
Sent: Tuesday, April 30, 2024 3:15 PM
To: Qrome/marquee-scroller ***@***.***>
Cc: n7qnm ***@***.***>; Author ***@***.***>
Subject: Re: [Qrome/marquee-scroller] Getting "connection to weather data failed (Issue #288)
I also am running 5 units and do not see this issue. I am curious what do you have your minutes between refresh set to? It defaults to 15 minutes? Maybe you should try reducing that if you have changed it.
—
Reply to this email directly, view it on GitHub <#288 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGDARKPMBSKOYGSP6XDGNCLZAAJXNAVCNFSM6AAAAABGTJCZ2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBXGU2TGOJZGY> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AGDARKO65SAJIM5KRXSN5ETZAAJXNA5CNFSM6AAAAABGTJCZ2KWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT4NWF4Y.gif> Message ID: ***@***.*** ***@***.***> >
|
|
I took have tried multiple settings for refresh times & all after an initial successful first run default back to connection error. Oddly though the correct info shows in the web portal. I'm not good at coding, despite trying to learn, but would it be easy to change provider? |
|
Please use the serial monitor and capture the error and post it here. |
|
Sorry for the delay. I hope this is what you need, I'm not great with Arduino IDE 😬 It doesn't have the news API inserted as I don't need that feature, but I have had it in the past with the same results. connection for time data failed Time update unsuccessful! Getting Weather Data Updating Time... Time update unsuccessful! Displays: 8 |
|
So, looking at the code and where that message is created, it is a connection issue to the endpoint -- not making it to the end point. It is also interesting to note that the TimeDB call -- yet a different API call is also failing to make a connection even though the GET request looks correct. I am not able to replicate this. Can you check and make sure your device is not getting dumped from the DHCP -- or check how long the device can keep the IP. I don't think this is a coding issue but appears to be a connection issue. I am not able to replicate it. |
|
I will try to look through the router logs tomorrow, but the IP shouldn't be an issue as I assigned a static one just to avoid those kinds of issues. |
|
Spent a fair bit of time today, going through router settings & there is no issue there, I was making sure it's not isolated or blocked which it isn't. There does not seem to be any connection issues on the router end. The odd thing is, if I manually click refresh the data, it retrieves the weather info but not the time. If I leave it to auto update it fails after the intial connection. Anyway, spent way too much time on this. Thank-you for the design & the help but I think i'll just recylce it down to another project now :) |
|
@Barkingmad15 -- thanks for the comments, sorry it isn't working for you. I reached out to a few buddies that are also running it, and none of us are seeing the issues you mentioned. Good luck with your new hardware adventure. |
|
@n7qnm - I will open this again as requested, but honestly, only 2 people have had this connection issue. It does not appear to be wide spread as I have confirmed with others using it as my self. PLEASE provide useful information. The logs reported by Barkingmad show that he was having connection issues to both the TimeDB api as well as the weather. The connection failed on making a HTTP connection on port 80. This does not appear to be a coding issue. Please provide logs from your Serial Monitor -- other guessing does not help. Please confirm that your DHCP server is not expiring the IP addresses of the devices. |
|
Thanks! Based on several years of flawless performance, and the way this is manifesting, I would be surprised if it was a software issue. Something’s happened at OpenWeather, and their first line people don’t really want to waste their time on “freeloaders”.
Interesting – I just switched my Internet connection from a local WiMax provider to Verizon Home Internet with the corresponding IP address change and at 8 minutes, 2 of my 4 devices are still connecting, which is longer than they’ve held in the past.
The reason I asked you to reopen the issue is that I’d like to play with the code a little bit and see if there’s a tweak, like a timeout or retry parameter that can be tweaked and I was hoping to be able to ask questions once I get into things.
Thanks!
Clay
N7QNM
From: Qrome ***@***.***>
Sent: Tuesday, May 7, 2024 3:59 PM
To: Qrome/marquee-scroller ***@***.***>
Cc: n7qnm ***@***.***>; Mention ***@***.***>
Subject: Re: [Qrome/marquee-scroller] Getting "connection to weather data failed (Issue #288)
@n7qnm <https://github.com/n7qnm> - I will open this again as requested, but honestly, only 2 people have had this connection issue. It does not appear to be wide spread as I have confirmed with others using it as my self. PLEASE provide useful information. The logs reported by Barkingmad show that he was having connection issues to both the TimeDB api as well as the weather. The connection failed on making a HTTP connection on port 80. This does not appear to be a coding issue.
—
Reply to this email directly, view it on GitHub <#288 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGDARKLEUPYVGQULURXK7KLZBFMETAVCNFSM6AAAAABGTJCZ2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJZGQ2DINRVHA> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AGDARKJ7VWW3PTJZDX2EWQDZBFMETA5CNFSM6AAAAABGTJCZ2KWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT5EL53E.gif> Message ID: ***@***.*** ***@***.***> >
|
|
At 2200 last night, my marquees suddenly started working again – absolutely NO changes in my end. I just happened to catch the transition out of the corner of my eye.
Thanks for your bearing with me, I had actually allocated some time later tonight to work on this – will do something else 😊.
I am gonna start contributing weather data, which will get me access to their lowest level paid API, so at some point I may try to change the code to use that call – I’ll keep you posted.
Clay
N7QNM
From: Qrome ***@***.***>
Sent: Tuesday, May 7, 2024 3:59 PM
To: Qrome/marquee-scroller ***@***.***>
Cc: n7qnm ***@***.***>; Mention ***@***.***>
Subject: Re: [Qrome/marquee-scroller] Getting "connection to weather data failed (Issue #288)
Reopened #288 <#288> .
—
Reply to this email directly, view it on GitHub <#288 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGDARKJD3HYT3IY4NJEZZ4DZBFMEVAVCNFSM6AAAAABGTJCZ2KVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSG4ZTMMZQGI2TENI> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AGDARKOJLWQMIWOUVNIBDVDZBFMEVA5CNFSM6AAAAABGTJCZ2KWGG33NNVSW45C7OR4XAZNWJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XKUY3PNVWWK3TUL5UWJTYAAAAAF5ZERW6Q.gif> Message ID: ***@***.*** ***@***.***> >
|
I have 4 scrollers, one for each US TimeZone - About a week ago, they all started showing "Connection for Weather Data Failed". If I connect to them and refresh data, the data will show for some period of time; but then start failing again. Wondering if I'm rate-limiting on OpenWeather, of if they've changed their T&Cs
The text was updated successfully, but these errors were encountered: