How can we help?


Error in parser 'NOAA Parser'...urlopen error timed out

Comments

5 comments

  • Avatar
    RainMachine Nicholas

    This looks like it's related to a local network condition (WIFI?) as the calls timeout. This will probably happen to other weather services. What I can suggest is to check WIFI signal from Settings > System > Network Tools. 

    0
    Comment actions Permalink
  • Avatar
    BB

    I had time-out issues related to my router config and I was able isolate the issue by using SSH on my RainMachine Pro.


    Once you get in, try pinging the weather server with escalating packet sizes using the ping -s parameter. I found mine would lose packets over 1200 bytes.

         ping -s 1200 rainmachine.com

     

    Also, you can carefully use the wget command to download various file sizes to confirm transfer speeds and any timeout issues.

    For example, I used the following syntax to download a 5 MB test file. You can download from any valid source but don't download files that are larger than the available space on the RainMachine..

          wget http://ipv4.download.thinkbroadband.com/5MB.zip

     

    Once done testing, make sure to remove any downloaded files.  Use ls to view a list of files and rm to remove files.

           rm 5MB.zip

     

    0
    Comment actions Permalink
  • Avatar
    David Pankros

    @RainMachine Nicholas -  I can see why you would think that and it would make sense, but it's not the case.  The rain machine has a semi-dedicated AP (<10ft away) and a high gain antenna to ensure it gets a strong signal as I had problems in the past related to signal-strength because the signal needs to penetrate a cinderblock wall.  Now, however, I've not seen any such problems. In fact, network tools shows everything in the green, except the HTTPS call to NOAA (FAIL).  The WiFi signal strength is -30 dBm.

    @BB I tried pings of different sizes up to my MTU (less overhead) and they all work. Trying the test file at think broadband failed immediately with a "HTTP/1.1 403 Forbidden". Now, there are no proxies on my local network but without a more detailed http trace it's hard to know for sure that the 403 is coming from them, even though it's likely the case.  What I wouldn't do to be able to "curl -v" right now so I could at least see the header information.  I tried a 16MB test file from another site and it downloaded fine, however.  Wget doesn't allow https urls so I'm extremely limited with what I can try.

    I'm no android master, though I'd say I'm very linux literate.  Most of my goto network tools don't seem to be available so I feel like I have one hand tied behind my back here.  Any suggestions on how to get better information?

     

    0
    Comment actions Permalink
  • Avatar
    BB

    Looks like you can eliminate issues with download speeds from the RainMachine then.  I wouldn't worry about the forbidden error if you are able to wget from other sites successfully.

    You could try running a continuous ping to the RainMachine from a device on your local network and log it to a file for a day or two.  This could reveal short WiFi disconnects or other network issues you wouldn't normally notice. 

     

    0
    Comment actions Permalink
  • Avatar
    RainMachine Nicholas

    Quite strange that all 3 servers are not reachable (forecast.rainmachine, noaa.rainmachine, weather.gov). RainMachine will keep retrying (with some random backoff). 

    Could you try to enable MET.NO parser to see if it works. The 2 parsers (NOAA, MET.NO) should run sequentially so if there would be a local network issue they might both fail.

    0
    Comment actions Permalink

Please sign in to leave a comment.