How can we help?


Firmware 4.0.1122 WU Warning: No observed data received from stations.

Comments

4 comments

  • Avatar
    Vern Scherbenske

    I tested my WU data retrieval using a web browser by using the information from this post:  https://support.rainmachine.com/hc/en-us/community/posts/360033585633-Struggling-with-Weather-Underground-and-WeatherLink-

    It retrieved the proper rain for today 0.04". 

    So it appears that the WeatherFlow and WU parts are working properly.  The WeatherFlow is reporting the rain to WU, and WU returns the same data when requested.  However, the RainMachine is reporting it does not receive the data.

    Any recommendations beyond deleting the WU setup and trying again?

    Thanks.

     

     

    0
    Comment actions Permalink
  • Avatar
    RainMachine Support

    Hi, all
    Please make sure:
    - you are using the RainMachine Web app to set the WUnderground weather station
    - your API key is correct, no empty spaces
    - check the "Use Nearby Weather Stations" and then click on "REFRESH NOW" button
    - the nearby weather station should be listed
    - select the desired weather station from the "Use Nearby Weather Stations" list and copy it's name then paste it into the "Use Nearby Weather Stations" input field. If you want to add more weather stations, use comma to separate their names
    - check the "SAVE" button and then "REFRESH ALL"
    - a full reload of the webpage should be useful, too.
    - wait a few moments until the weather data is fetched.

    If it still doesn't work for you, would you please try using the WUnderground weather service without the API key?

    Thank you, all
    Julian
    RainMachine Support

    0
    Comment actions Permalink
  • Avatar
    Nick Hawke

    I had the same problem. I had tried to add my PWS via the app and then when I looked at the setup on the web based app I could see a space had been added at the end of my weather station name. I deleted this space and it immediately started working

    Nick

    0
    Comment actions Permalink
  • Avatar
    Julius

    FYI, I posted separate thread on this but there was a change in WU service, I think, and it now requires ANY apiKey in the URL as otherwise it returns error. It needs anything send in apiKey value so long it is 32 characters long.

    My set up was for a long time without any apiKey value in the box and it's been working fine for long time, since sep 5th 2019 I am getting the same error as above.

     

    Plugging in fake apiKey into the box fixed the issue for me.

    0
    Comment actions Permalink

Please sign in to leave a comment.