API requests stop firing after a couple hours for custom module

[NateDee]

Mochman are you using a setTimeout() or setInterval() function to schedule your requests? I was using a setTimeout() and just switched over to setInterval(), I will let you know how it goes. Mine pretty much always cuts out within a few hours.

From the javascript docs, setTimeout() calls the function once, and I rely on a call to a scheduleUpdate() function to call setTimeout() after each successful request. If any hiccup in the request, setTimeout() won’t be called again. However, setInterval() calls repeatedly unless told to stop, so no dependency on any successful runs.

I’ll update you if that does the trick for me.

[pinsdorf]

First thing I’d try is logging HTTP request and response into a file to collect some more details to reason on. Don’t forget to log timestamps and all headers.

Having said that, I think @NateDee’s explanation makes a lot of sense to me.

[mochman]

@NateDee I tried the same thing. The weird thing is that all the other modules update normally, just the one weather one. Nay luck with your issue?

[NateDee]

@mochman after 10 hours it’s still running and updating! I think that did the trick! It would always freeze during the overnight hours, I’m guessing I was having some hiccup for when no buses and trains were running. Do you have a thread open for your issue?

@pinsdorf I had logs running, including logging json respones, but I never saw any errors the requests would just stop.

[cowboysdude]

You could also do a console.log to see if you’re getting regular outputs after your request…